Can't net to router or beyond
Kent West
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.
I can ssh to the other box in the LAN, and run a web browser remotely
and get to the router and beyond, so I know the problem is in this box,
not the router.
I suspected it was perhaps an IPV6 thing, so I disabled the loading of
that module by changing /etc/modprobe.d/aliases:
#alias net-pf-10 ipv6
alias net-pf-10 off
Now after a reboot the IPV6 module no longer shows up in the output of
"lsmod".
But the problem remains.
Here's the contents of /etc/network/interfaces:
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
>
> # The loopback interface
> # automatically added when upgrading
> auto lo
> iface lo inet loopback
>
> # The first network card - this entry was created during the Debian
> installation
> # (network, broadcast and gateway are optional)
> # automatically added when upgrading
> auto eth0
> #iface eth0 inet static
> # address 192.168.123.2
> # netmask 255.255.255.0
> # network 192.168.123.0
> # broadcast 192.168.123.255
> # gateway 192.168.123.254
>
> iface eth0 inet dhcp
If I switch to the static numbers above and comment out the dhcp, and
restart networking, the problem still remains.
Here's the output of "ifconfig" (using the dhcp entry above):
> enjae[westk]:/home/westk> sudo ifconfig
> eth0 Link encap:Ethernet HWaddr 00:02:E3:06:C0:7B
> inet addr:192.168.123.108 Bcast:192.168.123.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:34933 errors:4 dropped:0 overruns:0 frame:0
> TX packets:37894 errors:1 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:18638456 (17.7 MiB) TX bytes:15615368 (14.8 MiB)
> Interrupt:11 Base address:0xec00
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:124 errors:0 dropped:0 overruns:0 frame:0
> TX packets:124 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:11905 (11.6 KiB) TX bytes:11905 (11.6 KiB)
For comparison, here's the output of "ifconfig" on the other box on the
LAN (through which I'm ssh'd and running Thunderbird remotely to write
this email):
> westk[@westk03]:/home/westk> sudo ifconfig
> Password:
> eth0 Link encap:Ethernet HWaddr 00:00:E8:11:83:F7
> inet addr:192.168.123.176 Bcast:192.168.123.255
> Mask:255.255.255.0
> inet6 addr: fe80::200:e8ff:fe11:83f7/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:6188511 errors:66 dropped:0 overruns:0 frame:66
> TX packets:4477232 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:3419924488 (3.1 GiB) TX bytes:457839904 (436.6 MiB)
> Interrupt:5 Base address:0xd000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:118589 errors:0 dropped:0 overruns:0 frame:0
> TX packets:118589 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:80098696 (76.3 MiB) TX bytes:80098696 (76.3 MiB)
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.
I'd drop back to my earlier kernel, except my / partition is too small
to hold more than one kernel at a time, so I killed the /lib/modules for
that older kernel to make room for the new kernel. (Seems like the old
idea of having a smallish root partition bit me; more recently I've been
moving to a partition size of about 500MB to avoid this sort of problem,
but on this box, / is only 183MB, with 15MB free. I'm eventually going
to have to rearrange partitions (ouch!), but not today, if I can help it.)
Thanks for any help in getting my network back up!
--
Kent
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Matt Zagrabelny
> I just upgraded my kernel to 2.6.8-2-k7; now my network is mostly broken.
what version were you running before?
>
> 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
<snip>
> 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).
what does your routing table look like?
# route -n
-matt zagrabelny
Kent West
>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
>
>
westk@enjae:~$ 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
Kent West
>>>I just upgraded my kernel to 2.6.8-2-k7; now my network is mostly broken
>>>
westk@enjae:~$ sudo ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:157 errors:0 dropped:0 overruns:0 frame:0
TX packets:157 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12757 (12.4 KiB) TX bytes:12757 (12.4 KiB)
westk@enjae:~$ sudo /etc/init.d/networking start
* /etc/network/options is deprecated.
Setting up IP spoofing protection...done (rp_filter).
Configuring network interfaces...ifup: interface lo already configured
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth0/00:02:e3:06:c0:7b
Sending on LPF/eth0/00:02:e3:06:c0:7b
Sending on Socket/fallback/fallback-net
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.123.254
bound to 192.168.123.108 -- renewal in 3599400 seconds.
done.
westk@enjae:~$ ping 192.168.123.254
PING 192.168.123.254 (192.168.123.254) 56(84) bytes of data.
>From 192.168.123.108 icmp_seq=1 Destination Host Unreachable
>From 192.168.123.108 icmp_seq=2 Destination Host Unreachable
>From 192.168.123.108 icmp_seq=3 Destination Host Unreachable
--- 192.168.123.254 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5000ms
, pipe 3
westk@enjae:~$ ping 192.168.123.176
PING 192.168.123.176 (192.168.123.176) 56(84) bytes of data.
64 bytes from 192.168.123.176: icmp_seq=1 ttl=64 time=0.205 ms
64 bytes from 192.168.123.176: icmp_seq=2 ttl=64 time=0.167 ms
64 bytes from 192.168.123.176: icmp_seq=3 ttl=64 time=0.168 ms
--- 192.168.123.176 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.167/0.180/0.205/0.017 ms
Matt Zagrabelny
> >>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.
what kernel is the other box that can "see" the outside world running?
also is ipv6 tromping on anything?
have you thought about rolling your own kernel?
what is the output of lsmod?
-matt zagrabelny
Kent West
>>>>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.
>>>>
>>>>
>
>what kernel is the other box that can "see" the outside world running?
>
>
>
westk[@westk03]:/home/westk> uname -a
Linux westk03 2.6.11-1-k7 #1 Mon Jun 20 21:26:23 MDT 2005 i686 GNU/Linux
>also is ipv6 tromping on anything?
>
>
I don't know. I googled for how to disable ipv6, and accordingly, on the
box that can't see beyond the router, changed /etc/modprobe.d/aliases:
#alias net-pf-10 ipv6
alias net-pf-10 off
Even after a reboot this made no difference in the behaviour.
>have you thought about rolling your own kernel?
>
>
Yes. But stock kernels usually work fine for me, and I'm surprised this
one doesn't. In the meanwhile, I've rebuilt the box to rearrange
partitions, and in the process have made it possible for me to drop back
to a 2.4 kernel which is working.
>what is the output of lsmod?
>
>
Can't get to that machine at the moment (must not have enabled ssh
incoming yet). I'll post it later.
--
Kent
Meni Shapiro
Matt Zagrabelny wrote:
>>>>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.
>>>>
>>>>
>
>what kernel is the other box that can "see" the outside world running?
Sorry to barge in on a thread like that, can you discribe your net and procedures been taken??
Meni
>
>
>
westk[@westk03]:/home/westk> uname -a
Linux westk03 2.6.11-1-k7 #1 Mon Jun 20 21:26:23 MDT 2005 i686 GNU/Linux
>also is ipv6 tromping on anything?
>
>
I don't know. I googled for how to disable ipv6, and accordingly, on the
box that can't see beyond the router, changed /etc/modprobe.d/aliases:
#alias net-pf-10 ipv6
alias net-pf-10 off
Even after a reboot this made no difference in the behaviour.
>have you thought about rolling your own kernel?
>
>
Yes. But stock kernels usually work fine for me, and I'm surprised this
one doesn't. In the meanwhile, I've rebuilt the box to rearrange
partitions, and in the process have made it possible for me to drop back
to a 2.4 kernel which is working.
>what is the output of lsmod?
>
>
Can't get to that machine at the moment (must not have enabled ssh
incoming yet). I'll post it later.
--
Kent
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
--
--
Meni Szapiro
Kent West
>
>
> On 10/27/05, *Kent West* <we...@acu.edu <mailto:we...@acu.edu>> wrote:
>
> Matt Zagrabelny wrote:
>
> >>>>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.
> >>>>
> >>>>
> >
> >what kernel is the other box that can "see" the outside world
> running?
>
>
> Sorry to barge in on a thread like that, can you discribe your net and
> procedures been taken??
>
Here's most of my original post:
------
<Start of Original Post>
I just upgraded my kernel to 2.6.8-2-k7; now my network is mostly broken.
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.
I can ssh to the other box in the LAN, and run a web browser remotely
and get to the router and beyond, so I know the problem is in this box,
not the router.
I suspected it was perhaps an IPV6 thing, so I disabled the loading of
that module by changing /etc/modprobe.d/aliases:
#alias net-pf-10 ipv6
alias net-pf-10 off
Now after a reboot the IPV6 module no longer shows up in the output of
"lsmod".
But the problem remains.
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.
<End of Original Post>
----
If I drop back to a 2.4 kernel, networking works fine.
I was planning to send the output of "lsmod" while booted into the 2.6 kernel, but haven't gotten to it yet.
we...@acu.edu
From: Meni Shapiro
> so...you got 2 machines on the same subnet which is: 192.168.123.x
> You are using a DHCP server from your router.
> I guess the router address is the gateway address which is:
> 192.168.123.254??
> and you are using a class C netmask...255.255.255.0...
>
> ok...
> So lets call machine A the one with the problem and machine B
> the one 'ok'.
> Can you ping from B to A??
No. I can ping (ssh, etc) from A to B, but not from B to A.
> Can you post the route tables of A??
I'm on unfamiliar territory here; I ran "route -v" and got these results:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.123.254 0.0.0.0 UG 0 0 0 eth0
> Are you running iptables??
Again, I'm on unfamiliar territory. I'm not sure one way or the other. This is what I get with the 2.4 (working) kernel:
westk@enjae:~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
I'll have to reboot to get the output for the 2.6 kernel (which I'll do later). But it's a stock kernel, so unless iptables is something that's turned on within the kernel itself, I imagine the results will be similar.
Earlier I was asked for the output of "lsmod" while booted into the 2.6 non-working kernel; here it is:
Module Size Used by
af_packet 22600 2
uhci_hcd 32784 0
usbcore 118308 3 uhci_hcd
via82cxxx_audio 30280 0
uart401 11844 1 via82cxxx_audio
sound 83372 2 via82cxxx_audio,uart401
soundcore 10400 2 via82cxxx_audio,sound
ac97_codec 18700 1 via82cxxx_audio
tulip 46880 0
dm_mod 59644 0
rtc 12728 0
capability 4616 0
commoncap 7296 1 capability
ide_cd 42528 0
cdrom 40284 1 ide_cd
ext3 126760 6
jbd 61848 1 ext3
mbcache 9284 1 ext3
ide_generic 1472 0
via82cxxx 13980 1
ide_disk 19264 8
ide_core 138724 4 ide_cd,ide_generic,via82cxxx,ide_disk
sd_mod 21696 0
ata_piix 8132 0
libata 41412 1 ata_piix
scsi_mod 124812 2 sd_mod,libata
unix 28660 0
font 8448 0
cfbcopyarea 3840 0
cfbimgblt 3072 0
cfbfillrect 3712 0
I've about decided the 2.6.8-2-k7 is just horribly broken. The networking issues are the only thing I've posted about, but I have several issues when booted into this kernel. (psmouse not loading, therefore no mouse, video in console changing to hard-to-read light gray during boot-up, fbset garbling the console screen beyond recognition, sound being scratchy, etc). I'd try a different 2.6 kernel, but there doesn't seem to be another suitable k7-optimized stock kernel available (which surprises me, because I thought the debian repositories tended to have several versions available):
westk@enjae:~$ cat /etc/apt/sources.list
deb http://mirrors.kernel.org/debian/ unstable main contrib non-free
deb http://mirrors.kernel.org/debian/ stable main contrib non-free
deb http://security.debian.org/ stable/updates main contrib non-free
westk@enjae:~$ sudo aptitude search kernel-image-2.6
v kernel-image-2.6 -
p kernel-image-2.6-386 - Linux kernel 2.6.12 image on 386-class machines - trans
p kernel-image-2.6-686 - Linux kernel 2.6 image on PPro/Celeron/PII/PIII/P4 mach
p kernel-image-2.6-686-smp - Linux kernel 2.6 image on PPro/Celeron/PII/PIII/P4 SMP
p kernel-image-2.6-amd64-generic - Linux kernel image for version 2.6 on generic x86_64 sy
p kernel-image-2.6-amd64-k8 - Linux kernel image for version 2.6 on AMD64 systems
p kernel-image-2.6-amd64-k8-smp - Linux kernel image for version 2.6 on AMD64 SMP systems
p kernel-image-2.6-em64t-p4 - Linux kernel image for version 2.6 on Intel EM64T syste
p kernel-image-2.6-em64t-p4-smp - Linux kernel image for version 2.6 on Intel EM64T SMP s
p kernel-image-2.6-k7 - Linux kernel 2.6 image on AMD K7 machines - transition
p kernel-image-2.6-k7-smp - Linux kernel 2.6 image on AMD K7 SMP machines - transit
p kernel-image-2.6.8-11-amd64-generic - Linux kernel image for version 2.6.8 on generic x86_64
p kernel-image-2.6.8-11-amd64-k8 - Linux kernel image for version 2.6.8 on AMD64 systems
p kernel-image-2.6.8-11-amd64-k8-smp - Linux kernel image for version 2.6.8 on AMD64 SMP syste
p kernel-image-2.6.8-11-em64t-p4 - Linux kernel image for version 2.6.8 on Intel EM64T sys
p kernel-image-2.6.8-11-em64t-p4-smp - Linux kernel image for version 2.6.8 on Intel EM64T SMP
p kernel-image-2.6.8-2-386 - Linux kernel image for version 2.6.8 on 386.
p kernel-image-2.6.8-2-686 - Linux kernel image for version 2.6.8 on PPro/Celeron/PI
p kernel-image-2.6.8-2-686-smp - Linux kernel image for version 2.6.8 on PPro/Celeron/PI
i kernel-image-2.6.8-2-k7 - Linux kernel image for version 2.6.8 on AMD K7.
p kernel-image-2.6.8-2-k7-smp - Linux kernel image for version 2.6.8 on AMD K7 SMP.
I don't really want to roll my own; I'd just as soon stick with 2.4 than do that.
If anyone wants to help beat this problem into submission, I'd be glad to continue on; it'd be a good education. But if not, don't worry about it; like I say, I'll just stick with 2.4 until another 2.6-k7 version makes it into the repositories, or until I need to move to 2.6 for some reason, at which time I may reconsider compiling my own.
(Just for the record; this all started when an upgrade to x.org broke my older ATI TV card playback; it used to be that whenever an upgrade of xserver-xfree86 hosed my playback, I could just drop in the ATI.2 drivers from GATOS and restart X; apparently the move to x.org broke something there. I thought I'd try an upgrade to a 2.6 kernel to see if that made any difference; it did, but in the wrong direction. D'oh!)
Thanks!
--
Kent
Meni Shapiro
(Writing from webmail, as my ISP's IMAP server is sick, so apologies for any formatting/etc issues.)
From: Meni Shapiro
> so...you got 2 machines on the same subnet which is: 192.168.123.x
> You are using a DHCP server from your router.
> I guess the router address is the gateway address which is:
> 192.168.123.254??
> and you are using a class C netmask...255.255.255.0...
>
> ok...
> So lets call machine A the one with the problem and machine B
> the one 'ok'.
> Can you ping from B to A??
No. I can ping (ssh, etc) from A to B, but not from B to A.
> Can you post the route tables of A??
I'm on unfamiliar territory here; I ran "route -v" and got these results:
Try :
$route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.123.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.123.254 0.0.0.0 UG 0 0 0 eth0
> Are you running iptables??
Again, I'm on unfamiliar territory. I'm not sure one way or the other. This is what I get with the 2.4 (working) kernel:
try :
$ps -e |grep iptables
If you got a result then it is probably on, so try turn it off:
$/etc/init.d/iptables stop
What OS is it? i guess debian serge??
pls post /etc/hosts.allow /etc/hosts.deny here...
Meni
--
--
Meni Szapiro
we...@acu.edu
> On 10/29/05, we...@acu.edu wrote:
> > I'm on unfamiliar territory here; I ran "route -v" and got
> > these results:
>
>
>
> Try :
> $route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.123.254 0.0.0.0 UG 0 0 0 eth0
> try :
> $ps -e |grep iptables
> $/etc/init.d/iptables stop
This script does not exist.
>
> What OS is it? i guess debian serge??
> > westk@enjae:~$ cat /etc/apt/sources.list
> >
> > deb http://mirrors.kernel.org/debian/ unstable main contrib non-free
> > deb http://mirrors.kernel.org/debian/ stable main contrib non-free
> >
> > deb http://security.debian.org/ stable/updates main contrib non-free
> >
# /etc/hosts.allow: list of hosts that are allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example: ALL: LOCAL @some_netgroup
# ALL: .foobar.edu EXCEPT terminalserver.foobar.edu
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/portmap/portmapper.txt.gz for further information.
#
westk@enjae:~$ cat /etc/hosts.deny
# /etc/hosts.deny: list of hosts that are _not_ allowed to access the system.
# See the manual pages hosts_access(5), hosts_options(5)
# and /usr/doc/netbase/portmapper.txt.gz
#
# Example: ALL: some.host.name, .some.domain
# ALL EXCEPT in.fingerd: other.host.name, .other.domain
#
# If you're going to protect the portmapper use the name "portmap" for the
# daemon name. Remember that you can only use the keyword "ALL" and IP
# addresses (NOT host or domain names) for the portmapper. See portmap(8)
# and /usr/doc/portmap/portmapper.txt.gz for further information.
#
# The PARANOID wildcard matches any host whose name does not match its
# address. You may wish to enable this to ensure any programs that don't
# validate looked up hostnames still leave understandable logs. In past
# versions of Debian this has been the default.
# ALL: PARANOID
--
Kent
Meni Shapiro
2 more things though that i would like 2 c, if u don't mind...
$mii-tool
$ifconfig
Meni
--
Meni Szapiro