Does Omega2 wireless chip support 802.11s mode?



  • I'd like to know if Omega2 supports 802.11s wireless mode for building mesh applications. What wireless driver does it use and what is iw dev command output on OpenWrt?



  • I have no experience with the WarpCore driver, which is the (proprietary) driver the official Onion FW uses.

    But if you use vanilla OpenWrt on the Omega2, the driver is mt76 which definitely does support 802.11s.

    What I don’t know, because I have little WiFi knowledge, is wether the MT7866 SoC has the needed HW to allow mt76 to support 802.11s.

    But I can provide iw dev on a Omega2 running Wifi with mt76:

    # iw dev
    phy#0
    	Interface wlan0
    		ifindex 4
    		wdev 0x2
    		addr 40:a3:6b:c1:XX:XX
    		ssid XXXXXXX
    		type AP
    		channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz
    		txpower 13.00 dBm
    		multicast TXQ:
    			qsz-byt	qsz-pkt	flows	drops	marks	overlmt	hashcol	tx-bytes	tx-packets
    			0	0	1009	0	0	0	4	377291		1109
    

    Does not look overly telling to me. But experimenting a bit with what iw has to offer I'd guess iw phy could be more interesting, especially the "mesh point" mode listing 😉

    # iw phy
    Wiphy phy0
    	max # scan SSIDs: 4
    	max scan IEs length: 2257 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)
    	Available Antennas: TX 0x1 RX 0x1
    	Configured Antennas: TX 0x1 RX 0x1
    	Supported interface modes:
    		 * IBSS
    		 * managed
    		 * AP
    		 * AP/VLAN
    		 * monitor
    		 * mesh point
    	Band 1:
    		Capabilities: 0x17e
    			HT20/HT40
    			SM Power Save disabled
    			RX Greenfield
    			RX HT20 SGI
    			RX HT40 SGI
    			RX STBC 1-stream
    			Max AMSDU length: 3839 bytes
    			No DSSS/CCK HT40
    		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
    		Minimum RX AMPDU time spacing: 4 usec (0x05)
    		HT TX/RX MCS rate indexes supported: 0-7
    		Frequencies:
    			* 2412 MHz [1] (13.0 dBm)
    			* 2417 MHz [2] (13.0 dBm)
    			* 2422 MHz [3] (13.0 dBm)
    			* 2427 MHz [4] (13.0 dBm)
    			* 2432 MHz [5] (13.0 dBm)
    			* 2437 MHz [6] (13.0 dBm)
    			* 2442 MHz [7] (13.0 dBm)
    			* 2447 MHz [8] (13.0 dBm)
    			* 2452 MHz [9] (13.0 dBm)
    			* 2457 MHz [10] (13.0 dBm)
    			* 2462 MHz [11] (13.0 dBm)
    			* 2467 MHz [12] (13.0 dBm) (no IR)
    			* 2472 MHz [13] (13.0 dBm) (no IR)
    			* 2484 MHz [14] (13.0 dBm) (no IR)
    	valid interface combinations:
    		 * #{ IBSS } <= 1, #{ managed, AP, mesh point } <= 4,
    		   total <= 4, #channels <= 1, STA/AP BI must match
    	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:
    		* [ RRM ]: RRM
    		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
    		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
    		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
    


  • Thank you! Yeah, it looks like it supports 802.11s peering. If it works in practice, that's awesome.


Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.