Virtual AP

[guidonet]

Virtual AP feature on next AirOS?

[Vitis]

Its old, but I vote for this feature.

Is there any progress on it?

[marekm]

Its old, but I vote for this feature.

Is there any progress on it?

It can be done right now, just not easily - in /etc/persistent/rc.poststart like this.


#! /bin/sh

vlan_ath0=2
vlan_ath1=3

wlanconfig ath1 create wlandev wifi0 wlanmode ap

iwpriv ath1 authmode 1
iwconfig ath1 essid xxxxxxxx \
key [1] aaaaaaaaaaaaaaaaaaaaaaaaaa \
key [2] bbbbbbbbbbbbbbbbbbbbbbbbbb \
key [3] cccccccccccccccccccccccccc \
key [4] dddddddddddddddddddddddddd \
key [1] open

iwpriv ath1 wds 1
for i in `cat /etc/persistent/wds_peers` ; do
iwpriv ath1 wds_add $i
done

iwpriv ath1 maccmd 1
for i in `cat /etc/persistent/mac_acl` ; do
iwpriv ath1 addmac $i
done

iwpriv ath1 ap_bridge 0
iwpriv ath1 hide_ssid 1
iwpriv ath1 shpreamble 0

ip link set ath1 up

brctl delif br0 ath0

vconfig add br0 $vlan_ath0
ip link set br0.$vlan_ath0 up
brctl addbr br1
brctl addif br1 ath0
brctl addif br1 br0.$vlan_ath0
ip link set br1 up

vconfig add br0 $vlan_ath1
ip link set br0.$vlan_ath1 up
brctl addbr br2
brctl addif br2 ath1
brctl addif br2 br0.$vlan_ath1
ip link set br2 up


ath0 is set up with the web GUI first, to run WPA2 for new customers.
ath1 is then added by the script, so that old gear can still connect using WEP.
wds_peers and mac_acl files are lists of MAC addresses in xx:xx:xx:xx:xx:xx format, one per line.
The script also creates two new bridge devices and tagged VLANs, so the untagged is only for management, and the two VAPs are bridged to separate tagged VLANs.
This example is based on my working setup, but provided with no warranty or support. Understand what it does, don't just copy blindly and don't sue if your Bullet hits the wrong target. Writing corresponding /etc/persistent/rc.prestop to undo this is left as an exercise to the reader :)

[jrlinux]

It can be done right now, just not easily - in /etc/persistent/rc.poststart like this.


#! /bin/sh

vlan_ath0=2
vlan_ath1=3

wlanconfig ath1 create wlandev wifi0 wlanmode ap

iwpriv ath1 authmode 1
iwconfig ath1 essid xxxxxxxx \
key [1] aaaaaaaaaaaaaaaaaaaaaaaaaa \
key [2] bbbbbbbbbbbbbbbbbbbbbbbbbb \
key [3] cccccccccccccccccccccccccc \
key [4] dddddddddddddddddddddddddd \
key [1] open

iwpriv ath1 wds 1
for i in `cat /etc/persistent/wds_peers` ; do
iwpriv ath1 wds_add $i
done

iwpriv ath1 maccmd 1
for i in `cat /etc/persistent/mac_acl` ; do
iwpriv ath1 addmac $i
done

iwpriv ath1 ap_bridge 0
iwpriv ath1 hide_ssid 1
iwpriv ath1 shpreamble 0

ip link set ath1 up

brctl delif br0 ath0

vconfig add br0 $vlan_ath0
ip link set br0.$vlan_ath0 up
brctl addbr br1
brctl addif br1 ath0
brctl addif br1 br0.$vlan_ath0
ip link set br1 up

vconfig add br0 $vlan_ath1
ip link set br0.$vlan_ath1 up
brctl addbr br2
brctl addif br2 ath1
brctl addif br2 br0.$vlan_ath1
ip link set br2 up


ath0 is set up with the web GUI first, to run WPA2 for new customers.
ath1 is then added by the script, so that old gear can still connect using WEP.
wds_peers and mac_acl files are lists of MAC addresses in xx:xx:xx:xx:xx:xx format, one per line.
The script also creates two new bridge devices and tagged VLANs, so the untagged is only for management, and the two VAPs are bridged to separate tagged VLANs.
This example is based on my working setup, but provided with no warranty or support. Understand what it does, don't just copy blindly and don't sue if your Bullet hits the wrong target. Writing corresponding /etc/persistent/rc.prestop to undo this is left as an exercise to the reader :)

Hi dear Friend.

Is possible the second SSID run WPA too? Is yes, how i can do this?
Thank you!