--On Tuesday, November 30, 2004 1:26 AM -0600 Adam 'Starblazer' Romberg <[EMAIL PROTECTED]> wrote:
The stores are set up where the clients are assigned local addresses. (192.168.1.*). They are handed STEAM logins thru CAServer. All Cafe logins are handed to the clients on a dynamic basis due to CAserver.
It sounds like you might want not NAT but a tunnel. Let's say one store is 192.168.1.0/24 and the other is 192.168.2.0/24, and you route between them using a tunnel over the public network. You don't need encryption because you don't care if the packets are sniffed.
I don't know how CAServer works, though, so I don't know if this helps the situation.
The problem is that when a local store computer (bgr), connects to the STEAM network, the STEAMnetwork assigns the UserID ticket of Badger's External, which is 209.103.209.250. However, when that client tries to connect to the server at 209.103.209.244, the STEAM server sees the clients IP address of 192.168.1.x, not 209.103.209.250, which the UID Ticket was assigned to. That's the problem.
This sounds backwards. Client behind .250 registers with Steam and should look to Steam like it's .250. When connecting to server at .244, it should look to .244 like it's .250. Where does Steam learn that it's 192.168.1.x?
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
