Yeah, changing CARP addresses after configuration is a little tricky. I need to sit down and play with that code a bit, I suspect we don't do it quite right. A reboot is a GOOD idea if you modify anything to do with a CARP address after it's already in place.
--Bill On 8/25/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > Maybe it was a bug in that specific version of pfSense I was using at > the time because i couldn't get the network to function until i changed > them to /32's. Maybe I'll give it a shot again at some point. > > On Thu, 2005-08-25 at 10:21 -0500, Bill Marquette wrote: > > Actual netmask of the network the CARP address lives on...a /32 > > _should_ work, that's how I've had mine setup for ages, but I opened > > it up to the netmask for correctness sake. > > > > --Bill > > > > On 8/25/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > > > Is this always supposed to be a /32? I'm using /32 on all of them > > right > > > now and it works but it still seems to me that since its asking for > > the > > > netmask of that ip that I should be using /24 (192.168.1.0 network) > > for > > > the private gw vips and /27 (which is what my public ip range is) > > for > > > the public vips. Back when I first added the interfaces several > > > revisions ago things just wouldn't work unless I used a /32 .. which > > is > > > the single ip correct? > > > > > > i know enough about networking to be dangerous :) > > > > > > > > > >
