Alternative lobby TCP port

[fabio]

It looks the lobby uses the port 5222 which may be closed in some environments (e.g. the one I am trying it now). Since the server is managed by WFG can another standard common port be used (80/443?)? Eventually 5222 could also be left open (especially if it is intended to be used by other xmpp clients other than the game itself), the game could try connecting to 5222 and, if it fails after a timeout or get a ICMP destination unreachable, try the other port.

[RedFox]

If we manage to get NAT hole punching to work, then it doesn't matter what port number the client uses. As long as the listener server has its listening port open, we can create numerous connections from client to server and use the automatically opened ports on the client.

[Ykkrosh]

It sounds like the problem is with clients trying to connect to the server's TCP port 5222, behind a firewall or proxy that doesn't allow arbitrary outgoing TCP connections. NAT hole punching can't help with that.

Gloox apparently supports BOSH, which is an HTTP-based protocol and is more likely to be able to pass through HTTP proxies successfully that the standard protocol - it may be best to set up the server to support BOSH on port 80, and use that as a fallback when the standard connection fails.

[gameboy]

I also want to set up such a server, but does not provide built inside svn server files!

thank you!

Edited November 9, 2013 by gameboy