Re: [hlds_linux] srcds and hlds port assignment
I recently had my ISP host open these ports in the firewall after a firewall reset: 1200 UDP 27000-27020 UDP 27024-27050 TCP These are all in-bound. I also use 123 for NTP plus the usual ones for ssh and http. Hope that helps ...Chuck (Old and Slow) cgi...@compuserve.com -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Kacper Nowak Sent: Thursday, September 09, 2010 6:22 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] srcds and hlds port assignment It seams it does, but what is the range ? > Doesn't steam use its own ports, too? > > Thanks, > - Saul. > > > On 9 September 2010 11:50, Kacper Nowak wrote: > >> Hi, everyone >> >> I have question about port usage, by srcds and hlds. >> >> With netstat -nlp i can see that my server is using port specified, by >> -port -tv_port command + tcp port= -port (rcon), but it also uses other >> ports, in quite random manner. >> >> If i`m assigning ports for dedicated server within range 27000 - 29000, >> then at some point new server port will cause problem with one of this >> randomly opened ports. >> >> example listing: >> >> Two srcds servers: >> >> tcp0 0 85.128.48.130:27000 0.0.0.0:* LISTEN >> 20955/srcds_linux >> tcp0 0 85.128.48.130:27001 0.0.0.0:* LISTEN >> 19838/srcds_linux >> udp0 0 85.128.48.130:28998 0.0.0.0:* >>19838/srcds_linux >> udp0 0 85.128.48.130:28999 0.0.0.0:* >>20955/srcds_linux >> udp0 0 85.128.48.130:26901 0.0.0.0:* >>19838/srcds_linux >> udp0 0 85.128.48.130:26902 0.0.0.0:* >>20955/srcds_linux >> udp0 0 85.128.48.130:27000 0.0.0.0:* >>20955/srcds_linux >> udp0 0 85.128.48.130:27001 0.0.0.0:* >>19838/srcds_linux >> udp 1440 0 85.128.48.130:27005 0.0.0.0:* >>19838/srcds_linux >> udp0 0 85.128.48.130:27006 0.0.0.0:* >>20955/srcds_linux >> >> Three hlds servers: >> udp0 0 85.128.48.130:26900 0.0.0.0:* >>29647/hlds_amd >> udp0 0 85.128.48.130:26903 0.0.0.0:* >>32730/hlds_amd >> udp0 0 85.128.48.130:26904 0.0.0.0:* >>18006/hlds_amd >> udp0 0 85.128.48.130:26905 0.0.0.0:* >>24325/hlds_amd >> udp0 0 85.128.48.130:27002 0.0.0.0:* >>32730/hlds_amd >> udp0 0 85.128.48.130:27003 0.0.0.0:* >>18006/hlds_amd >> udp0 0 85.128.48.130:27004 0.0.0.0:* >>24325/hlds_amd >> udp0 0 85.128.48.130:27015 0.0.0.0:* >>29647/hlds_amd >> >> Can anyone explain how does it work? And most of all how to avoid port >> number conflict if srcds and hlds take random ports in addition to those >> assigned by command line ? >> >> Best wishes >> KN >> >> ___ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> > ___ > To unsubscribe, edit your list preferences, or view the list archives, please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] srcds and hlds port assignment
It seams it does, but what is the range ? Doesn't steam use its own ports, too? Thanks, - Saul. On 9 September 2010 11:50, Kacper Nowak wrote: Hi, everyone I have question about port usage, by srcds and hlds. With netstat -nlp i can see that my server is using port specified, by -port -tv_port command + tcp port= -port (rcon), but it also uses other ports, in quite random manner. If i`m assigning ports for dedicated server within range 27000 - 29000, then at some point new server port will cause problem with one of this randomly opened ports. example listing: Two srcds servers: tcp0 0 85.128.48.130:27000 0.0.0.0:* LISTEN 20955/srcds_linux tcp0 0 85.128.48.130:27001 0.0.0.0:* LISTEN 19838/srcds_linux udp0 0 85.128.48.130:28998 0.0.0.0:* 19838/srcds_linux udp0 0 85.128.48.130:28999 0.0.0.0:* 20955/srcds_linux udp0 0 85.128.48.130:26901 0.0.0.0:* 19838/srcds_linux udp0 0 85.128.48.130:26902 0.0.0.0:* 20955/srcds_linux udp0 0 85.128.48.130:27000 0.0.0.0:* 20955/srcds_linux udp0 0 85.128.48.130:27001 0.0.0.0:* 19838/srcds_linux udp 1440 0 85.128.48.130:27005 0.0.0.0:* 19838/srcds_linux udp0 0 85.128.48.130:27006 0.0.0.0:* 20955/srcds_linux Three hlds servers: udp0 0 85.128.48.130:26900 0.0.0.0:* 29647/hlds_amd udp0 0 85.128.48.130:26903 0.0.0.0:* 32730/hlds_amd udp0 0 85.128.48.130:26904 0.0.0.0:* 18006/hlds_amd udp0 0 85.128.48.130:26905 0.0.0.0:* 24325/hlds_amd udp0 0 85.128.48.130:27002 0.0.0.0:* 32730/hlds_amd udp0 0 85.128.48.130:27003 0.0.0.0:* 18006/hlds_amd udp0 0 85.128.48.130:27004 0.0.0.0:* 24325/hlds_amd udp0 0 85.128.48.130:27015 0.0.0.0:* 29647/hlds_amd Can anyone explain how does it work? And most of all how to avoid port number conflict if srcds and hlds take random ports in addition to those assigned by command line ? Best wishes KN ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] srcds and hlds port assignment
Doesn't steam use its own ports, too? Thanks, - Saul. On 9 September 2010 11:50, Kacper Nowak wrote: > Hi, everyone > > I have question about port usage, by srcds and hlds. > > With netstat -nlp i can see that my server is using port specified, by > -port -tv_port command + tcp port= -port (rcon), but it also uses other > ports, in quite random manner. > > If i`m assigning ports for dedicated server within range 27000 - 29000, > then at some point new server port will cause problem with one of this > randomly opened ports. > > example listing: > > Two srcds servers: > > tcp0 0 85.128.48.130:27000 0.0.0.0:* LISTEN > 20955/srcds_linux > tcp0 0 85.128.48.130:27001 0.0.0.0:* LISTEN > 19838/srcds_linux > udp0 0 85.128.48.130:28998 0.0.0.0:* > 19838/srcds_linux > udp0 0 85.128.48.130:28999 0.0.0.0:* > 20955/srcds_linux > udp0 0 85.128.48.130:26901 0.0.0.0:* > 19838/srcds_linux > udp0 0 85.128.48.130:26902 0.0.0.0:* > 20955/srcds_linux > udp0 0 85.128.48.130:27000 0.0.0.0:* > 20955/srcds_linux > udp0 0 85.128.48.130:27001 0.0.0.0:* > 19838/srcds_linux > udp 1440 0 85.128.48.130:27005 0.0.0.0:* > 19838/srcds_linux > udp0 0 85.128.48.130:27006 0.0.0.0:* > 20955/srcds_linux > > Three hlds servers: > udp0 0 85.128.48.130:26900 0.0.0.0:* > 29647/hlds_amd > udp0 0 85.128.48.130:26903 0.0.0.0:* > 32730/hlds_amd > udp0 0 85.128.48.130:26904 0.0.0.0:* > 18006/hlds_amd > udp0 0 85.128.48.130:26905 0.0.0.0:* > 24325/hlds_amd > udp0 0 85.128.48.130:27002 0.0.0.0:* > 32730/hlds_amd > udp0 0 85.128.48.130:27003 0.0.0.0:* > 18006/hlds_amd > udp0 0 85.128.48.130:27004 0.0.0.0:* > 24325/hlds_amd > udp0 0 85.128.48.130:27015 0.0.0.0:* > 29647/hlds_amd > > Can anyone explain how does it work? And most of all how to avoid port > number conflict if srcds and hlds take random ports in addition to those > assigned by command line ? > > Best wishes > KN > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
[hlds_linux] srcds and hlds port assignment
Hi, everyone I have question about port usage, by srcds and hlds. With netstat -nlp i can see that my server is using port specified, by -port -tv_port command + tcp port= -port (rcon), but it also uses other ports, in quite random manner. If i`m assigning ports for dedicated server within range 27000 - 29000, then at some point new server port will cause problem with one of this randomly opened ports. example listing: Two srcds servers: tcp0 0 85.128.48.130:27000 0.0.0.0:* LISTEN 20955/srcds_linux tcp0 0 85.128.48.130:27001 0.0.0.0:* LISTEN 19838/srcds_linux udp0 0 85.128.48.130:28998 0.0.0.0:* 19838/srcds_linux udp0 0 85.128.48.130:28999 0.0.0.0:* 20955/srcds_linux udp0 0 85.128.48.130:26901 0.0.0.0:* 19838/srcds_linux udp0 0 85.128.48.130:26902 0.0.0.0:* 20955/srcds_linux udp0 0 85.128.48.130:27000 0.0.0.0:* 20955/srcds_linux udp0 0 85.128.48.130:27001 0.0.0.0:* 19838/srcds_linux udp 1440 0 85.128.48.130:27005 0.0.0.0:* 19838/srcds_linux udp0 0 85.128.48.130:27006 0.0.0.0:* 20955/srcds_linux Three hlds servers: udp0 0 85.128.48.130:26900 0.0.0.0:* 29647/hlds_amd udp0 0 85.128.48.130:26903 0.0.0.0:* 32730/hlds_amd udp0 0 85.128.48.130:26904 0.0.0.0:* 18006/hlds_amd udp0 0 85.128.48.130:26905 0.0.0.0:* 24325/hlds_amd udp0 0 85.128.48.130:27002 0.0.0.0:* 32730/hlds_amd udp0 0 85.128.48.130:27003 0.0.0.0:* 18006/hlds_amd udp0 0 85.128.48.130:27004 0.0.0.0:* 24325/hlds_amd udp0 0 85.128.48.130:27015 0.0.0.0:* 29647/hlds_amd Can anyone explain how does it work? And most of all how to avoid port number conflict if srcds and hlds take random ports in addition to those assigned by command line ? Best wishes KN ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
