Re: [Pengfork-devel] Tunnelling

[Nicolas Burrus]

On Friday 30 August 2002 02:10, Jean-Charles Salzeber wrote:
> On Fri, Aug 30, 2002 at 01:26, Nicolas Burrus wrote:
> > My tuntap drivers works fine in fact, pengaol can open tun0 interface by
> > /dev/net/tun, and I could with pengfork too :)
>
> Really? Is it *working* without being able to do an ifconfig!

In fact, to be able to do an ifconfig, a program must have opened 
/dev/net/tun, that's why it does not work if you just type ifconfig tun0 up, 
but if I have penfork running (and opening the file), no problem, ifconfig -a 
shows tun0.

> Vtun project, creators of the tun interface use ifconfig to setup the
> interface. It's quite portable. Pengaol use code (crouteurlinux.cpp) to
> setup the interface, it is very restricted to linux but I don't think it
> do more than ifconfig!
>
> I will try tomorrow and say more.
>
> > I've commited very little fixes in linux/tun.c, as I don't know if you
> > are working on it, in which case you can override my changes.
> >
> > I can work on linux tun driver, so that you can focus on openbsd driver
> > if you want.
>
> Currently, I have severals problem on OpenBSD:
>   * many random bytes are dropped, I don't know why!
>     As an example sometimes I send an ATDT... and because echo is
>     enabled I receive ATT... so the D has been dropped!
>     I will not say you what does it means on packet I receive from AOL %)
>     That's why I commited a change this morning to handle big
>     transmission errors.
>   * My tun fd seems in blocking mode even if I opened it with O_NONBLOCK.
>     It's obviously embarassing because it will wait until the buffer is
>     full!

Argh :(