Nerijus wrote:
> Hello,
>
> I've setup diald 0.99 on RedHat 6 intel machine and it works,
> but I get some errors in /var/log/messages.
snip
>
> Jun 9 15:52:43 server diald[958]: start sl0: SIOCSIFMETRIC: Operation not
> supported
> Jun 9 15:52:43 server diald[958]: start sl0: SIOCADDRT: File exists
> Jun 9 15:52:43 server diald[958]: start sl0: SIOCADDRT: File exists
snip
>
> Jun 9 15:54:25 server diald[958]: start ppp0: SIOCSIFMETRIC: Operation not
> supported
>
> What do these errors mean?
These errors come from 'route add...' commands, which are issued from
/etc/rc.d/init.d/network and /etc/sysconfig/network-scripts/ifup scripts at
boot-up. Specifically, look at this portion of the /etc/rc.d/init.d/network
script:
for i in $interfaces; do
./ifup $i boot
done
Here, /etc/sysconfig/network-scripts/ifup either tries to add a route, or calls
/etc/sysconfig/network-scripts/ifup-$i (if it exists) which tries to add a
route.
These 'route add ...' commands are fed parameters from the ifcfg-ppp0,
ifcfg-eth0, etc files. The parameters are probably wrong, but either the
resultant errors don't have much practical effect (eg, I suspect the
SIOCSIFMETRIC related error is one of these), or they get corrected later on
when diald or pppd is invoked.
I have a suspicion that this is why so many apparently redundant or spurious
routes appear in the routing tables after upgrading to kernel 2.2.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
