On Wed, 23 Jan 2002 20:42:59 -0800 (PST), nate wrote: ><quote who="Gary Turner"> >
> >while i haven't had this problem, so this is more of >a generic answer. check your process table for anything see my addendum--found suspicious characters in /proc/modules >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 it's there, 'slip.o' >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. I think I avoided this. See below. > >ifconfig sl0 down may do it too Yes, that worked. ifdown s10 did not. > >hope this helps ...... > >nate It did, very much. Thanks. >From Donald R Spoon >Take a look and see if the "diald" pacakge is installed. (dpkg -l diald) > If I recall correctly, diald would create a "psuedo" serial interface >called s10 to monitor network traffic and then initiate a modem dial-out >if it detected a packet destined for outside the LAN. Since you have >DSL with a working router, you really don't have any need for diald. I >would just remove it. Went to dselect, found it and one or two other unneeded apps and purged 'em. The routes and interfaces cleaned up nicely. Had to reboot to make it work, but now I'm back on line. (As I think about it there's probably a way to rerun init's or something.) Thanks to both of you, Don and Nate, for your help. I'm getting closer to the day the Linux box can actually start doing honest work. gt Yes I fear I am living beyond my mental means--Nash
