Hi Lourdes,
may be there are cross connections to my problem I recently posted to this list
(please see below).
> > I just installed RH 6.1 on a new system. I'm trying to use Diald .16.3
> > (It's worked on every system since 4.0).
>
> Go to a minimum of diald 0.16.5 (and there's still a good chance of route
> problems). I'd recommend the 0.99.3 build (patched) from
> http://diald.sourceforge.net
>
> > Using the same config files as on my RH 5.2 system - I get
> > the following
> > problems:
> >
> > 1. route dies with an error - crashing diald.
>
> Welcome to the joys of kernel 2.2 routing. It's made some changes and diald
> doesn't always handle it properly.
Do you think that the mysterious error messages
Feb 21 01:08:33 terra diald[5048]: start sl0: SIOCSIFMETRIC: Operation not supported
Feb 21 01:08:34 terra diald[5048]: start sl0: RTNETLINK answers: File exists
Feb 21 01:08:34 terra diald[5048]: start sl0: RTNETLINK answers: File exists
Feb 21 01:08:34 terra diald[5048]: stop ppp0: RTNETLINK answers: No such process
Feb 21 01:08:34 terra diald[5048]: start sl0: SIOCSIFMETRIC: Operation not supported
Feb 21 01:08:34 terra diald[5048]: start sl0: RTNETLINK answers: File exists
Feb 21 01:08:34 terra diald[5048]: start sl0: RTNETLINK answers: File exists
could have something to do with this?
(posted already under thread "Can' get one bit over established connection";
sorry for posting this part twice, but it may be here the better place to ask this)
In particular:
- What operation is not supported?
- Which file already exists, a lock file?
The only thing that's clear to me is that no ppp0 was to kill (3rd line) as the
sl0 device has never been substituted by ppp0 (output of ifconfig was staying the
same).
An additional question to this:
is there a catalog available documenting the error messages of diald?
Regards
Tom
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
