[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Hurdish TCP stack
|
From: |
olafBuddenhagen |
|
Subject: |
Re: Hurdish TCP stack |
|
Date: |
Wed, 2 Apr 2008 00:08:13 +0200 |
|
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
Hi,
On Tue, Apr 01, 2008 at 05:20:54PM +0200, Richard Braun wrote:
> /dev/net/tcp/123 is OK. /dev/eth0/tcp/321 isn't. As I said, you must
> consider TCP as a global layer, otherwise you will run into name space
> conflict problems. For example, a socket in listen mode on INADDR_ANY
> is bound to no interface, or all interfaces (at your choice).
Well, that's why we suggested having both /net/eth0/tcp and /net/tcp,
using the former when listening on an individual interface, and the
latter when listening on all. Do you think there are cases where this
approach would pose problems?
-antrik-