HercMull Posted August 10, 2016 Share Posted August 10, 2016 I've got a shiny new Asix Electronics AX88179-based USB 3.0 GigE network adapter that isn't behaving quite right. A couple of notes: When trying to install the kernel module from the default repositories, opkg will install the kernel module for kernel version 3.18.20-1 even though the NANO is running kernel 3.18.23-1. Running insmod for that module causes a segmentation fault (to be expected). I can successfully install the 3.18.23-1 kernel module manually from the OpenWRT website. The module loads successfully and the interface is detected, but does not appear to be receiving traffic. Logs: Wed Aug 10 21:19:39 2016 kern.info kernel: [93776.600000] ax88179_178a 1-1.3:1.0 eth1: register 'ax88179_178a' at usb-ehci-platform-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, MAC_ADDR_REDACTED Wed Aug 10 21:19:40 2016 daemon.notice netifd: Interface 'wan2' is enabled Wed Aug 10 21:19:42 2016 kern.info kernel: [93778.850000] ax88179_178a 1-1.3:1.0 eth1: ax88179 - Link status is: 1 Wed Aug 10 21:19:42 2016 daemon.notice netifd: Network device 'eth1' link is up Wed Aug 10 21:19:42 2016 daemon.notice netifd: Interface 'wan2' has link connectivity Wed Aug 10 21:19:42 2016 daemon.notice netifd: Interface 'wan2' is setting up now Wed Aug 10 21:19:42 2016 daemon.notice netifd: wan2 (3862): udhcpc (v1.23.2) started Wed Aug 10 21:19:42 2016 daemon.notice netifd: wan2 (3862): Sending discover... Wed Aug 10 21:19:45 2016 daemon.notice netifd: wan2 (3862): Sending discover... Wed Aug 10 21:19:48 2016 daemon.notice netifd: wan2 (3862): Sending discover... Output of ethtool: Settings for eth1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 3 Transceiver: internal Auto-negotiation: on Supports Wake-on: pg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes Output of ifconfig: eth1 Link encap:Ethernet HWaddr REDACTED UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:621 dropped:0 overruns:0 frame:0 TX packets:144 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:50400 (49.2 KiB) The interface does not receive an address via DHCP, nor does it work when configured with a static IP. You may also note the high number of receive errors which I originally suspected may be the result of a speed/ duplex mismatch, but have confirmed is not the case (using two separate switches). tcpdump shows DHCP discover packets being sent, but no return traffic. This adapter works fine on other systems, including Raspberry Pis running Raspbian and Ubuntu. Quote Link to comment Share on other sites More sharing options...
tman Posted August 14, 2016 Share Posted August 14, 2016 I am trying to get the Lanturtle to work with my Nano without any success. Same issue with module being downloaded to 3.18.20. Quote Link to comment Share on other sites More sharing options...
HercMull Posted August 14, 2016 Author Share Posted August 14, 2016 I don't have a one, what module does the LANTurtle use? Quote Link to comment Share on other sites More sharing options...
tman Posted August 16, 2016 Share Posted August 16, 2016 same module you are having the problem with. ax88179_178a module. Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted August 16, 2016 Share Posted August 16, 2016 I'll ensure this module makes it into the firmware this week. This might get rid of any issues. Quote Link to comment Share on other sites More sharing options...
tman Posted August 21, 2016 Share Posted August 21, 2016 good new. with the newest firmware 1.1.1 asix network adapters are recognized. Now you see something similar to this in dmesg: ax88179_178a 1-1.3:1.0 eth1: register 'ax88179_178a' at usb-ehci-platform-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:05:1b:b0:3e:1f You still need to update /etc/config/network to use the interface. Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted August 21, 2016 Share Posted August 21, 2016 39 minutes ago, tman said: good new. with the newest firmware 1.1.1 asix network adapters are recognized. Now you see something similar to this in dmesg: ax88179_178a 1-1.3:1.0 eth1: register 'ax88179_178a' at usb-ehci-platform-1.3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:05:1b:b0:3e:1f You still need to update /etc/config/network to use the interface. Correct Quote Link to comment Share on other sites More sharing options...
squish Posted August 25, 2016 Share Posted August 25, 2016 I'm still new to the pineapple and turtle. Would you mind posting the necessary edit to the network file that lets us use the turtle connected through the usb on the pineapple? Quote Link to comment Share on other sites More sharing options...
HercMull Posted August 29, 2016 Author Share Posted August 29, 2016 You'll want to check the output of dmesg (see above) to confirm which interface your LANTurtle is, then you just need to modify /etc/config/network with the parameters you want to use. In my case, the interface is eth1 and I am using DHCP so my config was modified to include: config interface 'wan2' option ifname 'eth1' option proto 'dhcp' option dns '8.8.8.8, 8.8.4.4' I have also added the wan2 interface to the wan zone in /etc/config/firewall: config zone option name wan list network 'wan' list network 'wan2' option input ACCEPT option output ACCEPT option forward ACCEPT option masq 1 option mtu_fix 1 After you've made these changes, you'll want to run /etc/init.d/network reload to apply them. 2 Quote Link to comment Share on other sites More sharing options...
bsalita Posted August 30, 2016 Share Posted August 30, 2016 Newbie here. Using firmware 1.1.1. When I plug in the LAN Turtle into the Nano, dmesg shows: [ 758.300000] usb 1-1.3: new high-speed USB device number 6 using ehci-platform However, ifconfig -a doesn't show eth1 or wan2 or any new interface. I'm guessing the issue is that the LAN Turtle is recognized as a generic USB device but not an Ethernet device? What am I missing? What commands should I use to install or debug? Quote Link to comment Share on other sites More sharing options...
HercMull Posted August 30, 2016 Author Share Posted August 30, 2016 What does it show under Advanced > USB or lsusb from the CLI? It should look something like this: Quote Link to comment Share on other sites More sharing options...
bsalita Posted August 30, 2016 Share Posted August 30, 2016 Bus 001 Device 006: ID 0bda:8152 Realtek Semiconductor Corp. Bus 001 Device 004: ID 05e3:0745 Genesys Logic, Inc. Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n Bus 001 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Same as what you posted accept a bit of difference in the first line. Quote Link to comment Share on other sites More sharing options...
bsalita Posted August 30, 2016 Share Posted August 30, 2016 er, make that a lot of difference in the first line. Quote Link to comment Share on other sites More sharing options...
bsalita Posted August 30, 2016 Share Posted August 30, 2016 Windows reports the LAN Turtle as a Realtek USB FE Class Family Controller. An ASIX AX88772A is also mentioned but doesn't disappear when I put out the Turtle. Quote Link to comment Share on other sites More sharing options...
bsalita Posted August 30, 2016 Share Posted August 30, 2016 I'm seeing that the ASIX AX88772A listed in Windows Device Manger is the Pineapple Nano plugged into the USB port. The Turtle uses a Realtek controller which, when plugged into Windows, is shown in the Device Manager as a Realtek network controller. When plugged into the Pineapple, it is shown as: Bus 001 Device 006: ID 0bda:8152 Realtek Semiconductor Corp. However, the Pineapple's `ifconfig -a` doesn't display its interface. Quote Link to comment Share on other sites More sharing options...
squish Posted August 30, 2016 Share Posted August 30, 2016 I'm actually having the same issue. I think it has to do with the ethernet side and the usb side. If you plug it up to a mac you get both adapters listed in the system report. I think the problem is the nano not seeing the ASIX part of the adapter. I wonder if it's a setting on the turtle that's causing this. Quote Link to comment Share on other sites More sharing options...
Just_a_User Posted August 31, 2016 Share Posted August 31, 2016 (edited) good point - I checked in my lanturtle and noticed i had clomac enabled in the modules. have disabled it now will try again. laptop dmesg [ 7950.188404] usb 8-1: new high-speed USB device number 17 using ehci-pci [ 7950.326151] usb 8-1: New USB device found, idVendor=0bda, idProduct=8152 [ 7950.326164] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7950.326170] usb 8-1: Product: USB 10/100 LAN [ 7950.326176] usb 8-1: Manufacturer: Realtek [ 7950.326182] usb 8-1: SerialNumber: 00E04C3611FE [ 7950.440320] usb 8-1: reset high-speed USB device number 17 using ehci-pci [ 7950.602599] r8152 8-1:1.0 eth1: v1.08.3 [ 7950.663186] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 7950.720327] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready [ 7952.342170] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready laptop lsusb Bus 008 Device 017: ID 0bda:8152 Realtek Semiconductor Corp. nano dmesg [ 87.580000] usb 1-1.3: new high-speed USB device number 5 using ehci-platform nano lsusb Bus 001 Device 005: ID 0bda:8152 Realtek Semiconductor Corp. Edited August 31, 2016 by Just_a_User Quote Link to comment Share on other sites More sharing options...
HercMull Posted August 31, 2016 Author Share Posted August 31, 2016 Per Sebkinne, the ax88179 kernel module is now part of the base 1.1.1 firmware and when I plug in a generic (i.e. non-LANTurtle) ax88179 adapter, the kernel module is loaded automagically as expected. I don't know what Realtek chipset the LANTurtle uses (quick Google search suggests RTL8152?), but it sounds like the module isn't loaded. If it's working on another Linux-based system, running lsmod on that system should give you an idea where to start and which module(s) you may need to install on the nano. Quote Link to comment Share on other sites More sharing options...
Just_a_User Posted August 31, 2016 Share Posted August 31, 2016 (edited) Thank you for the info @HercMull makes sense. Will check it out. update:- I don't see a pre-compiled kmod specificly for the rtl8152, There are various kmod-usb-net but again nothing specific to the rtl8152. Will put this on a back burner as I don't need this specifically and would only be a "nice to have" - for me anyway. Edited August 31, 2016 by Just_a_User Quote Link to comment Share on other sites More sharing options...
bsalita Posted September 4, 2016 Share Posted September 4, 2016 (edited) I sent a request to @Sebkinne for support of Lan Turtle (Realtek) USB-to-Ethernet adapters within Nano firmware. Hopefully this will be included in a future firmware update. Seems like the LAN Turtle should be supported as its the only USB-to-Ethernet adapter sold by Hak5. That said, I went ahead and purchased a ASIX AX88179 chipset based USB-to-Ethernet adapter, a Plugable Technolgies USB3-E1000 for $15. It works OOB with the Nano's 1.1.1 firmware. Be sure to follow the networking setup described by @HercMull above. Edited September 4, 2016 by bsalita Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.