Matt Zagrabelny wrote: >On Mon, 2005-10-24 at 07:52 -0500, Kent West wrote: > > >>I just upgraded my kernel to 2.6.8-2-k7; now my network is mostly broken. >> >> > >what version were you running before? > > 2.6.3-1-k7
> > >>I can access another box on the local home LAN (ping, ssh, sftp, etc), >>but I can't ping or otherwise get to my USRobotics wired/wireless router >>or beyond. >> >> > >so you can't ping the gateway? > >$ ping 192.168.123.254 > > Correct. I can not ping the gateway. >>I have firmcoded within the router the DHCP addresses given out to these >>boxes, which is why separated by such a large gap, and which indicates >>that the broken box is getting dhcp information from the router. >> >> > >if your broken box is getting dhcp leases from the router then i would >think you could ping the gateway (as mentioned above). > > I would think so also. >what does your routing table look like? > ># route -n > > [EMAIL PROTECTED]:~$ sudo route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.123.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.123.254 0.0.0.0 UG 0 0 0 eth0 Because I wanted to rearrange my partitions, I wiped the drive completely and did a completely new install of Sid. With the 2.4.25-1-386 kernel I started out with on the Sid netinstaller, networking worked fine. I've built the box up to a point close to what it was before the rebuild, and then ugpraded the kernel again to 2.6.8-2-k7, and the networking again fails to work, in exactly the same way I described earlier. I'm confident that I can reboot into the 2.4 kernel and get my network back, but I'd like to stick with the 2.6 kernel if anyone can help me figure out what I need to do to fix my networking. Thanks! -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
