http://www.mail-archive.com/[email protected]/msg67721.html


Invalid protocol was able to help me solve the issue when I was operating 
servers on a linux platform, this same issue has arose on windows, generally 
after a couple hours of uptime the servers will update the "Public IP" field, 
the problem is they're not using the assigned IP after this update. Below is a 
"status" command example of the issue. 

version : 1.2.1.4/21 4961 secure
         udp/ip  : ***.***.***.92:27015  (public ip: ***.***.***.88)
         account : not logged in  (Cannot locate owner's steam account)
         map     : ctf_2fort at: 0 x, 0 y, 0 z
         players : 6 (24 max) The problem with this is that the "Public IP" 
field is what users join off of through steam invites, when the server is 
"updating" this value, it's causing the server to show non-responsive because 
no server is running on the ip requested.This issue was solved before by 
keeping 27015 through TCP closed, however this is being used as the rcon port 
and cannot be closed as rcon is how I'm managing this on the fly. Has anyone 
found a solution to this? Or can we get a valve employee to look into this 
issue? I don't understand why a process utilizing UDP connections is 
automatically adjusting itself to harbor a TCP connection.Thank you.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds

Reply via email to