Paul Civati wrote:
Has anyone tested this?

yes, it doesn't work, carp with vlan aren't supported on FreeBSD. There is a thread about that on freebsd-pf :

http://lists.freebsd.org/mailman/htdig/freebsd-pf/2005-May/001033.html


It doesn't seem to work for me (although from some brief googling I got the impression it should).

In my testing the carp0 for em3 interface negotiates MASTER/BACKUP as it should, however the carp1 interface never leaves the 'INIT' state. From another host in the 111 .1q VLAN/subnet I can ping .67
and .66 (the other CARP partner).

em3: flags=18943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,POLLING> mtu 
1500
        options=4b<RXCSUM,TXCSUM,VLAN_MTU,POLLING>
        inet X.X.X.3 netmask 0xffffffc0 broadcast X.X.X.63
inet6 fe80::230:48ff:fe83:4807%em3 prefixlen 64 scopeid 0x4 ether 00:30:48:83:48:07
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 carp0: flags=41<UP,RUNNING> mtu 1500 inet X.X.X.1 netmask 0xffffffc0 carp: BACKUP vhid 1 advbase 1 advskew 100
vlan111: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        inet Y.Y.Y.67 netmask 0xffffffe0 broadcast Y.Y.Y.95
inet6 fe80::230:48ff:fe83:4806%vlan111 prefixlen 64 scopeid 0x7 ether 00:30:48:83:48:07
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 111 parent interface: em3
carp1: flags=0<> mtu 1500
inet Y.Y.Y.65 netmask 0xffffffe0 carp: INIT vhid 2 advbase 1 advskew 100

-Paul-

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


--
Philippe PEGON
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to