Gl-x750v2 with USB Wifi AWUS036ACHM

Surfer2010 · 2022-08-29T20:32:38.382Z

Hello,
I am using a gl-x750v2 Router and want to add the AWUS036ACHM WiFi as a USB device and use it to connect to known wifi available.
How can I do this?

So far I did:

opkg update
	opkg install usbutils
	opkg install kmod-mt7601u
	
	
	mkdir /lib/firmware/mediatek
	cd /lib/firmware/mediatek
	wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/mt7610u.bin

But how can I access this new Wifi Device on either the GL-Webinterface or the luci webinterface?

Thanks for your help

wcs2228 · 2022-08-29T23:44:36.604Z

The Alfa AWUS036ACHM has the MediaTek MT7610U chipset:

ALFA Network Inc.

AWUS036ACHM

AWUS036ACHM is a mini USB dual-band AC600 WiFi adapter The AWUS036ACHM USB adapter incorporates highly integrated MT7610U WLAN chipset, with support for 802.11ac standard. This device supports dual-band operation (2.4 or 5 GHz band), is backward...

Price: USD 0.00

Check if there is a package with a driver for that model.

I do not work for and I do not have formal association with GL.iNet

Surfer2010 · 2022-08-30T00:28:46.022Z

As you can read in my code section above, Already downloaded the bin file.
Now how do i continue?
Will it be shown at the webinterface?

wcs2228 · 2022-08-30T01:50:39.878Z

Your bin file download looks like for Linux and I think OpenWRT packages are different ipk files for different architectures. Maybe you can try installing using Upload Package via LuCI → System → Software.

If the driver works, then the USB wifi adapter should be detected and show up in the existing GL.iNet UI and LuCI UI.

LupusE · 2022-08-30T06:02:59.577Z

Before it will be shown anywhere it needs to be loaded.
The steps in your first post looks promising, but as said before, it is not sure the Linux .bin will work on the router, too.

Login via SSH
Type lsmod and look out for the mt7601u module.
Type iw, is the new device listed? (Try plugged in and pluged out, is there a difference?)
…

And if this fails, there is always dmesg. Sometimes a lot of input. But start the router without the Stick, plug it in and execute dmesg. If anything is missing or the bin can’t be loaded, this should appear at the very bottom of the long list.
Even if it doesn’t look at the first sight, most parts of the log are very good readable/to understand for humans.

The next steps are more GL.iNet specific. I think it will be enough to use LuCI to add the new device to the bridge LAN or something like that.

Surfer2010 · 2022-08-30T07:18:56.362Z

Thanks sounds like a good plan:
plugged in
here the output of lsmod: GobiNet 380918 0GobiSerial 7130 0act_connmark - Pastebin.com
here the output of iw: root@GL-X750:~# iwUsage: iw [options] commandOptions: --debug - Pastebin.com

Surfer2010 · 2022-08-30T07:26:25.001Z

unplugged I get the follwoing outputs
here the output of lsmod: pastebin com → rNj9zi8J
here the output of iw: pastebin com → kRnkZh4r

dsmesg plugging in and unplugging gives me this:

[57206.325361] usb 1-1.3: USB disconnect, device number 5
[57647.712673] usb 1-1.3: new high-speed USB device number 6 using ehci-platform
[57671.989335] usb 1-1.3: USB disconnect, device number 6
[57682.782681] usb 1-1.3: new high-speed USB device number 7 using ehci-platform

Surfer2010 · 2022-08-30T08:22:23.575Z

I did try to install the driver using this tutorial from openwrt (github --> morrownr How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md, but those guys told me it is no original openwrt, so they cannot help me:

here dmesg: pastebin → vPgkpJHK
and the iw-list output:

root@GL-X750:~# iw list
Wiphy phy1
        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)
        Device supports RSN-IBSS.
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2)
                * CCMP-128 (00-0f-ac:4)
                * CCMP-256 (00-0f-ac:10)
                * GCMP-128 (00-0f-ac:8)
                * GCMP-256 (00-0f-ac:9)
                * CMAC (00-0f-ac:6)
                * CMAC-256 (00-0f-ac:13)
                * GMAC-128 (00-0f-ac:11)
                * GMAC-256 (00-0f-ac:12)
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS
        Band 1:
                Capabilities: 0x11ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 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-15
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
                Frequencies:
                        * 2412 MHz [1] (23.0 dBm)
                        * 2417 MHz [2] (23.0 dBm)
                        * 2422 MHz [3] (23.0 dBm)
                        * 2427 MHz [4] (23.0 dBm)
                        * 2432 MHz [5] (23.0 dBm)
                        * 2437 MHz [6] (23.0 dBm)
                        * 2442 MHz [7] (23.0 dBm)
                        * 2447 MHz [8] (23.0 dBm)
                        * 2452 MHz [9] (23.0 dBm)
                        * 2457 MHz [10] (23.0 dBm)
                        * 2462 MHz [11] (23.0 dBm)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * start_ap
                 * new_station
                 * new_mpath
                 * set_mesh_config
                 * set_bss
                 * authenticate
                 * associate
                 * deauthenticate
                 * disassociate
                 * join_ibss
                 * join_mesh
                 * remain_on_channel
                 * set_tx_bitrate_mask
                 * frame
                 * frame_wait_cancel
                 * set_wiphy_netns
                 * set_channel
                 * set_wds_peer
                 * tdls_mgmt
                 * tdls_oper
                 * probe_client
                 * set_noack_map
                 * register_beacons
                 * start_p2p_device
                 * set_mcast_rate
                 * testmode
                 * connect
                 * disconnect
                 * channel_switch
                 * set_qos_map
                 * set_multicast_to_unicast
        Supported TX frame types:
                 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
        Supported RX frame types:
                 * IBSS: 0x40 0xb0 0xc0 0xd0
                 * managed: 0x40 0xd0
                 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * mesh point: 0xb0 0xc0 0xd0
                 * P2P-client: 0x40 0xd0
                 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * P2P-device: 0x40 0xd0
        software interface modes (can always be added):
                 * AP/VLAN
                 * monitor
        valid interface combinations:
                 * #{ 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 }

        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
        Device supports TX status socket option.
        Device supports HT-IBSS.
        Device supports SAE with AUTHENTICATE command
        Device supports low priority scan.
        Device supports scan flush.
        Device supports AP scan.
        Device supports per-vif TX power setting
        P2P GO supports CT window setting
        Driver supports full state transitions for AP/GO clients
        Driver supports a userspace MPM
        Device supports active monitor (which will ACK incoming frames)
        Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
        Device supports configuring vdev MAC-addr on create.
        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
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 RSN-IBSS.
        Device supports AP-side u-APSD.
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2)
                * CCMP-128 (00-0f-ac:4)
                * CMAC (00-0f-ac:6)
                * CMAC-256 (00-0f-ac:13)
                * GMAC-128 (00-0f-ac:11)
                * GMAC-256 (00-0f-ac:12)
        Available Antennas: TX 0x1 RX 0x1
        Configured Antennas: TX 0x1 RX 0x1
        Supported interface modes:
                 * managed
                 * AP
                 * monitor
                 * mesh point
        Band 2:
                Capabilities: 0x196f
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        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-7
                VHT Capabilities (0x33800132):
                        Max MPDU length: 11454
                        Supported Channel Width: neither 160 nor 80+80
                        RX LDPC
                        short GI (80 MHz)
                        RX antenna pattern consistency
                        TX antenna pattern consistency
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: not supported
                        3 streams: not supported
                        4 streams: not supported
                        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: not supported
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 Mbps
                Bitrates (non-HT):
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
                Frequencies:
                        * 5180 MHz [36] (23.0 dBm)
                        * 5200 MHz [40] (23.0 dBm)
                        * 5220 MHz [44] (23.0 dBm)
                        * 5240 MHz [48] (23.0 dBm)
                        * 5260 MHz [52] (23.0 dBm) (radar detection)
                        * 5280 MHz [56] (23.0 dBm) (radar detection)
                        * 5300 MHz [60] (23.0 dBm) (radar detection)
                        * 5320 MHz [64] (23.0 dBm) (radar detection)
                        * 5500 MHz [100] (23.0 dBm) (radar detection)
                        * 5520 MHz [104] (23.0 dBm) (radar detection)
                        * 5540 MHz [108] (23.0 dBm) (radar detection)
                        * 5560 MHz [112] (23.0 dBm) (radar detection)
                        * 5580 MHz [116] (23.0 dBm) (radar detection)
                        * 5600 MHz [120] (23.0 dBm) (radar detection)
                        * 5620 MHz [124] (23.0 dBm) (radar detection)
                        * 5640 MHz [128] (23.0 dBm) (radar detection)
                        * 5660 MHz [132] (23.0 dBm) (radar detection)
                        * 5680 MHz [136] (23.0 dBm) (radar detection)
                        * 5700 MHz [140] (23.0 dBm) (radar detection)
                        * 5720 MHz [144] (23.0 dBm) (radar detection)
                        * 5745 MHz [149] (30.0 dBm)
                        * 5765 MHz [153] (30.0 dBm)
                        * 5785 MHz [157] (30.0 dBm)
                        * 5805 MHz [161] (30.0 dBm)
                        * 5825 MHz [165] (30.0 dBm)
                        * 5845 MHz [169] (disabled)
                        * 5865 MHz [173] (disabled)
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * start_ap
                 * new_station
                 * new_mpath
                 * set_mesh_config
                 * set_bss
                 * authenticate
                 * associate
                 * deauthenticate
                 * disassociate
                 * join_ibss
                 * join_mesh
                 * remain_on_channel
                 * set_tx_bitrate_mask
                 * frame
                 * frame_wait_cancel
                 * set_wiphy_netns
                 * set_channel
                 * set_wds_peer
                 * probe_client
                 * set_noack_map
                 * register_beacons
                 * start_p2p_device
                 * set_mcast_rate
                 * testmode
                 * connect
                 * disconnect
                 * channel_switch
                 * set_qos_map
                 * set_multicast_to_unicast
        Supported TX frame types:
                 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
        Supported RX frame types:
                 * IBSS: 0x40 0xb0 0xc0 0xd0
                 * managed: 0x40 0xd0
                 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * mesh point: 0xb0 0xc0 0xd0
                 * P2P-client: 0x40 0xd0
                 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * P2P-device: 0x40 0xd0
        software interface modes (can always be added):
                 * monitor
        valid interface combinations:
                 * #{ AP, mesh point } <= 8, #{ managed } <= 1,
                   total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 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
        Device supports TX status socket option.
        Device supports HT-IBSS.
        Device supports SAE with AUTHENTICATE command
        Device supports scan flush.
        Device supports AP scan.
        Device supports per-vif TX power setting
        Driver supports full state transitions for AP/GO clients
        Driver supports a userspace MPM
        Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
        Device supports static SMPS
        Device supports configuring vdev MAC-addr on create.
        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

LupusE · 2022-08-30T10:17:47.523Z

Okay, looks good so far. I’ve hat iwconfig in my mind, that’s why I was somewhat confused at the beginning.
Only 54 Mbps? Is is a BG only stick?

Could you give is the output of the command iw dev? (or iwconfig, but I will be too lazy to read it all).

I expect something like:

root@GL-AXT1800:~# iw dev
phy#1
	Interface wlan1
		ifindex 11
		wdev 0x100000002
		addr 00:03:7f:xx:xx:xx
		ssid GL-AXT1800-xxx
		type AP
		channel 6 (2437 MHz), width: 20 MHz, center1: 2437 MHz
		txpower 20.00 dBm

And in the next step we could try to assign it.

http://192.168.8.1/cgi-bin/luci
User: root, Password: Your individual password

The page ‘Network - Interfaces - Tab: Devices’ says for the option ‘Bridge ports’:

Specifies the wired ports to attach to this bridge. In order to attach wireless networks, choose the associated interface as network in the wireless settings.

In ‘Network - Wireless’ with the Button [Edit] at the device, at ‘Interface Configuration’ I can see the Option ‘Network’, with the value ‘LAN’ …

I do tink this is what you are searching, But I don’t have a USB WLAN device with me and checked it on the AXT-1800 (Slate AX) with Firmware 4.0.2 (Kernel 5.4) … So it could be somewhat different at your device.

wcs2228 · 2022-08-30T19:41:18.951Z

I have a USB wifi adapter with MediaTek MT7612U chipset (maybe similar to MT7610U) that works on 2 of my GL.iNet routers.

For reference, here is what dmesg (Kernel Log) shows when I plug it in:

MT7612u-11713×415 163 KB

Here is what lsusb and lsusb -t shows:

image1920×285 45.1 KB

The package is kmod-mt76x2u and the driver name is displayed as bound to the device if it works. The adapter does not show up in the Gl,.iNet UI, so I have to use the LuCI UI for configuration via LuCI → System → Wireless.

Surfer2010 · 2022-08-30T21:25:49.700Z

Thanks that helped a lot!!!

wcs2228 · 2022-08-31T00:30:09.979Z

Here is what LuCI → System → Wireless shows after the MT7612U USB wifi adapter has been configured with radio2 as an access point with SSID MT7612U (Master)

MT7612U-32376×1456 396 KB

Surfer2010 · 2022-08-31T18:53:07.813Z

I would want to have it as a “backup” so if there is no LTE, it should connect to a known wifi best would be from a list of known wifis

wcs2228 · 2022-08-31T19:35:25.504Z

To configure the USB wifi adapter as a Client (a.k.a. Station), click on the Scan button for radio2 (instead of the Add button) which will then display and let you chose from the list of SSID’s that you can connect to.

You will have to change the connection priorities so that LTE takes priority over wifi.

GL-AX1800 (Flint) - Change Connection Order Technical Support for Routers

You can edit the /etc/config/mwan3 by logging in via SSH, or install the luci-app_mwan3 package that adds the function LuCI → Network → Load Balancing. Also, check the metric values in /etc/config/network to follow the same priority. The config files are “usually” not overwritten on firmware update, but it depends on the nature and compatibility of the new firmware. I do not work for and I do not have formal association with GL.iNet