Bug 140358 - 8.0RC2: [arp] arp: writing to routing socket: Invalid argument with -S key usage
Summary: 8.0RC2: [arp] arp: writing to routing socket: Invalid argument with -S key usage
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-07 14:30 UTC by Oleg Ginzburg
Modified: 2017-12-31 22:27 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oleg Ginzburg 2009-11-07 14:30:01 UTC
When i try 

/usr/sbin/arp -S IP 0:24:21:51:b1:1e pub

(where IP from my networks)

arp works successful and return errors message:

arp: writing to routing socket: Invalid argument

Some soft who analyzing return code (for example, net/mpd5 with proxy-arp settings) work incorrectly when doing system(3) for /usr/sbin/arp.

With 7x branch behaviors is fine
Comment 1 Gavin Atkinson freebsd_committer freebsd_triage 2009-11-07 14:32:34 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).  I can verify this on my machine (19th Oct HEAD) 
so it's not due to his custom kernel.
Comment 2 Qing Li freebsd_committer freebsd_triage 2009-12-09 23:17:52 UTC
Responsible Changed
From-To: freebsd-net->qingli

Take ownership of this issue.
Comment 3 sddex 2013-10-17 23:00:04 UTC
How-To-Repeat

# uname -a
FreeBSD a 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Fri Sep 27 
03:52:52 UTC 2013 
root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC  i386

# ifconfig em0 inet 10.0.0.1/24
# ifconfig em1 inet 10.0.1.1/16    #note the 2nd net includes 1st net
# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
         ether 08:00:27:06:94:50
         inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
         media: Ethernet autoselect (1000baseT <full-duplex>)
         status: active
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
         ether 08:00:27:16:75:d3
         inet 10.0.1.1 netmask 0xffff0000 broadcast 10.0.255.255
         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
         media: Ethernet autoselect (1000baseT <full-duplex>)
         status: active

# netstat -rnf inet    #note network addresses are identical
Destination        Gateway            Flags    Refs      Use  Netif Expire
10.0.0.0/24        link#1             U           0      110    em0 =>
10.0.0.0/16        link#2             U           0        0    em1
10.0.0.1           link#1             UHS         0        0    lo0
10.0.1.1           link#2             UHS         0        0    lo0
127.0.0.1          link#3             UH          0       48    lo0

# arp -s 10.0.2.1 auto pub    #note correct iface and MAC
using interface em1 for proxy with address 08:00:27:16:75:d3

# arp -an    #note incorrect iface and correct MAC
? (10.0.1.1) at 08:00:27:16:75:d3 on em1 permanent [ethernet]
? (10.0.2.1) at 08:00:27:16:75:d3 on em0 permanent published [ethernet]
? (10.0.0.1) at 08:00:27:06:94:50 on em0 permanent [ethernet]

# arp -d 10.0.2.1
arp: writing to routing socket: Invalid argument

# arp -an    #note nothing was changed
? (10.0.1.1) at 08:00:27:16:75:d3 on em1 permanent [ethernet]
? (10.0.2.1) at 08:00:27:16:75:d3 on em0 permanent published [ethernet]
? (10.0.0.1) at 08:00:27:06:94:50 on em0 permanent [ethernet]
Comment 4 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:17 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped