What's new

ASUS RT-AC3100 flipping out

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

ngerasimatos

Regular Contributor
This morning I woke to an email from my internet provider stating that there was a brute force attack and my home IP address was unfortunately in the block of IPs they blacklisted. Worked with them to get things resolved but noticed my router has been acting strange. I decided to reset it and configure it again net new.

I have tried the typical methods of resetting it, holding the reset button for 30 seconds until power light flashes, then rebooting and connecting to the default IP but upon reboot wifi doesn't come back online. I figured I would use the restore firmware utility but that fails as well.

Not sure where to go from here. WAN/LAN seem to work fine but I cannot get to the router setup page.

Any ideas?
 
Disconnect everything except the controlling computer from the router (including WAN).

Do a hard reboot (pull the ac power and wait a couple of minutes before plugging it back in).

Can you access the web ui then?
 
No change. Upon reboot I can ping 192.168.1.1 but cannot login and the restore utility fails. The power light is flashing slowly as it should. I'm baffled.
 
My 3200 used to flake out if the modem was acting wonky. If you haven't done it (especially since the attack), power cycle your modem by unplugging everything from it, then reconnect and restore power.
 
Same result. Tried a different browser. Tried a different laptop. It's always the same result, unable to connect to the web UI and cannot perform a reset or a router restore. It goes into the power light blinking, i can ping 192.168.1.1 but the router restore fails.

Is there a special way of restoring his router other than the usual?
 
I got it to boot to the restore utility and flashed the new firmware. I was then able to log in at 192.168.1.1 but as soon as I entered my username and password it locked up again.

Right now it's "pretending" to work since the light are all on and stable and the wan light is flashing. DHCP is not handing out any IP addresses and WiFI is not working, though the lights are on it's not broadcasting.

I set a static IP and I cannot ping the router, thus, I cannot log in. It's basically a brick. A 30/30/30 reboot brings it back to the restore utility but the results are always the same. After the Wizard splash screen it tries to save the config and then bricks itself.
 
The router has been working now for 0 days 4 hours 40 minute(s) 55 seconds ever since I set it to use 20Mhz for both 2.4 and 5Ghz bands and am running it in Access Point mode. I am not seeing any errors in the logs. I am using 380.57_0 Merlin firmware.

What else should I check?

Note: Logs have been sanitized


Mar 10 05:35:04 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:35:07 kernel: dhd_detach(): thread:dhd_watchdog_thread:1a8 terminated OK
Mar 10 05:35:08 kernel: dhd_detach(): thread:dhd_watchdog_thread:1a4 terminated OK
Mar 10 05:35:14 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:35:14 kernel: dhd_attach(): thread:dhd_watchdog_thread:391 started
Mar 10 05:35:14 kernel: CUR_ETHERADDR : 6
Mar 10 05:35:14 kernel: *******************
Mar 10 05:35:14 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:35:14 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:35:15 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:35:15 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:35:15 kernel: dhd_attach(): thread:dhd_watchdog_thread:395 started
Mar 10 05:35:15 kernel: CUR_ETHERADDR : 6
Mar 10 05:35:15 kernel: *******************
Mar 10 05:35:15 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:35:15 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:35:15 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:36:03 rc_service: httpd 783:notify_rc restart_wlcscan
Mar 10 05:43:53 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:43:55 kernel: dhd_detach(): thread:dhd_watchdog_thread:395 terminated OK
Mar 10 05:43:55 kernel: dhd_detach(): thread:dhd_watchdog_thread:391 terminated OK
Mar 10 05:44:02 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:44:02 kernel: dhd_attach(): thread:dhd_watchdog_thread:48f started
Mar 10 05:44:02 kernel: CUR_ETHERADDR : 6
Mar 10 05:44:02 kernel: *******************
Mar 10 05:44:02 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:44:02 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:44:02 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:44:02 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:44:02 kernel: dhd_attach(): thread:dhd_watchdog_thread:493 started
Mar 10 05:44:03 kernel: CUR_ETHERADDR : 6
Mar 10 05:44:03 kernel: *******************
Mar 10 05:44:03 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:44:03 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:44:03 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:44:11 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:44:11 rc_service: waitting "restart_wireless" via httpd ...
Mar 10 05:44:25 kernel: dhd_detach(): thread:dhd_watchdog_thread:493 terminated OK
Mar 10 05:44:25 kernel: dhd_detach(): thread:dhd_watchdog_thread:48f terminated OK
Mar 10 05:44:31 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:44:32 kernel: dhd_attach(): thread:dhd_watchdog_thread:566 started
Mar 10 05:44:32 kernel: CUR_ETHERADDR : 6
Mar 10 05:44:32 kernel: *******************
Mar 10 05:44:32 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:44:32 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:44:32 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:44:32 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:44:32 kernel: dhd_attach(): thread:dhd_watchdog_thread:56a started
Mar 10 05:44:32 kernel: CUR_ETHERADDR : 6
Mar 10 05:44:32 kernel: *******************
Mar 10 05:44:32 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:44:32 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:44:32 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:45:12 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:45:14 kernel: dhd_detach(): thread:dhd_watchdog_thread:56a terminated OK
Mar 10 05:45:15 kernel: dhd_detach(): thread:dhd_watchdog_thread:566 terminated OK
Mar 10 05:45:21 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:45:21 kernel: dhd_attach(): thread:dhd_watchdog_thread:63d started
Mar 10 05:45:22 kernel: CUR_ETHERADDR : 6
Mar 10 05:45:22 kernel: *******************
Mar 10 05:45:22 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:45:22 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:45:22 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:45:22 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:45:22 kernel: dhd_attach(): thread:dhd_watchdog_thread:641 started
Mar 10 05:45:22 kernel: CUR_ETHERADDR : 6
Mar 10 05:45:22 kernel: *******************
Mar 10 05:45:22 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:45:22 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:45:22 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:45:32 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:45:32 rc_service: waitting "restart_wireless" via httpd ...
Mar 10 05:45:46 kernel: dhd_detach(): thread:dhd_watchdog_thread:641 terminated OK
Mar 10 05:45:46 kernel: dhd_detach(): thread:dhd_watchdog_thread:63d terminated OK
Mar 10 05:45:53 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:45:53 kernel: dhd_attach(): thread:dhd_watchdog_thread:712 started
Mar 10 05:45:53 kernel: CUR_ETHERADDR : 6
Mar 10 05:45:53 kernel: *******************
Mar 10 05:45:53 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:45:53 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:45:53 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:45:53 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:45:53 kernel: dhd_attach(): thread:dhd_watchdog_thread:716 started
Mar 10 05:45:54 kernel: CUR_ETHERADDR : 6
Mar 10 05:45:54 kernel: *******************
Mar 10 05:45:54 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:45:54 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:45:54 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:47:03 dropbear[1950]: Password auth succeeded for 'user' from ***.***.***.***:63099
Mar 10 05:52:16 ntp: start NTP update
Mar 10 05:52:16 rc_service: ntp 1997:notify_rc restart_diskmon
Mar 10 04:52:16 disk_monitor: Finish
Mar 10 05:52:17 disk monitor: be idle
Mar 10 05:53:50 ntp: start NTP update
Mar 10 05:53:53 ntp: start NTP update
Mar 10 05:53:53 rc_service: ntp 2010:notify_rc restart_diskmon
Mar 10 05:53:53 disk_monitor: Finish
Mar 10 05:53:54 disk monitor: be idle
Mar 10 06:00:54 disk_monitor: Got SIGALRM...
 
Been up and running stable on 20Mhz for both 2.4 and 5Ghz bands. As soon as I change it to 40/80Mhz the router locks up after a small period of time. Pretty sure its either a firmware bug or the firmware is casuing the radios to overheat when bonding channels.
 
The router has been working now for 0 days 4 hours 40 minute(s) 55 seconds ever since I set it to use 20Mhz for both 2.4 and 5Ghz bands and am running it in Access Point mode. I am not seeing any errors in the logs. I am using 380.57_0 Merlin firmware.

What else should I check?

Note: Logs have been sanitized


Mar 10 05:35:04 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:35:07 kernel: dhd_detach(): thread:dhd_watchdog_thread:1a8 terminated OK
Mar 10 05:35:08 kernel: dhd_detach(): thread:dhd_watchdog_thread:1a4 terminated OK
Mar 10 05:35:14 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:35:14 kernel: dhd_attach(): thread:dhd_watchdog_thread:391 started
Mar 10 05:35:14 kernel: CUR_ETHERADDR : 6
Mar 10 05:35:14 kernel: *******************
Mar 10 05:35:14 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:35:14 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:35:15 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:35:15 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:35:15 kernel: dhd_attach(): thread:dhd_watchdog_thread:395 started
Mar 10 05:35:15 kernel: CUR_ETHERADDR : 6
Mar 10 05:35:15 kernel: *******************
Mar 10 05:35:15 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:35:15 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:35:15 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:36:03 rc_service: httpd 783:notify_rc restart_wlcscan
Mar 10 05:43:53 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:43:55 kernel: dhd_detach(): thread:dhd_watchdog_thread:395 terminated OK
Mar 10 05:43:55 kernel: dhd_detach(): thread:dhd_watchdog_thread:391 terminated OK
Mar 10 05:44:02 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:44:02 kernel: dhd_attach(): thread:dhd_watchdog_thread:48f started
Mar 10 05:44:02 kernel: CUR_ETHERADDR : 6
Mar 10 05:44:02 kernel: *******************
Mar 10 05:44:02 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:44:02 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:44:02 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:44:02 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:44:02 kernel: dhd_attach(): thread:dhd_watchdog_thread:493 started
Mar 10 05:44:03 kernel: CUR_ETHERADDR : 6
Mar 10 05:44:03 kernel: *******************
Mar 10 05:44:03 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:44:03 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:44:03 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:44:11 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:44:11 rc_service: waitting "restart_wireless" via httpd ...
Mar 10 05:44:25 kernel: dhd_detach(): thread:dhd_watchdog_thread:493 terminated OK
Mar 10 05:44:25 kernel: dhd_detach(): thread:dhd_watchdog_thread:48f terminated OK
Mar 10 05:44:31 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:44:32 kernel: dhd_attach(): thread:dhd_watchdog_thread:566 started
Mar 10 05:44:32 kernel: CUR_ETHERADDR : 6
Mar 10 05:44:32 kernel: *******************
Mar 10 05:44:32 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:44:32 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:44:32 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:44:32 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:44:32 kernel: dhd_attach(): thread:dhd_watchdog_thread:56a started
Mar 10 05:44:32 kernel: CUR_ETHERADDR : 6
Mar 10 05:44:32 kernel: *******************
Mar 10 05:44:32 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:44:32 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:44:32 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:45:12 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:45:14 kernel: dhd_detach(): thread:dhd_watchdog_thread:56a terminated OK
Mar 10 05:45:15 kernel: dhd_detach(): thread:dhd_watchdog_thread:566 terminated OK
Mar 10 05:45:21 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:45:21 kernel: dhd_attach(): thread:dhd_watchdog_thread:63d started
Mar 10 05:45:22 kernel: CUR_ETHERADDR : 6
Mar 10 05:45:22 kernel: *******************
Mar 10 05:45:22 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:45:22 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:45:22 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:45:22 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:45:22 kernel: dhd_attach(): thread:dhd_watchdog_thread:641 started
Mar 10 05:45:22 kernel: CUR_ETHERADDR : 6
Mar 10 05:45:22 kernel: *******************
Mar 10 05:45:22 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:45:22 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:45:22 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:45:32 rc_service: httpd 783:notify_rc restart_wireless
Mar 10 05:45:32 rc_service: waitting "restart_wireless" via httpd ...
Mar 10 05:45:46 kernel: dhd_detach(): thread:dhd_watchdog_thread:641 terminated OK
Mar 10 05:45:46 kernel: dhd_detach(): thread:dhd_watchdog_thread:63d terminated OK
Mar 10 05:45:53 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:45:53 kernel: dhd_attach(): thread:dhd_watchdog_thread:712 started
Mar 10 05:45:53 kernel: CUR_ETHERADDR : 6
Mar 10 05:45:53 kernel: *******************
Mar 10 05:45:53 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:45:53 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:45:53 kernel: Register interface [eth1] MAC: *******************
Mar 10 05:45:53 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
Mar 10 05:45:53 kernel: dhd_attach(): thread:dhd_watchdog_thread:716 started
Mar 10 05:45:54 kernel: CUR_ETHERADDR : 6
Mar 10 05:45:54 kernel: *******************
Mar 10 05:45:54 kernel: Dongle Host Driver, version 1.366.5 (r588294)
Mar 10 05:45:54 kernel: Compiled in drivers/net/wireless/bcmdhd on Nov 10 2015 at 03:41:52
Mar 10 05:45:54 kernel: Register interface [eth2] MAC: *******************
Mar 10 05:47:03 dropbear[1950]: Password auth succeeded for 'user' from ***.***.***.***:63099
Mar 10 05:52:16 ntp: start NTP update
Mar 10 05:52:16 rc_service: ntp 1997:notify_rc restart_diskmon
Mar 10 04:52:16 disk_monitor: Finish
Mar 10 05:52:17 disk monitor: be idle
Mar 10 05:53:50 ntp: start NTP update
Mar 10 05:53:53 ntp: start NTP update
Mar 10 05:53:53 rc_service: ntp 2010:notify_rc restart_diskmon
Mar 10 05:53:53 disk_monitor: Finish
Mar 10 05:53:54 disk monitor: be idle
Mar 10 06:00:54 disk_monitor: Got SIGALRM...
Forums should have a limit to the length of posts as my thumb gets tired of paging down.
 
Wireless settings that are holding stable.


SSID: "ASUS"
RSSI: 0 dBm SNR: 0 dB noise: -91 dBm Channel: 9
BSSID: F8:32:E4:55:03:90 Capability: ESS ShortSlot
Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]
VHT Capable:
Chanspec: 2.4GHz channel 9 20MHz (0x1009)
Primary channel: 9
HT Capabilities:
Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ]
VHT Capabilities:
Supported VHT (tx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11
Supported VHT (rx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11

Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PSM SGI STBC MUBF Tx rate Rx rate Connect Time
**:**:**:**:**:** Yes Yes -72dBm Yes Yes Yes No 72.2M 6M 00:34:57
**:**:**:**:**:** Yes Yes -75dBm Yes Yes Yes No 1M 24M 00:35:42
**:**:**:**:**:** Yes Yes -65dBm No Yes Yes No 65M 65M 00:36:23
**:**:**:**:**:** Yes Yes -68dBm Yes Yes No No 1M 72.2M 00:36:27

SSID: "ASUS_5G"
RSSI: 0 dBm SNR: 0 dB noise: -92 dBm Channel: 157
BSSID: F8:32:E4:55:03:94 Capability: ESS
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
VHT Capable:
Chanspec: 5GHz channel 157 20MHz (0xd09d)
Primary channel: 157
HT Capabilities:
Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ]
VHT Capabilities:
Supported VHT (tx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11
Supported VHT (rx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11

Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PSM SGI STBC MUBF Tx rate Rx rate Connect Time
**:**:**:**:**:** Yes Yes -45dBm Yes Yes Yes Yes 173.3M 173.3M 00:33:32
**:**:**:**:**:** Yes Yes -35dBm Yes Yes Yes No 6M 24M 00:35:49
**:**:**:**:**:** Yes Yes -67dBm Yes Yes Yes No 24M 6M 00:35:51
**:**:**:**:**:** Yes Yes -57dBm No Yes Yes No 130M 144.4M 00:36:21
**:**:**:**:**:** Yes Yes -69dBm No Yes Yes No 144.4M 144.4M 00:36:22
**:**:**:**:**:** Yes Yes -35dBm No Yes Yes No 130M 144.4M 00:36:23

 
Could be, still pretty long. I'm on a phone with tapatalk and don't see that click to expand option.
I can't post with thoughts of how it effects 3rd party applications. In addition my post was light hearted in regards to the length of posts and how long it takes to get to the bottom of the page when members feel compelled to post 12 inches of log files.
 
Wireless settings that are holding stable.


SSID: "ASUS"
RSSI: 0 dBm SNR: 0 dB noise: -91 dBm Channel: 9
BSSID: F8:32:E4:55:03:90 Capability: ESS ShortSlot
Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]
VHT Capable:
Chanspec: 2.4GHz channel 9 20MHz (0x1009)
Primary channel: 9
HT Capabilities:
Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ]
VHT Capabilities:
Supported VHT (tx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11
Supported VHT (rx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11

Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PSM SGI STBC MUBF Tx rate Rx rate Connect Time
**:**:**:**:**:** Yes Yes -72dBm Yes Yes Yes No 72.2M 6M 00:34:57
**:**:**:**:**:** Yes Yes -75dBm Yes Yes Yes No 1M 24M 00:35:42
**:**:**:**:**:** Yes Yes -65dBm No Yes Yes No 65M 65M 00:36:23
**:**:**:**:**:** Yes Yes -68dBm Yes Yes No No 1M 72.2M 00:36:27

SSID: "ASUS_5G"
RSSI: 0 dBm SNR: 0 dB noise: -92 dBm Channel: 157
BSSID: F8:32:E4:55:03:94 Capability: ESS
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
VHT Capable:
Chanspec: 5GHz channel 157 20MHz (0xd09d)
Primary channel: 157
HT Capabilities:
Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ]
VHT Capabilities:
Supported VHT (tx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11
Supported VHT (rx) Rates:
NSS: 1 MCS: 0-11
NSS: 2 MCS: 0-11
NSS: 3 MCS: 0-11
NSS: 4 MCS: 0-11

Mode : AP Only

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PSM SGI STBC MUBF Tx rate Rx rate Connect Time
**:**:**:**:**:** Yes Yes -45dBm Yes Yes Yes Yes 173.3M 173.3M 00:33:32
**:**:**:**:**:** Yes Yes -35dBm Yes Yes Yes No 6M 24M 00:35:49
**:**:**:**:**:** Yes Yes -67dBm Yes Yes Yes No 24M 6M 00:35:51
**:**:**:**:**:** Yes Yes -57dBm No Yes Yes No 130M 144.4M 00:36:21
**:**:**:**:**:** Yes Yes -69dBm No Yes Yes No 144.4M 144.4M 00:36:22
**:**:**:**:**:** Yes Yes -35dBm No Yes Yes No 130M 144.4M 00:36:23
Example #2
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top