I've just finished another 18+ hour day. If this doesn't make sense. Send
me two aspirin and try again after Tuesday. :)
Hi Thom,
>
> Do you think that the mysterious error messages
>
> Feb 21 01:08:33 terra diald[5048]: start sl0:
> SIOCSIFMETRIC: Operation not supported
With kernel 2.2 adding the metric in this command no longer works. kernel
reports the fact that it did not do what you wanted it to. It did do
everything else to start the interface so you're fine.
> Feb 21 01:08:34 terra diald[5048]: start sl0: RTNETLINK
> answers: File exists
kernel 2.2+ now automatically create routes for interfaces. the file that
exists is the routing entry.
> Feb 21 01:08:34 terra diald[5048]: start sl0: RTNETLINK
> answers: File exists
same thing, sl0 is probably being brought up with a specific route for the
interface AND a net route as well (so you get 2 attempts at duplicate
routes).
> Feb 21 01:08:34 terra diald[5048]: stop ppp0: RTNETLINK
> answers: No such process
kernel 2.2+ now removes routes for downed interfaces
> 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
repeats of the above.
> 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)
These messages are so far harmless... they should not stop a connection.
What I don't see are configs and a complete log showing chat etc info.
You need to add 'debug' to pppd options, add '-v' to the chat command (if
that's how you are dialing)
Lourdes
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
