After reboot, need to disable/re-enable virtual IPs, gateway, static routes?
-
I have a pfSense system based on an Intel Atom D2500 with Intel ethernet ports. The router LAN address is 192.168.4.1/24, and most things work fine. But, I'm trying to route a guest network through a VPN (VPN endpoint is on the pfSense box, guest network is identified with 192.168.5.0/24 addresses), and it only works once I disable and re-enable some components after rebooting.
The pfSense box has a virtual IP address (IP Alias) of 192.168.5.1/32. I have another router on my internal network acting as a wifi access point, with an IP address of 192.168.5.12. I've added that IP address as a gateway on my pfSense box, and set up a static route of 192.168.5.0/24 on the pfSense box to point to that gateway.
When I reboot the system, if I log into a shell on the pfSense box and try to ping 192.168.5.12, I get a "arpresolve: can't allocate llinfo…" message. I've searched, and seen other message that suggest that that message indicates that the target IP isn't on a locally-connected network. But, I thought that with the gateway and static route set up, it should be able to find that address. And, in fact, if I go to pfSense's Virtual IP page, "edit" and re-save the Virtual IP (making no changes), then disable both the static route and 192.168.5.12 gateway, and then re-enable both of those, everything works just fine: I can ping that address, and the guest network has internet access.
My main question is: why should I need to re-save the Virtual IP address, and then disable/re-enable the route and gateway?
My secondary question is: is there some way for me to script the above steps, to simplify the process?
Thank you for your help.
Editing to add: I'm on 2.4.1; this has happened for at least the last few months.