What's new

ROG Rapture GT-AC5300 (Owners)

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

It stands for 802.11ad. But I assume it's an error in their code and most likely for the next gen.

Sent from my SM-G955U1 using Tapatalk
 
It stands for 802.11ad. But I assume it's an error in their code and most likely for the next gen.

Sent from my SM-G955U1 using Tapatalk

That'd be for the RT-AD7200, according to the GPL drop ;)

Latest GPL drop also has references to two 802.11ax models...
 
Any eta on those?

The only thing I know is the model name, as seen in the source code. Beyond that, I don't know anything about hardware specs or release date. And even that is subject to change - sometimes Asus use a temporary device name, and will change it at launch. For example, the RT-AC68U_V2 eventually became the RT-AC66U_B1.
 
For example, the RT-AC68U_V2 eventually became the RT-AC66U_B1.

Whoever made that decision should be spanked. So much confusion has come from the RT-AC66U_B1 name for that router. RT-AC68U_V2 actually describes the router very well!
 
Whoever made that decision should be spanked. So much confusion has come from the RT-AC66U_B1 name for that router. RT-AC68U_V2 actually describes the router very well!

At the time I didn't understand it either. Now that the RT-AC86U launched, I understand what marketing wanted to do. Basically, the RT-AC66U_B1 is seen as an update to the RT-AC66U, while the RT-AC86U is seen as an update to the RT-AC68U. One of the FCC registered name for the RT-AC86U is... RT-AC68U Extreme Performance. Ultimately, they are marketing it as the RT-AC86U instead, which is a good thing.

Marketing seem to think that how the router looks like is more important in determining a device name than its internals. This isn't really new, look at what Linksys did with the WRT54G over the years. Keeping in mind that the average end-user does not need to know about the internal details, their decision can be understood. It's only firmware tinkers and such who need to worry about these details.
 
I'm getting a ton of these update_qos_data entries in the log. I have QoS disabled. Running 15984. Any insight?

Code:
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
 
I'm getting a ton of these update_qos_data entries in the log. I have QoS disabled. Running 15984. Any insight?

Code:
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!

I had a lot of entries after turning my vpn off. I did a reboot of the router and that fixed it. Try a reboot and clear the log.


Sent from my iPhone using Tapatalk
 
This isn't really new, look at what Linksys did with the WRT54G over the years

At least Asus has been consistent across the variants - the WRT54G's jumped all over the place, and woe to one that picked up a VXWorks based device.
 
I'm getting a ton of these update_qos_data entries in the log. I have QoS disabled. Running 15984. Any insight?

Code:
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:09:53 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:08 kernel: ERR[set_app_info_qos_meta:3361] It's a paid app, please assign a default bandwidth!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:12 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!
Sep  1 12:15:13 kernel: ERR[update_qos_data_by_ip:3436] Failed to find udb entry by skb dst-IP!


Port 3436 is normally Exchange protocol. My wife had something like that on her laptop in the router log. I had her close out of Outlook and reopen and the error went away. Guessing it is still a bug but one that appears only after Outlook has been open for sometime.
 
That'd be for the RT-AD7200, according to the GPL drop ;)

Latest GPL drop also has references to two 802.11ax models...

It's getting clearer now? :p

I wonder, will they do a quad band version, 1 2.4GHz radio, 2, 5GHz radios, and 1 802.11ad radio?

Also, are they finally ditching the decrepit 1GbE?

Unlikely ..... from what i have heard ..... not sure it's possible to co-exist and operate 802.11ad and 802.11ax standard together.

Although ASUS has 802.11ad 1x1 on board on both their ASUS Intel X299 ROG Rampage VI Extreme (ASUS AREION 10GbE onboard) and ASUS AMD X399 Zenith Extreme with (ASUS AERION 10GbE as separate NIC).

https://www.asus.com/us/Motherboards/ROG-RAMPAGE-VI-EXTREME/

https://www.asus.com/us/Motherboards/ROG-ZENITH-EXTREME/

https://www.asus.com/Motherboard-Accessory/ROG-AREION-10G/
 
Anyone else having a issue to where when a device first connects the phy data TX rate is fine but this value keeps going down until less than 2Mbps?
 
Seems when I'm downloading from the USB 3.0 Harddrive via LAN my XboxOne ingame ping spikes to 500+ with massive packet loss! Never had this issue with the AC-5300..

Firmware: 3.0.0.4.382_15984-gf481f58
 
Anyone else having a issue to where when a device first connects the phy data TX rate is fine but this value keeps going down until less than 2Mbps?

That's normal power management, speed should go up once you actively start transferring data.
 
Hi, I've read through the whole thread. Still not sure whether to go for the GT -AC5300 or RT-AC5300. I like the idea of the GT newer model hardware etc.. just torn as I currently use your firmware on my rt-N66u. Getting an RT-AC5300 would be going backwards in terms of progression, but firmware wise a safe bet. Any solid recommendations would be appreciated
 
Port 3436 is normally Exchange protocol. My wife had something like that on her laptop in the router log. I had her close out of Outlook and reopen and the error went away. Guessing it is still a bug but one that appears only after Outlook has been open for sometime.
Thanks for the insight, I have Outlook open 24/7 so that is definitely plausible. Benefits and drawbacks of working from home :)
 
Hi, I've read through the whole thread. Still not sure whether to go for the GT -AC5300 or RT-AC5300. I like the idea of the GT newer model hardware etc.. just torn as I currently use your firmware on my rt-N66u. Getting an RT-AC5300 would be going backwards in terms of progression, but firmware wise a safe bet. Any solid recommendations would be appreciated
Based on the lack of reported issues with the latest firmware, myself included, I think it's pretty solid right now with GT-AC5300. I'm loving it.
 
Agree with SyntaxInvalid,
Latest firmware out on August 25th, version 3.0.0.4.382.15984 appears to fix many of the issues which basically disabled the router from it's boasted features. Most of these appear to now be working, although there are still many bugs that should be worked out in the months ahead. I may need to update my Amazon review to say this router is finally ready for primetime.

A reminder to everyone seeing something in your logs. Use the FEEDBACK tab on the router and send in the problems you see. This will go back directly to ASUS design engineers with logs from your device so they can work out the bugs. No one in the forum here is a worker from ASUS.
 

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