I have tried to get vassal to run through a proxy, but there are a
few problems. It does appear that the server status application ONLY
uses HTTP (tcp port 80), but the actual game connectivity stuff uses
tcp port 5050, and it is a listening socket. This makes me think that
when you connect to the server once you have your scenario loaded, it
automatically creates a room for you. What this means is that you
can't connect to games through a proxy server, only browse the server
status details. Also the port may change if 5050 is in use, ie.
5051, 5052, and so on.
You can't really use a proxy for gaming because of this. The code
either has to be changed to tunnel all the game connectivity data
through the proxy, or you have to be able to choose which IP and port
can be used so you can tunnel the traffic through ssh or some other
tunneling technology.
I will say the following: If you have NAT enabled on your firewall,
you will have to create a redirection rule on it to make your games
work. In OpenBSD pf rules it would look like this:
rdr on $ext_if inet proto tcp from any to $ext_if port 5050 ->
$int_host port 5050
Where $ext_if is the routable ip address of your firewall, and
$int_host is the (most likely) rfc1918 ip address of the host running
the vassal software. You will also have to permit tcp/5050 outbound
inbound to that internal host IP as well to make this work.
Personally, I would love to see all connectivity wrapped under the
proxy, as it is easier to use, and requires no real changes to
firewalls, but this may not be the easiest way to code it.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/vassalengine/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
