All Barracuda Web Filters
Websites determine the location of web traffic looking at the incoming IP, and then seeing where that IP is located. Under normal circumstances, the IP they will see is your external IP. However, when traffic passes through the web filter we can attach headers to it that expose the IP of the client machine. This can create an issue if your internal IP is not from the private range.
If your internal IP range is not from the private IP ranges (10.0.0.0/8, 172.16-31.0.0/16, 192.168.0.0/16), then it may be tied to a specific location. For example, the IP 220.127.116.11/24 comes from Canada, so if you are surfing from a client machine with an internal IP of 18.104.22.168, and it is passed through headers to a website, they may think you are coming from Canada.
To resolve this issue:
1. Navigate to the Advanced > Proxy page.
2. Set X-Forwarded-For Header to No.
3. Save changes and test. Make sure to clear your browser cache first.
Websites should now track you correctly as coming from your external IP.
If you are unsure where your internal IP range is located, you can run a whois command search. If this is not available, you should also be able to track down the owner/location of the IP range by searching for the IP online. For example:
-bash-4.2$ whois 22.214.171.124
# available at: https://www.arin.net/whois_tou.html
# Query terms are ambiguous. The query is assumed to be:
# "n 126.96.36.199"
# Use "?" to get help.
# The following results may also be obtained via:
NetRange: 188.8.131.52 - 184.108.40.206
NetType: Direct Allocation
OrgName: TekSavvy Solutions Inc.
Address: 800 Richmond St.
PostalCode: N7M 5J5
Link To This Page: