Many many thanks! My multiplayer Odyssey behaves like single player now. Bugs and disconnects are gone! Even harmless put fear-inducing lag during jump transitions is gone.
It's night and day!
The Port Forwarding thread: Minimizing multiplayer connection issues
- Thread starter Viajero
- Start date
It's night and day!
07 all
Has anyone manged to get Full_Cone NAT while using a VPN? If so how did you do this? Was it just like that with the VPN you used. If that's the case which VPN are you using. The reason I need to use a VPN is due to me having mine and my partners PC running with the game at the same time. I have manged to get Full_Cone on my pc, not with the ports recommend but by opening different ports that I found the game uses in a certain range. The problem I have is her game also wants to use the same range of ports. This then causes her NAT to be symmetric. This causes no end of dsync problems. So I though let's see how a VPN helps. It got her out of symmetric but now it's port restricted. I think restricted is better than symmetric from what I've read esspecially if someone joins ourcwing who is port_restricted but would still like to get full cone if possible. Any help would be greatly appreciated 07.
Side note if anyone here would like help setting up full_cone the way I do it let me know. I'm pretty sure no one has ever used the utility I use to see the extra ports the game tries to use. From my investigations the game uses a range of ports from 40000 to 65535 and it could be any port within that range. Only by opening that range did I achieve full_cone nat regardless of using the method stated. It would be great to know why the game uses those extra ports and would be even better if I we could control which of those extra ports the game uses (3 in total) so I wouldn't have to open such a large range.
Has anyone manged to get Full_Cone NAT while using a VPN? If so how did you do this? Was it just like that with the VPN you used. If that's the case which VPN are you using. The reason I need to use a VPN is due to me having mine and my partners PC running with the game at the same time. I have manged to get Full_Cone on my pc, not with the ports recommend but by opening different ports that I found the game uses in a certain range. The problem I have is her game also wants to use the same range of ports. This then causes her NAT to be symmetric. This causes no end of dsync problems. So I though let's see how a VPN helps. It got her out of symmetric but now it's port restricted. I think restricted is better than symmetric from what I've read esspecially if someone joins ourcwing who is port_restricted but would still like to get full cone if possible. Any help would be greatly appreciated 07.
Side note if anyone here would like help setting up full_cone the way I do it let me know. I'm pretty sure no one has ever used the utility I use to see the extra ports the game tries to use. From my investigations the game uses a range of ports from 40000 to 65535 and it could be any port within that range. Only by opening that range did I achieve full_cone nat regardless of using the method stated. It would be great to know why the game uses those extra ports and would be even better if I we could control which of those extra ports the game uses (3 in total) so I wouldn't have to open such a large range.
Last edited:
It isn't required at all, or I wouldn't be able to play, and yet I've flown a full team around for hours at a time without issues. My current ISP uses cgnat to serve more customers with fewer public IP addresses, and I disable uPnP on my network.
Port forwarding is specifically meant for hosting a dedicated server, where incoming connections can arrive at any time, from any source IP, without prior announcement. In a peer to peer scenario, this never happens - both peers know when they expect to hear from each other, and trigger the opening of a port on a temporary basis simply by sending the outgoing handshake to initiate the connection.
While port forwarding can be used to work around some problems, it does not fix them - and in some cases, the effects of the problem being avoided are simply pushed onto another peer in the network. This can lead to wild goose chases, where the affected peer starts trying to find out why their network is giving them trouble, when the problem isn't their network to begin with (while the person with the actual configuration issue sits back, confidently yet incorrectly believing that their end of the connection is fine).
It would be better if people addressed issues such as MTU size and buffer bloat. An incorrect MTU can result in packet fragmentation, where a single packet is divided into two or more smaller packets - if just one of those fragments doesn't make it to the intended recipient, the entire packet is considered lost and will be resent in its entirety (which will be fragmented again). Packet loss leads to high latency, rubberbanding, and dropped connections - basically all of the issues people see with networking in Elite.
Viajero
Volunteer Moderator
Port forwarding itself it is not always required indeed. Some player routers work just fine or with minimal issues within the peer to peer network architecture FDEV devised for Elite. But that is not the case for all router set ups, some encounter lots of issues where port forwarding can definitely help.
Last edited:
Be nice if you could link those people to something regarding how to deal with this.
The port forwarding suggestion in this thread does not work for most people using isp router/modems. If you are in the UK and on BT or SKY DM me and I'll show you how to get Full_Cone NAT on elite using My own methods. If you are on virgin and use the Hub 5 then I'm sorry to say port forwarding is broken on that model and by the looks of things virgin are not looking into a fix.
Two things off the top of my head are MTU size and buffer bloat. If your MTU is larger than it should be, then packets of data will have to be fragmented into smaller pieces, increasing the overhead because each packet has to have a full header. And if one fragment of a packet fails to make it to the destination, the entire packet has to be sent again (and will be fragmented again, compounding the issue).
Here's an adequate guide for testing MTU size in Windows: https://kb.netgear.com/19863/Ping-Test-to-determine-Optimal-MTU-Size-on-Router
Once you know your target MTU, you'll need to set it in your router (ideally) or your computer if you don't have access to your router's config. The directions will vary per router, but googling "MTU" with your router model will find the right guide in most cases. If you must resort to setting it on your computer instead, these instructions will get you there:
Code:
Type “netsh interface ipv4 show subinterface”.
Press Enter.
You will see a list of network interfaces.
Type “netsh interface ipv4 set subinterface `Local Area Connection` mtu=1472 store=persistent”.
You should replace Local Area Connection with the name that appeared in the “Interface” column from steps 1-3.
Press Enter.
Type “netsh interface ipv4 show subinterface” to check the result.This site has a test for buffer bloat, and a pretty good explanation of what it is and why it can affect network performance:
Bufferbloat and Internet Speed Test - Waveform
Is bufferbloat causing issues with your internet connection? Run this test to find out.
www.waveform.com
Would certainly like to hear about your effort. I am in the same situation. Can't wait for that fiber to get installed!After nearly 2 decades of signing petitions... I have fiber being installed in couple of weeks
I will try all of this again and hope it improves my experience.
In the meantime, while I'm still using what I have, I'd like to experiment with the MTU settings. I have a two-router setup.* I presume that I can simply specify the same MTU setting on both.
* Long story short: ISP provides their gateway that's beyond old (last firmware update forever-ago), so I have zero choice but to have my own, secure, trusted router protecting my network.
What did I say above? Can't wait for that fiber!
Last edited:
pray that this new fiber ISP grants a public dynamic IPv4 address. Mine after i got fiber wanted to get paid extra for it (3 euros a month extra, but still...)After nearly 2 decades of signing petitions... I have fiber being installed in couple of weeks
I will try all of this again and hope it improves my experience.
Viajero
Volunteer Moderator
By the way, @Kerrash may correct me if I am wrong but according to what he said in one of his streams after the new ISP installation, many of the connectivity problems he had before disappeared after it.
Not suggesting that changing ISP or type of connexion is a must or guarantees improvements, but this goes to show that many of the issues we all can have in peer to peer may be directly linked to the type of router and connexion indeed.
I have the distinct impression that the massive difference in bandwidth has improved all the issues I was seeing.
Yeah. I thought the same when all my instancing issues with friends issues magically went away after changing ISP and getting more bandwidth. I'd tried all the things, but no joy, then like magic everything great.
That said, starting to have troubles initially instancing with a friend since update 13.
We have to supercruise away and back to our carrier before we can actually see each other and board my ship.
Anyone else seeing this change since update 13?
Ok I came here to go over the port forwarding guide and nothing in my settings has changed and I am guessing it will be the same for my friends.. but after update 13 we have had some serious instancing issue. Prior to the update we would see each other when logging into the game even before forming a team but now.. we have to team up and both of US need to hit super cruise in order to be able to instance with each other.
Viajero
Volunteer Moderator
As fas as we know no major changes have occurred to the games network structure in update 13. Has anything in your or your friend´s local network setup changed recently? Changed router, or connection to router, or internet provider etc? New devices using your network?
Either way I suggest you try the port forward check/test as described in Step 4 of the first post here, and see if it is still good?
Last edited:
I helped him check the settings and we both performed the port test after getting pfcopnfig from the site
Nothing in our network has changed both of us still have same ISP .. only other thing was he upgraded to windows 11 recently and we re-added Elite to the the AV exclusion and the issue still occurs. I don't think it's us though because this started right after update 13
They did implement a fix for the issue of a player getting stuck/disconnection when they were on your ship and it was either jumping or entering supercruise and while that error happens considerably less then it did before we now have this weird instancing issue.
And this is how weird the issue is... I was already in the game and my friend joins the game.. we form a team.. he logged on in the carrier and I was a system away.. I jump to the system the carrier is in drop out of supercruise.. I can see his team signal... I dock and he cannot join my ship or can I see him just the team signal.. We then both have to enter supercruise and only then we can see each other and everything is fine after that.
Viajero
Volunteer Moderator
Gotcha, I still suggest you try the port forward check/test as described in Step 4 of the first post here, and see if it is still good?
I did again and I still sadly have no luck with the error... for both of us our results come up good
Last edited: