119 reputation
4
bio website catzo.com
location Oakland, CA
age
visits member for 8 months
seen Oct 5 at 21:58

Jul
23
awarded  Informed
May
21
awarded  Teacher
Feb
13
revised CARP changes in FreeBSD 10
added 63 characters in body
Feb
13
comment CARP changes in FreeBSD 10
Yes that is true the ifconfig_<interface>_alias<n> rc.conf property functionality has not changed. I only noticed this behavior after converting a lot of carp addresses to aliases. So yes, it has nothing to do with carp itself. However I feel the question is valid because I and maybe others ran into this "difficult to manage behavior" when updating carp interfaces to this new syntax.
Feb
13
awarded  Student
Feb
13
revised CARP changes in FreeBSD 10
fix incorrect interface init.
Feb
13
comment CARP changes in FreeBSD 10
CARP has been rewritten in freebsd-10. Having to change all my ifconfing_carp<n> properties to aliases is what inspired this question. In freeBSD < 10 carp was defined as a cloned interfase and the order didn't matter. Never dealing with more than a couple of alias I was unaware of the requirement of sequential numbering. I have since answered my own question. I have opted to use ifconfig_<interface>_aliases making it easier to add and remove carp interfaces.
Feb
13
answered CARP changes in FreeBSD 10
Feb
13
awarded  Editor
Feb
13
revised CARP changes in FreeBSD 10
edited body
Feb
13
comment CARP changes in FreeBSD 10
whoops the /24 was a typo they are on the same subnet. I have to indicate a vhid for each address according to the new carp manual. it is just crazy that each alias have to be in order starting with _alias0.
Feb
13
asked CARP changes in FreeBSD 10