>
> Thomas David Rivers wrote:
> >
> > To add more to this - tracing through in.c in the kernel,
> > I see that when you configure an interface it eventually
> > works its way down to rtrequest - to add a route for
> > the new interface.
> >
> > I believe rtrequest() is the one returning EEXIST
Thomas David Rivers wrote:
>
> To add more to this - tracing through in.c in the kernel,
> I see that when you configure an interface it eventually
> works its way down to rtrequest - to add a route for
> the new interface.
>
> I believe rtrequest() is the one returning EEXIST which is
> what cau
To add more to this - tracing through in.c in the kernel,
I see that when you configure an interface it eventually
works its way down to rtrequest - to add a route for
the new interface.
I believe rtrequest() is the one returning EEXIST which is
what causes ifconfig on sl0 to always complain "Fil
>
>
> I don't seem to be able to get 3.2 to do a SL/IP
> install (this is for a laptop which seems to be
> having PAO problems...)
>
> Turning on DEBUG in the install options, I can watch
> it nicely execute:
>
> ifconfig sl0 inet 10.0.0.98 10.0.0.99 netmask 255.255.255.0
>
> but - not matter
I don't seem to be able to get 3.2 to do a SL/IP
install (this is for a laptop which seems to be
having PAO problems...)
Turning on DEBUG in the install options, I can watch
it nicely execute:
ifconfig sl0 inet 10.0.0.98 10.0.0.99 netmask 255.255.255.0
but - not matter what - that always seems
5 matches
Mail list logo
