| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20080228183054.GA903@linuxace.com> Date: Thu, 28 Feb 2008 10:30:54 -0800 From: Phil Oester <kernel@...uxace.com> To: Nebojsa Miljanovic <neb@...atel-lucent.com> Cc: linux-kernel@...r.kernel.org, "Kittlitz, Edward \(Ned\)" <nkittlitz@...atel-lucent.com>, asweeney@...atel-lucent.com, "Polhemus, William \(Bart\)" <bpolhemus@...atel-lucent.com> Subject: Re: SO_REUSEADDR not allowing server and client to use same port On Thu, Feb 28, 2008 at 12:15:06PM -0600, Nebojsa Miljanovic wrote: > Hello all, > I have seen similar complaints about this issue before in the list archive, but > I have not seen any resolution. So, I am posting the question again in hope of > getting some replies. > > Currently, Linux does not allow reuse of same local port for both TCP server and > TCP client. I understand that there may be a need to prevent two servers from > binding to the same local port, but having 1 server and 1 outgoing client use it > should be allowed. Other Unix like operating systems do allow it. Further more, > Linux SCTP socket API allows for this to happen. And, I can't imagine why this > restriction would exists for TCP and not for SCTP. You'd likely get better response by posting this on the netdev list. Phil -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists