LAGG - interface comes up but no laggports

[Bernhard Schmidt]

On Tuesday, February 22, 2011 14:17:46 Damien Fleuriot wrote:
> On 2/22/11 1:18 PM, Bernhard Schmidt wrote:
> > On Tuesday, February 22, 2011 12:31:34 Damien Fleuriot wrote:
> >> rc.conf
> >> ---
> >> # LINK AGGREG
> >> ifconfig_lagg0="laggproto failover laggport em0 laggport em1"
> >> ipv4_addrs_lagg0="192.168.1.3/29"
> >> ifconfig_lagg0="inet6 fe80::3/64"
> > 
> > You are overwriting the variable, you have to use some alternative
> > or move everything into one statement.
> 
> Good  call, it now works correctly:
> 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
>         nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
>         media: Ethernet autoselect
>         status: active
>         laggproto failover
>         laggport: em1 flags=0<>
>         laggport: em0 flags=5<MASTER,ACTIVE>
> 
> 
> You'll notice that using ipv6_addrs didn't work, as the interface is
> using an automatic address instead of fe80::3/64 which I tried to
> set.
> 
> I suppose I could use the crontab for this, @reboot ifconfig lagg0
> inet6 fe80::3/64 , or perhaps rc.local

I'm using ipv6_ifconfig_XXX0[_aliasX] to assign IPv6 addresses, might be 
worth a try? I don't see ipv6_addrs_XXX0 to be even defined somewhere. 

-- 
Bernhard