[wpad] AP/VLAN supported?

[anon45274024]

• Master 4.19.93
• wpad-mesh-wolfssl 2019-08-08

---

iw list | grep "Supported interface modes" -A 8 prints

    Supported interface modes:
             * managed
             * AP
             * AP/VLAN
             * monitor
             * mesh point

In LuCI however AP/VLAN is absent.

Missing something or is that not supported (by wpad)?

[juppin]

I'm not sure, but I think your desired option is a specific configuration of "Access Point".

As I know, vlans are only supported with the dynamic_vlan option on WPA Enterprise.
This option should be at the security tab.

https://openwrt.org/docs/guide-user/network/wifi/basic#wpa_enterprise_access_point

What do you wanna realize with the mode AP/VLAN?

Edit:
From: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf

# Per-Station AP_VLAN interface mode
# If enabled, each station is assigned its own AP_VLAN interface.
# This implies per-station group keying and ebtables filtering of inter-STA
# traffic (when passed through the AP).
# If the sta is not assigned to any VLAN, then its AP_VLAN interface will be
# added to the bridge given by the "bridge" configuration option (see above).
# Otherwise, it will be added to the per-VLAN bridge.
# 0 = disabled (default)
# 1 = enabled
#per_sta_vif=0

Or is this the desired config option?

[anon45274024]

@juppin

What do you wanna realize with the mode AP/VLAN?

802.1Q tag awareness for Wlan access port (PVID untagged).

iw provides

dev <devname> station set <MAC address> vlan <ifindex>
		Set an AP VLAN for this station.

and such is not exposed in LuCI. Not sure (yet) whether that achieves what I am looking for.

The chipset is a Qualcomm Atheros QCA9880 with:

Supported TX frame types:
    * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
    * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
    * IBSS: 0x40 0xb0 0xc0 0xd0
    * managed: 0x40 0xd0
    * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
    * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
    * mesh point: 0xb0 0xc0 0xd0
    * P2P-client: 0x40 0xd0
    * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
    * P2P-device: 0x40 0xd0

[anon45274024]

Seems that it pertains to STA mode in a 802.11s setup, which is not my uses case.

Suppose that however it is not the Mesh ID and thus probably would make sense to implement with UCI | LuCI (unless I missed it somehow) in order to cater for a 802.11s scenario that involves VLAN.