# Error with "Anomaly detections based on Autonomous Systems information"

**URL:** <https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185>\
**Category:** Web Proxy, URL Filter & Update Accelerator\
**Created:** [4 July 2022 16:44 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185 "2022-07-04T16:44:43Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![roberto](https://community.ipfire.org/user_avatar/community.ipfire.org/roberto/32/8265_2.png) [@roberto](https://community.ipfire.org/u/roberto)\
**Post date:** [4 July 2022 16:44 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/1 "2022-07-04T16:44:43Z")

</div>

Hi.

I come on vacation and I encounter this problem:

With his activated:

 ![imagen](https://community.ipfire.org/uploads/default/original/2X/9/99103c42f8a8d0abab3825b06b058acd1aebc27c.png)

The following occurs:

 ![imagen](https://community.ipfire.org/uploads/default/original/2X/d/d18698b4b8ea9124ecc3ddfbabd685119dbe6da6.png)

If I uncheck the corresponding boxes for “Anomaly detections based on Autonomous Systems information”, everything starts to work correctly.

The affected pages (as far as I am aware), are:

> [https://blog.ipfire.org/](https://blog.ipfire.org/)  
> [https://community.ipfire.org/](https://community.ipfire.org/)  
> [https://www.caixabank.es/](https://www.caixabank.es/)

Can anyone else confirm?

Regards.

---

<div class="post-metadata">

**Author:** ![roberto](https://community.ipfire.org/user_avatar/community.ipfire.org/roberto/32/8265_2.png) [@roberto](https://community.ipfire.org/u/roberto)\
**Post date:** [5 July 2022 08:15 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/2 "2022-07-05T08:15:16Z")

</div>

I just restarted the IPFire and now I can’t navigate to any page with the options checked.

More specifically, it is by having the “Deny access to destinations hosted on selectively announced networks” box checked.

Any solution?.

Greetings.

---

<div class="post-metadata">

**Author:** ![cfusco](https://community.ipfire.org/user_avatar/community.ipfire.org/cfusco/32/9213_2.png) [@cfusco](https://community.ipfire.org/u/cfusco)\
**Post date:** [5 July 2022 09:09 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/3 "2022-07-05T09:09:28Z")

</div>

@roberto What happens if you clear the cache?

---

<div class="post-metadata">

**Author:** ![roberto](https://community.ipfire.org/user_avatar/community.ipfire.org/roberto/32/8265_2.png) [@roberto](https://community.ipfire.org/u/roberto)\
**Post date:** [5 July 2022 09:11 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/4 "2022-07-05T09:11:32Z")

</div>

Hello @cfusco .

I have tried both to clear the proxy cache of the IPFire and the local computer (W11) but it does not solve anything.

Greetings.

---

<div class="post-metadata">

**Author:** ![cfusco](https://community.ipfire.org/user_avatar/community.ipfire.org/cfusco/32/9213_2.png) [@cfusco](https://community.ipfire.org/u/cfusco)\
**Post date:** [5 July 2022 09:30 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/5 "2022-07-05T09:30:52Z")

</div>

I find this very suspicious. If you read the [blog post](https://blog.ipfire.org/post/feature-spotlight-weaponising-ipfire-location-to-proactively-detect-fast-flux-setups) concerning fast flux, it is based on an excessive diversity of ip address over several ASNs, returned by a dns query. Clearly the ipfire project FQDNs is not falling in this category. Why your system believes the opposite?

EDIT: Can it be that the feed of your provider somehow is not receiving [AS24679](https://asnlookup.com/ipv4/81.3.27.38/) which is BGP routing the IPs of the IPFire project?

---

<div class="post-metadata">

**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\
**Post date:** [5 July 2022 14:58 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/6 "2022-07-05T14:58:15Z")

</div>

Hi,

thank you for reporting this. Unfortunately, I cannot reproduce it here.

What is the output of

```auto
location version

```

on the affected IPFire machine?

Thanks, and best regards,  
Peter Müller

---

<div class="post-metadata">

**Author:** ![roberto](https://community.ipfire.org/user_avatar/community.ipfire.org/roberto/32/8265_2.png) [@roberto](https://community.ipfire.org/u/roberto)\
**Post date:** [5 July 2022 15:44 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/7 "2022-07-05T15:44:59Z")

</div>

Hi @pmueller

```auto
[root@bs ~]# location version
Fri, 01 Jul 2022 06:00:18 GMT
[root@bs ~]#

```

Thanks.

---

<div class="post-metadata">

**Author:** ![roberto](https://community.ipfire.org/user_avatar/community.ipfire.org/roberto/32/8265_2.png) [@roberto](https://community.ipfire.org/u/roberto)\
**Post date:** [5 July 2022 15:49 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/8 "2022-07-05T15:49:07Z")

</div>

Hi @cfusco and @pmueller.

I have updated using “location update” and now I have day 05 and everything works correctly now.

If it’s just this, I’ll take it for granted.

Greetings and many thanks to both of you.

---

<div class="post-metadata">

**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\
**Post date:** [5 July 2022 16:16 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/9 "2022-07-05T16:16:39Z")

</div>

Hi,

> [@roberto](#):
>
> If it’s just this, I’ll take it for granted.

hm, I am not satisfied with that, but glad to hear that things are solved for your for the time being. Will investigate on `libloc`’s backend side to see what happened on July 1st…

Thanks, and best regards,  
Peter Müller

---

<div class="post-metadata">

**Author:** ![ralph](https://community.ipfire.org/user_avatar/community.ipfire.org/ralph/32/10935_2.png) [@ralph](https://community.ipfire.org/u/ralph)\
**Post date:** [6 July 2022 12:21 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/10 "2022-07-06T12:21:59Z")

</div>

today i got errors if I want to reach [google.de](http://google.de), [google.com](http://google.com), [bing.com](http://bing.com), [amazon.de](http://amazon.de)  
in combination with “fast flux”.

After I disabled it everything works.

Anybody else? Any hint for a secure solution?

The problem exists only when  
“Deny access to destinations hosted on selectively announced networks:” is checked.

Update:  
I have also checked - “location version” and got  
Fri, 01 Jul 2022 06:00:18 GMT

Update2:  
after “location update”  
 → Downloaded new database from Wed, 06 Jul 2022 06:08:28 GMT

and everything works

---

<div class="post-metadata">

**Author:** ![xperimental](https://community.ipfire.org/user_avatar/community.ipfire.org/xperimental/32/16702_2.png) [@xperimental](https://community.ipfire.org/u/xperimental)\
**Post date:** [6 July 2022 12:44 UTC](https://community.ipfire.org/t/error-with-anomaly-detections-based-on-autonomous-systems-information/8185/11 "2022-07-06T12:44:52Z")

</div>

Just checked it and I have no trouble with this sites. But my version is Wed, 06 Jul 2022 06:08:28 GMT.
