i'd to use 802.11r with OpenWRT 22.03.06
I configured the settings with LUCI and tested with different settings.
No client use Fast Transistion on my wireless network (iPhone SE-2, Huawei P20Pro or Windows 10 Laptop with supported Intel Wifi Chip).
I have 3 different SSID Wifi Networks with 3 Network Vlan. Wifi works with no Problems.
Every Wifi Access Point get its own Nas Identifier and R0 Key Holder.
What is wrong in my setup? Is 802.11r supported with multiple SSID ?
Hi, I suggest you upgrade to 23.05 as it has had improvements for 802.11r, including a new dedicated WLAN roaming tab on the wifi interface configuration page, which IIRC wasn't there on 22.03:
That said, I'm not seeing 802.11r related configuration on your wifi interfaces, this is what I have on mine configured with the above tab (looking at a 22.03 backup this was there also):
It doesn't look like this device is supported in 23.05, so 22.03.6 is probably the end of the line in terms of OpenWrt supported versions.
That said, I see a bunch of things in your network config that just don't look quite right. If disabling 802.11r doesn't solve the problem, we should revisit your network config (I'd actually suggest resetting to defaults and then building back up -- this will be much easier than fixing the issues).
Hi, Thank you very much for your answer. I know, that 22. 03 is the last supported Version.
This network config was the only way, get tagged vlan based on 802.1q Standard working.
The Problem is the architecture of the Board. But all vlan are working perfect. Every interface is reachable
What is your recommendation for the network config?
Typically the vlan is sequential (1, 2, 3...). If the vid is not specified, the VLAN ID will be the same. If a different VLAN ID is desired, that's when you use vid. What's unusual here is that you have non-sequential vlan and then a different vid -- this is true for all your VLANs.
Since you already have the switch config setup accordingly, you don't actually need the 802.1q stanzas.
The option type bridge should not be specified in the network interface stanza. Instead, it should be a seperate device definition like this:
config device
option name 'br-vlan1101'
option type 'bridge'
list ports 'eth1.101'
config interface 'lan1101'
option device 'br-vlan1101'
option proto 'static'
option ipaddr '192.168.12.4'
option netmask '255.255.255.0'
option gateway '192.168.12.1'
Also, for a dumb AP, it is best practice to only have an address on one interface -- that would be the one that is used to manage the device (i.e. a trusted lan or management network). The others should be unmanaged (note that I used the same br-vlanxxxx type device in the interface as I showed above):
config interface 'lan1103'
option device 'br-vlan1103'
option proto 'none'
WPJ419 is 'only' missing the DSA conversion, that should be doable - and coincidentally that would make VLANs on ipq40xx much easier…
Yes, the device currently is supported, but there is nothing fundamentally in the way of getting it supported again in the future, if someone with the device spends the development time needed on it to get it ported over to DSA. Yes, it needs works - and it needs work urgently, but it's not doomed.