Thread (2 messages) 2 messages, 2 authors, 2007-05-31

Re: [PATCH] use default 32768-61000 outgoing port range in all cases

From: David Miller <davem@davemloft.net>
Date: 2007-05-31 22:43:34

From: Mark Glines <redacted>
Date: Tue, 15 May 2007 15:50:54 -0700
I noticed I had chopped off a whole comment, when I meant to only remove
part of it.  So I've fixed that.

This is a reissued use-high-ports-for-local-stuff.diff, with a comment
fix.  Does anyone have a problem with this patch in its current form?
Any chance of applying it?

This diff changes the default port range used for outgoing connections,
from "use 32768-61000 in most cases, but use N-4999 on small boxes
(where N is a multiple of 1024, depending on just *how* small the box
is)" to just "use 32768-61000 in all cases".

I don't believe there are any drawbacks to this change, and it keeps
outgoing connection ports farther away from the mess of IANA-registered
ports.

Signed-off-by: Mark Glines <redacted>
Sorry for taking forever to wrap my brain around this, I think your
patch is the way to go and I will merge it.

The code was trying to match the allowed port range with the sizing
of the bind hash table, which is hashed by local port number.  But
even considering that I think it's OK to use the full range by
default, always.

Thanks a lot.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help