And how can I find out if 1.2-RC4 uses that freebsd fix?
Gary Buckmaster wrote:
LAGG isn't supported yet, which means that you're not going to get
your question answered here. LAGG support will be coming with the 1.3
release, however, not with the 1.2 series, so this means it will also
not be in any of the 1.2 release candidates.
Fabio C Flores wrote:
Hello there,
I know lagg is not yet supported but since its freebsd Im encouraged
to use it. After creating the interface using /ifconfig lagg0 create/
it works nicely and I can setup everything under the web gui
including firewall rules.
My setup requires the use of CARP on the lagg interface which Im
failing to make it work. The lagg itself is failing over as expected,
but looks like its not sending multicast link events via the lagg.
I've checked it with tcpdump.
I found this fix http://www.freebsd.org/cgi/query-pr.cgi?pr=113956 ,
which would sort the problem. Im not sure if 1.2-RC4, the version Im
using, incorporates that fix.
This is causing both master and backup nodes to become MASTER:
master
> carp1: flags=49<UP,LOOPBACK,RUNNING> mtu 1500
> inet 10.0.2.3 netmask 0xffff0000
> carp: MASTER vhid 12 advbase 1 advskew 0
backup
> carp1: flags=49<UP,LOOPBACK,RUNNING> mtu 1500
> inet 10.0.2.3 netmask 0xffff0000
> carp: MASTER vhid 12 advbase 1 advskew 100
This is how I created the lagg interface under config.xml:
> <shellcmd>ifconfig lagg0 create</shellcmd>
> <shellcmd>ifconfig lagg0 laggproto failover laggport
em0 laggport bge1 10.0.2.7 netmask 255.255.0.0</shellcmd>
> <shellcmd>route delete 10/16</shellcmd>
> <shellcmd>route add -net 10/16 -interface
lagg0</shellcmd>
Thanks in advance,
Fabioc
