[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [warn] Error binding network socket: Address already in use

Quoth Olaf Selke <olaf.selke@xxxxxxxxxxxx>, on 2009-11-10 16:22:34 +0100:
> Drake Wilson wrote:
> > 
> >   # echo 24576 65000 > /proc/sys/net/ipv4/ip_local_port_range
> one question again: why don't set it to "1024 65535"? Is there any good
> reason to exclude a certain port range besides the ports below 1024 from
> being chosen as local port?

That depends on your system.  It's possible there is no reason not to
do that on your system.  The main reason would be if you have other
processes that may need to run services on predefined ports in that
range.  E.g., if your machine is dedicated to Tor, then you may not
experience any problems with a setting of 1024--65535 for dynamic port
allocations.  You can check with netstat or similar, then experiment
as desired.

The IANA theoretically registers up to port 49151, with 0--1023 being
the Well Known ports and 1024--49151 being the Registered Ports; in
practice this is probably too conservative.

   ---> Drake Wilson
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/