Did you tried port forwarding ?
It surelly gives more work than simple NAT, but then again, the IP would
always be the public one, despite if you have the server or not in the
same network, as long as the port forward is ok.
Never tried PF with UDP protocols, so don't have a clue... just an idea

Adam 'Starblazer' Romberg wrote:

I posted this on the forums, and for sake of my santy, I'm posting it
here too.

http://www.steampowered.com/forums/showthread.php?s=&postid=1682656

--- begin cut ---
Okay, I dont want to dump another 309$ into my router because of
STEAM.

Here we go.

The steam networks retarded authentication breaks on NAT. We have a
server which we would like to have publicly available, with an
externally supplied address. Our customers route to our SLS server,
and then bounce out of external address. When they try to route to our
server, our router just bounces them to our external, yet they connect
as the internal scope (192.168.1.100-125).

This of course, throws out an invalid STEAM UserID ticket error,
because the original IP that was used to register to the master
servers doesn't match the connecting ip.

Anyone else have this issue and have a resolution?

ps. Nat-On-A-Stick will not work, we will bake our Cisco 1721.
Already pushing 50% at peak times.

---- end cut ----

any other clues guys?

Thanks in advance,

Adam

----------------------------------------------------
Adam 'Starblazer' Romberg     Appleton: 920-738-9032
System Administrator       Valley Fair: 920-968-7713
ExtremePC LLC    -=-  http://www.extremepcgaming.net

_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux






_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to