That makes sense but doesn't really explain why diald is starting 2
sl0 interfaces and won't bring the link up. Should I be using the
ethertap interface with this kernel? Or just hunt down the older
diald?
On 11 Dec 99, at 8:16, Robert C. Paulsen, Jr. wrote:
> Philip Wall wrote:
> >
> > Anyone explain where this error is coming from?
> >
> > Dec 11 02:15:34 wildcard diald[1104]: start sl0: SIOCSIFMETRIC:
> > Operation not supported
> >
>
> The answer is that it's not an error. It's just a statement of fact.
>
> >From an earlier posting by Mike Jagdis (diald author/maintainer):
>
> ==================================================================
> SIOCSIFMETRIC is generated when diald invokes ifconfig passing
> it a "metric" option. Diald does this in the vague hope that it
> may be running on a kernel that supports interface metrics. If it
> is the metric will be set on the interface so it is there for
> things like routed that might be paying attention. Interface
> metrics have been dropped from more recent Linux kernels.
>
> SIOCADDRT is generated when diald invokes route to add routes
> through an interface. Diald does this because older kernels
> needed routes to be set up by hand. Newer kernels automatically
> create routes when interfaces are configured - hence the EEXISTS
> error when diald tries.
>
> It's simply easier to try these things and get some noise if
> they weren't actually needed than it is to try and work out if
> we even need to try them :-).
> ==================================================================
>
> --
> ____________________________________________________________________
> Robert Paulsen http://paulsen.home.texas.net
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
