Meni Shapiro wrote:
On 10/27/05, *Kent West* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> 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.
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):
[EMAIL PROTECTED]:/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.
<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.
--
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
