|
Networking issues with 2.6.3 Kernel
I recently upgraded to the 2.6.3 kernel and have run into an interesting problem.
When get into the GUI and try to load a Web page, it resolves the address and begins to connect. Eventually it'll time out. It does the same thing in Lynx through the terminal.
I've been able to ping both DNS and IP addresses via terminal without any problems, including the gateway and DNS addresses assigned to the system.
I've turned off Kudzu and rebooted the system to make sure that wasn't part of the issue. I've also manually restarted networking using the following command:
/etc/rc.d/init.d/network restart
I'm just at a loss as to what this problem could be.
Here's the info on my system:
Fedora Core 1 using Kernel 2.6.3, based off of the .config file available from the RedHat 2.6.3 kernel RPM. The only adjustments I've made to the RPM kernel is to enable NTFS support and compile all network modules directly into the kernel instead of loading as a module.
The RedHat RPM kernel also had the exact same problem. This is why I chose to compile in all the modules to see if I would experience the same issue.
My Ethernet card info is as follows:
00:09.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
Subsystem: Kingston Technologies: Unknown device f002
Flags: bus master, medium devsel, latency 32, IRQ 10
I/O ports at d000 [size=256]
Memory at e7000000 (32-bit, no prefetchable) [size=256]
Expansion ROM at <unassigned> [disabled] [size=256]
My network card uses the Tulip module. As a test, I've tried changing the hardware type on the card to other cards that also use the Tulip module. No luck on any of these. I've also tried using other modules to see if any of them will work, no go here either.
Some other things to note:
If I reboot my system and choose the 2.4.x kernel, I can get into Linux and networking works as it should. This only happens when I boot into the 2.6.3 kernel.
I can navigate to IP addresses internally in my home network via the Web browser, so the network is partially working. I can also navigate to other machines via Samba.
I'm not running a firewall on this machine.
I get no errors when using /sbin/ifup eth0.
I do have the hostname, primary and secondary DNS, and DNS search path filled out with their proper values. I have reset these values to make sure nothing has changed on my ISP's end. They're always re-assigned the same.
There are no proxies or anything enabled on the machine, nor does my ISP require a proxy.
I don't have a spare network card to try out, but the NIC in this machine is only a month and a half old. I don't think that it's a bad NIC, otherwise Windows and the 2.4.x kernel would be having fits too.
Some other thoughts:
Does the 2.6.x kernel come with a built in firewall that is turned on by default? This machine acts as if the network ports are blocked. This is the only thing that I can think of since it seems that everything else internallly seems to be working properly.
Any thoughts would be greatly appreciated in this very frustrating experience.
|
