[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: /servers/socket/2 -- why only one inet socket?
|
From: |
Marcus Brinkmann |
|
Subject: |
Re: /servers/socket/2 -- why only one inet socket? |
|
Date: |
Mon, 14 Oct 2002 13:06:22 +0200 |
|
User-agent: |
Mutt/1.4i |
On Mon, Oct 14, 2002 at 07:00:24AM -0400, Clemmitt Sigler wrote:
> On this point, there must be something fundamental about the Hurd's
> architecture I don't understand. Why shouldn't it be possible to
> just do this:
>
> # settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a u.v.w.x -m ...
> # settrans /servers/socket/2 /hurd/pfinet -i eth1 -a u.v.y.z -m ...
>
> to configure multiple 'net interfaces? This is (more of less) the
> way I'd do it in some flavor *nix. Thanks :^)
Because if a program opens a socket, it can only ever talk to one of the two
tcp/ip stack servers.
What you want is
# settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a ... -i eth1 -a ...
Marcus
--
`Rhubarb is no Egyptian god.' GNU http://www.gnu.org marcus@gnu.org
Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/
Marcus.Brinkmann@ruhr-uni-bochum.de
http://www.marcus-brinkmann.de/