Hi all, here we have carp pfsync setup mostly for wireless and mobile users. Beside from pure forwarding and firewalling boxes are dhcp server with dhcpsync.
>From time to time in logs i can see: May 17 11:44:18 bcbnfw1 /bsd: arpresolve: 10.30.0.0: route contains no arp information I've route monitor it and i think that this is the one: got message of size 272 on Tue May 17 11:44:18 2022 RTM_MISS: Lookup failed on this address: len 272, priority 0, table 0, if# 0, pid: 0, seq 0, errno 17 flags:<DONE> fmask: use: 0 mtu: 0 expire: 0 locks: inits: sockaddrs: <DST,GATEWAY> 10.30.15.39 (53) Qb2.20.00.80.ff.ff.7c.dd.7e.81.ff.ff.ff.ff.00.00.00.00.00.00.00.00.07.00.00.00.00.00.00.00.70.0d.26.66.80.fd.ff.ff.80.65.01.00.60.00.00.00.00.00.00.00.00.00.00.00.38.36.b2.20.00.80.ff.ff.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.11 at that time 11:44:18 there are few logs for ip 10.30.15.39 (mobile phone), please see log in attachment. route 10.30.0/20 is connected route to interface vlan1130 Destination Gateway Flags Refs Use Mtu Prio Iface 10.30.0/20 10.30.0.2 UCn 141 22619 - 4 vlan1130 arp -an | grep 10.30.15.39 10.30.15.39 76:b9:98:72:7c:9c vlan1130 15m30s Beside that in logs there are lot's of: arp: attempt to add entry for 10.33.0.116 on vlan1133 by a4:45:19:7d:bb:28 on vlan1132 i'm explaining this log to myself - because there is one SSID (eduroam) and lots of vlans i will this this log no matter what .. is this "arpresolve log" bug ?
got message of size 192 on Tue May 17 11:44:18 2022 RTM_ADD: Add Route: len 192, priority 3, table 0, if# 37, name vlan1130, pid: 0, seq 0, errno 0 flags:<UP,HOST,DONE,LLINFO,CLONED> fmask: use: 0 mtu: 0 expire: 0 locks: inits: sockaddrs: <DST,GATEWAY,IFP,IFA> 10.30.15.39 link#37 90:e2:ba:d7:1b:f4 10.30.0.2 got message of size 192 on Tue May 17 11:44:18 2022 RTM_DELETE: Delete Route: len 192, priority 3, table 0, if# 37, name vlan1130, pid: 0, seq 0, errno 0 flags:<UP,HOST,DONE,LLINFO,CLONED> fmask: use: 0 mtu: 0 expire: 0 locks: inits: sockaddrs: <DST,GATEWAY,IFP,IFA> 10.30.15.39 link#37 90:e2:ba:d7:1b:f4 10.30.0.2 got message of size 192 on Tue May 17 11:44:18 2022 RTM_ADD: Add Route: len 192, priority 3, table 0, if# 37, name vlan1130, pid: 0, seq 0, errno 0 flags:<UP,HOST,DONE,LLINFO,CLONED> fmask: use: 0 mtu: 0 expire: 0 locks: inits: sockaddrs: <DST,GATEWAY,IFP,IFA> 10.30.15.39 link#37 90:e2:ba:d7:1b:f4 10.30.0.2 got message of size 192 on Tue May 17 11:44:18 2022 RTM_DELETE: Delete Route: len 192, priority 3, table 0, if# 37, name vlan1130, pid: 0, seq 0, errno 0 flags:<UP,HOST,DONE,LLINFO,CLONED> fmask: use: 0 mtu: 0 expire: 0 locks: inits: sockaddrs: <DST,GATEWAY,IFP,IFA> 10.30.15.39 link#37 90:e2:ba:d7:1b:f4 10.30.0.2 got message of size 192 on Tue May 17 11:44:18 2022 RTM_ADD: Add Route: len 192, priority 3, table 0, if# 37, name vlan1130, pid: 0, seq 0, errno 0 flags:<UP,HOST,DONE,LLINFO,CLONED> fmask: use: 0 mtu: 0 expire: 0 locks: inits: sockaddrs: <DST,GATEWAY,IFP,IFA> 10.30.15.39 link#37 90:e2:ba:d7:1b:f4 10.30.0.2 got message of size 272 on Tue May 17 11:44:18 2022 RTM_MISS: Lookup failed on this address: len 272, priority 0, table 0, if# 0, pid: 0, seq 0, errno 17 flags:<DONE> fmask: use: 0 mtu: 0 expire: 0 locks: inits: sockaddrs: <DST,GATEWAY> 10.30.15.39 (53) Qb2.20.00.80.ff.ff.7c.dd.7e.81.ff.ff.ff.ff.00.00.00.00.00.00.00.00.07.00.00.00.00.00.00.00.70.0d.26.66.80.fd.ff.ff.80.65.01.00.60.00.00.00.00.00.00.00.00.00.00.00.38.36.b2.20.00.80.ff.ff.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.11 got message of size 192 on Tue May 17 11:44:18 2022 RTM_RESOLVE: Route created by cloning: len 192, priority 3, table 0, if# 37, name vlan1130, pid: 0, seq 0, errno 0 flags:<UP,HOST,DONE,LLINFO,CLONED> fmask: use: 0 mtu: 0 expire: 0 locks: inits: sockaddrs: <DST,GATEWAY,IFP,IFA> 10.30.15.39 76:b9:98:72:7c:9c 90:e2:ba:d7:1b:f4 10.30.0.2
