I have had my RT AC-5300 running firmware version 3.0.0.4.380.1355 for about a month and I have noticed what I believe is a bug with the 2.4Ghz. I have read a few posts that make me believe that it is a known issue but I would think more people would be complaining if it was. So I want to verify that this is a known bug. (Yes, I did a factory reset after upgrading to 1355 - Twice actually
)
When I first installed the router, I set it up using smart connect with all three radios and I noticed that when I came home thru the garage my iPhone attaches to 2.4Ghz due to the distance and I experience extreme connectivity issues. Meaning most functions fail to connect to the Internet.
So I did a few tests:
I ran these tests on both my iPhone 6 plus and my wife's iPhone 6 with the same results.
So my questions are:
Thank you very much for any info you can provide.
Dan

When I first installed the router, I set it up using smart connect with all three radios and I noticed that when I came home thru the garage my iPhone attaches to 2.4Ghz due to the distance and I experience extreme connectivity issues. Meaning most functions fail to connect to the Internet.
So I did a few tests:
- I enabled the 2.4Ghz Wireless MAC filter in Reject Mode and added my iPhone. I tested for a few weeks and never had an issue except the 5Ghz signal isn’t quite usable in my garage. This causes problems when the weak wifi gets in the way of LTE. When I try to map a destination or start streaming music before pulling out of the garage is simply doesn’t work due to the fact that it keeps connecting and disconnecting from the wifi due to the weak signal.
- I then enabled the 5Ghz-1 and 5Ghz-2 Wireless MAC filter in Reject Mode and added my iPhone. Within a few hours I experienced connectivity issues even when sitting on my couch which is 10 feet from the router.
I ran these tests on both my iPhone 6 plus and my wife's iPhone 6 with the same results.
So my questions are:
- Is this a known issue to the community here?
- Are there any work arounds?
- Is this a known issue to ASUS?
- Any ETA on a fix?
- Does this issue exist in the Alpha (Version 20151231)?
Thank you very much for any info you can provide.
Dan
Last edited: