LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (http://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Kernel updated, now Internet dead (http://www.linuxquestions.org/questions/linux-networking-3/kernel-updated-now-internet-dead-438908/)

dmorrell 04-26-2006 02:49 AM

Kernel updated, now Internet dead
 
I can connect to the Internet but not do anything since I updated the kernel from 2.6.15-1.1830_FC4 to 2.6.16-1.2096_FC4.

The problem might be that I can no longer see the domain name servers while the new kernel is in charge. However, there's a sting in the tail, as you will see right at the end of this message.

I've seen other posts referring to trouble with the Internet after upgrading the kernel to 2.6.16, but they have all related to problems communicating with a NIC via eth0. I'm using a modem on a serial port.

Help! What's going on?

Here's the guts of it.

The update was done via:

yum update kernel

The Yum config included the Livna repository, though I don't know if the new kernel came from there.

I connect via an ISP using a 56k dialup modem on a serial port. No changes were made there.

Here are the results of testing using the old and updated kernels.

I see a gateway at 202.173.204.247 with both kernels.

netstat -rn

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
202.173.204.247 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 lo
0.0.0.0 202.173.204.247 0.0.0.0 UG 0 0 0 ppp0


I am being assigned an IP address dynamically with both kernels. Note the line in the following that says;

inet addr:202.173.206.81 P-t-P:202.173.204.247 Mask:255.255.255.255

/sbin/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:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4224 (4.1 KiB) TX bytes:4224 (4.1 KiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:202.173.206.81 P-t-P:202.173.204.247 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:9649 errors:1 dropped:0 overruns:0 frame:0
TX packets:8698 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:11363341 (10.8 MiB) TX bytes:833727 (814.1 KiB)


DNS is available with the old kernel but not the new one.

OLD:

nslookup www.abc.net.au
Server: 202.173.204.250
Address: 202.173.204.250#53

Non-authoritative answer:
Name: www.abc.net.au
Address: 203.2.218.61


NEW:

nslookup www.abc.net.au
;; connection timed out; no servers could be reached

When this happened I tried bypassing the DN servers and connecting directly to a web server via its IP address.

OLD:

Typed http://66.102.7.104/ into the address bar and got Google.

NEW:

Same process and got a 'can't connect' timeout.
___________________________
Regards,

David Morrell

squallabc 04-26-2006 03:40 AM

Your /etc/resolve.conf is right?


All times are GMT -5. The time now is 03:56 PM.