I'm just leaving this here in case I actually found anything of note. If not just disregard. My setup is an RT-AC68U with Merlin 384.14_2.
Scenario 1.
I was pentesting with mdk4's packet fuzzer using assorted flags. After a few minutes of this I noticed packets to/from WAN would randomly drop out for 20s at random. Nothing unusual seemed to appear in the logs. I reflashed the firmware but it didn't fix it. After about a day the dropouts cleared up on its own.
Scenario 2.
I was pentesting with mdk4's 'a' flag (fake clients) on a different router I owned. After about 30 minutes of pentesting I noticed all of the RT-AC68U's ethernet devices could not communicate with anything on LAN. Nothing related to ethernet worked properly. No devices could get packets to/from WAN either. I rebooted the device. DHCP would not give any of my ethernet devices a lease. On my ethernet devices I could use a static IP and every reboot there was a 1 minute window where I could access the router's web interface (which lagged) or SSH to it before the dropouts began. My wireless devices had no problem, I could access things on LAN and the web interface did not lag.
I was unable to resolve the router's glitched state over its interface. I tried reflashing the firmware and factory clearing its settings on the admin page. Even on the new router setup page my ethernet would drop out after about 1 minute of booting. The only way I could fix it was to do a full reset by holding down all the reset buttons, hitting "clear nvram" on the recovery page and repeating this process a few times. Then the dropouts stopped and I could restore my nvram settings and JFFS and there were no problems.
The logs had nothing unusual besides some acsd statements I had never seen before, like doing a DFS switch due to the 2.4 GHz network scan. If this bug exists it's probably very low level in the hardware somehow.
Scenario 1.
I was pentesting with mdk4's packet fuzzer using assorted flags. After a few minutes of this I noticed packets to/from WAN would randomly drop out for 20s at random. Nothing unusual seemed to appear in the logs. I reflashed the firmware but it didn't fix it. After about a day the dropouts cleared up on its own.
Scenario 2.
I was pentesting with mdk4's 'a' flag (fake clients) on a different router I owned. After about 30 minutes of pentesting I noticed all of the RT-AC68U's ethernet devices could not communicate with anything on LAN. Nothing related to ethernet worked properly. No devices could get packets to/from WAN either. I rebooted the device. DHCP would not give any of my ethernet devices a lease. On my ethernet devices I could use a static IP and every reboot there was a 1 minute window where I could access the router's web interface (which lagged) or SSH to it before the dropouts began. My wireless devices had no problem, I could access things on LAN and the web interface did not lag.
I was unable to resolve the router's glitched state over its interface. I tried reflashing the firmware and factory clearing its settings on the admin page. Even on the new router setup page my ethernet would drop out after about 1 minute of booting. The only way I could fix it was to do a full reset by holding down all the reset buttons, hitting "clear nvram" on the recovery page and repeating this process a few times. Then the dropouts stopped and I could restore my nvram settings and JFFS and there were no problems.
The logs had nothing unusual besides some acsd statements I had never seen before, like doing a DFS switch due to the 2.4 GHz network scan. If this bug exists it's probably very low level in the hardware somehow.
Last edited:
