Re: n-hurd networking

[Simon Law]

On Wed, Aug 07, 2002 at 12:22:02PM -0700, Thomas Bushnell, BSG wrote:
> My dreaming suggest the following:
> 
> One IP address is allocated to each individual Hurd, and an additional
> IP address is allocated to the collective as a whole.  Generally, only
> the latter is seen by most users.
> 
> The Hurd's use their individual IP addresses to talk to each other and
> to send Mach (or whatever kernel) IPC with network transparency.
> 
> The Collective's IP address is managed something like as follows:
> 
> Each Hurd has a copy of the routing table.
> 
> Each Hurd has responsibility for some subset of the incoming network
> traffic.  Each TCP connection, for example, is owned by a particular
> Hurd.  Each SYN listener is owned by a particular Hurd.  Etc.  For
> obvious reasons, the Collective tries to have the owner of a network
> connection be the same Hurd on which is running the user land program
> that has the socket open.
> 
> Listening to ICMP would generally be owned by only a single Hurd.

        Wouldn't it be easier to have the Hurd running closest to the
hardware, the one on boot, have full control of the network?  Any
sub-Hurds could be running on a private internal network, and the
primary Hurd could do NAT.

        Of course, this would require something like Netfilter to be
ported.  *sigh*

Simon