What's new

[RT-AX88U] New Firmware version 3004.384_6210

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

Firmware version 3004.384_6210
- Release Note -

Bug fixes and improvement:
1. Optimized AiMesh backhaul connection.
2. System stability improvement.
3. Fixed IPv6 related bugs.

A link to the firmware would be helpful. :)
 
You are right but unfortunately this one is not available on the ASUS website. I discovered on my router few minutes ago ;)
 
Surprisingly it is only available if Windows 8.1 32 Bit is selected as an option. :p

Edit: Now available for all OS.

BTW Asus cannot get their arse around unresponsive GUI buttons problem in Firefox. Yes. Some buttons in router interface just dont work in Firefox.
 
Last edited:
Hi, any feedback about this firmware ? any idea if the source code will be released soon ? I am still verifying merlin 384.12, but and as sooner or later it will integrate this firmware level, it would be interesting to hear about how it is working ...
 
Running smoothly & continuously
Hi, any feedback about this firmware ? any idea if the source code will be released soon ? I am still verifying merlin 384.12, but and as sooner or later it will integrate this firmware level, it would be interesting to hear about how it is working ...

Running smoothly & continuously from installation.
 
  • Like
Reactions: FTC
Well I have had this build on my router a day, or two without any issues, besides the "WAN Aggregation" issue that has been there since the last build included this feature. I have a Arris SB8200, and with this router, having rebooted both units with LAG enabled, no cables attached between the two, until both have fully rebooted. Which is what the instructions of this router asks you to do.

However once this feature is enabled, and starts passing data over the WAN, the router starts spamming errors, which I will tag in this post below. I hope ASUS gets it together with this issue. As I have already discussed this with one of the docsis engineers from my ISP's HQ, and he told me, they have reached out to ASUS for test units, and have never heard anything back. Which is sad to hear, because it tells me, they lack communication overall. As my ISP(Cox) is a good sized provider here in the US. No reason why ASUS should be ignoring them.

Code:
May 10 12:28:23 kernel: net_ratelimit: 91 callbacks suppressed
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: net_ratelimit: 83 callbacks suppressed
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: net_ratelimit: 100 callbacks suppressed
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: net_ratelimit: 96 callbacks suppressed
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: net_ratelimit: 82 callbacks suppressed
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
 
Would anyone here care to tell me what speeds they are getting when using Asus Download Master on the RT-AX88U?

I have an older AC56U router and I usually get around 8-9000 KBps in Asus D.M. (my internet speed is 300Mbps) and I 'm wondering if an upgrade would be worthwhile.

PS: D.M. is installed on a Kingston A400 SSD attached to the router via USB 3.0.
 
Well I have had this build on my router a day, or two without any issues, besides the "WAN Aggregation" issue that has been there since the last build included this feature. I have a Arris SB8200, and with this router, having rebooted both units with LAG enabled, no cables attached between the two, until both have fully rebooted. Which is what the instructions of this router asks you to do.

However once this feature is enabled, and starts passing data over the WAN, the router starts spamming errors, which I will tag in this post below. I hope ASUS gets it together with this issue. As I have already discussed this with one of the docsis engineers from my ISP's HQ, and he told me, they have reached out to ASUS for test units, and have never heard anything back. Which is sad to hear, because it tells me, they lack communication overall. As my ISP(Cox) is a good sized provider here in the US. No reason why ASUS should be ignoring them.

Code:
May 10 12:28:23 kernel: net_ratelimit: 91 callbacks suppressed
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:23 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: net_ratelimit: 83 callbacks suppressed
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:29 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: net_ratelimit: 100 callbacks suppressed
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:35 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: net_ratelimit: 96 callbacks suppressed
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:41 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: net_ratelimit: 82 callbacks suppressed
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1
May 10 12:28:47 kernel: protocol 0800 is buggy, dev eth1

With WAN AG on are you able to get over gig speeds?

I have everything configured right with WAN AG working connected via LAG LACP to my RT-AX88U. I then have LAG LACP going from the RT-AX88u to a 10gig switch. My download is still capped at 950 Mbps. However, when using this exact same configuration, but replacing the RT-AX88U with a Netgear router with WAN AG on I get 1150 Mbps down. It is like the WAN AG is not working on the RT-AX88U.

I am tempted to factory reset and try this new ASUS firmware to see if it resolves this as I am currently running Merlin 384.12.

Any feedback would be very helpful.

Thanks!
 
Last edited:
Yeah speeds for me have been very inconsistent when this feature is enabled on the router, and modem. I have higher more consistent speeds with it disabled. At least for me the router system log is repeatedly spammed filled with the same two errors I listed above. I honestly feel that's part of the problem, and why it isn't working as intended.

At this point it's hard to know who's to blame on this. What I do know is one of my ISP's guys who works at their HQ, has tried to reach out to ASUS to get a test unit, to try to figure this out. Sadly ASUS hasn't communicated with them. So getting this resolved is damn near impossible right now. I know my ISP guy has reached out to them more then once as well. At this point, I'm not happy with ASUS support. Yes they push out firmwares often, but having damn near nonexistent customer support, is pathetic to be honest.
 
Last edited:
OK. I factory reset. Loaded 3.0.0.4.384_6210 and factory reset again to be safe. All is well now!

I get ~1,150 Mbps now and WAN AG is working properly now.
My log no longer has those "protocol 0800 is buggy, dev eth1" errors flooding it.

Please note. Turning on Traffic analyzer, QOS, Bandwidth Monitor, AiProtection, or Parental Controls will all reduce the speed back down to about 800-900 Mbps. As I am assuming they disable the HW Acceleration and it will slow down the router some.

I am going to rock this firmware for now. I am sure Merlin is hard at work like always working on the next one of his firmwares. I am going to assume he will utilize this version and hopefully it will be fixed in his next firmware release.

Please let me know if you need any assistance in getting your running nicely like I am now.
 
At this point, I'm not happy with ASUS support. Yes they push out firmwares often, but having damn near nonexistent customer support, is pathetic to be honest.

I've called their (US) Support 3-4 times over the years and they have always answered my call, opened a case, and worked to resolve my issue. On one case, they provided custom firmware and communicated back and forth over e-mail to troubleshoot the issue. No complaints here.

OE
 
I've called their (US) Support 3-4 times over the years and they have always answered my call, opened a case, and worked to resolve my issue. On one case, they provided custom firmware and communicated back and forth over e-mail to troubleshoot the issue. No complaints here.

OE

Well I can't say the same... as I did this not to long ago, regarding this issue. I exchanged email's with them, they asked for certain info, which I provided, only for them to reply back asking for the same info. Which I had already sent back to them, and they replied to that email. So as a customer in this case, that's not good on their part. That to me is piss poor, as it seems like the person replying to the email isn't even reading over it, before replying asking for same stuff again.

I ended up exchanging multiple email's with their support, and honestly felt like I was going in a circle, trying to get the issue looked into further. I just stopped replying at a certain point, due to how things were going. I have better things to do, then to explain an issue 5+ times, and supply the info they asked multiple times. Never getting the issue looked into further. I have always been very respectful, and given support reps plenty of time, before I am done with them. Which is what happen to me about a month, or so ago.

Things may have went better for you, but in my case it didn't, and also hearing from my ISP guy saying he also got nothing back from them. That to me is enough, for me to say their customer support is lacking a lot. So I will stay with my opinion on that for now. Overall I'm glad things have worked out better for you, when you have contacted them. Not the case for me, and to top it off. I have always been one to provide plenty of info as well, when reporting an issue. So there wasn't a lack of detail on my part, when I reported this to them.
 
Well I can't say the same... as I did this not to long ago, regarding this issue. I exchanged email's with them, they asked for certain info, which I provided, only for them to reply back asking for the same info. Which I had already sent back to them, and they replied to that email. So as a customer in this case, that's not good on their part. That to me is piss poor, as it seems like the person replying to the email isn't even reading over it, before replying asking for same stuff again.

I ended up exchanging multiple email's with their support, and honestly felt like I was going in a circle, trying to get the issue looked into further. I just stopped replying at a certain point, due to how things were going. I have better things to do, then to explain an issue 5+ times, and supply the info they asked multiple times. Never getting the issue looked into further. I have always been very respectful, and given support reps plenty of time, before I am done with them. Which is what happen to me about a month, or so ago.

Things may have went better for you, but in my case it didn't, and also hearing from my ISP guy saying he also got nothing back from them. That to me is enough, for me to say their customer support is lacking a lot. So I will stay with my opinion on that for now. Overall I'm glad things have worked out better for you, when you have contacted them. Not the case for me, and to top it off. I have always been one to provide plenty of info as well, when reporting an issue. So there wasn't a lack of detail on my part, when I reported this to them.

E-Mail, like texting, is problematic by itself. I prefer to call and negotiate the service I need, which has proven to be most reliable.

OE
 
E-Mail, like texting, is problematic by itself. I prefer to call and negotiate the service I need, which has proven to be most reliable.

OE

See this is where I disagree with you. When trying to discuss problem's like this, it's much better to do it via email, then over the phone. Due to being able to show the problem via text, especially when talking about errors happening via the system log. Plus you can easily attach files, and screenshots, and such. Over the phone, it can easily be hard to explain certain issues, while trying to "show" them the actual issue happening.

So when it comes to routers, and problem's within the software running on these router. The router companies need to be very good at customer support via email. I have used email a million times, and never had an issue understand another person's email. Unless they were typing things all jacked up. The "whole" issue to me... seems to come down to the people they have answering customer support emails. One being they're not taking the time to actually read the email, and number two, a lot of companies have a default response system. Which is piss poor to begin with.

Finally I have used phone support many of times over the years, and there's a time, and place for it. But when trying to explain certain issue's, like the one I mentioned in this thread. It's much easier on both sides, for info to be exchanged via email. Overall easier to explain the issue, and provide more detail to the issue itself. So as of now, I will not change my view on ASUS's customer support. It is poor, and needs to be better. Customers shouldn't have to repeatedly send the same info, especially when you know they got the email, and replied back to you, from that email. As I said above, it just shows a lack of support reps actually reading the email. Before replying with a standard response, asking for more info.
 
I think this issue is an oldie but a goodie: The wan disconnects at irregular intervals.
From my logs:

Jul 4 14:55:53 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Jul 4 14:55:56 WAN Connection: ISP's DHCP did not function properly.
Jul 4 14:56:01 WAN Connection: Ethernet link down.
Jul 4 14:56:04 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex
Jul 4 14:56:06 WAN Connection: Ethernet link up.
Jul 4 14:56:06 rc_service: wanduck 9858:notify_rc restart_wan_if 0
Jul 4 14:56:06 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link DOWN.
Jul 4 14:56:09 kernel: eth0 (Int switch port: 3) (Logical Port: 3) (phyId: c) Link UP at 1000 mbps full duplex
Jul 4 14:56:13 rc_service: udhcpc 11467:notify_rc start_firewall

I share the internet connection with another router. It has no issues.

W
 
Jul 4 14:56:01 WAN Connection: Ethernet link down.

This indicates that your modem got physically disconnected, has a bad cable, or rebooted itself.
 
This indicates that your modem got physically disconnected, has a bad cable, or rebooted itself.
Yes, you would think that, but the fact that the internet is shared with another router (I pull 2 IP's) that never disconnects, is what throws me. Also WAN issues have been discussed before by those with an AX88U. I also seem to remember that during a breakdown of the unit when it was initially released, the person doing the analysis, found an issue with the mounting of the WAN connector. (tell me if I am wrong)
Of course all this would allow for the possibility that the issue could be hardware related (rather than firmware) :confused:

UPDATE: I have now replaced all older cables with the newer ribbon style cables on my system.
So now I am in "hurry up wait" mode.
 
Last edited:
Well the weekend has come and gone and things have stabilized. It seems that I have solved this issue. The only thing I can say for sure is that the WAN disconnects were not firmware related.
I did the following 3 things:
1) I powered down a network camera that was flooding my LAN with traffic because I had turned off internet access. (trying to call home)
2) I was using ping to check my internet status and was pinging my ISP's gateway to do that. Possibly my ISP did'nt like that.
3) On the off chance the problem was cable related, I upgraded all my cables to the newer "ribbon" style cables.

FYI
 

Latest threads

Sign Up For SNBForums Daily Digest

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