Odd arpresolve messages on console screen

[Shoresy]

Can anyone decipher what these arpresolve messages mean that are consistently sprayed onto my console?



igc0 is assigned to my primary WAN, which is gateway 68.xx.xx.x
igc1 is assigned to my secondary WAN, which is gateway 74.xx.xx.x

Yet the arpresolve messages indicate that the wrong interface is trying to "allocate llinfo" for the other interface's gateway? I am load balancing both of these interfaces, so they're both set to Tier 1 within the gateway group settings.

Is this a bug in OPNsense, or expected behavior? I'm not seeing any performance or connectivity issues here, just wondering why an interface would be trying to resolve a gateway IP over the wrong interface.

[axsdenied]

Means it can't reach the gateway for that interface.

[Shoresy]

Well that makes sense...since it's trying to reach out to the gateway on the wrong WAN interface. Why would that interface attempt to reach the other interface's WAN gateway? Doesn't make a lot of sense I guess.

[axsdenied]

If it's an active interface, it monitors the state of that interface.  Doesn't matter if it's the "failover".

[Shoresy]

So what's happening is the interface that is up (online) is trying to reach the gateway of the interface that is down? Sorry if the questions seem dumb, just a little confused on how this is working. I also noticed that when I physically pulled the plug from each of the ISP interfaces (ONT for Fios and Cable modem for Spectrum), OPNSense appears to report the OPPOSITE gateway being down, rather than reporting the gateway down where I pulled the cable. Seems like something is reversed.

[mimugmail]

Most of the time its a wrong route, just check them. Maybe die to wrong multiwan or failover

[Shoresy]

Found the problem...Settings > General, I had the DNS server assignments reversed. I used the DNS server IP's as the monitoring IP's for each gateway, and flip-flopped how I had them assigned in Settings > General. Once I set them so that they were consistent with the Gateway > Single settings, the ARPresolve error messages vanished.