Jump to content

(PSN)snakerage666

PSN Member
 View Profile  See their activity

  • Posts

    15

  • Joined

  • Last visited

 Content Type 

Posts posted by (PSN)snakerage666

    New Network Ports

    in PSAs and Announcements

    Posted

     

    We have changed the default network ports used by Warframe; this should have been done a long time ago but we kept putting it off because of the trouble it is going to cause. Since there has been increased attention on matchmaking bugs after the massive changes in Update 14 we felt like it was time to act.
     
    In short: the default UDP ports used by Warframe are now 4950 and 4955.
     
    This change is currently live for PC and will be coming to PS4 with Update 14.
     
    If your router supports UPnP you should not have to change anything (it should update everything automatically) but if you have configured manual port-forwarding rules they will have to be updated. 
     
    If you have multiple PCs on your home network that play Warframe you probably have configured Warframe on each PC to use unique ports to avoid conflicts (hit ESC, select Options, Network Ports is near the bottom); since all port settings have been reset to defaults and you will have to reconfigure these.
     
    You should know if there is a problem shortly after arriving in your ship; it runs a diagnostic test to confirm your network is working properly and a dialog will pop out to warn you of any problems.
     
    You can run the test manually from your ship: hit ESC, select Options, and press the Analyze Network button at the bottom of the first page. If everything is fine it should say “All systems nominal.” If there is a problem there should be a help button on the warning dialog that should bring you to a web-page with more information.
     
    We regret any inconvenience this may cause but hope that in the short term it will improve connectivity for everybody.
     
    The problem with 3960 & 3962
     
    Many years ago when we picked ports to use for Dark Sector we had no idea the lengths we would have to go to work around the quirks of various routers and firewalls; we just picked a pair of unused ports and got on with making the game (which was primarily single-player at the time). 
     
    Since Dark Sector we have learned all kinds of tricks for dealing with routers. In cases where there is no UPnP service to forward ports for us we have to try to hint to the router what kind of mapping we will need and then try to figure out how it ended up forwarding the ports so that we can coordinate connecting with other players.
     
    Here is a simplified example of how it should normally work:
     
    The game sends a packet out of UDP port 4950 to the matchmaking service.
     
    Your router forwards this out of the public IP on port 4950 and makes a temporary port-forward so that packets can come back along the same chain.
     
    The matchmaking service tells your friend he can reach you on port 4950.
     
    Your friend sends data to your router, your router forwards it to you, and you go kill some crewmen.
     
    The problem is that the port selected by the router is beyond our control – it is up to the router to pick a port that it feels is appropriate. If the port you would expect was currently reserved (possibly by another PC on your home network) it is free to select a different port for the mapping. 
     
    The game does not care what public port is mapped – it just cares that it stays mapped (or that the mapping will work for all your friends).
     
    The problem is that a router can sometimes decide to change the mapping on the fly – this can happen if the router decides to expire a mapping before you are done with it and replace it with a different port. 
     
    Coincidentally, strict NAT is a very closely related to this problem; if your router is strict the mapping depends on who you are talking to: the matchmaking service might think that port 4950 is mapped for you but when your friend tries to use 4950 to reach you the router ignores your friend because the router has decided that 4950 is *strictly* for the matchmaking service everybody has to get their own mapping. There is a whole lot more to how we handle strict NAT but it has nothing to do with why we changed the default ports so we will leave that for another time.
     
    Let us continue with the example above:
     
    Time passes and your router expires the mapping; when renewed it decides to map 4951 instead (since 4950 was used recently and it does not want reuse it right away).
     
    Your friend tries to send data to you via port 4950 but it is no longer being forwarded so the data goes nowhere.
     
    The game attempts to cope with this by predicting that your router will use port 4951 because it is the next port in sequence; this turns out to be correct and you get to kill some more crewmen.
     
    Currently if there is a problem the game will try the next two ports after the one it hoped would be mapped. If we are trying to connect to 3960 and it is not working we will try 3961 and then 3962 which astute readers might have already noticed is the other default port for the game! 
     
    By changing the default ports so that they are spaced wider apart we can not only avoid conflicting mappings but we can also safely try predicting more ports in the event that the first 3 fail.

     

    Update 12.4: Tethra's Doom

    in PlayStation Update Notes

    Posted

     

    Update 12.4.4: Tethra's Doom

    P.S: Prime Access info:

     

    We are rolling out Rhino Prime Access as quickly as we can. Please note that they will be going live in each region separately as we get everything final. North American regions will see it sometime today, EU regions will likely see it tomorrow, and Asia/Japan will be coming later.

     

×
×
  • Create New...