What's new

[Release 384/NG] Asuswrt-Merlin 384.5 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!

Just setup a 86U plus have a Raspberry Pi 3 Model B+ running Picoreplayer and everything is working ok over 5ghz WiFi
Ok, did some more research...
Just reset / factory default / initialize the router, RT-AC88u and reconfigured everything from scratch.
The two Raspberry's 3 B are the only devices NOT connecting to the WiFi
BUT
when I enable any Guest Wifi, then they connect to the correct SSID (not the guest SSID). :D :D Funny, right?
 
Last edited:
Ok, did some more research...
Just reset / factory default / initialize the router, RT-AC88u and reconfigured everything from scratch.
The two Raspberry's 3 B are the only devices NOT connecting to the WiFi
BUT
when I enable any Guest Wifi, then they connect to the right SSID (not the guest SSID). :D :D Funny, right?

Only time i've had problems with WiFi and Pi's is if a use symbols in the password
 
Problems with wireless

Here is the setup - all brand new with NO old configs

central router - rt-ac88u
two repeater bridges - rt-ac68u

wired works great
wireless 5ghz clients do not work on the repeater bridges - but the repeater bridges are connected to the ac88u using 5ghz

2.4ghz wireless on the ac88u speed degrades over time until a hard or soft reboot fixes it


Short of going back to the old code base, not sure what to do now. Will try and disable mimo and beamforming and see if that makes any difference.
 
@RMerlin do you know why or if there is anything that can be done about Traditional QOS classifying all VPN traffic as low priority? I know Traditional QOS monitors upload traffic only but it is clearly being classed as low traffic. I have changed ports on the VPN to use port 80 which should automatically class it as highest priority. You can work around this by using the TQOS settings creatively but it would be nice if it was classed right. I couldn't care less if the bandwidth monitor page stays messed up I know that is a known issue. The graph in TQOS stats page displays the information correctly. A lot of people are using VPNs now a days it would be nice to see this problem fixed. Would the developer of the recent patch be open to looking into this for us?
 
Anyone see anything like this in their logs since upgrading? I'm getting this on one of the two remote repeaters rt-ac68u both running 384.5.

ay 17 16:59:02 kernel: TCP: time wait bucket table overflow
May 17 16:59:02 kernel: TCP: time wait bucket table overflow
May 17 16:59:02 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: net_ratelimit: 433 callbacks suppressed
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:07 kernel: TCP: time wait bucket table overflow
May 17 16:59:18 kernel: net_ratelimit: 29 callbacks suppressed


Netstat doesn't show anything

tcp 0 0 0.0.0.0:5473 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:18017 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3394 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:printer 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:laserjet 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9998 0.0.0.0:* LISTEN
tcp 3 0 0.0.0.0:www 0.0.0.0:* LISTEN
tcp 0 0 localhost.localdomain:domain 0.0.0.0:* LISTEN
tcp 0 0 router.asus.com:domain 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3838 0.0.0.0:* LISTEN
tcp 0 0 router.asus.com:www 192.168.1.174:58521 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58528 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58519 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58520 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58529 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58512 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58491 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58523 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58505 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58488 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58538 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58525 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58530 TIME_WAIT
tcp 457 0 router.asus.com:www 192.168.1.174:58547 ESTABLISHED
tcp 0 0 router.asus.com:www 192.168.1.174:58479 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58489 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58555 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58554 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58507 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58508 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58503 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58499 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58524 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58510 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58537 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58498 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58556 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58480 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58517 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58552 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58483 TIME_WAIT
tcp 0 0 router.asus.com:www 192.168.1.174:58504 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58514 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58485 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58522 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58515 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58518 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58490 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58534 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58544 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58546 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58492 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58526 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58542 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58535 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58533 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58516 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58502 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58553 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58487 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58549 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58527 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58543 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58540 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58493 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58484 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58511 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58541 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58509 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58500 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58506 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58513 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58545 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58501 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58494 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58482 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58539 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58548 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58551 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58531 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58486 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58532 TIME_WAIT
tcp 0 0 router.asus.com:www dellxps8700:58536 TIME_WAIT
 
After updating 3200 I am no longer able to connect to 2.4 wireless will try doing a factory reset.
 
@RMerlin do you know why or if there is anything that can be done about Traditional QOS classifying all VPN traffic as low priority? I know Traditional QOS monitors upload traffic only but it is clearly being classed as low traffic. I have changed ports on the VPN to use port 80 which should automatically class it as highest priority. You can work around this by using the TQOS settings creatively but it would be nice if it was classed right. I couldn't care less if the bandwidth monitor page stays messed up I know that is a known issue. The graph in TQOS stats page displays the information correctly. A lot of people are using VPNs now a days it would be nice to see this problem fixed. Would the developer of the recent patch be open to looking into this for us?

The traffic classifier is configured for the eth0 and br0 interface, therefore it won't touch the tun2* or tun1* traffic. That means traffic probably ends up in the default queue.
 
Only numbers and characters, no symbols.
Is there a bugzilla or similar available with RMerlin?

Anything wifi related is outside of my control, so there's no point in filing a bug report.
 
Problems with wireless

Here is the setup - all brand new with NO old configs

central router - rt-ac88u
two repeater bridges - rt-ac68u

wired works great
wireless 5ghz clients do not work on the repeater bridges - but the repeater bridges are connected to the ac88u using 5ghz

2.4ghz wireless on the ac88u speed degrades over time until a hard or soft reboot fixes it


Short of going back to the old code base, not sure what to do now. Will try and disable mimo and beamforming and see if that makes any difference.


I think I read something about Asus broke Repeater Mode for quite some time ago, but I'm not sure since I gave up repeater mode a couple of years ago and switched to ap mode instead.

You write "repeater bridges", and that's two different modes. I believe you have 4 choices: Router, repeater, access point and media bridge. Are you sure you haven't chosen media bridge? (then wired would work, but not wireless). In repeater mode wireless should work, but not wired. The only way to get both wired and wireless working at the same time, is to stretch a cable and choose ap mode.
 
Last edited:
I updated my RT-AC56U to 384.5 and got these new errors and functions not working properly. I did factory reset and updated from 380.70 to 384.5 over each version number by single:

1. Traffic monitor does not work, no real values recorded, just a few MB.
2. Copying files from USB to USB does kill the smb share, cant work with it on LAN.
3. Tor does not longer support changing of the exit node with a new Nym.
And maybe 4. there are some additional new errors in the log

kernel: Virtual device eth2 asks to queue packet!
kernel: Virtual device eth1 asks to queue packet!

Now I have to rollback to 369, because needed function no longer work :-(
 
I updated my RT-AC56U to 384.5 and got these new errors and functions not working properly. I did factory reset and updated from 380.70 to 384.5 over each version number by single:

1. Traffic monitor does not work, no real values recorded, just a few MB.
2. Copying files from USB to USB does kill the smb share, cant work with it on LAN.
3. Tor does not longer support changing of the exit node with a new Nym.
And maybe 4. there are some additional new errors in the log

kernel: Virtual device eth2 asks to queue packet!
kernel: Virtual device eth1 asks to queue packet!

Now I have to rollback to 369, because needed function no longer work :-(

Why? Doesn't 380.70 work any longer either?

You have of course "Initialized" not just factory default after upgrading to 384.5, reset browser cache and not read in some old backup file of any settings, but configured all from scratch?
 
Government laptop won't stay connected to 5Ghz. All other wireless devices are fine.
It works fine with wired. I see this in log. It mean anyting?

May 18 07:05:48 dnsmasq-dhcp[814]: Ignoring domain internal.hatma.dom for DHCP host name FLL1D45424
May 18 07:08:03 dnsmasq-dhcp[814]: Ignoring domain internal.hatma.dom for DHCP host name FLL1D45424
May 18 07:19:01 dnsmasq-dhcp[814]: Ignoring domain internal.hatma.dom for DHCP host name FLL1D45424
Ma
 
Government laptop won't stay connected to 5Ghz. All other wireless devices are fine.
It works fine with wired. I see this in log. It mean anyting?

May 18 07:05:48 dnsmasq-dhcp[814]: Ignoring domain internal.hatma.dom for DHCP host name FLL1D45424
May 18 07:08:03 dnsmasq-dhcp[814]: Ignoring domain internal.hatma.dom for DHCP host name FLL1D45424
May 18 07:19:01 dnsmasq-dhcp[814]: Ignoring domain internal.hatma.dom for DHCP host name FLL1D45424
Ma

Your laptop is requesting an address using it's full domain name, FLL1D45424.internal.hatma.dom. DHCP is ignoring the domain part and only using the host name to register an IP address to. It's an informational message and there's nothing to worry about.
 
Not worried but it won't stay connected to WiFi. Husband's laptop.
I see the same entries but only 2 when wired.
Your laptop is requesting an address using it's full domain name, FLL1D45424.internal.hatma.dom. DHCP is ignoring the domain part and only using the host name to register an IP address to. It's an informational message and there's nothing to worry about.
 
I think I read something about Asus broke Repeater Mode for quite some time ago, but I'm not sure since I gave up repeater mode a couple of years ago and switched to ap mode instead.

You write "repeater bridges", and that's two different modes. I believe you have 4 choices: Router, repeater, access point and media bridge. Are you sure you haven't chosen media bridge? (then wired would work, but not wireless). In repeater mode wireless should work, but not wired. The only way to get both wired and wireless working at the same time, is to stretch a cable and choose ap mode.

Yeah, i meant repeater mode. In repeater mode, wired and wireless both work. I have had it running in this configuration for quite some time. Just not on this code base. The two repeaters are connecting to the central router via 5ghz. All of the wired ports are then directly connected to media devices on the repeaters. And the repeaters provide coverage for that area.


In case it helps anyone else...

I completely initialized the two remote repeaters and reconfigured them again and they appear to be stable for now and I can connect to them wired, 2.4 and 5ghz now. This time i turned off one while i setup the other to just to test out everything and make sure it wasn't' some sort of broadcast or layer 2 interference.

Still having problem with the ac88, but only on 2.4ghz speed throughput goes down to less than 1 megabit/s. Wired and 5ghz are fine and at full speed. Still trying to track this down. I noticed changing the SSID immediately restores the performance for a period of time, then it goes back to being slow. Logs don't really show anything. May change the channel bandwidth and modulation scheme next to see if they make any difference.
 
Last edited:
Not worried but it won't stay connected to WiFi. Husband's laptop.
I see the same entries but only 2 when wired.

What os? what adapter? Are the adapter drivers up to date? Which mode AC/N? Does he have admin rights to check the device settings? If its a government issued laptop and you can't connect and don't have admin rights.... my recommendation is stick with 2.4 ghz if that is working.
 

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