> my thoughts: > IP:PORT from the network-package AFTER NAT > for example my server has ip 192.168.1.3, port 27015. Now the > router get's > the package and changes the ip to my online-ip and uses a random port. > So the server apears at the masterlist, but with a wrong > port. So connecting > via masterlist doesn't work. > When the router doesn't change the port, all is fine and > connection works > via masterlist. > > Would be great if someone who KNOWS how it works can give me > some hints :)
You've hit the nail on the head. To fix this problem, you'll have to force your NAT device to leave the port intact after NAT'ing the IP address. Depending on the firmware of the router, you may or may not be able to do this (if it's a hardware router). If your NAT device is a PC with Linux or another OS, you should be able to fix this problem with a rule. Please respond with full details of your NAT device, and we'll see what we can come up with for you. StanTheMan rcon admin at: Beer for Breakfast servers <http://bfb.bogleg.org/> 66.111.111.66:27015 (CS multi-map) 66.111.111.66:27016 (CS militia/dust2) Dallas, TX _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
