Posted: Sun Sep 15, 2019 23:55 Post subject: Asus RT-68U BS Build 41027, loss of all networking
Hello everyone, first post. I have an Asus RT-AC68U which has been quite reliable. I recently decided to add a virtual AP for the first time, and it seems to have kicked out any kind of connectivity, from Ethernet to Wifi in general.
I connected a TTY to USB adapter to the serial header on the PCB and noticed that the terminal continuously repeats the following:
Code:
base addr 38:2C:4A:9C:D6:2A
local bit addr 3A:2C:4A:9C:D6:2A
eth2: Invalid argument
eth2: Not supported
eth2: Not supported
eth2: Invalid argument
eth2: Invalid argument
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Not supported
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
eth2: Invalid argument
enable bss eth2 0 (0)
enable bss eth2 1 (0)
br0: port 3(wl1.1) entered disabled state
total vif count 2
eth2: Not supported
base addr 38:2C:4A:9C:D6:2A
local bit addr 3A:2C:4A:9C:D6:2A
eth2: Invalid argument
I am able to login to the serial console, and tried to enable logging but no dice. What info can I provide you folks with to fix this?
I am using : DD-WRT v3.0-r39960M kongac (06/08/19). It works pretty well (apart from VAP startup - wlconf restart issue) on RT AC68U.
I have tried the latest BS build on my RT AC5300 over the weeked. As Gateway it worked very well. No issues at all for over 24 hrs! It's only when I was setting up VAPs bridged with VLANs I ran into issues. It could totally be unrelated but in general the VLAN.asp(switch config) and Network.asp pages make the router unresponsive for me in this build.
Hello kernel-panic69 and bkaskar, thanks for taking the time to look.
When I initially faced thsi problem, I wasn't able to visit the webUI even after manually setting my IP to the expected address range. DHCP wouldn't work on any interface. It could be the wland daemon, or dnsmasq.
This issue seems to be a bit of a heisenbug, when I reset my router to defaults and rebuilt the settings (without using a config backup file) it once again didn't work. My route table was empty, and the message about no support for eth2 kept going on and on.
I tried once again, except I set the VAP to unbridged and then everything seemed ok-ish. After adding the VAP to a nwe bridge and setting DHCP for it, all interfaces work except the VAP. I rebooted the router and let it sit for about 3-4 minutes, and once again I had no connectivity on any LAN interface. WAN was OK though.
Could it be a race of some kind? Something is trying to use one of the bridges but it hasn't been created just yet?
I had to dig up kong's tutorial on guest networks on web.archive.org, he or she mentions that the guest AP should not be bridged.
My goal is to segment my network, creating a VLAN for less trustworthy devices, and a VLAN for more trustworthy devices. Two bridges (for different ethernet ports to be tied to the respective VLANs), two DHCP servers, and two wireless networks on one radio.
I appreciate your help in advance! bkaskar, I'll jump back to 39960M if I cannot contribute some useful info to the devs somehow with this build.
Joined: 24 Feb 2013 Posts: 1642 Location: Belgrade
Posted: Tue Sep 17, 2019 6:17 Post subject:
free99 wrote:
Hello kernel-panic69 and bkaskar, thanks for taking the time to look.
When I initially faced thsi problem, I wasn't able to visit the webUI even after manually setting my IP to the expected address range. DHCP wouldn't work on any interface. It could be the wland daemon, or dnsmasq.
This issue seems to be a bit of a heisenbug, when I reset my router to defaults and rebuilt the settings (without using a config backup file) it once again didn't work. My route table was empty, and the message about no support for eth2 kept going on and on.
I tried once again, except I set the VAP to unbridged and then everything seemed ok-ish. After adding the VAP to a nwe bridge and setting DHCP for it, all interfaces work except the VAP. I rebooted the router and let it sit for about 3-4 minutes, and once again I had no connectivity on any LAN interface. WAN was OK though.
Could it be a race of some kind? Something is trying to use one of the bridges but it hasn't been created just yet?
I had to dig up kong's tutorial on guest networks on web.archive.org, he or she mentions that the guest AP should not be bridged.
My goal is to segment my network, creating a VLAN for less trustworthy devices, and a VLAN for more trustworthy devices. Two bridges (for different ethernet ports to be tied to the respective VLANs), two DHCP servers, and two wireless networks on one radio.
I appreciate your help in advance! bkaskar, I'll jump back to 39960M if I cannot contribute some useful info to the devs somehow with this build.
it's known problem on brcm routers since of wl driver upgrade... BS cannot fix it only broadcom devs...
on atheros VAPs works bridged or unbridged no matter... on brcm just unbridged...
there are some scripts that can make it working (with restarting wl driver) but that is not good solution...
Joined: 08 May 2018 Posts: 16742 Location: Texas, USA
Posted: Tue Sep 17, 2019 17:35 Post subject:
Mile-Lile wrote:
it's known problem on brcm routers since of wl driver upgrade... BS cannot fix it only broadcom devs...
on atheros VAPs works bridged or unbridged no matter... on brcm just unbridged...
there are some scripts that can make it working (with restarting wl driver) but that is not good solution...
If it's not a K2.6 kernel in the firmware, it is running a modified FOSS driver straight out of the Linux kernel. Okay, so it's a driver provided by Broadcom, but it's not the 100% proprietary driver in stock firmware. There have been manipulations and patches done to the driver code for DD-WRT... if you follow the commits. The things you learn as you follow the bouncing red ball...