What's new

Release Asuswrt-Merlin 384.19 is now available

  • 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!

Status
Not open for further replies.
If not, then I'll manually set these channels and set the bandwidth to 40 MHz and 80 Mhz for the 2.4 GHz and 5 GHz bands, respectively.
Leave the 2.4 Ghz radio on 20 MHz channel width. There isn't enough spectrum in the 2.4 GHz band for 40 MHz channels to work without severe cross channel interference, and beside that, it is not very neighbourly :).
You will end up with more problems with a 40 MHz channel set.
 
Can anyone tell me if this combination of settings makes any sense and what it does? I thought that Wi-Fi6 only is a 5GHz thing..

RT-AX88U.png
 
@bbunge: Since my last post, I did some reading on selecting a channel and bandwidth for the 2.4 GHz and the 5 GHz bands. My router has selected Channel 11 (2.4 GHz) and 149 (5 GHz). These seem like reasonable choices given the distribution of neighboring networks, with only a couple of lower-powered networks that overlap some or all of each channel.

Since turning on Smart Connect, the single device that initially glitched has been working smoothly and there have been no further problems. I'll monitor it for awhile and if it remains stable, then I'll leave the settings as-is. If not, then I'll manually set these channels and set the bandwidth to 40 MHz and 80 Mhz for the 2.4 GHz and 5 GHz bands, respectively.
2.4 GHZ ch 1, 6, or 11 @ 20 MHZ and 5 GHZ non DFS ch @ 80 MHZ
 
It doesn't need to make that distinction; it is a general guide. The proper method for the specific router is what it suggests. That is what makes a difference. :)

The 'clue' is to perform the WPS reset and get the setup Wizard. Otherwise, try again.
nonsense... Asus seems to think it makes a difference and wrote two distinct procedures... fix your guide. - or don't - your choice...


You are misreading what I wrote. Let me try again.

My guide states to use the procedure that works for your router. As a general guide, it is correct. I just don't list all the different ways (now, and in the future) that the methods I describe should be done on any particular router. Hope that is clear to you now.
 
You are misreading what I wrote. Let me try again.

My guide states to use the procedure that works for your router. As a general guide, it is correct. I just don't list all the different ways (now, and in the future) that the methods I describe should be done on any particular router. Hope that is clear to you now.
Well, you can expect the heat to continue about poorly written instructions. I learned a long time ago that how too do things needs to be written in the lowest common denominator. My guess is that 90 to 95 percent of the folks visiting this forum for help know next to nothing about about the workings of computers and even less about networking.
I am really trying not to be acerbic but you need to give a bit as well.

bb
 
I don't have any issue for anyone asking for clarifications of anything I write.

But you don't seriously think I (or anyone else for that matter) can predict how any one person will interpret what is written?

I can't write for the lowest common denominator. Most don't know what a router is.
 
Just to keep everyone up to date: My AC86U has been running well all week on .19 with my wife working from home, she VPN's to work, and my daughter is currently schooling from home due to COVID, mostly Google classroom.
I have been watching TV and movies which all stream through the internet without a single hiccup until last night. Just as I was switching between Amazon and Netflix my router burped a couple of times. The router did not do a full reboot but enough to lose a connection.
As I'm typing up this post the router has rebooted 3 times within 15 minutes. I see from a couple of members they have been up for over a month without an issue...That's great for them, cheers.
My configuration is so minimal, I'm not running any scripts at all. All I'm running is pretty much what the router comes from the factory since my last format. I do have AiProtection on, QOS (Bandwidth Limiter), Cloud disk, and Smart access. That's it...
So I have decided to go out and purchase another AC86U so as not to break the bank with any newer version of the router since I was happy with it before the last firmware upgrade.
I then can start from scratch and not worry about disrupting anyone at home with internet outages.
Here is a snippet of the log from last night:

Sep 24 05:36:10 kernel: protocol 0800 is buggy, dev br0
Sep 24 05:36:10 kernel: protocol 0800 is buggy, dev br0
Sep 25 08:10:57 miniupnpd[2816]: send(res_buf): Connection reset by peer
May 5 01:05:15 kernel: nand: Could not find valid ONFI parameter page; aborting
May 5 01:05:15 kernel: brcmboard registered
May 5 01:05:15 kernel: genirq: Flags mismatch irq 36. 00000000 (brcm_36) vs. 00000000 (brcm_36)
May 5 01:05:15 kernel: pci 0000:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 01:05:15 kernel: pci 0000:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 01:05:15 kernel: pci 0001:00:00.0: of_irq_parse_pci() failed with rc=-22
May 5 01:05:15 kernel: pci 0001:01:00.0: of_irq_parse_pci() failed with rc=-22
May 5 01:05:15 kernel: broadcomThermalDrv brcm-therm: init (CPU count 2 2 2 2)
May 5 01:05:15 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
May 5 01:05:15 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex
May 5 01:05:15 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link DOWN.
May 5 01:05:15 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
May 5 01:05:15 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
May 5 01:05:15 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) Link UP 1000 mbps full duplex
May 5 01:05:15 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
May 5 01:05:15 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
May 5 01:05:18 acsd: selected channel spec: 0x1001 (1)
May 5 01:05:18 acsd: Adjusted channel spec: 0x1001 (1)
May 5 01:05:18 acsd: selected channel spec: 0x1001 (1)
May 5 01:05:18 acsd: acs_set_chspec: 0x1001 (1) for reason APCS_INIT
May 5 01:05:19 acsd: selected channel spec: 0xe29b (157/80)
May 5 01:05:19 acsd: Adjusted channel spec: 0xe29b (157/80)
May 5 01:05:19 acsd: selected channel spec: 0xe29b (157/80)
May 5 01:05:19 acsd: acs_set_chspec: 0xe29b (157/80) for reason APCS_INIT
May 5 01:05:20 Mastiff: init
May 5 01:05:35 modprobe: module scsi_wait_scan not found in modules.dep
May 5 01:05:35 modprobe: module uas not found in modules.dep
May 5 01:05:35 modprobe: module mbcache not found in modules.dep
May 5 01:05:35 modprobe: module jbd not found in modules.dep
May 5 01:05:35 modprobe: module ext3 not found in modules.dep
May 5 01:05:35 modprobe: module ext4 not found in modules.dep
May 5 01:05:35 modprobe: module ext2 not found in modules.dep
May 5 01:05:35 modprobe: module btusbdrv not found in modules.dep
Sep 25 21:01:17 crond[1305]: time disparity of 1259755 minutes detected
Sep 25 21:03:58 syslogd started: BusyBox v1.25.1
Sep 25 21:03:58 kernel: klogd started: BusyBox v1.25.1 (2020-08-14 15:19:48 EDT)
Sep 25 21:04:01 kernel: DROP IN=eth0 OUT= MAC=0c:9d:92:2d:0b:88:00:17:10:9a:f3:02:08:00 SRC=185.176.27.234 DST=99.233.114.188 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=16290 PROTO=TCP SPT=46981 DPT=3520 SEQ=1506164958 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Sep 25 21:04:01 kernel: DROP IN=eth0 OUT= MAC=0c:9d:92:2d:0b:88:00:17:10:9a:f3:02:08:00 SRC=146.88.240.4 DST=99.233.114.188 LEN=32 TOS=0x00 PREC=0x00 TTL=245 ID=54321 PROTO=UDP SPT=43232 DPT=5683 LEN=12 MARK=0x8000000
Sep 25 21:04:01 kernel: protocol 0000 is buggy, dev eth0
Sep 25 21:04:01 kernel: protocol 0000 is buggy, dev eth0
Sep 25 21:04:01 kernel: protocol 0000 is buggy, dev eth0

I have attached the Syslog of the last reboot.

Online here:

Cheers,

X
 
Another reboot!!!
How can this be happening...
I haven't done anything in a week!!!

:mad:
 
Leave the 2.4 Ghz radio on 20 MHz channel width. There isn't enough spectrum in the 2.4 GHz band for 40 MHz channels to work without severe cross channel interference, and beside that, it is not very neighbourly :).

You will end up with more problems with a 40 MHz channel set.

2.4 GHZ ch 1, 6, or 11 @ 20 MHZ and 5 GHZ non DFS ch @ 80 MHZ

Thank you both for your advice. Picking a channel (except for steering clear of DFS channels) seems easy enough, but the bandwidth part had me scratching my head.
 
Sep 25 21:04:01 kernel: protocol 0000 is buggy, dev eth0
Sep 25 21:04:01 kernel: protocol 0000 is buggy, dev eth0
Sep 25 21:04:01 kernel: protocol 0000 is buggy, dev eth0

Another reboot!!!
How can this be happening...
I haven't done anything in a week!!!
A small search in the form showed this discussion thread. Why not searching a bit yourself and opening a new thread as this topic is not related to the .19 release... :rolleyes:
 
A small search in the form showed this discussion thread. Why not searching a bit yourself and opening a new thread as this topic is not related to the .19 release... :rolleyes:
Thank you for the link.
My question wasn't about "protocol is buggy".
But the mysterious rebooting is and it started with the 384.19 update. That's my biggest issue!
 
Last edited:
But the mysterious rebooting started with the 384.19 update. That's my biggest issue!

Not that mysterious LOTS of people having issues with 384.19. For now it's best to just use 384.18 or go back to Stock until this mess gets sorted out when the new 386 code base becomes available.
 
Not that mysterious LOTS of people having issues with 384.19. For now it's best to just use 384.18 or go back to Stock until this mess gets sorted out when the new 386 code base becomes available.
Thank you for your response. I think I'll have to do that with my present router.
I may purchase a new AC86U for hot-swapping and to test firmware updates with the second unit.
 
Last edited:
<snip>... My guide states to use the procedure that works for your router. As a general guide, it is correct. I just don't list all the different ways (now, and in the future) that the methods I describe should be done on any particular router. Hope that is clear to you now.
pay attention - your procedure for a WPS reset is specifically for non-HND routers - as you state,"your router should reboot" - which it will never do - which confuses new users... several people have brought this up before - specifically two in this thread... your obsequious defense is tiring...
 
I have attached the Syslog of the last reboot.

I would disable firewall logging, as this may potentially cause issues under high load. It's generally only meant for network troubleshooting, not for daily usage.
 
I would disable firewall logging, as this may potentially cause issues under high load. It's generally only meant for network troubleshooting, not for daily usage.
Thank you, Merlin, I'll do that right away!
 
pay attention - your procedure for a WPS reset is specifically for non-HND routers - as you state,"your router should reboot" - which it will never do - which confuses new users... several people have brought this up before - specifically two in this thread... your obsequious defense is tiring...

It's not my procedure, this is the post I got that information from.


As for the two people that have had issues, did you help them with that?

If you didn't, I'm sure others did.
 
Status
Not open for further replies.

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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