You still need to deal with the steamport, clientport (27005), matchmakingport 
(27025), systemlinkport (27030) in order to actually start up the servers, but 
on the firewall front you should be good. This is how the PC servers I have 
setup are firewalled.

The systemlink and matchmaking ports are likely to go away at some point. These 
are vestiges of the Xbox networking code. So this will make things a little 
easier.

M.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David A. Parker
Sent: Thursday, November 13, 2008 2:00 PM
To: Half-Life dedicated Linux server mailing list
Subject: Re: [hlds_linux] Opening ports for forked servers

So a forked server should work under our existing configuration?  That's
excellent.  Thanks!

     - Dave

Milton Ngan wrote:
> The only port you need to have exposed to the world is the +hostport (aka 
> -port aka +port). This is the default 27015 UDP port. Add the rcon and netcon 
> ports as you need them. The other ports need to be allocated (unless you can 
> disable them like the hltv port), but are only used for outbound 
> communication (or not used at all), so they don't need to be open inbound on 
> your firewall.
>
> M.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David A. Parker
> Sent: Thursday, November 13, 2008 1:39 PM
> To: Half-Life dedicated Linux server mailing list
> Subject: [hlds_linux] Opening ports for forked servers
>
> Hi,
>
> I'm trying to figure out which ports I would need to request to have
> opened through our firewall if I decide to run a forked L4D server
> (which I would like to do).  As it stands right now, we have the
> following ports open to each of our game server IPs:
>
> TCP 27015
> UDP 1200
> UDP 27000-27015
>
> Let's say I start a server using the following command line:
>
> ./srcds_run \
> -game left4dead \
> -ip x.x.x.x \
> -nohltv \
> +map l4d_dem_hospital01_apartment\
> -fork 8
>
> This should start 8 servers, and since I'm not using hltv, they should
> be listening on sequential UDP ports 27015-27022.  In this case I would
> simply ask to have UDP ports 27016-27022 opened up.  However, in
> Milton's e-mail he mentioned other options, such as -steamport,
> +clientport +hostport, +matchmakingport, and +systemlinkport.  Would any
> of these ports need to be specified as well?
>
>      Thanks,
>      Dave
>
> --
>
> Dave Parker
> Utica College
> Integrated Information Technology Services
> (315) 792-3229
> Registered Linux User #408177
>
> _______________________________________________
> 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
>

--

Dave Parker
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177

_______________________________________________
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

Reply via email to