Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an interface that I can arping to by its IP, but not its MAC address:

# arping -i eth2
60 bytes from 02:68:b3:29:da:98 ( index=0 time=81.062 usec
60 bytes from 02:68:b3:29:da:98 ( index=1 time=46.968 usec
60 bytes from 02:68:b3:29:da:98 ( index=2 time=73.910 usec
60 bytes from 02:68:b3:29:da:98 ( index=3 time=46.968 usec

# arping -i eth2 02:68:b3:29:da:98
ARPING 02:68:b3:29:da:98
(no reply)

I don't have this problem with other interfaces on my network. What are the possible issues that could cause this?

I'm running on Ubuntu 12.04.

share|improve this question
What is the problem exactly? Is pinging by MAC address a requirement for you? – David Schwartz Mar 12 '13 at 7:23
arping -i eth2

Send out an ARP packet asking, "Who has the IP"

arping -i eth2 02:68:b3:29:da:98

Sends out an IPv4 ping to the IP address with the target MAC of 02:68:b3:29:da:98.

It is common nowadays to disable responding to broadcast pings. On a Linux system (well any, but I'm only providing a link for one), you can re-enable replies to broadcast IP addresses.

share|improve this answer
I do see outbound packets when pinging against a MAC, if I do this: tcpdump -ennqti eth2 \( arp or icmp \). I just don't see any come back. – Lorin Hochstein Mar 12 '13 at 1:58
Oops, I messed up my filters. Let me post a new one with the right answer now that I realize what happened. – Jeff Ferland Mar 12 '13 at 2:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.