> 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 have no use for a tunnel... the other store plays just fine, because it registers to the STEAMnetwork as .230, and connects to the server as .230, because it has to cross the line and go 2 miles ^^ > I don't know how CAServer works, though, so I don't know if this helps the > situation. Said for completeness, CAserver really doesn't have anything to do with the problem, but I wanted to be complete. > > 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? When the client connects to the CS server(.244). Because it's an internal client. The packet gets routed to the cisco, and the cisco routes the packet to the CS server (.244), without any translation, because the Cisco is on the same LAN. Thanks, 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
