tcpdump works outside the interfaces so you could run tcpdump on your LAN and WAN interfaces at the same time and capture the packets to file. You should then be able to do a 1-to-1 match between the interfaces for both outgoing and incoming interfaces.
[edit]
Remember pings use ICMP tather than TCP or UDP
[/edit]

It is possible also to log firewall messages but there is no point going down that route unless the tcpdump shows packets being dropped between the interfaces.

BTW, if you upgrade the NIC driver, unless you're good at the command line, you need to reboot the server for the change to take effect.

My switch shows no errors on the port.

I changed the LAN interface of the clearOS box to another port on the card and the result is the same. The WAN/Internet interface is also on the same card. It is a 4 port Intel NIC.

I've attached a ping plot graph of pinging another host on my network. Ping plotter is on the same host in both cases, both he nas and clearOS are connected to the same switch. I've also tried swapping cables and switch ports. Literally the only packet loss I see anywhere on my network is tot he LAN nterface of clear OS.

I've also attached a graph of ping plotting google DNS.

Nick Howitt wrote:

You only want the e1000e driver. The other is completely different.

If ping plotter shows the issue to the LAN interface, doesn't that rule out a ClearOS routing issue? Are your NIC's standalone or on the motherboard? Can you check any switches and cables on the LAN between the workstation and ClearOS?

You only want the e1000e driver. The other is completely different.

If ping plotter shows the issue to the LAN interface, doesn't that rule out a ClearOS routing issue? Are your NIC's standalone or on the motherboard? Can you check any switches and cables on the LAN between the workstation and ClearOS?

Also, I can run a ping from the clear OS SSH shell to a well known internet server such as google's DNS at 8.8.8.8, and never see a drop. The drop only seems to happen from the LAN to Internet interface, indicating that there is some kind of issue with the ClearOS routing between the interfaces.

Nick Howitt wrote:

I'm not sure how to track the packet loss down, but there is a later ElRepo e1000e driver than is available in the kernel. I have it compiled here. You're welcome to try it.

Do you know what version should show up if is installed correctly? Also, are both RPM's needed or just the one with e1000 in the name?

Thanks,

I'm not sure how to track the packet loss down, but there is a later ElRepo e1000e driver than is available in the kernel. I have it compiled here. You're welcome to try it.