3 # Setup an ap that accepts wds traffic from associated stations.
4 # This can be used as the "back end" for setup.extender and/or
5 # setup.repeater. Note that the wds vap's are created by the
6 # wlanwds program that listens for wds discovery events (to create
7 # wds vaps) and for sta leave events (to destroy wds vaps it
8 # created). The WDSUP script is invoked for each wds vap that
9 # gets created--to add the vap to a bridge.
13 # * If the main AP VAP is running with encryption, the plumbed up
14 # WDS VAP needs to have privacy enabled (wepmode mixed, for example)
15 # otherwise frames transmitted from the WDS AP to the WDS STA
16 # will not be encrypted.
18 # * Because wlanwds is running on the physical interface (for now),
19 # and NOT the parent VAP, it will create cloned interfaces using
20 # the MAC address of the physical interface. So, until that
21 # whole setup is fixed, please only associate DWDS to the first
22 # VAP on a physical interface, which shares the MAC address of
30 SSID='freebsd+wdsmain'
33 #mwldebug state+node+reset+xmit+recv+beacon+hal+hal2
34 WLAN_AP=`ifconfig wlan create wlanmode hostap wlandev $WIRELESS`
35 ifconfig $WLAN_AP ssid "$SSID" channel $CHANNEL mtu 1500
36 ifconfig $WLAN_AP dwds -apbridge
37 wlandebug -i $WLAN_AP state+scan+assoc+auth+wds+11n
39 BRIDGE=`ifconfig bridge create`
41 # NB: start wlanwds first to avoid races.
46 ifconfig $BRIDGE addm \$DEV
50 $WLANWDS -v -s $WDSUP &
52 ifconfig $BRIDGE addm $WLAN_AP addm $WIRED up