Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 28 subscribers
  • Views 8360 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

So my XG thinks the 47.133.23.* subnet isn't in United States...wtf...

Greg Rogers

I filter my traffic by country for incoming dnats. I have it set so only United States can get thru to these ports. However I can access my server from any other connection inside my country except my own home. Which has an ip of 47.133.23.* which if you look it up, registers as in USA. 

 

Someone needs to fix this list....



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to rfcat_vk

    At least they can get the ISP right bahaha. 

     

    But no really, this sucks. Someone should come up with a fix. Maybe check a few sources at the same time and do a vote count before accepting? Although I can only imagine that would slow things down a bit. Maybe go with a provider that has better results? Or maybe let the owner of the XG choose which provider out of a list, to use?

  • 0 in reply to Greg Rogers

    There are couple of scenarios, which you can do.

    But you need to know, you have to pay to use most of these databases.

    https://stackoverflow.com/questions/19514749/best-ip-to-country-database

     

    In my point of view, geo ip seems not to be "good" in times of Proxy solutions and the current Boom of cloud providers (AWS, azure etc.), because nobody can say, which "country" they are coming from. If i buy a ec2 instance in US and go through a VPN to this instance, am i a US company? Don´t think so. Just my 2 cents.