Thanks. There has been much discussion about which ports L4D uses when
forked, but I'm not using a forked server in my set up. It seems
abnormal to have a server process bind to 40+ apparently random ports
which would most likely be firewalled anyway.
Any ideas from the Valve devs?
Thanks,
Dave
Pete wrote:
> I rember reading around somehwere that l4d uses random ports, so maybe
> this is the reason. But I wasent really looking into it so I could
> have got the wrong idea.
>
> HTH
>
> 2008/11/12 David A. Parker <[EMAIL PROTECTED]>:
>> Possible bug, perhaps?
>>
>> - Dave
>>
>> Antoine Libert wrote:
>>> On Wed, Nov 12, 2008 at 21:34, David A. Parker <[EMAIL PROTECTED]> wrote:
>>>> Hi,
>>>>
>>>> I have a single-instance L4D server (no forks) running on a specific IP
>>>> address. When the server first started it bound to the normal ports
>>>> (TCP 27015, and UDP 27005, 27015, 27020) and not much else. But after
>>>> running for a few days, it's now bound to 47 UDP ports:
>>>>
>>>> [lots of ports]
>>> Hi,
>>>
>>> I'm experiencing the same thing on my dedi too...
>>>
>> --
>>
>> 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
