"IP changed mid session"?

It's part of that combat logging investigation some claim they don't do.

I couldn't fathom playing on wireless - wireless is so much slower than a wired connection, and running a long network cable, even making one, is not that hard... OW-O, GW-B, BW-G, BrW-Br and done.


That makes absolutely no sense.

If your IP changes mid-session you're still connected, not logging out. It happens to me on occasion because I have my PC set to automatically connect to two different Wifi routers. I'll use one or the other depending on which has the better connection, because my connection is spotty. If the connection I'm currently using drops out entirely, my PC will automatically connect to the second wifi router before ED notices that I'm not connected to the internet anymore and try to resume communication with the game.

But by switching routers, my IP changes, so ED drops me, along with every other program I'm running that requires logging in from a stable location like Steam, Battle.net, some video playing websites, etc..... It's a simple concept and it has nothing to do with combat logging or any investigation thereof.
 
Appreciate the info but my network/router/cables/ are not the issue.
My 5GHZ wifi is the only 5GHZ in the area and my machine was the only device connected to it. Connection was stable with 30-40Mbps.
Issue was also present when connected via POE, wired as well as direct connect to the router and happened when nothing else was streaming. connected, accessing the network. IPv6 is not active.
The problem was at random points, and even before I could start I received the 'cannot connect to matchmaking server' notice.

Same PC, same hardware, same set up worked fine after 20 minutes.

I'll monitor and advise if it comes back but as there are now more comments, its obviously a server traffic issue
 
Appreciate the info but my network/router/cables/ are not the issue.
My 5GHZ wifi is the only 5GHZ in the area and my machine was the only device connected to it. Connection was stable with 30-40Mbps.
Issue was also present when connected via POE, wired as well as direct connect to the router and happened when nothing else was streaming. connected, accessing the network. IPv6 is not active.
The problem was at random points, and even before I could start I received the 'cannot connect to matchmaking server' notice.

Same PC, same hardware, same set up worked fine after 20 minutes.

I'll monitor and advise if it comes back but as there are now more comments, its obviously a server traffic issue

Do you have any power hungry devices
or satellite receivers/consoles on the same
power grid?

Their power supplies can induce distorting
signals into the mains, that when all devices
are on the same power grid,
can affect your connectivity.
 
Appreciate the info but my network/router/cables/ are not the issue.
My 5GHZ wifi is the only 5GHZ in the area and my machine was the only device connected to it. Connection was stable with 30-40Mbps.
Issue was also present when connected via POE, wired as well as direct connect to the router and happened when nothing else was streaming. connected, accessing the network. IPv6 is not active.
The problem was at random points, and even before I could start I received the 'cannot connect to matchmaking server' notice.

Same PC, same hardware, same set up worked fine after 20 minutes.

I'll monitor and advise if it comes back but as there are now more comments, its obviously a server traffic issue

Then my next suspicion would be that the IP check FDev is running goes through your entire route of servers you take to get to their servers, and that your ISP is redirecting you occasionally based on traffic.

I used to find that happening a lot. In my case it was because I had a sleazebag ISP that would redirect all video streaming traffic through places like Finland and Belgium during peak hours. I live in the southern U.S., so when my streams were suddenly being bounced halfway around the world and back I'm sure you can imagine what happened to the quality and stability.

If you live in a country where every cable and ISP company isn't a greedy megaconglomerate out to screw their customers over they're likely just keeping their network stable and providing the highest possible speed, and it's FDev being a bit overzealous in their IP checks.

Start doing traceroutes before you enter the game, save the route, and run it again when you get the message again.
 
No. 1 router. 1 device connected. 2.4ghz disabled . 5ghz active. 1 channel, 1 Pc. Single line filter fitted (and before you suggest it, thats fine too).

Its a Frontier server traffic/pipeline (or DOS attack) issue. Mains, Newtork line speed, jitter, lag, delay, ping are all great Earth magnetic field, Moons gravitational pull, tide, wind direction and everything else is fine too..
 
No. 1 router. 1 device connected. 2.4ghz disabled . 5ghz active. 1 channel, 1 Pc. Single line filter fitted (and before you suggest it, thats fine too).

Its a Frontier server traffic/pipeline (or DOS attack) issue. Mains, Newtork line speed, jitter, lag, delay, ping are all great Earth magnetic field, Moons gravitational pull, tide, wind direction and everything else is fine too..

You can have that setup and still experience what I'm talking about. Once your connection leaves your router, the route that it takes is 100% up to your ISP and they can change it at any time without changing your individual IP.

You will not see anything happen on your end, not even a split second blip of packet loss, unless you run traceroutes and check the IP of every server you bounce off of.
 
Great idea. do you have a list of the different servers used at Frontier I can to trace to?. Hitting Frontier.com simply traced to the main site not to the sever with the issue. Unless you know the server then you can only trace to the 1st access point.
Trace too frontier.com with a solid connection came back with 4 hops over a 24 range with the worst RTT variation per hop at 7ms. longest RTT was to frontier at 78ms with a 3ms variation. Same result when the server issue came up as the route didnt change. In fact the return from Frontier was 6ms better
 
I've also got this problem with " IP changed mid session". Like I'm supposed to care about the technically of it. Great... i know when.. Mid session.. Who cares ? It's 2018 and we can't handle an IP change?
I'm tethering from my phone on 4g and I've got 3-4 bars/4 and 20-40 mbps at all times cause i work night shift and so the network is like empty and also I'm in London UK with the network 3.
And i drive for a living and if i have to pause the game, by hitting escape and closing the lid, usually it's good if i don't move much, like a few streets, but if i do a bit further then obviously the 4g phone switches towers and the IP, one of them internal or external or mythical IP, changes and the game refuses to reconnect ???
And sometimes it says "network blabla: error unknown". Great!
And guess what? It takes 4 minutes to restart the game !

This is a bug and needs fixing asap !

Ps: in fact this is what you get for making THE huge kindly epically bad mistake of making the game online only for single player. I don't care about markets updating and other such total nonsense excuses. It doesn't matter at all if i buy or sell a bunch of nothing or buy a ship or whatever with 5% plus or minus. It doesn't matter au all in the hand scheme of things. All the npc can spawn just fine everywhere like in every other hand ever made while offline.
There's not a single element of it that NEEDS to be online when I'm solo.
 
That makes absolutely no sense.

If your IP changes mid-session you're still connected, not logging out.

I'm afraid it makes perfect sense. If your IP address suddenly changes then you no longer have active sessions on anything that isn't session-less because the sessions are tied to the previous IP address. I've always gone static IP since the advent of broadband and never suffered the problem.
 
It is highly likely from the symptoms discussed in the thread that it is the Public IP address that your router has, has changed.

Most home networks use a private range starting 10.xxx.xxx.xxx or 192.168.xx.xxx to allocate unique IPs to your PC, Alexa, Wifi connected tumble dryer etc. This is done by the router using DHCP and these addresses are dynamic. ie. you cannot guarantee the address you will get when you connect. They also are dished out on a lease (typically 24 hours) and after that time your device will ask for a new address and the router will give you one (most routers are clever enough to remember what you had and allow the end device to keep teh same address as before).

but if any device wants to connect to the internet (google, www.wibblywobblydanglyones.com or even Frontier game servers) your Router must hide your private address behind a public one - using NAT or Network Address Translation. The public address your router has is dynamic (unless you pay your ISP extra for a static address which a majority of users do not and a majority of ISP's don't offer) so again it is on a lease from the ISP and can get renewed, again it will be randomly assigjned from the ISP cabn use, but it can change.

It sounds to me that this may be 1 of 2 things - the ISP lease is expiring on the public address and its getting renewed with a different one.

Workarounds - .Restart game. Inquire costs from ISP for static IP address, check if you can swap to another ISP that has a better rep/service that does offer this.

Or Router is having issues with NAT and therefore resets the NAT session and possibly uses a different port for the session to Frontier (this would basically break your session as frontier were expecting you to use a certain port and its changed).

Workaround - Set up static port forwarding for Elite see https://support.frontier.co.uk/kb/faq.php?id=344 . Reboot router once a week to get it to reset itself. Buy a newer router. Change ISP to get new hardware.
 
Ridiculous... The work around is to fix the game bug error calamity that it is.
I can't be asked to move house or get a military grade router just to play a game.
What is this ? It's clear that pre version 2.3.something that someone else has mentioned a few pages back, that this error didn't happen back then.

See ? Look here:

I've only seen the error since 2.3

So it was fine before 2.3 with no such IP error.
 
Last edited:
I tend to agree with c00ky1970 when he talks about the router using dynamic DHCP addresses.
I'm going to set up port forwarding and see if it makes a difference.

The fact that we didn't get this problem previously might not be relevant. We could have had the same problem appearing differently, or it may be in order to fix one problem Frontier have created another (lesser) problem.
 
I have the same problem and I have static IP addresses from my ISP through to my end devices. MY router has a static external IP address provided by my ISP and all of my local devices have static IP addresses on my LAN. I do not use DHCP for anything. Whatever the cause of the problem, it cannot be (or cannot solely be) changing IP addresses because mine never change.
 
I have the same problem and I have static IP addresses from my ISP through to my end devices. MY router has a static external IP address provided by my ISP and all of my local devices have static IP addresses on my LAN. I do not use DHCP for anything. Whatever the cause of the problem, it cannot be (or cannot solely be) changing IP addresses because mine never change.

Ignore that! What I should have typed was "thank you Frontier for giving me a way to see that my ISP has removed my static IP address without telling me". :eek: It turns out my IP address is changing between dropouts. Looking forward to the hold music on the ISP support line already... [mad]
 
Back
Top Bottom