[vox] quake3 serving from behind a firewall
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vox] quake3 serving from behind a firewall
ok, after much procrastination, i rolled up my sleeves and set up a
quake3 server. here's the topology of my LAN:
--- 64.164.47.8
mephisto
LEAF
firewall 192.168.0.2 satan
192.168.0.1 -------------------- 192.168.0.3 navalle
192.168.0.4 lucifer
192.168.0.4 lucifer
192.168.0.4 moloch
on the firewall:
# ipmasqadm portfw -l
prot localaddr rediraddr lport rport pcnt pref
UDP adsl-64-164-47-8 satan.diablo.localnet ntp ntp 10 10
UDP adsl-64-164-47-8 satan.diablo.localnet 27960 27960 8 10
TCP adsl-64-164-47-8 lucifer.diablo.localnet 27500 27500 10 10
TCP adsl-64-164-47-8 satan.diablo.localnet ntp ntp 10 10
TCP adsl-64-164-47-8 satan.diablo.localnet 6346 6346 7 10
TCP adsl-64-164-47-8 satan.diablo.localnet ssh ssh 9 10
TCP adsl-64-164-47-8 satan.diablo.localnet 24 ssh 10 10
TCP adsl-64-164-47-8 satan.diablo.localnet smtp smtp 9 10
TCP adsl-64-164-47-8 satan.diablo.localnet www www 2 10
TCP adsl-64-164-47-8 satan.diablo.localnet ftp ftp 10
i ran the dedicated server on satan (192.168.0.2):
q3ded +set dedicated 2 +net_ip 64.164.47.8 +map q3dm17 +set com_hunkmegs 200
now on satan (192.168.0.2), i *can't* connect to the server by
specifying a connect to server 64.164.47.8 which surprises me. however,
i can connect to the server by specifying 192.168.0.2 which is no
surprise.
however, on lucifer (192.168.0.4) i *can* connect to the server by
specifying a connect to server 64.164.47.8. i can also specify
192.168.0.2. this is groovy.
because lucifer can connect to the server via 64.164.47.8, it seems to
indicate that things have been set up correctly. however, i'm a bit
surprised that satan cannot connect to this address.
any ideas?
if someone with quake3 can try to connect to 64.164.47.8 and let me know
whether you can connect ok, i'd be grateful.
thanks!
pete
Attachment:
pgp00000.pgp
Description: PGP signature
|