New wAP AC (RBwAPG-5HacD2HnD)

For Developers
24

Anyone having success with VLAN tagging on this AP?
Using 22.03.3 i did get tagged vlan on br-lan via eth0, but i just can't get eth1 (wan) to accept untagged/untagged vlan on same port.

tried via eth1.X or bridge filtering.
is "switch" section just for eth0 port or are bridge vlan filtering and "switch" section mutualy exclusive ?

edit:

might find some info here IPQ40xx Switch Config "Strangeness" (swconfig) - #109 by debug

It's labeled wan but really isn't, it's used as fourth lan port in my case.

anyone checked this?

25

new wAP AC wireless phy issue

Why is the phy interface assignment different from the old wAP AC?
How to switch it back ?
Who can help? @p34t

old: phy0=5, phy1=2.4
new: phy0=2.4, phy1=5

Impact: complicated scripting

22.03.5
old: as usual
new: snapshot from 2023-05-29

new wAP AC 

# iw dev
phy#1
        Interface phy1-ap0
                ifindex 8
                wdev 0x100000002
                channel 52 (5260 MHz), width: 80 MHz, center1: 5290 MHz
phy#0
        Interface phy0-ap0
                ifindex 9
                wdev 0x2
                channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz

old wAP AC 

# iw dev
phy#1
        Interface wlan1
                ifindex 6
                wdev 0x100000002
                channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
phy#0
        Interface wlan0
                ifindex 7
                wdev 0x2
                channel 112 (5560 MHz), width: 80 MHz, center1: 5530 MHz

Thanks
Odon
2023-05-29T22:00:00Z

26
27

tried 23.05.0-rc2 and snapshot.

i just can get VLANs to work.
one VLAN per one bridge with eth0.X as list-ports

28

Machine model: MikroTik hAP ac2 (RBwAPG-5HacD2HnD)

It has two eth ports

eth0 is also PoE powered - it is listed as 'wan' port on eth0 "switch"
eth1 is listed as 'lan1' port on eth0 "switch"

in 22.3.5 it works with bridge filtering (br-lan and then br-lan.X as interfaces).

My section of VLAN setting for 23.05.0-rc2:

I use vlan 333 only on wifi-iface/ssid and as untagged on "lan" port on this AP so i can get to it via LAN cable or via WLAN if anything else fails [dhcp,...]:

wan {eth0} port gets guest tagged vlan 67 network.
lan1 {eth1} port has mgmt_local untagged vlan 333 network.

I added wan to bridge br-lan so i can do bridge vlan filtering.

config device 'device1'
	option bridge_empty '1'
	option name 'br-lan'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'
	list ports 'wan'
        option type 'bridge'

config device 'device10'
	option ifname 'br-lan'
	option name 'br-lan.67'
	option type '8021q'
	option vid '67'

config device 'device11'
	option ifname 'br-lan'
	option name 'br-lan.333'
	option type '8021q'
	option vid '333'

config bridge-vlan 'bridge_vlan4'
	option device 'br-lan'
	list ports 'wan:t'
	option vlan '67'

config bridge-vlan 'bridge_vlan7'
	option device 'br-lan'
	list ports 'lan1:u*'
	option vlan '333'

config interface 'lan_guest'
	option proto 'none'
	option device 'br-lan.67'
	option force_link '1'
	option defaultroute '0'
	option delegate '0'

config interface 'mgmt_local'
	option proto 'static'
	option device 'br-lan.333'
	option ipaddr '192.168.2.2'
	option netmask '255.255.255.0'
	option delegate '0'
	option defaultroute '0'

config wifi-iface 'mgmt_local'
	option device 'radio0'
	option disabled '0'
	option mode 'ap'
	option ssid '$hostname'
	option key 'triplexxx'
	option encryption 'psk2+ccmp'
	option network 'mgmt_local'
	option isolate '1'

config wifi-iface 'guest5'
	option device 'radio1'
	option disabled '0'
	option mode 'ap'
	option ssid 'guest'
	option key '123123123z'
	option encryption 'psk2+ccmp'
	option network 'lan_guest'
	option isolate '1'

So far so good.