https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233995
Bug ID: 233995
Summary: Inconsistent arp handling in multiple fibs
Product: Base System
Version: 12.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: pat...@hildingsson.se
uname -a; FreeBSD lrrr.guld.sen 12.0-RELEASE FreeBSD 12.0-RELEASE r341666
GENERIC amd64
uname -U; 1200086
uname -K; 1200086
lagg0;
laggproto lacp lagghash l2,l3,l4
laggport: em0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
laggport: igb0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
groups: lagg
fib0 contains
Internet:
Destination Gateway Flags Netif Expire
default 192.168.23.1 UGS lagg0
192.168.23.0/24 link#4 U lagg0
192.168.23.124 link#4 UHS lo0
fib1 contains
Internet:
Destination Gateway Flags Netif Expire
default 192.168.22.1 UGS lagg0.200
192.168.22.0/24 link#17 U lagg0.200
192.168.22.13 tt:uu:vv:xx:yy:zz UHS lagg0.200
When attempting communication in fib 1 with remote hosts within the same
routing domain , i.e. 192.168.22.1 it fails and the following logentry is
written:
Dec 13 21:00:03 lrrr kernel: arpresolve: can't allocate llinfo for 192.168.22.1
on lagg0.200
When adding the following entry in fib0 the communication works.
setfib 0 route add -net 192.168.22.0/24 -iface lagg0.200
In addition, when adding a static ARP entry the communication works.
setfib 1 arp -s 192.168.22.1 ss:uu:vv:xx:yy:zz
It seems to me that ARP should work in either fib regardless of fib0 having the
network in question. This issue seems to have existed before according to
https://lists.freebsd.org/pipermail/freebsd-net/2012-May/032340.html
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
