Forged Alliance Forever

Re: Logs Show Port Forwarding Problems Despite Port Forwardi

2019-01-24T01:56:04+02:00

Sry, forgot the launch script, run it from the command line using "java - jar PortTester.jar".

Unless sombody has created the worst logging ever STUN means you have a public connection. (actually STUN has nothing to do with the type of connection which just shows that the logging is bad, but that's a different Story)

You can use any client and any port when forcing proxy.

Statistics: Posted by Geosearchef — 24 Jan 2019, 01:56

Re: Logs Show Port Forwarding Problems Despite Port Forwardi

2019-01-23T23:35:16+02:00

So I tried downloading your port tester, but when I try to run it literally nothing happens. From the wiki, if my connection was working correctly I should see "Connectivity state is PUBLIC" in that line instead of "Connectivity state is STUN," so I think there is still a problem going on. Also when I'm forcing a proxy, should I switch the game port that is being used in the client? Lastly, when forcing the proxy do I have to play on Downlord's client (because I can see it has the light to show it supports proxy connections vs nothing in the legacy client) or does it matter?

Statistics: Posted by AuroraCeleste — 23 Jan 2019, 23:35

Re: Logs Show Port Forwarding Problems Despite Port Forwardi

2019-01-23T14:16:52+02:00

Try testing with the following tool. Just have somebody else outside your network run it in send mode.

https://geosearchef.de/PortTester.jar

Statistics: Posted by Geosearchef — 23 Jan 2019, 14:16

Re: Logs Show Port Forwarding Problems Despite Port Forwardi

2019-01-23T11:10:34+02:00

STUN connectivity is what you'd expect as a direct connection. But maybe it detects a direct connection but the direct connection then fails later on. A workaround would be to force a proxy connection (block port 6112, udp in the WINDOWS firewall completely). I'll also post a link to a simple port tester tool I've written once I find it.

Statistics: Posted by Geosearchef — 23 Jan 2019, 11:10

Logs Show Port Forwarding Problems Despite Port Forwarding

2019-01-23T08:30:23+02:00

Hi yall,

Been getting into PVP FAF recently to relive my childhood, but a few people have said they have connection issues with me. Roughly every other game where I'll lose connection with 1 player at a random point in the match. Sometimes I'll reconnect after a couple mins, sometimes I won't and they get kicked. I know it's not always me, but the past few games people have repeatedly said they've had issues with me. I checked the Connection Issues and Solutions page on the wiki and investigated my client logs. Sure enough it gives me this line: "INFO connectivity.helper.ConnectivityHelper Connectivity state is STUN, mapped address: 68.180.94.164:50104". According to that page, the solution would be to port forward, which I did. However, no matter what I seem to do, that line still reappears in my logs every single time I try to host a lobby. I've been using the legacy client this whole time, but I downloaded and tried with Downlord's client and I still see a similar line in that log too. Here are the things I've tried to do to fix it:

1. Port Forward 6112 and 7001 on my router (and yes I set up a static IP).

2. Add ports 6112 and 7001 to my firewall.

3. Tried to use ports 6112 and 7001 on both clients.

4. Tried with UPnP both enabled and disabled on the FAF legacy client.

5. Checked to make sure UPnP is enabled on my router.

6. Restart my computer.

7. Restart FAF on both clients.

I tried searching the forum and did find one guy in 2016 that appeared to have a similar issue but he never received any help. Attached are my logs for both the legacy client and Downlord's client, as well the game log. Any assistance you guys could give would be appreciated. Thanks.

Statistics: Posted by AuroraCeleste — 23 Jan 2019, 08:30