So far I am finding that Shadow does not want to bring up the wireless LAN when I try to boot with a MT7610U dongle plugged in, and kmod-76x0u installed. Going to have to drag out ethernet cables etc. I’ll update this post with my findings.
Here’s a sequence of events that happened while testing Shadow with latest stable GL-inet firmware and the MT7610U dongle:
- Factory reset Shadow, plug its WAN port into internet and my laptop into its LAN port with Ethernet cables (the idea being to avoid touching any wifi settings until the MT7610U device is plugged in), and power it up without MT7610U device plugged in
- Set a root password
- install Luci
- in Luci, install (without updating package lists … using what’s already there presumably from us installing Luci in the previous step)
kmod-mt76x0u
- power cycle the router without MT7610U device installed to see if it comes up and brings the built-in radio up
- it brings the built-in radio up
- power off the router and plug in the MT7610U dongle
- power up the router
- it comes up but does not bring either radio up
- Luci now sees both radios, interesting values are as follows
radio0
Type: 80211bgn
Bitrate: -
SSID: GL-AR300m-7a3
Mode: Master
BSSID: -
Encryption: -
Associations: -
radio1
Type: 801.11bgnac
Bitrate: -
SSID: OpenWRT
Mode: Master
Wireless is disabled
Log tidbits:
```
Wed Aug 10 22:41:21 2022 kern.info kernel: [ 29.547372] mt76x0u 1-1:1.0: ASIC revision: 76100002 MAC revision: 76502000
Wed Aug 10 22:41:21 2022 kern.info kernel: [ 30.720378] mt76x0u 1-1:1.0: EEPROM ver:02 fae:01
Wed Aug 10 22:41:21 2022 kern.debug kernel: [ 31.197181] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Wed Aug 10 22:41:21 2022 kern.info kernel: [ 31.199053] usbcore: registered new interface driver mt76x0u
Wed Aug 10 22:41:21 2022 kern.debug kernel: [ 31.374528] ath: EEPROM regdomain: 0x0
Wed Aug 10 22:41:21 2022 kern.debug kernel: [ 31.374538] ath: EEPROM indicates default country code should be used
Wed Aug 10 22:41:21 2022 kern.debug kernel: [ 31.374541] ath: doing EEPROM country->regdmn map search
Wed Aug 10 22:41:21 2022 kern.debug kernel: [ 31.374558] ath: country maps to regdmn code: 0x3a
Wed Aug 10 22:41:21 2022 kern.debug kernel: [ 31.374564] ath: Country alpha2 being used: US
Wed Aug 10 22:41:21 2022 kern.debug kernel: [ 31.374567] ath: Regpair used: 0x3a
Wed Aug 10 22:41:21 2022 kern.debug kernel: [ 31.388120] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Wed Aug 10 22:41:21 2022 kern.info kernel: [ 31.390054] ieee80211 phy1: Atheros AR9531 Rev:2 mem=0xb8100000, irq=13
Wed Aug 10 22:41:21 2022 user.info kernel: [ 31.422048] kmodloader: done loading kernel modules from /etc/modules.d/*
Wed Aug 10 22:41:31 2022 daemon.notice procd: /etc/rc.d/S30gl_ssids: uci: Entry not found
Wed Aug 10 22:41:31 2022 daemon.notice procd: /etc/init.d/gl_ssids: uci: Entry not found
Wed Aug 10 22:41:32 2022 daemon.notice procd: /etc/rc.d/S36gl_route_policy: uci: Entry not found
Wed Aug 10 22:41:43 2022 kern.info kernel: [ 56.505001] eth0: link up (100Mbps/Full duplex)
Wed Aug 10 22:41:44 2022 daemon.notice netifd: wan (2330): udhcpc: started, v1.30.1
Wed Aug 10 22:41:44 2022 daemon.notice netifd: radio0 (2092): command failed: Too many open files in system (-23)
Wed Aug 10 22:41:44 2022 user.notice mac80211: Failed command: iw phy phy1 interface add wlan0 type __ap
Wed Aug 10 22:41:44 2022 daemon.notice netifd: wan (2330): udhcpc: sending discover
```
Perhaps the built-in wifi chip is being detected as phy1 instead of phy0 and then GL-inet firmware is getting confused?
At this point I gave up and decided to try vanilla OpenWrt in the hopes of improved drivers. The Shadow does boot up just fine and recognize my MT7610U dongle with kmod-mt76x0u installed.
After verifying that, I ran directly into the fact that I don’t actually know how to set up a second radio and get it to act just like GL-inet “repeater” mode in OpenWRT, and it was quite late, so I will have to continue later.
In this case, Shadow is to be a travel router for me, so if I can get a stable & reliable connection using a MT76xxU based USB device as the client radio, the next questions will be, how easy is OpenVPN to setup in vanilla OpenWRT, and how resilient / user friendly will vanilla OpenWRT be about being a travel router. But I suppose that’s for a different thread.