Do you have iptables running? That could be preventing the replies.
What does /var/log/messages say when you attempt the pings?
I have an intel pro 1000 mt nic installed using Red Hat 2.6.9-42.0.3.EL. When pinging from another machine , I can see that it receives the packets but it is not transmitting. This is on a private network. here is the routing table of the machine that cannot transmit. Built and loaded the module with the default settings...
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth1
where eth0 is the interface...
output from ifconfig
eth0 Link encap:Ethernet HWaddr 00:07:E9:0F:70:FF
inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::207:e9ff:fe0f:70ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:69 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:6762 (6.6 KiB) TX bytes:0 (0.0 b)
Base address:0xa800 Memory:df000000-df020000
The issue appeared to be the pci slot it was in, which I'm assuming it was the irq preventing it to work correctly. Put it in another slot and it now transmits, BUT .... I can't get it to communicate with the system on the other end at 1000 Mb/s ... software says both are at 1000 Mb/s but the light on one of them is green while the other is yellow meaning 100 Mb/s and 1000 Mb/s. both are attached to a non managed linksys gigabit switch.... I'm stumped... I've tried forcing it to 1000 Mb/s which does change the lights to both yellow but then the software states one is at 100 Mb/s and the other is at 1000 Mb/s....
Have you tried forcing it with ethtool or mii-tool ?
Perhaps your ether cable isn't truely a cat6...
Don't worry Ma'am. We're university students, - We know what We're doing.
'Ruiat coelum, fiat voluntas tua.'Datalogi - en livsstil; Intet liv, ingen stil.
I suggest you try shutting down the packet filter. the packets are being received but dropped on the interface.
# pfctl -d
and see the outcome.
We had a similar problem on a secondary network interface. The issue turned out to be a bridged module built into the kernel. You can see if a bridge is enabled by using lsmod. If so, use modeprobe -vr bridge and then reboot.