Connection Issues in GW

[Deering]

Since the fixes this week I have been having more problems connecting to people. I have 6112 forwarded to my pc. The odd thing is straight before/after failing to connect in gw we can connect fine in a custom game. Wondering if there is anything else I can do to try to help this.

Also while in setting up automatch the timeout is broken. It sometimes works and sometimes does not. Have just sat in the screen for 20 minutes without timeout. Logs below.

[Eximius]

Deering's router's port forwarding is broken and doesn't let through the packets. The game defaults to proxy for us both in custom and GW games. The problem in GW it seems, is that the packets never get through the proxy to the other end.

I also opened the zips for GW and FAF game modes and GW has different lobby code, which might be why this is happening.
(lua code for p2p connection handling should be identical?)

I'm attaching my side of the logs here.

My forever.log is actually a debugger console dump, because I was running faf in a debugger.
For reference, I am attaching game_control.log which is a custom game log (in which we were connected over the proxy correctly).

[Ze_PilOt]

The lobby is not used in GW, so it doesn't matter.

[Eximius]

Is lobby(Comm) not used to set up the p2p connections at start? Well there is one thing that is peculiar is that normal FAF uses a weird lobbyComm.lua as it does not log System messages. (Even though both lobby.nxt and faforever.faf have the logging enabled (Though I really do not know the structure of FAF, so I'm just going on hunches here)).

If lobby(Comm).lua is not even used in GW, why is it in the package?

The connection behaviour in GW in this instance seems to be:
Regular: Peer ~> Host ; Connect
Regular: Host ~(fail)~> Peer ; Connection response (Never reaches Peer)
Proxy: Peer ~> Host ; Connect
Proxy: Host ~(reject)~>Peer ; Unexpected connection
Regular: Host ~(Disconnect)~>Peer ; (Regular connection failure?)
Proxy: Peer ~> Host ; Connect
Proxy: Host ~(fail)~> Peer ; Connection response (Never reaches Peer)

EDIT: Noted the LIES AND SLANDER I wrote.
EDITEDIT: I was right the first time. I honestly doubt myself way too much.

[Ze_PilOt]

No idea what you are talking about. There is no special lobbycom for GW.

[Deering]

Ok, so is there anything I can do about connection issues or any reason why they would appear in gw and not in a custom game

[Ze_PilOt]

Are you sure you are able to connect to these players in custom game?

If so, I need logs when you failed on GW but succeed on custom, with the same exact players.

[Eximius]

We did exactly that with the control game. Also, my thoughts on the connection pattern were completely wrong. EDIT: Nope!

Our forever.log s contain both games. (Look at the last 2 game slavings only in Deering's log.)

I looked at both forever.log s and it seems that the connection slaving on the client worked both times, but the GW in-game is still stuck at 'Setting up automatch...' and not timing out.

[Ze_PilOt]

Please retry and post logs of both attempt for all players.

[Deering]

Will do, currently on a different internet connection so will see what happens on it. Will try to imitate it sometime in the next week.