Troubles setting up guest WiFi in 19.02 according to guide

rjb · April 5, 2020, 12:11pm

Dear community

I tried setting up the guest WiFi according to this tutorial: https://openwrt.org/docs/guide-user/network/wifi/guestwifi/configuration

While this worked well for 18.06, in 19.02 either 2.4 GHz or 5 GHz with same SSID would work only, while for the other frequency the clients couldn't connect successfully.
It seems that it's depending on which physical interface is selected in the guest interface. In my case, if it is wlan0-1, clients would only be able to connect to 5 GHz network and if it is wlan1-1, clients would only be able to connect to the 2.4 GHz network.

As a side note, there seems to be a little issue with this configuration line of the tutorial:
set firewall.${FW_ZONE}_dns.proto=tcp udp
After reloading the firewall there is a message similar to: no protocol defined, assuming TCP/UDP.
After pasting the commands I corrected this in the GUI. However, this is not causing the issues described above.

trendy · April 5, 2020, 4:52pm

Could you post the wireless configuration that has the problem?
uci export wireless

rjb · April 5, 2020, 5:18pm

Sure, here it is. It is about the wifi interfaces wifinet2 and wifinet3:

config wifi-device 'radio0'
	option type 'mac80211'
	option hwmode '11a'
	option path 'soc/1b500000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
	option country 'CH'
	option htmode 'VHT160'
	option channel 'auto'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'WiNet'
	option encryption 'psk2'
	option wpa_disable_eapol_key_retries '1'
	option ieee80211w '1'
	option key 'xxxxx'

config wifi-device 'radio1'
	option type 'mac80211'
	option hwmode '11g'
	option path 'soc/1b700000.pci/pci0001:00/0001:00:00.0/0001:01:00.0'
	option country 'CH'
	option htmode 'HT40'
	option channel 'auto'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid 'WiNet'
	option encryption 'psk2'
	option wpa_disable_eapol_key_retries '1'
	option ieee80211w '1'
	option key 'xxxxx'

config wifi-iface 'wifinet2'
	option ssid 'WiNetGuest'
	option encryption 'psk2'
	option device 'radio0'
	option isolate '1'
	option key 'yyyyy'
	option mode 'ap'
	option wpa_disable_eapol_key_retries '1'
	option ieee80211w '1'
	option network 'guest'

config wifi-iface 'wifinet3'
	option ssid 'WiNetGuest'
	option encryption 'psk2'
	option device 'radio1'
	option isolate '1'
	option key 'yyyyy'
	option mode 'ap'
	option wpa_disable_eapol_key_retries '1'
	option ieee80211w '1'
	option network 'guest'

trendy · April 5, 2020, 6:11pm

From what I see you have both guest interfaces same as the lan interfaces, minus the isolation. I hope I didn't miss anything.
For WiNet ssid everything works fine for both frequencies, but in WiNetGuest

I don't quite understand that. Both wifi interfaces for guest are configured for both frequencies.

Also, better assign a channel yourself, rather than leaving it to auto.
Test with lower bandwidth, like VHT80 on 5GHz
During upgrade from 18.06 to 19.07 did you keep settings or started from scratch?

rjb · April 6, 2020, 6:05pm

The device has been set up from scratch. Actually, the VHT160 with auto channel setting will always take channel 100 at 80 MHz on my device, so no issue for me there.

But there is something really strange in the guest interface settings and wifi settings.
The GUI does some strange stuff. It doesn't really like to put

option network 'guest'

on both guest interfaces. If you restart a radio from the GUI it would always remove this line if there is one for each guest wifi interface.
At the same time, within guest interface in the GUI, in physical interface section, the value would change accordingly between wlan0-1 and wlan1-1.

And even if you make sure both guest wifi interfaces have that line, only one of them would work properly.

trendy · April 6, 2020, 7:01pm

Can you paste the iw info? Maybe there is some limitation in hardware.

rjb · April 6, 2020, 9:35pm

you probably mean iw list, correct?
I would be surprised if it was a hardware limitation as it had been working in 18.06.

Wiphy phy1
	max # scan SSIDs: 16
	max scan IEs length: 195 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Available Antennas: TX 0xf RX 0xf
	Configured Antennas: TX 0xf RX 0xf
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
		 * P2P-device
	Band 1:
		Capabilities: 0x19ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-31
		VHT Capabilities (0x339b79b2):
			Max MPDU length: 11454
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
			SU Beamformer
			SU Beamformee
			MU Beamformer
			MU Beamformee
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			4 streams: MCS 0-9
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			4 streams: MCS 0-9
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		Frequencies:
			* 2412 MHz [1] (20.0 dBm)
			* 2417 MHz [2] (20.0 dBm)
			* 2422 MHz [3] (20.0 dBm)
			* 2427 MHz [4] (20.0 dBm)
			* 2432 MHz [5] (20.0 dBm)
			* 2437 MHz [6] (20.0 dBm)
			* 2442 MHz [7] (20.0 dBm)
			* 2447 MHz [8] (20.0 dBm)
			* 2452 MHz [9] (20.0 dBm)
			* 2457 MHz [10] (20.0 dBm)
			* 2462 MHz [11] (20.0 dBm)
			* 2467 MHz [12] (20.0 dBm)
			* 2472 MHz [13] (20.0 dBm)
			* 2484 MHz [14] (disabled)
	valid interface combinations:
		 * #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
		   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }

	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Supported extended features:
		* [ VHT_IBSS ]: VHT-IBSS
		* [ RRM ]: RRM
		* [ SET_SCAN_DWELL ]: scan dwell setting
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
Wiphy phy0
	max # scan SSIDs: 16
	max scan IEs length: 199 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Available Antennas: TX 0xf RX 0xf
	Configured Antennas: TX 0xf RX 0xf
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
		 * P2P-device
	Band 2:
		Capabilities: 0x19ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-31
		VHT Capabilities (0x339b79fa):
			Max MPDU length: 11454
			Supported Channel Width: 160 MHz, 80+80 MHz
			RX LDPC
			short GI (80 MHz)
			short GI (160/80+80 MHz)
			TX STBC
			SU Beamformer
			SU Beamformee
			MU Beamformer
			MU Beamformee
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			4 streams: MCS 0-9
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 1560 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			4 streams: MCS 0-9
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 1560 Mbps
		Frequencies:
			* 5180 MHz [36] (20.0 dBm) (radar detection)
			* 5200 MHz [40] (20.0 dBm) (radar detection)
			* 5220 MHz [44] (20.0 dBm) (radar detection)
			* 5240 MHz [48] (20.0 dBm) (radar detection)
			* 5260 MHz [52] (20.0 dBm) (radar detection)
			* 5280 MHz [56] (20.0 dBm) (radar detection)
			* 5300 MHz [60] (20.0 dBm) (radar detection)
			* 5320 MHz [64] (20.0 dBm) (radar detection)
			* 5500 MHz [100] (27.0 dBm) (radar detection)
			* 5520 MHz [104] (27.0 dBm) (radar detection)
			* 5540 MHz [108] (27.0 dBm) (radar detection)
			* 5560 MHz [112] (27.0 dBm) (radar detection)
			* 5580 MHz [116] (27.0 dBm) (radar detection)
			* 5600 MHz [120] (27.0 dBm) (radar detection)
			* 5620 MHz [124] (27.0 dBm) (radar detection)
			* 5640 MHz [128] (27.0 dBm) (radar detection)
			* 5660 MHz [132] (27.0 dBm) (radar detection)
			* 5680 MHz [136] (27.0 dBm) (radar detection)
			* 5700 MHz [140] (27.0 dBm) (radar detection)
			* 5720 MHz [144] (disabled)
			* 5745 MHz [149] (disabled)
			* 5765 MHz [153] (disabled)
			* 5785 MHz [157] (disabled)
			* 5805 MHz [161] (disabled)
			* 5825 MHz [165] (disabled)
			* 5845 MHz [169] (disabled)
			* 5865 MHz [173] (disabled)
	valid interface combinations:
		 * #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
		   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }

	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Supported extended features:
		* [ VHT_IBSS ]: VHT-IBSS
		* [ RRM ]: RRM
		* [ SET_SCAN_DWELL ]: scan dwell setting
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs

trendy · April 6, 2020, 9:58pm

Right, my wrong.
Hardware supports 16 SSIDs so this is not the issue either.
Unfortunately no more ideas from me

rjb · April 7, 2020, 3:22pm

anyhow, thanks a lot for your effort.
As new information I could add that usually the next morning it will be in a state where only 2.4 GHz clients can connect. By restarting the guest interface the 5 GHz clients can connect (but not the 2.4 GHz clients).
When i say 2.4 GHz clients I mean clients that can use 2.4 GHz only (802.11g).
5 GHz clients are those that are able to use both frequency ranges.

There is also some differences between clients. While 2.4 GHz devices are able to connect, my Android phone can't connect - it probably tries to connect to 5 GHz only, if both are available with strong signal.
A Windows laptop will connect, but shows "no internet".