🚀 go-pugleaf

Phill Edwards wrote:
> 
> When I do a dmesg I get these diald errors. I'm still trying to get
> diald to work. At the last count it wouldn't negotiate IP addresses.
> Then I sawthat my kernel had a slip thing in as a module and I'm not
> using modules so I recompiled. But now I get this and diald doesn't even
> attempt to dial any more.
> 
> Mar 18 22:49:21 oak diald[78]: Creating FIFO
> Mar 18 22:49:22 oak kernel: diald uses obsolete (PF_INET,SOCK_PACKET)
> Mar 18 22:49:22 oak diald[78]: Error on control fifo: Interrupted system
> call

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.

> -- Phill --

--
Andrew

diald requires slip, even if you use ppp for dialup

Phill Edwards (pedwards@mpx.com.au) wrote:
: When I do a dmesg I get these diald errors. I'm still trying to get
: diald to work. At the last count it wouldn't negotiate IP addresses.
: Then I sawthat my kernel had a slip thing in as a module and I'm not
: using modules so I recompiled. But now I get this and diald doesn't even
: attempt to dial any more.

: Mar 18 22:49:21 oak diald[78]: Creating FIFO
: Mar 18 22:49:22 oak kernel: diald uses obsolete (PF_INET,SOCK_PACKET)
: Mar 18 22:49:22 oak diald[78]: Error on control fifo: Interrupted system
: call

: Any ideas anyone? I'm starting to think the only cure it to scrap the
: machine and start again, this time with Red Hat instead of Debian.

: TIA,
: -- Phill --


--
/* George Durbridge  Melbourne, Victoria, Australia */
/* tel (03) 9280 3390            fax (03) 9280 3288 */

> 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.

> > 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

I upgraded my kernel to 2.2 and diald has never worked since. If you rely on
it I'd think twice before upgrading.
Regards,
-- Phill --