Could you please describe how aggressively steer to 5Ghz can be done?
Thank you!
Sent from my ONE A2003 using Tapatalk
I posted already the settings in screenshots!
Sent from my iPhone using Tapatalk
Could you please describe how aggressively steer to 5Ghz can be done?
Thank you!
Sent from my ONE A2003 using Tapatalk
I am a J2EE developer...Yea, the Network Map code was much better in 380 as Merlin maintained it.
Asus have now closed source that code in the new 382 branch and so it has re-gained many of the fixes Merlin added over the years. It’s a real shame IMO!
As I mention above though, for devices you set manual IP for in the DHCP Server you can work around the issues.
The point on refresh, I find if I’m patient and let it refresh a second time it will correct itself. The System Log>Wireless Log is more reliable for seeing device>band associations and I use it more frequently since moving to the 382 code.
Sent from my iPhone using Tapatalk
Uhm... I do not know where I read that the CPU of the RT-AC88U is more powerful and the "routing" is better.I think Merlin plans to keep the 380 branch alive for a while with critical security patches only (so it will keep the open source network map code). Most development is focused on 382 now (which already has as many 380 Merlin changes as possible merged into it).
The DSL variant is identical hardware except for the addition of the DSL port instead of WAN port. The DSL variants cannot run Merlin code though as the DSL drivers are not possible to include.
Sent from my iPhone using Tapatalk
Ok, but powerline kill VDSL...I also have to use a separate DSL modem, but for me it is an advantage.
The modem is on the phone master socket, and then a secure powerline sends Ethernet to my office where the 88U is, so I have the best Wi-fi in the office and the 8x LAN ports.
If I just DSL-88U I would have to get a separate LAN switch in the office and Wi-fi would be not as strong going across the house.
Sent from my iPhone using Tapatalk
Ok, but powerline kill VDSL...
Ah ok.1300Mbps powerline and 50Mbps VDSL. Has 0 impact for me!!
Sent from my iPhone using Tapatalk
Ah ok.
Sorry, I imagined you in the US with 10 GB of FTTH...
In my small Italian village of 4800 men a month ago I had ADSL at 3 (!!!) MB and 0.8 kb upload...
Now at least VDSL at 75-80 MB and 20 uploads, for me gold.
And think that I always speak ugly of Italy...I’m similar to you, rural UK, small town. Max 80Mbps VDSL, but I am too far from the FTTC to get more than 50
Sent from my iPhone using Tapatalk
When viewing the list of clients connected under Network Map > View List, the MAC address is populating the client name instead of using the netbios name. This seems to occur for most devices and various OS. It leads to further problems when say you’re defining openvpn client policy routing. The colon in the MAC address is not an acceptable character so you have to rename it.
Device: RT-AC86U
Firmware: 382.1
working fine with 382 no problem so farAbout a week ago, Astrill updated their Router Plug-in to 2.9.9.5
Has any tried whether this is now compatible with the 382 branch?
I just installed 382_1 on my RT-AC88u after having problems with the latest asus firmware in relation to my Chromecast. With the latest asus firmware my chromecasts wouldnt even be discoverable from my Android phone. With an older asus firmware (Aug 2016) Chromecast worked perfectly, showed up instantly. With 382_1 chromecasts are discoverable but it takes a bit of time - 10-15 seconds.
Are there prospects for improving this on 382? Should I go back to the latest 380? I hate to use the old Aug 2016 asus firmware because of all the security issues....
Update: Problem resurfaced on the 382 firmware after a while similar to stock firmware symptoms - chromecasts aren't discoverable. Tried 380.68_4 and same symptoms - Chromecasts don't show up at all. Guess I'm back to the Aug 16 Asus firmware for now, as at least that works..
I just installed 382_1 on my RT-AC88u after having problems with the latest asus firmware in relation to my Chromecast. With the latest asus firmware my chromecasts wouldnt even be discoverable from my Android phone. With an older asus firmware (Aug 2016) Chromecast worked perfectly, showed up instantly. With 382_1 chromecasts are discoverable but it takes a bit of time - 10-15 seconds.
Are there prospects for improving this on 382? Should I go back to the latest 380? I hate to use the old Aug 2016 asus firmware because of all the security issues....
Update: Problem resurfaced on the 382 firmware after a while similar to stock firmware symptoms - chromecasts aren't discoverable. Tried 380.68_4 and same symptoms - Chromecasts don't show up at all. Guess I'm back to the Aug 16 Asus firmware for now, as at least that works..
Its appears that's not the case mine show up perfectly fine.
Have you tried searching for them with the home app after rebooting them.
Sometimes they can get stuck in a cycle of thinking they are connected when they are not after a wireless loss.
I regularly use a Chromecast at home on my RT-AC88U (about 2-3 times a week), never had any discoverability issue.
I wonder if it's some setting that I have or if I should factory reset.....
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!