COMPANY CONFIDENTIAL
70
3.3.1 Bridge Configuration in mBSSID and VLAN mode
If one prefers to use commands to configure VLANs in mBISSID mode. The following bridge configuration need to be
achieved. APUP script can get the following configuration when AP_STARTMODE is set to
multivlan
and
corresponding VLAN tag values.
br0 with no interfaces
br2 with
ath0.
second_tag
,
eth0.
second_tag
,
eth1.
second_tag
br3 with
ath1.
third_tag
,
eth0.
third_tag
,
eth1.third_tag
br4 with
ath2.
fourth_tag
,
eth0.
fourth_tag
,
eth1.
fourth_tag
br5 with
ath3.
fifth_tag
,
eth0.
fifth_tag
,
eth1.
fifth_tag
For all other IP communications IP address need to be assigned to eth0.
Here is sample the output from ‘brctl show’ command when configured in
multivlan
mode.
bridge name bridge id STP enabled interfaces
br5 8000.0e037f0ca088 no eth0.5
ath3.5
br4 8000.0a037f0ca088 no eth0.4
ath2.4
br3 8000.06037f0ca088 no eth0.3
ath1.3
br2 8000.00037f0ca088 no eth0.2
ath0.2
3.4 Multiple BSS
The design of the Atheros driver allows for the association of multiple VAP instances to a single ath hardware instance.
This is called Multiple BSSID, or mBSSID. The repeater case is an example of an mBSSID configuration. These are
typically used to create separate classes of interfaces (one secure, the other open) to allow a single AP to perform
multiple roles.
The scripting system has been designed to support mBSSID configurations through defining environmental variables. It
is assumed that no client type VAPs will be created for the mBSSID cases. This can be revisited in future releases.
To configure multiple VAPs, all relevant environmental variables must be configured. For the AP_SSID,
AP_SECMODE, and AP_SECFILE variables, extended versions with _2, _3, and _4 appended are provided to specify
the configuration for the appropriate VAP. To enable a specific VAP instance, you simply need to define the AP_SSID
variable for the instance (VAP 1 is always assumed to be defined). VAP instances must be defined in order, e.g. it is
illegal to define VAP 2 and VAP 4 without defining VAP 3.
For this release, the beacon interval is automatically set to 400 microseconds when defining multiple VAPs. This is to
support spreading of beacons out to reduce impact on traffic.
3.4.1 Multiple Open APs
This configuration is a simple creation of a number of VAPs using no security modes. The following example shows the
creation of 4 VAPs with different SSIDs. Note that ALL VAPs must be on the same channel, and will have the same RF
parameters. This is a property of the shared ath object, and cannot be multiply defined.
# export AP_STARTMODE=multi
# export AP_SSID=FirstSSID
# export AP_SSID_2=SecondSSID
# export AP_SSID_3=ThirdSSID
# export AP_SSID_4=FourthSSID
# apup
