I have found few cases, that were working fine before, but not so good
now on CURRENT.
There is two interfaces:
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM>
ether 00:1b:24:c5:5b:09
inet 192.168.3.131 netmask 0xffffff00 broadcast 192.168.3.255
inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0
mtu 1500
1) I am going to reuse Ethernet address as local for PtP link:
%ifconfig ng0 10.0.0.1 10.0.0.2
ifconfig: ioctl (SIOCAIFADDR): File exists
%ifconfig ng0
ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0
mtu 1500
inet 10.0.0.1 --> 10.0.0.2 netmask 0xff000000
So as you can see, address was assigned, but request returned error
status. Probably it is related to the recent local address route changes.
2) I am going to configure arp-proxy:
%arp -s 10.0.0.2 00:1b:24:c5:5b:09 pub
arp: writing to routing socket: Invalid argument
And again it doesn't work, writing to syslog:
kernel: lla_rt_output: RTM_ADD publish (proxy only) is invalid
--
Alexander Motin
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
