I'm pretty sure the reported public IP is the one that Steam sees your packets coming from, and the other address it the one the game server is bound to.
Can you connect to your server via the eth0 address; 85.x.x.57:27015? If not then there's nothing to worry about. Also I don't know why you've hidden your IP, when it's publically available on the master servers ;) Kind regards, *Saul Rennison* On 22 July 2012 16:19, Ronny Schedel <[email protected]> wrote: > Hello, > > I have discovered a strange thing with our DOD:S and TF2 servers today. > Take a look at the line of the status output: > > udp/ip : 85.x.x.95:27015 (public ip: 85.x.x.57) > > We are binding our server to 85.x.x.95 with +ip as start parameters. The > public IP shows our IP address from the first network card eth0. Wtf? How > can I prevent this behaviour? > > Best regards > > Ronny > > ______________________________**_________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.**com/cgi-bin/mailman/listinfo/**hlds_linux<https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux> > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
