> No. These are normal on kernels that automatically create
> routes when you add an address to an interface. On other
> kernels they are necessary or you have no routes.
Um, I may be wrong about this, but at least on my box (LRP 2.9.4
running kernel 2.2.11 and iproute2), these errors were not always
innocuous. One of the problems diald had on my system was that
it did not install a new default route when ppp0 came up. When I
looked into the matter, it appeared the kernel was rejecting the new
ppp0 default route, because it conflicted with the already extant sl0
default route (hence the RTNETLINK error). When I patched diald
to follow the metric scheme described in the diald docs (e.g., proxy
link's metric is set to one greater than the real link's), this problem
(and error message) went away: apparently having a different
metric distinguishes the two default routes, as far as the kernel is
concerned.
Ed G.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
