# Core-Update-Level: 148 (Location-Filter)

**URL:** <https://community.ipfire.org/t/core-update-level-148-location-filter/2932>\
**Category:** Firewall Rules\
**Created:** [4 August 2020 14:16 UTC](https://community.ipfire.org/t/core-update-level-148-location-filter/2932 "2020-08-04T14:16:48Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [9 August 2020 10:42 UTC](https://community.ipfire.org/t/core-update-level-148-location-filter/2932/11 "2020-08-09T10:42:13Z")

</div>

Hi,

unfortunately, things are not that simple.

We cannot scrape Whois en masse, since RIRs tend to have very strict ratelimits  
on their servers. Their raw data is all we have (except for RIPE, where things look  
a little bit better), which cover direct RIR allocations only.

So, if a company acquires a /22 and splits it up into four /24 networks, we will  
not be able to determine the country codes of that sub-allocations, since they  
simply do not show up in the data we have.

Depending on the network your superior happens to get connectivity from, it might  
be a good idea to allow `EU` as well, since some networks are used across Europe.  
Either way, using a VPN service should be sufficient in order to keep dial-up procedures  
from your superior safe.

Thanks, and best regards,  
Peter Müller

---

_[View the full topic](https://community.ipfire.org/t/core-update-level-148-location-filter/2932)._
