Upstream/ISP/other involved routers that properly respect the addresses used by CARP.
-
I have been running High Availability with pfsense for several years now. It has been and continues to be a learning experience. I like it and so do my users. It is much more complex than it first appears.
Recently my ISP double NATed my connection. Argh! I have the option of bridging the connection which I plan on doing. However, that means I need a router that properly respects the addresses used by CARP. This is more or less a quote in the pfsense documentation.
https://www.netgate.com/docs/pfsense/highavailability/index.html?highlight=hardware%20redundancy
I found out that that is not a given in routers pretty fast.
The Arris modem handled this nicely, but bridging will eliminate that option.
So I am router shopping. Quite honestly I am a little unsure what to look for in router brands and router specs. I have been researching the issue and said standards in between doing other things. I read how VRRP works because I was curious, and have been studying the multicast system that CARP uses. Some have suggested IOS and others have said that those routers might now work. I don't want to buy a stack of routers and try them out.
So from the more experienced good folk out there I ask for suggestions.
-
Not quite sure why you need another router but I know for a fact Cisco IOS has zero problems with it. The problems with CARP are usually Layer 2. As far as another router and other Layer 3 devices go, they just have to properly honor the ARP responses for the CARP VIP.
When looking at solutions, you might just want to ask about VRRP compatibility. If it works with VRRP it will almost certainly work with CARP. And fewer people will look at you cross-eyed.
-
Hi Derelict,
I will only get one IP when I bridge, thus the need for the router for my server pair.
Roy
-
Oh - Derelict, Thanks for pointing me in the right direction and warning me about the reaction I might get if I ask about CARP.
reberhar
