CARP interfaces don't share L3 (IP) config with the parent, it's just the physical interface where packets travel through. You need to configure the netmask and ip address separately; they may even be in completely different networks. If you don't specify a netmask for carp0 some default will be used, which is likely wrong.
On Wed, Feb 11, 2009 at 01:39:32PM -0800, Vivek Ayer wrote: > carp0 doesn't automatically know the netmask of its parent? Well, that > would explain the problem, right? Because I don't believe I fiddled > with netmask in /etc/hostname.carp0. > > Thanks, > Vivek > > On Wed, Feb 11, 2009 at 12:43 PM, Jussi Peltola <pe...@pelzi.net> wrote: > > Everything to 184.159/16, that is, 184.159.x.x, goes out of carp0. You > > need to specify a netmask for carp just like any interface, and in any > > sane situation it should be the same as the parent's (I assume re0) when > > they both have (different) addresses in the same subnet. > > > > > > On Wed, Feb 11, 2009 at 12:35:05PM -0800, Vivek Ayer wrote: > >> I tried that and here's some interesting information. > >> > >> First of all, I forgot to mention that this router was carped with > >> another one. Not sure if this could be leading to the problem. But > >> anyway, I did route -n show and for my external interface re0 > >> corresponding to carp0 here's the relevant info: > >> > >> Dest Gateway Interface > >> default 184.159.35.1 re0 > >> 184.159/16 link #6 carp0 <--- > >> 184.159.35/24 link #2 re0 > >> 184.159.35.1 (MAC addr) re0 > >> 184.159.35.23 184.159.35.23 carp0 > >> > >> The second line is interesting because it makes me wonder whether > >> there's more to setting up the carp interface. I assume carp0 has the > >> same netmask as re0, but if you can explain the second line, that'd be > >> great. > >> > >> Thanks, > >> Vivek > >> > >> Just so that you don't get confused, I think in previous emails, I > >> said 29 was my subnet and I'm now saying 35 when I meant to say 29, > >> but you get the idea, whatever. > >> > >> On Wed, Feb 11, 2009 at 11:58 AM, Jussi Peltola <pe...@pelzi.net> wrote: > >> > 1. ifconfig > >> > 2. route -n show > >> > 3. a network topology description > >> > > >> > -- > >> > Jussi Peltola