I don't know what going here Philip....
I have the DIALD 99.x running on RH6.1 System
with the 2.2.13 Kernel. It is using a SLIP Connection.
I have my Kernel built with PPP, SLIP, PLIP, and
EtherTap as Modules. I am not experiencing the
problems you are seeing.
I think there must be something wrong in your
Slackware Network Configuration Settings.
I currently don't have a System running Slackware
7.0 (I currently have a SL4.0 System, with Kernel
2.2.6, but not with DIALD), but I might be able to
configure a System next week. You might query
the DIALD List for others running SL7.0 with
DIALD 99.x.
Jeff
----- Original Message -----
From: Philip Wall <[EMAIL PROTECTED]>
To: Robert C. Paulsen, Jr. <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Saturday, December 11, 1999 3:43 PM
Subject: Re: SIOCSIFMETRIC
> 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]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
