Re: Carp with aliases route problem

On 2009-02-24, Rod Whitworth wrote: > On Mon, 23 Feb 2009 17:52:33 -0600, Todd T. Fries wrote: > >>As a corrilary, for those ISP's who think there is only need for a >>single /30 for a client's router, the concept of failover routers >>means 1 physical IP per router, and 1 IP for the failover IP,

Re: Carp with aliases route problem

On Mon, 23 Feb 2009 17:52:33 -0600, Todd T. Fries wrote: >As a corrilary, for those ISP's who think there is only need for a >single /30 for a client's router, the concept of failover routers >means 1 physical IP per router, and 1 IP for the failover IP, aka >3 IP's for the client side, dictating

Re: Carp with aliases route problem

You cannot get internet access on a backup carp interface, period. I have seen what you see before, and it comes from not starting things up in proper order manually, i.e. configuring a system, and not rebooting it after it was configured so that boot time configs get processed in proper order. T

Re: Carp with aliases route problem

On 21:31, Mon 23 Feb 09, Stuart Henderson wrote: > I suspect you might want /32 on the carp interfaces (255.255.255.255 > rather than your 255.255.255.224). I'll try that in the next week. Thanks for the pointer. > > What are the exact symptoms of not being able to reach .197 when HostB > is in

Re: Carp with aliases route problem

I suspect you might want /32 on the carp interfaces (255.255.255.255 rather than your 255.255.255.224). What are the exact symptoms of not being able to reach .197 when HostB is in backup state? It may be stating the obvious but check there's no PF rule that might be blocking it. You don't mentio

Carp with aliases route problem

Hi all, I'm having some trouble with a two-node CARP setup. Configuration: HostA /etc/hostname.em0 inet XXX.XXX.XXX.196 255.255.255.244 XXX.XXX.XXX.223 \ media 100baseTX mediaopt full-duplex description External /etc/hostname.em1 inet 192.168.10.2 255.255.255.0 192.168.10.255 \