I reported this issue to Valve some time ago. Current workaround is to use -steamport in your command line and forward steamport and steamport+1 on your NAT. There is a sv_master_share_game_socket variable which should instruct server to use game port instead of steamport+1 but it is ignored by the engine at the moment.
Regards, Roman On Wed, Dec 14, 2011 at 7:37 PM, Mariano Peña Ascanio <[email protected]>wrote: > Hello, > > We have seen that the servers for Counter-Strike Source and Team Fortress > 2, use a public and private ip, we have realized that the private IP is > added in the start server line +ip xxx.xxx.xxx.xxx. and the public IP is > the first IP assigned to the network card. > > version : 1.0.0.68/19 4743 secure > udp/ip : xxx.xxx.xxx.32:27165 (public ip: xxx.xxx.xxx.140) > > +ip xxx.xxx.xxx.32 port 27065 > udp/ip : xxx.xxx.xxx.32:27065 > > first IP assigned to the network card. > (public ip: xxx.xxx.xxx.140) > > > I think this is causing an error connecting to the server to those who > want to follow other friends from steam. I believe there is another error, > while playing in quickplay. > > Anyone knows anything about this? Do you know how to make the public and > the private IP same? > > -- > Un saludo, > > Mariano Peña Ascanio > NoGravity S.L. > > > ______________________________**_________________ > 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
