Hi
I'm experiencing a problem with link aggregation on my laptop. lagg0 aggregates my wired and wireless interfaces (em0 and wlan0 respectively) as described in the handbook. It works "manually", but when configured by rc.conf there appears to be a problem due to the wlan0 interface not being ready before the lagg0 is configured.
My rc.conf snippet:
Starting the interfaces via rc.d:
By elimination I'm pretty sure the "bad value" message comes from the "laggport wlan0" clause in the ifconfig_lagg0 rc.conf line.
If I then manually enter [cmd=]ifconfig lagg0 laggport wlan0[/cmd] then all is well, however that is no good during boot and as a result a load of my boot processes are failing due to no network.
I can't see any way to force lagg0 configuration to wait for its component interfaces to be configured (wlan0 instantiation apparently being non-instantaneous).
Can anyone suggest solutions/hacks/commiserations?
Much obliged,
sim
I'm experiencing a problem with link aggregation on my laptop. lagg0 aggregates my wired and wireless interfaces (em0 and wlan0 respectively) as described in the handbook. It works "manually", but when configured by rc.conf there appears to be a problem due to the wlan0 interface not being ready before the lagg0 is configured.
My rc.conf snippet:
Code:
ifconfig_em0="ether 00:24:d7:6a:7f:58 up"
ifconfig_iwn0="up"
wlans_iwn0="wlan0"
ifconfig_wlan0="country GB WPA up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP SYNCDHCP up"
Starting the interfaces via rc.d:
Code:
root@tma1> /etc/rc.d/netif start
ifconfig: create: [B]bad value[/B]
ifconfig: SIOCS80211: Device busy
Starting wpa_supplicant.
ifconfig: SIOCSLAGGPORT: Device busy
Starting dhclient.
lagg0: no link .............. giving up
/etc/rc.d/dhclient: WARNING: failed to start dhclient
Starting Network: lo0 em0 iwn0 lagg0.
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:24:d7:6a:7f:58
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: no carrier
iwn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
ether 00:24:d7:6a:7f:58
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng
status: associated
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
ether 00:24:d7:6a:7f:58
inet6 fe80::224:d7ff:fe6a:7f58%lagg0 prefixlen 64 scopeid 0x6
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: no carrier
laggproto failover lagghash l2,l3,l4
[b]laggport: wlan0 flags=4<ACTIVE> [I]<--- this line is missing [/I][/b]
laggport: em0 flags=1<MASTER>
root@tma1>
By elimination I'm pretty sure the "bad value" message comes from the "laggport wlan0" clause in the ifconfig_lagg0 rc.conf line.
If I then manually enter [cmd=]ifconfig lagg0 laggport wlan0[/cmd] then all is well, however that is no good during boot and as a result a load of my boot processes are failing due to no network.
I can't see any way to force lagg0 configuration to wait for its component interfaces to be configured (wlan0 instantiation apparently being non-instantaneous).
Can anyone suggest solutions/hacks/commiserations?
Much obliged,
sim