So the NIC's are sending and receiving packets. What is the stack doing
('netstat -s')? My guess is that it's not doing the right thing with broadcast
packets. Do you have a resolv.conf file configured to do what you want? Maybe
it's not correct?
Cheers,
John
From: Jekels, Donny [mailto:[email protected]]
Sent: Wednesday, January 30, 2013 9:10 AM
To: Ronciak, John
Cc: [email protected]
Subject: Re: [E1000-devel] ARPING does not work
John,
The NIC works for TCP and UDP sessions however no broadcast and arp seems to
work.
we move IP's around between servers and part of this move is to garp the source
IP so the switches can update their mac tables.
without this functionality the NIC's are useless to us.
please help
root@postgres19:~# ethtool -S eth7
NIC statistics:
rx_packets: 11
tx_packets: 6
rx_bytes: 704
tx_bytes: 492
rx_broadcast: 11
tx_broadcast: 0
rx_multicast: 0
tx_multicast: 6
multicast: 0
collisions: 0
rx_crc_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 0
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_long_byte_count: 704
tx_dma_out_of_sync: 0
lro_aggregated: 0
lro_flushed: 0
lro_recycled: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
os2bmc_rx_by_bmc: 0
os2bmc_tx_by_bmc: 0
os2bmc_tx_by_host: 0
os2bmc_rx_by_host: 0
rx_errors: 0
tx_errors: 0
tx_dropped: 0
rx_length_errors: 0
rx_over_errors: 0
rx_frame_errors: 0
rx_fifo_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_queue_0_packets: 6
tx_queue_0_bytes: 468
tx_queue_0_restart: 0
rx_queue_0_packets: 11
rx_queue_0_bytes: 660
rx_queue_0_drops: 0
rx_queue_0_csum_err: 0
rx_queue_0_alloc_failed: 0
root@postgres19:~# ethtool -i eth7
driver: igb
version: 4.1.2
firmware-version: 1.6, 0x80000816
bus-info: 0000:04:00.3
root@postgres19:~# arping 10.11.12.13
ARPING 10.11.12.13
On Wed, Jan 30, 2013 at 11:05 AM, Ronciak, John
<[email protected]<mailto:[email protected]>> wrote:
Hi Donny,
Sorry to hear you are having problems. This most likely is not a NIC/driver
issue. Something is mostly not configured correctly on these systems. Did you
use ethtool to look at the HW stats of the interfaces you are trying to ping
out of? If not, please do so. Also, are each port/interface on a different
subnet? The stack does not do well (without extra configuration) with multiple
ports on the same subnet.
The reason Debian Squeeze doesn't have support is that they didn't pick up an
updated driver before they released it. This is not a problem with the Intel
drivers, it's a timing thing for Debian releases and how they update kernels
and drivers.
Cheers,
John
> -----Original Message-----
> From: Jekels, Donny [mailto:[email protected]<mailto:[email protected]>]
> Sent: Tuesday, January 29, 2013 8:35 PM
> To:
> [email protected]<mailto:[email protected]>
> Subject: [E1000-devel] ARPING does not work
>
> We have a handful of these Intel quad port NIC with the drive 4.1.7 and
> arping does not work on these NIC's.
>
> we run debian stock squeeze and had to compile igb driver from intel to
> get the NIC ordering correct.
>
> now arping is also not working.
>
> can you give me some advise how do I continue having this issue
> resolved?
>
> thanks,
> Donny
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit
http://communities.intel.com/community/wired
