LAGG - interface comes up but no laggports

[Damien Fleuriot]

On 2/22/11 1:51 PM, Ryan Stone wrote:
> On Tue, Feb 22, 2011 at 6:31 AM, Damien Fleuriot <ml at my.gd> wrote:
>> ifconfig_lagg0="laggproto failover laggport em0 laggport em1"
>> ipv4_addrs_lagg0="192.168.1.3/29"
>> ifconfig_lagg0="inet6 fe80::3/64"
> 
> You're setting ifconfig_lagg0 twice, so the first setting is being
> discarded.  Off-hand I'm not sure how you're supposed to configure
> ipv6 addresses.  There's nothing in the man page about an
> ipv6_addrs_lagg0 variable but that would be the obvious thing to try,


ipv6_addrs_XXX doesn't do the trick, however this one does:
ipv6_ifconfig_lagg0="fe80::3/64"


lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9014
        options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
        ether 00:15:17:37:17:e6
        inet6 fe80::215:17ff:fe37:17e6%lagg0 prefixlen 64 scopeid 0x5
        inet 192.168.1.3 netmask 0xfffffff8 broadcast 192.168.1.7
        inet6 fe80::3%lagg0 prefixlen 64 scopeid 0x5
        nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
        media: Ethernet autoselect
        status: active
        laggproto failover
        laggport: em1 flags=0<>
        laggport: em0 flags=5<MASTER,ACTIVE>




For a reason that eludes me, the interface still insists on getting an
automatic link local address, but I'll look into this ;)