Early this week I decided it was time for a fresh install of my home server, I was doing some memory upgrades anyway and wanted to clean-up some structure issues I had created. I have come across an issue with the external interface not allowing traffic on the external IP interface. Can't ping can't dig. Tried switching to a different nic with no resolution. Stopping Syswatch temporarily resolved it until Syswatch upgraded last night. Now it won't work even with stopping syswatch. On both interface, it would connect and function with a DHCP address. I have verified that my Static Assignment information is correct and have verified the connection with a static IP using my laptop so it's not an ISP issue. Some search on here led me to this post and rolling back syswatch. After reading through the majority of this thread I also found a reference to this post in regards to issues with the R8169 module. The other nic I that had the same issue on another NIC on this system that uses the e1000e driver as well. Rebooting networking firewall provides no resolution and the logs aren't very detailed. I can confirm that this started last night when Syswatch was started by the upgrade. Stopping Syswatch after the upgrade didn't resolve the connection issue and that is when I switch nics.
I really don't have any good idea where to start in resolving this issue. Prior to reloading the OS everything was working perfectly.
I really don't have any good idea where to start in resolving this issue. Prior to reloading the OS everything was working perfectly.
Share this post:
Accepted Answer
I don't know of any problems with the r8169 module when used with an RTL8169 card. Check with:
It is not easy to downgrade ClearOS supplied rpm's as old ones are not kept in the repos. You may need to pick it up from the installation disk.
Note both threads you have picked up are old and relate to ClearOS 6.x.
lspci -k | grep Eth -A 3
It does not work well with an RTL8111/8168/8411 NIC and you should install the kmod-r168 and kmod-r1869 drivers with a:yum install kmod-r816*
Then reboot.It is not easy to downgrade ClearOS supplied rpm's as old ones are not kept in the repos. You may need to pick it up from the installation disk.
Note both threads you have picked up are old and relate to ClearOS 6.x.
Responses (3)
-
Accepted Answer
-
Accepted Answer
Nick Howitt wrote:
I don't know of any problems with the r8169 module when used with an RTL8169 card. Check with:
It does not work well with an RTL8111/8168/8411 NIC and you should install the kmod-r168 and kmod-r1869 drivers with a:lspci -k | grep Eth -A 3
Then reboot.yum install kmod-r816*
It is not easy to downgrade ClearOS supplied rpm's as old ones are not kept in the repos. You may need to pick it up from the installation disk.
Note both threads you have picked up are old and relate to ClearOS 6.x.
I did notice that, but it fits the bill. Even with the previous version of syswatch stopped I was having issues with both nic types. I do fall into the category of having the RLT8111/8168/8411. I was referencing the module and misspoke, lacked clarification of the actual type of cards.
output of lspci -k | grep Eth -A 3
03:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06)
Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port Gigabit Server Adapter
Kernel driver in use: e1000e
Kernel modules: e1000e
03:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06)
Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port Gigabit Server Adapter
Kernel driver in use: e1000e
Kernel modules: e1000e
04:00.0 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06)
Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port Gigabit Server Adapter
Kernel driver in use: e1000e
Kernel modules: e1000e
04:00.1 Ethernet controller: Intel Corporation 82571EB/82571GB Gigabit Ethernet Controller (Copper) (rev 06)
Subsystem: Hewlett-Packard Company NC364T PCI Express Quad Port Gigabit Server Adapter
Kernel driver in use: e1000e
Kernel modules: e1000e
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
Kernel driver in use: r8169
Kernel modules: r8169
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Subsystem: Acer Incorporated [ALI] Device 8000
Kernel driver in use: r8169
Kernel modules: r8169
-
Accepted Answer
My assumption is if I switch back to the e1000e nic, downgrade syswatch, and then stop syswatch it will start working properly. This would mean there is an issue with syswatch. If I switch to the R8169 nic, then reconfigure the module and it works I am good to go, but if it doesn't and downgrading and stopping syswatch fixes it, we then still have an issue with syswatch upgrade package.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »