HercMull

Your images look like they're actually missing the default route (the button to enable it is there, but it doesn't appear to be in the actual route table). A couple of questions: Have you enabled any form of Internet connection sharing on the device your pineapple is connected to? Are your Wi-Fi clients getting IP addresses from the block 172.16.42.0/24? If you run traceroute on the Wi-Fi clients, where does it start to time out?

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.

What does it show under Advanced > USB or lsusb from the CLI? It should look something like this:

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.

I don't have a one, what module does the LANTurtle use?

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.

Upon closer inspection, it appears that /etc/config/firewall allows for multiple networks to be added to a zone: 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 I mistakenly thought that the zone name was directly linked to the logical network name and, therefore, a new interface would require creation of a new zone. Glad to be wrong about that.

Not looking to create a bridge, insofar as only one of the interfaces in question will ever be connected at a time. /etc/config/wireless contains: config wifi-iface option device 'radio2' option ifname 'wlan2' option mode 'sta' option network 'wan' Which associates the wlan2 interface w/ the WAN config block in /etc/config/network: config interface 'wan' option proto 'dhcp' option dns '8.8.8.8, 8.8.4.4' And, perhaps more importantly, w/ the WAN zone of the firewall and its related rules. In a perfect world, I would like to have the WAN settings from /etc/config/network and /etc/config/firewall applied to both the USB WLAN interface or the USB Ethernet, regardless of which is connected. However, if I add option ifname 'eth1' to the config interface 'wan' section /etc/config/network, those settings will no longer be applied to the WLAN interface. The ultimate goal is to have a single config block in /etc/config/network and /etc/config/network cover the settings for both interfaces.

I have my NANO successfully configured to use both a USB Wi-Fi dongle (wlan2) and a USB Ethernet adapter (eth1), however I would like to create a interface definition in /etc/config/network that would allow both to share configuration parameters (and, by extension, firewall rules). The OpenWRT Wiki provides some guidance for configuring multiple network settings for a single physical device but I can't seem to work out how to do the opposite: single network/ firewall configuration regardless of which physical device is connected to the USB port. Of course, it's possible to duplicate the configuration for each interface, but the simplicity/ consistency of a single setup for whichever "WAN" interface happens to be connected is preferable. Any thoughts?