Sorry for the delay (I've been away for 2 weeks).
As Ben pointed out, the act of opening the /dev device is the key -
specifically, the if_attach() called from tuncreate() called from
tunopen() does some permanent damage^Wgood.
I don't think ifconfig really has a chance of doing the right thin
On Thu, 27 Jul 2000 09:37:11 +0200, Poul-Henning Kamp wrote:
> > ifconfig tun0 inet 10.0.0.1
>
> I think you are seing the "interesting" side effect of the BSD
> concept of "POINT2POINT" lines.
I think that's anotehr issue. Once I'd read 0 bytes from /dev/tun0 with
dd(1), I was able to d
In message <[EMAIL PROTECTED]>, Sheldon Hearn writes:
>
>On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote:
>
>> Does this have anything to do with your recent change to if_tun.c?
>
>Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists.
>Someone locally insists that the ifcon
On Wed, 26 Jul 2000 16:26:48 +0100, Ben Smithurst wrote:
> I think the device needs to be opened before you can do anything with
> it. PPP of course does this for you, but if you want to ifconfig it
> yourself you might try something like ``dd if=/dev/tun0 of=/dev/null
> count=0'' first.
Ah,
Sheldon Hearn wrote:
> On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote:
>
>> Does this have anything to do with your recent change to if_tun.c?
>
> Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists.
> Someone locally insists that the ifconfig line
>
> ifconfig
On Wed, 26 Jul 2000 12:33:07 +0200, Sheldon Hearn wrote:
> Does this have anything to do with your recent change to if_tun.c?
Nope. I've reverted rev 1.75 of if_tun.c and the behaviour persists.
Someone locally insists that the ifconfig line
ifconfig tun0 inet 10.0.0.1
should work.
Hi Brian,
Does this have anything to do with your recent change to if_tun.c?
Ciao,
Sheldon.
Script started on Wed Jul 26 12:28:35 2000
# pwd
/root
# date
Wed Jul 26 12:28:39 SAST 2000
# uname -a
FreeBSD axl.ops.uunet.co.za 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Jul 26 12:01:00
SAST 2000