Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Mar 2013 15:47:11 +0100
From:      Fleuriot Damien <ml@my.gd>
To:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject:   carp regression in 9.1 ?
Message-ID:  <3B04FCB1-D0D4-4BC9-BB15-5221F438738C@my.gd>

next in thread | raw e-mail | index | archive | help
Hello list,


I'm experiencing this odd behavior with 9.1 r24791 for amd64.


Find below exerpts from my rc.conf related to carp:

=3D=3D=3D
# production
ifconfig_carp22=3D"inet 192.168.22.254/32 vhid 122 pass vrrp22 advskew =
100"
ifconfig_carp32=3D"inet 192.168.32.254/32 vhid 132 pass vrrp32 advskew =
100"
cloned_interfaces=3D"carp0 carp1 carp22 carp32"

# test interfaces, use different syntaxes
ifconfig_carp1=3D"vhid 124 advskew 100 192.168.22.240 netmask =
255.255.255.0"
ifconfig_carp0=3D"vhid 140 advskew 50 pass dsds 192.168.22.250"
ipv4_addrs_carp0=3D"192.168.22.241-249/24"
=3D=3D=3D


With all of these configuration lines, carp interfaces come up at boot.


The problem I experience is when destroying the carp interfaces and =
recreating them:
root@pf1-drt:~ # ifconfig carp1 destroy
root@pf1-drt:~ # ifconfig carp1 create
root@pf1-drt:~ # ifconfig carp1=20
carp1: flags=3D8<LOOPBACK> metric 0 mtu 1500
	nd6 options=3D21<PERFORMNUD,AUTO_LINKLOCAL>


FreeBSD 8.3 doesn't exhibit the same behaviour, when destroying then =
recreating the interfaces, they are initialized correctly.


Additionally, note the syntax I used for my test interface carp0:
ipv4_addrs_carp0=3D"192.168.22.241-249/24"

And the results at boot:
carp0: flags=3D49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
	inet 192.168.22.250 netmask 0xffffff00=20
	inet 192.168.22.241 netmask 0xffffff00=20
	inet 192.168.22.242 netmask 0xffffffff=20
	inet 192.168.22.243 netmask 0xffffffff=20
	inet 192.168.22.244 netmask 0xffffffff=20
	inet 192.168.22.245 netmask 0xffffffff=20
	inet 192.168.22.246 netmask 0xffffffff=20
	inet 192.168.22.247 netmask 0xffffffff=20
	inet 192.168.22.248 netmask 0xffffffff=20
	inet 192.168.22.249 netmask 0xffffffff



I'm really confused here, is this intended behaviour ?

FreeBSD 8.3 certainly doesn't act this way.


Does anyone have an idea what's happening there ?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B04FCB1-D0D4-4BC9-BB15-5221F438738C>