Regression #14912
closed
WAN Interfaces No Longer Able to Use Gateway Outside Subnet
Added by Kris Phillips over 1 year ago.
Updated over 1 year ago.
Affected Plus Version:
23.09
Affected Architecture:
All
Description
In pfSense Plus 23.09 BETA there seems to be a regression of this former bug:
https://redmine.pfsense.org/issues/972
Whenever the gateway of a WAN interface is outside of the subnet of the interface IP, System Logs report the following over and over:
arpresolve: can't allocate llinfo for [Gateway IP here] on [Interface here]
If you run the following command, the issue goes away:
route add -net [Gateway IP]/32 -iface [Interface]
For example:
route add -net 68.250.40.1/32 -iface ix1.1202
- Status changed from New to Rejected
I can't replicate this as stated. If I add a new route that is outside the subnet (e.g. by setting the interface as a /32), and I check the box in the advanced gateway settings to use the non-local gateway, then the route gets added to the table properly with the interface, same as running the command in the description by hand. I checked after adding the gateway, again after a reboot, and the route is the same each time. I can ping through the gateway and the states look OK. I see no llinfo errors and dpinger shows the gateway as online.
23.09-BETA (amd64)
built on Fri Oct 20 2:00:00 EDT 2023
FreeBSD 14.0-CURRENT
The code for handling the nonlocalgateway option has not changed in >2.5yrs.
Following through the code the only way it wouldn't add the interface is if the interface or IP address in the gateway config.xml block are empty or invalid in some way.
Might be worth deleting and re-creating the gateway, making sure the IP address and interface are selected properly, and that the non-local gateway box is checked in the advanced options.
Jim Pingle wrote in #note-1:
I can't replicate this as stated. If I add a new route that is outside the subnet (e.g. by setting the interface as a /32), and I check the box in the advanced gateway settings to use the non-local gateway, then the route gets added to the table properly with the interface, same as running the command in the description by hand. I checked after adding the gateway, again after a reboot, and the route is the same each time. I can ping through the gateway and the states look OK. I see no llinfo errors and dpinger shows the gateway as online.
[...]
The code for handling the nonlocalgateway option has not changed in >2.5yrs.
Following through the code the only way it wouldn't add the interface is if the interface or IP address in the gateway config.xml block are empty or invalid in some way.
Might be worth deleting and re-creating the gateway, making sure the IP address and interface are selected properly, and that the non-local gateway box is checked in the advanced options.
It looks like during my testing when I deleted and re-created the gateway, I forgot to re-check the "non-local gateway" checkbox during the migration. It was checked previously, but for some reason it just stopped working until being deleted and re-added, then re-checked. Either way appears to be a fluke and thanks for testing Jim!
Also available in: Atom
PDF
Updated by 
Updated by