Collect information about wireless features from supported devices

Hardware Questions and Recommendations
1

I would like to launch this thread related to another question I had on this forum:

Basically it would be interesting for someone looking for a new hardware device that supports OpenWRT to know with certainty what are the wireless capabilities of the device.

So my question/suggestion would be that as many people as possible that are running OpenWRT on any supported device reply to this thread with the output of the command "iw list" and of course the information which device they are using.

Would be interesting to have this thread as a kind of knowledge base for wifi-capabilities of devices, showing information such as does the device support 802.11s mesh, how many SSID's does the device support on the 2.4GHz and the 5 GHz band, ...

2

Ok, to get this started, stuff currently on my test network....
Edit: Get the wireless chip from the output of iwinfo

Model GL-MT6000, MediaTek MT7986:

iw list | grep -A 3 "valid interface combinations"
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
		   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }

--
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
		   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }

Model GL-MT300N-V2, MediaTek MT7628:

iw list | grep -A 3 "valid interface combinations"
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 4,
		   total <= 4, #channels <= 1, STA/AP BI must match

Model GL-MT1300, MediaTek MT7615E:

iw list | grep -A 3 "valid interface combinations"
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 16,
		   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 }

--
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 16,
		   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 }

GL-MT3000, MediaTek MT7981:

iw list | grep -A 3 "valid interface combinations"
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
		   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }

--
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
		   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }

GL-A1300, Qualcomm Atheros IPQ4019 (non-ct drivers):

iw list | grep -A 3 "valid interface combinations"
	valid interface combinations:
		 * #{ managed } <= 1, #{ AP, mesh point } <= 16,
		   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 }

--
	valid interface combinations:
		 * #{ managed } <= 1, #{ AP, mesh point } <= 16,
		   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 }

I can probably find some more....

1 Like
3

@efahl @brada4 @psherman @Hostle @frollic @lleachii
What do you guys have on your desks?

Edit: Adding a few more of the "usual suspects" :wink:
@_bernd @hecatae @apccv @appelsin

1 Like
4

@richb-hanover-priv
Here is an idea for you :wink:

5

On my desks are nothing interesting...

  • Linksys E7350 (at work)
  • GL-inet MT3000
  • Raspberry Pi 4 (not using wifi, wouldn't be worth it anyway)
  • Ubiquiti RouterStation Pro, no wifi installed
  • TP-Link TL-WR902ACv1
  • Linksys EA6300 (useless for wifi -- brcm53xx)
  • Linksys E3000 (useless for wifi -- brcm47xx)
  • TP-Link TL-MR3020v1 (obsolete)
1 Like
6

Asus ac88u (scavenged from Asus RT-AC88U only 1 device per radio can be enabled ) - brcmfmac survey kills multi-ap-ness

        valid interface combinations:
                 * #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
                   total <= 3, #channels <= 1
                 * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
                   total <= 4, #channels <= 1
                 * #{ AP } <= 4,
                   total <= 4, #channels <= 1, STA/AP BI must match
1 Like
7

WRX36 (which I noticed wasn't sold on Amazon any more), and EX5601/T-56, but Im guessing it's the same as the GL-MT6000.

Got some old ASUS Lyra MAP-AC2200s in a drawer, and LN1301s, but they're not running Openwrt.

Trendnet TEW-823 and one more, I don't recall atm :slight_smile:

1 Like
8

Wireless devices? Nothing of interest, except maybe my AP:

  • Archer C7 v4, really old
  • Belkin RT3200, old
  • Zyxel NWA50AX Pro

Here's the Zyxel MT7981B, so looks the same as your GL-MT3000.

valid interface combinations:
 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }
--
valid interface combinations:
 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }
1 Like
9

On the desk there's a mess and a cat.
Around but unplugged some ath79 I was testing on. Some other non-OpenWrt here or there.
Been working on ipq806x for the AppleTalk stuff. The Snapshot builds didn't get FW during the build but if you think you could use that I'll add it. This is a 23.05:

root@TestWrt-64:~# iw list | grep -A 3 "valid interface combinations"
	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 }
--
	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 }

Access points are MT6000:

root@AP1:~# iw list | grep -A 3 "valid interface combinations"
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
		   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }
--
	valid interface combinations:
		 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
		   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }

That helps?

1 Like
10

Did you have asked the various wireless community networks out there?
IIRC the italian one in pisa is >20k nodes in total; berlin has a dedicated backbone network; in spain are a bunch of small/local one, @nemesis is involved with them IIRC; the battlemesh (the wireless battle of the mesh) brings them together, so reach out to them, etc pp I assume there you can get a bunch of data and get information about the capabilities of the various devices in actually use out there.

11

@bluewavenet
Mercusys MR90x
Meraki MR18
Meraki MR42
Meraki MR12
Openmesh om2p
Openmesh om5p
Meraki Z1
GL inet Beryl AX
Linksys WHW03
Netgear Orbi SRR60
GL inet B2200
Unifi AC lite
Tplink ax23
GL inet Mango mt300n v2

That's all the wireless stuff I have running actual Openwrt in the vicinity of my desk.

But I am curious where @jefkebazaar wants to store all the iw list information.
Do they want it added to the wiki, as it's going to get buried on here and some of it's already available, for example the Meraki MR18 is well documented as having two 5ghz and one 2.4ghz radios, but one of the 5ghz radios is hardware crippled by Meraki as it was designed to be a optimization sniffer.

1 Like
12

Netgear WAX202

root@OpenWrt:~# iw list | grep -A 3 "valid interface combinations"
        valid interface combinations:
                 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
                   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }

--
        valid interface combinations:
                 * #{ IBSS } <= 1, #{ AP, mesh point } <= 16, #{ managed } <= 19,
                   total <= 19, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 160 MHz }

I'll post others when I can.

1 Like
13

7628 idem max 4/8
7621 idem max 19

Archer C7 V5 (EU)
ath9k

                 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

ath10k mainline idem max 8

usb mt7610u

                 * #{ IBSS } <= 1, #{ managed, AP, mesh point, P2P-client, P2P-GO } <= 2,
                   total <= 2, #channels <= 1, STA/AP BI must match
1 Like
14

Yes indeed. Tagging @richb-hanover as he had been doing some work on the wiki. Failing that I might have a go myself as time permits.

15

Same here :smiley:
What does iwinfo return for hardware?

16

F-k the hw, what about the cat ?

3 Likes
17

Asked and Answered?
*How OpenWrt Vanquishes Bufferbloat
*Collect information about wireless features from supported devices
*Crowd-sourcing the Wi-Fi Chip info

1 Like
18

Nope, no answers there.
What we are looking for is "Wireless Soc/chip" vs "valid interface combinations", ie how many logical interfaces/types are supported - unless I missed something in those links...

19

Please consider documenting these things on the corresponding device pages in the wiki, posting it in this thread will quickly become unusable. As observed in Please run iperf3 -c 127.0.0.1 and post results here to make router database, which is useless to begin with - and even more so in the form of that monster thread no one will ever read (or search).

2 Likes
20

Oh you've reminded me to update the results for 24.10 on there. :upside_down_face:

1 Like