Forged Alliance Forever

Re: FAF proxy cutting in after I'm already connected

2014-10-18T21:24:28+02:00

stalewee wrote:
Log is attached. You can see me connect to HZH fine:

2014-06-14 11:00:32,079 INFO faf.fa.relayer Command transmitted from FA to server : {"action": "Connected", "chuncks": ["80707"]}

At this point I can see HZH in chat and my ping is low. Then a little later:

2014-06-14 11:00:41,818 INFO faf.fa.relayer Command received from server : {"commands": [7, "24.63.134.147", "HZH", 80707], "key": "ConnectToProxy"}
2014-06-14 11:00:41,944 INFO faf.fa.relayer Command transmitted from FA to server : {"action": "Disonnected", "chuncks": ["80707"]}
2014-06-14 11:00:43,410 INFO faf.fa.relayer Command transmitted from FA to server : {"action": "Connected", "chuncks": ["80707"]}

After this, my ping is 800ms. FAF has severed my perfectly fine p2p connection to HZH and replaced it with an unplayable proxy connection.

This makes FAF almost impossible for Australians in particular. We would really be better off if there was no proxy.

Both peers must report the "Connected" state to the server. so if your client did report it that is only 50% of it.
without the forever.log from the other guy, can't say for sure.

Statistics: Posted by rootbeer23 — 18 Oct 2014, 21:24

Re: FAF proxy cutting in after I'm already connected

2014-08-09T15:57:51+02:00

D10ny5u5 wrote:
OK I've submitted a code change. Not sure it's the correct part or will even fix the issues of the proxy kicking in when it shouldn't. This is spoiling so many games.

You must test it before I can integrate it.

If it's about making the proxy optional, I won't integrate it. It's not an option.

Statistics: Posted by Ze_PilOt — 09 Aug 2014, 15:57

Re: FAF proxy cutting in after I'm already connected

2014-08-09T14:57:16+02:00

OK I've submitted a code change. Not sure it's the correct part or will even fix the issues of the proxy kicking in when it shouldn't. This is spoiling so many games.
I think it may be more then just adjusting the time out on connection. I've realised having the proxy optional won't work, unless we convince both parties to switch it off, however this will cause more issues with connections to RU and people who haven't configured the proxy correctly.
My next proposal is that we switch off proxy connections for AU to AU connections (May be NZ thrown in there too). Even if this means we will fail connections when AU or NZ haven't set up their firewalls, NAT, etc correctly.
I haven't heard anything about my first code change and don't really want to devote a lot of time to this, as I don't really know how to test the code and have little faith that it would be accepted.
Is ZEP still around? Or who is making decisions around these code changes now?

Statistics: Posted by D10ny5u5 — 09 Aug 2014, 14:57

Re: FAF proxy cutting in after I'm already connected

2014-08-03T15:42:51+02:00

I am not sure. The initial connection and then whatever is calling the proxy should be there though ... i think.

Statistics: Posted by Deering — 03 Aug 2014, 15:42

Re: FAF proxy cutting in after I'm already connected

2014-08-03T15:39:08+02:00

Does that include the proxy code?

Statistics: Posted by D10ny5u5 — 03 Aug 2014, 15:39

Re: FAF proxy cutting in after I'm already connected

2014-08-03T15:28:40+02:00

faf is open source, so if you want to try to help fix it that would be great. This might help you get started.

viewtopic.php?f=45&t=1788

Statistics: Posted by Deering — 03 Aug 2014, 15:28

Re: FAF proxy cutting in after I'm already connected

2014-08-01T15:04:27+02:00

This is causing issues to most Aussies at times. Around about 6 or so weeks ago there was a change, "for the better". Nothing wrong with connections, however the proxy decides we should use it. Happens more frequently when there a few Aussies and a few EUs in the game.
This is so frustrating.
Please ZEP we have our connections sorted out, please, please either put in a menu option for Proxy on or off, or at least increase the timer, or go back to the old code. I beg you.

Happy to attempt a crack at fixing the code...we have a bunch of professional developers playing FAF in Australia.

Thanks

Statistics: Posted by D10ny5u5 — 01 Aug 2014, 15:04

Re: FAF proxy cutting in after I'm already connected

2014-06-19T07:28:10+02:00

You need to enable logs for the game log. game.log will be rewritten every time that fa launches so that includes only the lobby.

If you are going to ask how to enable it. Read the red text again

Statistics: Posted by Deering — 19 Jun 2014, 07:28

Re: FAF proxy cutting in after I'm already connected

2014-06-19T02:20:11+02:00

RoLa wrote:
I think you have never been connected p2p with HZH

But we can see each other's chat in the lobby before the proxy connection is made.

RoLa wrote:
HZH was not the only one to connect through proxy. You had a total of 54 connections attempts and from that 38 turned to proxy connections

Yes, but you can see that I generally have a direct connection first, and then that direct connection is later broken so that the proxy can connect. I just chose HZH as a specific example.

Deering wrote:
If it happens again post the game.log

Ok, but will there be a game.log if I don't launch the game? I'm pretty sure this happens pretty much every lobby.

Thanks for looking into it.

Statistics: Posted by stalewee — 19 Jun 2014, 02:20

Re: FAF proxy cutting in after I'm already connected

2014-06-18T11:24:01+02:00

If it happens again post the game.log as well as fa. Normally with this kind of thing need everyone who is involved logs as well. I saw this happen to me a week or so ago as well, so not just you.

Statistics: Posted by Deering — 18 Jun 2014, 11:24

Re: FAF proxy cutting in after I'm already connected

2014-06-18T10:58:31+02:00

stalewee wrote:
2014-06-14 11:00:32,079 INFO faf.fa.relayer Command transmitted from FA to server : {"action": "Connected", "chuncks": ["80707"]}
After this, my ping is 800ms. FAF has severed my perfectly fine p2p connection to HZH and replaced it with an unplayable proxy connection.
This makes FAF almost impossible for Australians in particular. We would really be better off if there was no proxy.

I think you have never been connected p2p with HZH. But i must admit that reading the logs is really hard. Perhaps it would be easier if there were a seperate log with easier to understand entries. Or a tool to convert the log to something more readable.

2014-06-14 10:58:24,200 INFO faf.fa.relayer Command received from server : {"commands": ["24.63.134.147:34787", "HZH", 80707], "key": "ConnectToPeer"}
2014-06-14 10:58:39,221 INFO faf.fa.relayer Command received from server : {"commands": [10, "24.63.134.147", "HZH", 80707], "key": "ConnectToProxy"}
2014-06-14 11:00:26,828 INFO faf.fa.relayer Command received from server : {"commands": ["24.63.134.147:34787", "HZH", 80707], "key": "ConnectToPeer"}
2014-06-14 11:00:41,818 INFO faf.fa.relayer Command received from server : {"commands": [7, "24.63.134.147", "HZH", 80707], "key": "ConnectToProxy"}

EDIT:
i think you have firewall issues. HZH was not the only one to connect through proxy. You had a total of 54 connections attempts and from that 38 turned to proxy connections.

Spoiler: show

Statistics: Posted by RoLa — 18 Jun 2014, 10:58

Re: FAF proxy cutting in after I'm already connected

2014-06-18T08:06:35+02:00

Bump.

This problem is a massive pain in the butt. It ruins many games/lobbies.

It seems like it would be so easy to fix. Just check whether there is already a direct connection before making the proxy connection.

There is even a pop up message saying that it costs money whenever we use the proxy. I imagine a large portion of the proxy connections are not needed. Everybody loses.

Statistics: Posted by stalewee — 18 Jun 2014, 08:06

FAF proxy cutting in after I'm already connected

2014-06-14T03:24:38+02:00

This sequence of events happens pretty much every time I join a game:
1. Enter game lobby.
2. Establish connection to various players. Ping is low and we can read each other's chat.
3. Ten seconds later, it says that I've connected to the player again, and ping shoots up to 800ms.

Step 3 is the FAF proxy ruining my life for no valid reason.

Log is attached. You can see me connect to HZH fine:

2014-06-14 11:00:32,079 INFO faf.fa.relayer Command transmitted from FA to server : {"action": "Connected", "chuncks": ["80707"]}

At this point I can see HZH in chat and my ping is low. Then a little later:

2014-06-14 11:00:41,818 INFO faf.fa.relayer Command received from server : {"commands": [7, "24.63.134.147", "HZH", 80707], "key": "ConnectToProxy"}
2014-06-14 11:00:41,944 INFO faf.fa.relayer Command transmitted from FA to server : {"action": "Disonnected", "chuncks": ["80707"]}
2014-06-14 11:00:43,410 INFO faf.fa.relayer Command transmitted from FA to server : {"action": "Connected", "chuncks": ["80707"]}

After this, my ping is 800ms. FAF has severed my perfectly fine p2p connection to HZH and replaced it with an unplayable proxy connection.

This makes FAF almost impossible for Australians in particular. We would really be better off if there was no proxy.

Statistics: Posted by stalewee — 14 Jun 2014, 03:24