> Jeff Sheinberg writes:
JS> Perhaps I misunderstand what you mean by `dummy interface', but
JS> on my linux box, the `dummy interface' is a loopback, not a bit
JS> bucket.
Nope, it's a bit bucket. In your tests, you were contacting the local
host because 172.16.0.1 was your side of the
On Sun, Oct 01, 2000 at 05:14:48PM -0400, Jeff Sheinberg wrote:
> Marcus Brinkmann writes:
> [snip]
> > settrans /servers/socket/2 /hurd/pfinet -i dummy \
> > -a 192.168.0.1 -m 255.255.255.0 -g 192.168.0.2
> >
> > The dummy interface is the same as the dummy interface in
> > linux: A bottoml
On Sun, Oct 01, 2000 at 05:14:48PM -0400, Jeff Sheinberg wrote:
> Perhaps I misunderstand what you mean by `dummy interface', but on
> my linux box, the `dummy interface' is a loopback, not a bit
> bucket.
I used to use dummy interfaces on Linux for ethernet aliases before it
supported them, t
Marcus Brinkmann writes:
[snip]
> settrans /servers/socket/2 /hurd/pfinet -i dummy \
> -a 192.168.0.1 -m 255.255.255.0 -g 192.168.0.2
>
> The dummy interface is the same as the dummy interface in
> linux: A bottomless pit. You don't get a single packet out of
> i
Hi,
as an exercise, I implemented a dummy interface for pfinet. Apply the
attached diff, and compile pfinet. The interface name is "dummy".
settrans /servers/socket/2 /hurd/pfinet -i dummy -a 192.168.0.1 -m 255.255.255.0 -g
192.168.0.2
The dummy interface is the same as the dummy in
