That example is from the post,
http://www.mail-archive.com/hlds_linux@list.valvesoftware.com/msg67721.html
which was linked in the starting post. Using the same logic, I could say
people know don't know how to read
the original post before making judgemental, degrading comments towards
one's skillset should not be allowed
to post their "opition" on the mailing list.
----- Original Message -----
From: "Adam Nowacki" <nowa...@platinum.linux.pl>
To: "Half-Life dedicated Win32 server mailing list"
<hlds@list.valvesoftware.com>
Sent: Saturday, August 11, 2012 5:11 PM
Subject: Re: [hlds] UDP 27015 Reverting to TCP master IP
The tcp binding issue should of course get fixed. I'm saying that noone
not knowing (in my opition) the networking basics should not be hosting a
TF2 (as map points out) server for another 24 people.
(I'm venting a bit after the "Server Delisting" spam)
On 2012-08-11 22:54, Calvin Judy wrote:
I'm not sure I understand your reponse, this doesn't just effect TF2, it
effects srcds in general. The amount of servers being hosted
doesn't justify the fact that the issue exists on both linux and
windows. It needs to be fixed, it isn't utilizing TCP until hours after
the
process is online. (At least in my case on both linux & windows.) So it
doesn't appear to be expected behavior, as stated previously.
----- Original Message ----- From: "Adam Nowacki"
<nowa...@platinum.linux.pl>
To: <hlds@list.valvesoftware.com>
Sent: Saturday, August 11, 2012 4:49 PM
Subject: Re: [hlds] UDP 27015 Reverting to TCP master IP
Hint: direction of TCP SYN packets ... but maybe it's for the better,
there is no shortage of TF2 servers - leave it to those who know what
they are doing.
On 2012-08-11 22:11, Calvin Judy wrote:
http://www.mail-archive.com/hlds_linux@list.valvesoftware.com/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
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
