On a whim, I’d plugged in my 2.5Gbit USB Ethernet adaptor, a Realtek 8156 device (a “Plugable” I’d gotten from Amazon), and it’s recognized in “Tethering” as “USB0 (Android)”.
I plugged in my QNAP 5Gbit USB Ethernet adaptor (Aquanta chipset) and it was recognized in “Tethering” as “USB3 (iOS)”
What’s nice is now that I’ve lost an Ethernet port on the Brume and AXT1800 I can use this to replace the WAN port if I switch the Ethernet WAN to LAN- but now I wish I were where my Fiber internet is to see if I can get 2.5/5G bit thruput!
The USB port on the AXT1800 is USB3 (5Gbit), right? There’s no “lsusb” for me to tell via SSH.
I have tested with Realtek 8153 and Axis AX88179 (most common gigabit ethernet to usb 3.0 adapters) and no effect.
My realtek are (1: Vention usb-c hub 9-1, 2: Generic dongle usb-ethernet):
root@GL-AXT1800:~# lsusb
Bus 002 Device 003: ID 0bda:8153 Realtek USB 10/100/1000 LAN
root@GL-AXT1800:~# lsusb
Bus 001 Device 006: ID 0bda:8153 Realtek USB 10/100/1000 LAN
My axis is (Generic dongle usb-ethernet):
root@GL-AXT1800:~# lsusb
Bus 002 Device 005: ID 0b95:1790 ASIX Elec. Corp. AX88179
For Realtek 8153 you need kmod-usb-net-rtl8152, but not compiled for cortex-a7
For Axis AX88179 you need kmod-usb-net-asix-ax88179, but again not compiled.
Both my Linksys USB3GIG and TP-Link UE330 USB GbE adapters work for tethering, with both having Realtek RTL8153 chipset.
The TP-Link UE330 has a built-in 3-Port Hub and I can plug the Linksys USB3GIG into the hub. Both adapters are detected and work for tethering (one at a time). WOW!
Same. Just plugged them in. I also have a combo USB hub/Ethernet port I use on my Amazon Fire Sticks, I’ll have to see if this works as well (it should, it’s a RealTek 815[23] GigE device). If this works, this will solve the problem/bug where if I’ve got an Ethernet connected and has a lease, I can’t disconnect it via the UI; this way I can switch between (potentially slower) hotel Ethernet and my LTE Router via the UI.
root@GL-AXT1800:~# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=, Driver=cdc_ncm, 5000M
|__ Port 1: Dev 2, If 1, Class=, Driver=cdc_ncm, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
root@GL-AXT1800:~#
Ah- thanks! I know the port is blue and the label says “3.0”, but it’s nice to be sure.
And, now I know why 2.5GBit (and only a 1GBit) adaptors are supported in Beta8, and some are not- notice that’s the CDC-NCM driver, and not the RealTek driver. Now I wonder if I’m connected in Full-Duplex mode (many RealTek devices don’t connect in FDX when connected via CDC-NCM).
root@GL-AXT1800:~# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 4, If 0, Class=, Driver=hub/4p, 5000M
|__ Port 4: Dev 5, If 0, Class=, Driver=, 5000M
|__ Port 4: Dev 5, If 1, Class=, Driver=, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 1: Dev 4, If 0, Class=, Driver=hub/4p, 480M
root@GL-AXT1800:~# lsusb
Bus 002 Device 005: ID 0bda:8153 Realtek USB 10/100/1000 LAN
Bus 002 Device 004: ID 2109:0815 VIA Labs, Inc. USB3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux 4.4.60 xhci-hcd xHCI Host Controller
Bus 001 Device 004: ID 2109:2815 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux 4.4.60 xhci-hcd xHCI Host Controller
So I guess a feature request is @alzhao “Please build the r8152.ko kernel module as well in the next Beta”
Good news- I’m running the “Stable 4.0.0” and was able to load the kmod-usb-net-rtl8152 okpg today and can now see one of the combo USB3 Net/Hub adaptors I have (specifically this one: https://www.amazon.com/dp/B01J6583NK). I also now have my Netgear hotspot plugged into one of the ports on the same hub, and can now switch between Ethernet and Tethering(HS) via the WebUI.
So, a couple of requests for the GL-iNet team (@alzhao et al.):
Could we get the kmod-usb-net-rtl8152 opkg built into the router?
Could we just get a way to switch off Ethernet from the UI, even if it’s connected (so we don’t have to resort to such hacks in the first place? )
I’m going to test USB-interface thruput later, but as 99% of the time I’m on the road I’m limited to 100MBit thruput or less (even if I stumble upon GbE link speed), I’m not too worried about it with the processor in the AX.
My results are a bit mixed. Tested 4 devices. Individual usb-a to gigabit ethernet seems to work ok, more or less. But no result with usb-c hubs with ethernet adapter. With more detail:
Usb-a to gigabit ethernet with Realtek RTL8153 works ok.
Usb-a to gigabit ethernet with Axis AX88179 works ok, but intermitent. So not usable.
Tue Jun 7 21:29:43 2022 kern.info kernel: [ 141.134782] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
Tue Jun 7 21:29:43 2022 kern.info kernel: [ 141.548980] ax88179_178a 2-1:1.0 eth3: register 'ax88179_178a' at usb-xhci-hcd.0.auto-1, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c7:9e:64:25
Tue Jun 7 21:29:44 2022 daemon.notice netifd: Interface 'tethering' is enabled
Tue Jun 7 21:29:46 2022 kern.info kernel: [ 144.349776] ax88179_178a 2-1:1.0 eth3: ax88179 - Link status is: 1
Tue Jun 7 21:29:46 2022 daemon.notice netifd: Network device 'eth3' link is up
Tue Jun 7 21:29:46 2022 daemon.notice netifd: Interface 'tethering' has link connectivity
Tue Jun 7 21:29:46 2022 daemon.notice netifd: Interface 'tethering' is setting up now
Tue Jun 7 21:29:46 2022 daemon.notice netifd: tethering (8649): udhcpc: started, v1.33.1
Tue Jun 7 21:29:46 2022 daemon.notice netifd: tethering (8649): udhcpc: sending discover
Tue Jun 7 21:29:49 2022 daemon.notice netifd: tethering (8649): udhcpc: sending discover
Tue Jun 7 21:29:49 2022 daemon.notice netifd: tethering (8649): udhcpc: sending select for 192.168.8.134
Tue Jun 7 21:29:49 2022 daemon.notice netifd: tethering (8649): udhcpc: lease of 192.168.8.134 obtained, lease time 43200
Tue Jun 7 21:29:50 2022 daemon.info avahi-daemon[3600]: Joining mDNS multicast group on interface eth3.IPv4 with address 192.168.8.134.
Tue Jun 7 21:29:50 2022 daemon.info avahi-daemon[3600]: New relevant interface eth3.IPv4 for mDNS.
Tue Jun 7 21:29:50 2022 daemon.info avahi-daemon[3600]: Registering new address record for 192.168.8.134 on eth3.IPv4.
Tue Jun 7 21:29:50 2022 daemon.notice netifd: Interface 'tethering' is now up
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: reading /tmp/resolv.conf.d/resolv.conf.auto
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: using only locally-known addresses for domain test
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: using only locally-known addresses for domain onion
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: using only locally-known addresses for domain localhost
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: using only locally-known addresses for domain local
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: using only locally-known addresses for domain invalid
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: using only locally-known addresses for domain bind
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: using only locally-known addresses for domain lan
Tue Jun 7 21:29:50 2022 daemon.info dnsmasq[6172]: using nameserver 192.168.8.1#53
Tue Jun 7 21:29:50 2022 user.notice mwan3[8695]: Execute ifup event on interface tethering (eth3)
Tue Jun 7 21:29:51 2022 user.notice mwan3[8695]: Starting tracker on interface tethering (eth3)
Tue Jun 7 21:29:54 2022 user.info mwan3rtmon[3419]: Detect rtchange event.
Tue Jun 7 21:30:36 2022 user.notice firewall: Reloading firewall due to ifup of tethering (eth3)
Tue Jun 7 21:31:09 2022 user.info mwan3track[9068]: Check (ping) failed for target "8.8.4.4" on interface tethering (eth3)
Tue Jun 7 21:31:11 2022 user.info mwan3track[9068]: Check (ping) failed for target "8.8.8.8" on interface tethering (eth3)
Tue Jun 7 21:31:13 2022 user.info mwan3track[9068]: Check (ping) failed for target "208.67.222.222" on interface tethering (eth3)
Tue Jun 7 21:31:15 2022 user.info mwan3track[9068]: Check (ping) failed for target "208.67.220.220" on interface tethering (eth3)
Tue Jun 7 21:31:22 2022 user.info mwan3track[9068]: Check (ping) failed for target "8.8.4.4" on interface tethering (eth3)
Tue Jun 7 21:31:24 2022 user.info mwan3track[9068]: Check (ping) failed for target "8.8.8.8" on interface tethering (eth3)
Tue Jun 7 21:31:26 2022 user.info mwan3track[9068]: Check (ping) failed for target "208.67.222.222" on interface tethering (eth3)
Tue Jun 7 21:31:28 2022 user.info mwan3track[9068]: Check (ping) failed for target "208.67.220.220" on interface tethering (eth3)
Tue Jun 7 21:31:35 2022 user.info mwan3track[9068]: Check (ping) failed for target "8.8.4.4" on interface tethering (eth3)
Tue Jun 7 21:31:37 2022 user.info mwan3track[9068]: Check (ping) failed for target "8.8.8.8" on interface tethering (eth3)
Tue Jun 7 21:31:39 2022 user.info mwan3track[9068]: Check (ping) failed for target "208.67.222.222" on interface tethering (eth3)
Tue Jun 7 21:31:41 2022 user.info mwan3track[9068]: Check (ping) failed for target "208.67.220.220" on interface tethering (eth3)
Tue Jun 7 21:31:41 2022 user.notice mwan3[12009]: Execute ifdown event on interface tethering (eth3)
Tue Jun 7 21:31:42 2022 user.info mwan3track[9068]: Detect ifdown event on interface tethering (eth3)
Tue Jun 7 21:31:47 2022 user.notice mwan3track[9068]: Interface tethering (eth3) is offline
Usb-c hub Vention 9-to-1 with Realtek RTL8153 does not work.
Tue Jun 7 21:34:21 2022 kern.info kernel: [ 377.364472] usb 1-1: new high-speed USB device number 2 using xhci-hcd
Tue Jun 7 21:34:21 2022 kern.info kernel: [ 377.534128] hub 1-1:1.0: USB hub found
Tue Jun 7 21:34:21 2022 kern.info kernel: [ 377.534282] hub 1-1:1.0: 4 ports detected
Tue Jun 7 21:34:22 2022 kern.info kernel: [ 377.627470] usb 2-1: new SuperSpeed USB device number 3 using xhci-hcd
Tue Jun 7 21:34:22 2022 kern.info kernel: [ 377.694203] hub 2-1:1.0: USB hub found
Tue Jun 7 21:34:22 2022 kern.info kernel: [ 377.694410] hub 2-1:1.0: 4 ports detected
Tue Jun 7 21:34:22 2022 kern.info kernel: [ 378.264471] usb 1-1.4: new high-speed USB device number 3 using xhci-hcd
Tue Jun 7 21:34:22 2022 kern.info kernel: [ 378.430091] hub 1-1.4:1.0: USB hub found
Tue Jun 7 21:34:22 2022 kern.info kernel: [ 378.430219] hub 1-1.4:1.0: 4 ports detected
Tue Jun 7 21:34:23 2022 kern.info kernel: [ 378.704470] usb 1-1.4.1: new high-speed USB device number 4 using xhci-hcd
Tue Jun 7 21:34:23 2022 kern.info kernel: [ 378.806229] usb-storage 1-1.4.1:1.0: USB Mass Storage device detected
Tue Jun 7 21:34:23 2022 kern.info kernel: [ 378.806525] scsi host0: usb-storage 1-1.4.1:1.0
Tue Jun 7 21:34:23 2022 kern.info kernel: [ 379.304532] usb 2-1.4: new SuperSpeed USB device number 4 using xhci-hcd
Tue Jun 7 21:34:23 2022 kern.info kernel: [ 379.469863] usb 2-1.4: reset SuperSpeed USB device number 4 using xhci-hcd
Tue Jun 7 21:34:23 2022 kern.info kernel: [ 379.486024] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Unknown version 0x6010
Tue Jun 7 21:34:23 2022 kern.err kernel: [ 379.486059] r8152 2-1.4:1.0 (unnamed net_device) (uninitialized): Unknown Device
Tue Jun 7 21:34:24 2022 kern.notice kernel: [ 379.805098] scsi 0:0:0:0: Direct-Access Mass Storage Device 1.00 PQ: 0 ANSI: 0 CCS
Tue Jun 7 21:34:24 2022 kern.notice kernel: [ 380.089838] sd 0:0:0:0: [sda] Attached SCSI removable disk
Tue Jun 7 21:34:24 2022 kern.err kernel: [ 380.322699] ubi0 error: ubi_open_volume: cannot open device 0, volume 2, error -16
Tue Jun 7 21:34:24 2022 kern.err kernel: [ 380.322742] ubi0 error: ubi_open_volume: cannot open device 0, volume 2, error -16
Usb-c hub Lemorele 10-to-1 with Realtek RTL8153 does not work.
… but just so we’re clear, you’re plugging in the USB-C devices via an adaptor into the USB-A port on the AX, right? The USB-C port seems to be power-only (unfortunately).
Yes, testing with usb-c (female) to usb-a (male) adapter. Both usb 3.0 adapter and usb 2.0 adapter versions. Tested both adapters with the computer and working ok. They work also ok with QC charging.
No success. I did not even try the usb-c charging port, as I supposed it was power only.
)