[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: where does s10 come from in ifconfig?



<quote who="Gary Turner">

> sl0       Link encap:Serial Line IP
>          inet addr:192.168.0.1  P-t-P:192.168.0.2
>          Mask:255.255.255.0 UP POINTOPOINT RUNNING NOARP MULTICAST
>          MTU:1500  Metric:1 RX packets:0 errors:0 dropped:0
>          overruns:0 frame:0
>          TX packets:140 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:10
>          RX bytes:0 (0.0 b)  TX bytes:16574 (16.1 KiB)

while i haven't had this problem, so this is more of
a generic answer. check your process table for anything
that may be using the slip interface, if you can't find anything,
drop to single user mode, and see if sl0 goes away, if it
does, check /lib/modules/`uname -r`/ to see if you can find
a slip module anywhere(assuming your running a modular
kernel, i am not ..), if you find one, a quick workaround
would be to unload the module(rmmod <module>) and move the
module out of there to somewhere else(/root ? ) so if something
tries to load and tries to load the slip driver to screw up
your networking config it won't be able to.

ifconfig sl0 down may do it too, you mentioned you did
ifdown -a (?) which from the looks of it only touches
interfaces in /etc/network/interfaces.

if all else fails, recompile your kernel without slip
supprot and there should be no way anything should be
able to bring up a slip interface ..

of course these are are all short term solutions ..but
they should get the job done ..

my most recent woody systmes are about 2 weeks old, and
i haven't had any issues like this on them(i have SLIP
compiled into the kernel)

hope this helps ......

nate





Reply to: