HI,
I have installed Redhat 5.3 i had same issue so changed to Centos still i have the same issue which is described below.
When i do the ping there is no problem when i do traceroute to my local router i have a packet loss .We have changed from eht0 to eth4 still no luck all have same problem.IF we connect a windows machine there is no packet loss on trace .Please help if anyone know what is the issue if know please



dmesg | grep eth3
eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem dc000000, IRQ 122, node addr 0024e833498a
bnx2: eth3: using MSIX
ADDRCONF(NETDEV_UP): eth3: link is not ready
bnx2: eth3 NIC Copper Link is Up, 100 Mbps half duplex
ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
eth3: no IPv6 routers present
bnx2: eth3: using MSIX
ADDRCONF(NETDEV_UP): eth3: link is not ready
bnx2: eth3 NIC Copper Link is Up, 100 Mbps full duplex, receive & transmit flow control ON
ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
eth3: no IPv6 routers present
bnx2: eth3: using MSIX
ADDRCONF(NETDEV_UP): eth3: link is not ready
bnx2: eth3: using MSIX
ADDRCONF(NETDEV_UP): eth3: link is not ready
bnx2: eth3: using MSIX
ADDRCONF(NETDEV_UP): eth3: link is not ready
bnx2: eth3 NIC Copper Link is Up, 100 Mbps full duplex, receive & transmit flow control ON
ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready
eth3: no IPv6 routers present


traceroute 87.236.138.33
traceroute to 87.236.138.33 (87.236.138.33), 30 hops max, 40 byte packets
1 87.236.138.177 (87.236.138.177) 0.917 ms 1.221 ms 1.435 ms
2 87.236.138.25 (87.236.138.25) 1.601 ms 1.833 ms 2.010 ms
3 87.236.138.33 (87.236.138.33) 1.556 ms * *

Thank you
Regards
Surender

Hi,

Welcome to LQ


In this case, the machine is up and responding, but for whatever reason it did not respond to the second and third packets. This does not necessarily indicate a problem; in fact, it is usually normal, and just means that the system discarded the packet for some reason. Many systems do this normally. These are most often computers, rather than dedicated routers.

It's important to remember that timeouts are not necessarily an indication of packet loss. This is a common misconception, but since there are only three probes, dropping one response is no big deal.

HI,
Thank you for the answer.Sir 3 87.236.138.33 (87.236.138.33) 1.556 ms * * is a Cisco Router and also 3 87.236.138.33 (87.236.138.25)is also a cisco Router how many times ever you do the trace route we get the same result.Please can you help
ThANK YOU

since ping works OK, there is no packetloss.