Hello,On FreeBSD 9.1-RELEASE, the network stack sends an ARP who-has request with the following network settings:
# ifconfig em0 inet 18.104.22.168 netmask 255.255.255.255 broadcast 22.214.171.124
# route add -host 126.96.36.199 -link -iface em0 add host 188.8.131.52: gateway em0 # ping 184.108.40.206 PING 220.127.116.11 (18.104.22.168): 56 data bytes 64 bytes from 198.l50.219.l49: icmp_seq=0 ttl=64 time=0.031 ms 64 bytes from 198.l50.219.l49: icmp_seq=1 ttl=64 time=0.026 ms ^C --- 22.214.171.124 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.026/0.028/0.031/0.003 ms # arp -a ? (126.96.36.199) at 52:54:00:51:57:30 on em0 permanent [ethernet]How would you get a routing table entry that would provoke ARP? Even the NetBSD FAQ sdoesn't have a MAC address listed:
http://www.netbsd.org/docs/network/#nonsubnetgateway -Peter On 2013-08-22 8:57 AM, Greg Troxel wrote:
This does seem like a bug. It's interesting that it works on FreeBSD, since much of the code has shared heritage. The basic approach to arp is to have a cloning route ("C" flag) which causes arp procesing for addresses within the prefix but for which there isn't an llinfo (L) entry. route add -host 188.8.131.52 -link -iface vioif0 Why are you giving "-link", with no mac address? That seems wrong, and it seems like a bug in route not to throw an error. The trick is to have a routing table entry that will provoke arp. What command do you run on FreeBSD, and what does the routing table look like? I suggest running 'route -n monitor' while doing all of this, to watch the routing socket.
-- Peter Kieser <peter%kieser.ca@localhost> / 604.338.9294
Description: S/MIME Cryptographic Signature