🚀 go-pugleaf

> > Sound like you're using a 2.2 kernel? I found when I installed
> > 2.2.3 that simply recompiling diald makes it use the tap
> > driver for listening for incoming packets rather than slip.
> > That driver seems to be fine in 2.2 but it doesn't accept
> > setting metric from ifconfig which diald seems to be hard
> > wired to do. I hacked those calls out and all seems to be
> > working fine.
> 
> Could you elaborate on this?  I was just about to jump into the 2.2.3
> kernel....and I rely on diald.

I downloaded diald 0.98.3 having read about some problems with
diald and 2.2. By default it builds to use tap instead of
the old slip approach. When diald is running I see:

$ ifconfig tap0
tap0      Link encap:Ethernet  HWaddr FE:FD:00:00:00:00  
          unspec addr:[NONE SET]  Bcast:[NONE SET]  Mask:[NONE SET]
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:576  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          Interrupt:5 

[not sure about that interrupt?]

The only problem I found was that diald calls ifconfig with metric which
the new kernel won't handle for the tap device.
I hacked the source to prevent this.

I built tap as a module so I need this in conf.modules:

alias tap0      ethertap
options tap0    -o tap0 unit=0
alias tap1      ethertap
options tap1    -o tap1 unit=0

You might be better off to stick with your version of diald using
slip and see if you have problems first. You don't need to lose
your old kernel and configs to do the upgrade, ie. you can
always go back until you sort out any problems (like lp0 and lp1
getting switched!).

--
Andrew