On Tue, 30 Nov 2004, ScratchMonkey wrote: > Ah, so the problem is that packets within the LAN are going through the > Cisco instead of taking the direct route, host to host. Presumably because > they're using the external address of the server, not the internal one. > Does the server not listen on the internal address? Could you have the > client connect to the internal address? Or is this a different Steam > limitation?
No, it's not translating, it's taking the direct route. The Cisco isn't doing the translations, because normally it shouldn't have to. It needs to do them to make STEAMauth work. It doesn't make a difference if it's internal or not. I've tried making an alias to the internal-net, and that hasn't worked either. Thanks, Adam (Just have steamauth ignore the private IP blocks after a successful first authentication. and I'll go away, I promise, coz that'll fix this issue). If that's a major issue, have the server force the client to check with the auth servers to make sure that it is still the same client. Or you could make just cafe accounts ignore that second check too? I dunno guy. This is a very easy fix. ---------------------------------------------------- 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

