On Wed, 23 Jan 2002 10:54:04 -0600, Gary Turner wrote: > >Will somebody please come forward and point out whatever stupid thing I >did to get here. Then please show me the simple way home.
<cut a bunch here> >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) > <cut interfaces> >Kernel IP routing table >Destination Gateway Genmask Flags Metric Ref Use Iface >192.168.0.2 * 255.255.255.255 UH 1 0 0 sl0 >192.168.0.0 * 255.255.255.0 U 0 0 0 sl0 >192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 >default 192.168.0.1 0.0.0.0 UG 0 0 0 sl0 >default * 0.0.0.0 U 1 0 0 sl0 > Some more info. This Serial Line Internet Protocol from Linux NET2. It's used for dial-up connection by modem. I will enable a modem connection when I've upgraded the kernel for USR 3CP5610A support--but not yet. Even so, this does not look like a valid interface configuration. Where did it come from? Below is the /proc/modules file. nls_cp437 3896 2 (autoclean) vfat 9008 1 (autoclean) slip 7424 2 (autoclean) <<---- slhc 4436 1 (autoclean) [slip] <<---- af_packet 6048 1 (autoclean) <<--?? lockd 31100 0 (autoclean) sunrpc 52420 0 (autoclean) [lockd] serial 19564 0 (autoclean) <<--?? eepro100 15644 0 tulip 29860 1 unix 10212 10 (autoclean) Arrows point to possible villains. tulip and eepro100 are the only modules in /etc/modules. I think I know what's doing the damage. I don't know why it's doing what it does, where the offending files are, or how to fix it. Well, I do suspect /etc/rc*.d/, but can't pin it down--may be buried in something else? I'm hurtin' here folks, please help. gt Yes I fear I am living beyond my mental means--Nash
