IP addresses not UK - Can customers please report any problems here
Quote from: SE 146.199.106.43 You are in El Segundo
How silly of pn to do this
You might equally have said how silly of the website you were using to have relied on some presumption of where an IP is having not updated THEIR geo-location database.
IP addresses are reallocated all of the time - frequently issues such as the one you've reported are down to presumptions made by the business' applications. This is why no matter where you are in the UK PlusNet's IP addresses report as London or Sheffield, rather than where YOU are.
All of that said, the implementation of a full IPv6 facility would start to address these issues... Now whatever did happen to that pilot?
Quote from: Townman All of that said, the implementation of a full IPv6 facility would start to address these issues... Now whatever did happen to that pilot?
I'd take a guess that the Pilot was ex Lufthansa
I'm surprised that IPv6 has not yet made it to product offering yet - will it ever?
I got a USA IP addy (again !)
ISP picks up as INFONET Services Corporation
Sucks as MW3 cant lock me on as host in game, not that I can play properly anyway with my really messed up Fibre
ISP picks up as INFONET Services Corporation
Sucks as MW3 cant lock me on as host in game, not that I can play properly anyway with my really messed up Fibre
am still on US IP range
Quote from: StuartUK35 ISP picks up as INFONET Services Corporation
It will do. As explained, the IP's are still registered to Infonet and there's no immediate plan to change this.
Quote from: StuartUK35 Sucks as MW3 cant lock me on as host in game...
You might need to elaborate on that a little. I'm not really an ardent gamer so I'm not sure of the mechanics of a MW3 match. Perhaps you can explain in a bit more detail?
Quote from: StuartUK35 ... not that I can play properly anyway with my really messed up Fibre
If you've a problem with the line itself, then are you sure this issue is solely down to the IP address you're assigned?
I can see the problem there - although the range is allocated to Plusnet according to Infonet, they seem to say they are in the US, a French site seem to think they belong to Western Power Corporation in El Segundo, Los Angeles, California so obviously something needs sorting out 
If you encounter issues like that and need to access the site refusing you, just change your dynamic IP address by doing a Gateway hop, log in to your router and go to the Internet Box and find the button to click Disconnect. This drops the PPP Internet session. Wait about 30 seconds and then Click Connect.
If you encounter issues like that and need to access the site refusing you, just change your dynamic IP address by doing a Gateway hop, log in to your router and go to the Internet Box and find the button to click Disconnect. This drops the PPP Internet session. Wait about 30 seconds and then Click Connect.
Quote from: thedyes0 I've had this twice recently... the first time I didn't get the IP or gateway but it was effecting teamspeak, it gave me an American flag and for some reason was rather laggy (not sure why)
Doesn't look like you're alone. I've also managed to replicate this myself so I'll try and reach out to Teamspeak and get something done about it.
Quote from: thedyes0 The second time happened yesterday when doing a bet for a friend who doesn't have internet or pc/laptop, on the website: paddypower.com it rejected my bet based on my IP being from the USA where gambling is banned.
IP: 146.198.160.xxx
Struggling with this one. I've just signed up for a new Paddy Power account from an IP in the same subnet, deposited money into the account and placed a bet without any errors whatsoever
Quote from: Bob Struggling with this one. I've just signed up for a new Paddy Power account from an IP in the same subnet, deposited money into the account and placed a bet without any errors whatsoever
Weird... it definitely says it to me, I'll get my friend to re-use his account and see if it's fixed (he did email them telling them it was a British ip)
Quote from: Bob
Quote from: thedyes0 I've had this twice recently... the first time I didn't get the IP or gateway but it was effecting teamspeak, it gave me an American flag and for some reason was rather laggy (not sure why)
Doesn't look like you're alone. I've also managed to replicate this myself so I'll try and reach out to Teamspeak and get something done about it.
In fact, thinking about this one, the geo-location is probably dependent on the server. I seem to get both UK and US flags depending on the server I'm connecting to:
Looks like it's a job for the server admin, rather than Teamspeak themselves?
Quote from: thedyes0
Quote from: Bob In fact, thinking about this one, the geo-location is probably dependent on the server. I seem to get both UK and US flags depending on the server I'm connecting to:
Looks like it's a job for the server admin, rather than Teamspeak themselves?
Completely disagree, because I was on a server a few nights ago and my flag was USA, my connection dropped and my flag changed to UK.
I don't understand how that points to it being a Teamspeak issue?
You probably had a USA flag whilst assigned an IP from the 146.198.0.0/16, 146.199.0.0/16 or 146.200.0.0/16 subnets (these are the ones we know cause some issues).
Your connection drops, you reconnect to the same server, you're assigned an IP in a different subnet and your flag switches to UK.
The server you're connecting to is incorrectly identifying the first subnet as being geo-located in the USA.
That's still an issue for the server admin to resolve unless every Teamspeak server somehow speaks to a geo-location database administered by Teamspeak (which looks unlikely, based on the fact I get different flags for different servers whilst assigned the same IP address).
This is what they had to say when I last reached out to them.
Quote from: gofaster TeamSpeak embed the geolocation db from ip2location.com into the server. They update the data when they release new versions so the data used depends on which version of TeamSpeak the server is running.
Excellent! Thanks for the clarification, that's very useful to know
@thedyes0, a lookup at ip2location.com returns the correct information, so once the admin updates the Teamspeak server to the latest version, the correct flag should be assigned regardless of your IP:
