I'm testing a setup inside our office that will eventually drop into a
data center, so for now have our office router (also pfSense) set up with a
virtual IP (64.79.96.145) and a gateway and static route to direct
64.79.96.144/29 to the new router's WAN IP of 64.79.96.149. That setup works
from within my office, and I can ping 64.79.96.149 and 64.79.96.150 which I
plan to use as the shared CARP IP.
However when I update the office router's gateway and hence route above
to use the .150 CARP IP, the office router cannot find the .150 address, and
pinging .150 yields "Destination host unreachable" since it doesn't think it
has anywhere to send the routed traffic. I noticed our office router does not
detect an ARP entry for the CARP IP. Is there a reason and/or a way to force
that? Does it take more than a few minutes? It detects an ARP entry for
64.79.96.149 just fine. It also doesn't have an ARP entry for 64.79.96.148
which is the WAN IP of the second router.
--
Steve Yates
ITS, Inc.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
