What's new

Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

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

Status
Not open for further replies.
@banger what speed are you expecting exactly from a single client in Load Balance mode?

You're getting higher than I would have expected.
 
@banger what speed are you expecting exactly from a single client in Load Balance mode?

You're getting higher than I would have expected.
Agree.

Would not expect a load balancing mechanism to deliver anything faster than the fastest connection.

It's possible that either the 48 connection is actually faster or there is an error in measurement.
 
3 days up without a hitch. Aside from the quality of life requests from the members here this update has everything I need and is working well. It's kind of sad actually, now I have nothing to look forward to in upcoming firmwares.
 
It would be convenient if ASUS could add Quad9 DNS to this firmware.

OE
 
It would be convenient if ASUS could add Quad9 DNS to this firmware.

If you mean on the WAN dropdown, more important would be to remove the Symantec DNS servers, as that service was discontinued two years ago, back in November 2018.

The dropdown list also needs to be retrieved over https instead of http. When accessing the web interface over https, Chrome (among others) will refuse to retrieve the Asus-hosted DNS server list over http, as mixed content is no longer allowed. That prevents the dropdown from appearing at all when accessing your router over https.
 
If you mean on the WAN dropdown, more important would be to remove the Symantec DNS servers, as that service was discontinued two years ago, back in November 2018.

The dropdown list also needs to be retrieved over https instead of http. When accessing the web interface over https, Chrome (among others) will refuse to retrieve the Asus-hosted DNS server list over http, as mixed content is no longer allowed. That prevents the dropdown from appearing at all when accessing your router over https.

Sounds good... remove the defunct Symantec DNS selections and make the DNS dropdown list function over https.

And add Quad9. :)

OE
 
Yeah, I can never remember Quad9's IP when I have to enter it manually.;)

If ASUS were to include it, it would increase awareness and generate feedback, good or bad, which would help to inform us and to prove it.

OE
 
and make the DNS dropdown list function over https.

That one might be trickier to fix however. Asus's server uses a "generic" Amazon certificate, so it doesn't match with the canonical hostname used by Asus when accessing the file. Just switching to https will cause the browser to reject it due to mismatched SAN.
 
Grr im having some ugliness with my DSL and not sure if its the router or the connection which only coincidently started around the time of the last beta update...
And the modem isnt being helpful ..... partially because its in bridge mode...

-J
What kind of ugliness? I have had a couple of disconnects in short succession but it is typically the time of the day when ISPs reboot edge routers.
 
Does the RC6 support mesh with mixed wired/wireless backhauls? Meaning some nodes are on wired and some on wireless?
 
Does the RC6 support mesh with mixed wired/wireless backhauls? Meaning some nodes are on wired and some on wireless?
mlai,
Yes it works, I read you post, pulled out my Ethernet Cable RJ45 on one of my AiMesh Nodes :)
Screenshot 2020-10-12 at 18.02.32.pngScreenshot 2020-10-12 at 18.03.21.png
 
Last edited:
It's dedicated only for 3 bands routers. For 2 bands it's shared, so clients are connecting to the same radio that's used between router and node.
 
Is it still needed to move the routers close to each other to initialize an AiMesh node wireless, or can it be done on wired connection with the distance kept?
 
Is it still needed to move the routers close to each other to initialize an AiMesh node wireless, or can it be done on wired connection with the distance kept?

My latest factory reset was performed without moving the node.
Although they can see eachother on 2.4, with official release I couldn't enroll the node without bringing it closer.
 
Is it still needed to move the routers close to each other to initialize an AiMesh node wireless, or can it be done on wired connection with the distance kept?
Vispen74,
I have not move node closer to router for a long time like in the earlier days of AiMesh. For my case with CAT 6 / 7 cable connected between AiMesh Router and AiMesh Nodes, I have an unmanaged switch between them that works well in AiMesh Network.
 
Is it still needed to move the routers close to each other to initialize an AiMesh node wireless, or can it be done on wired connection with the distance kept?

I have been able to add my wireless remote node in place at 77' for quite awhile now. Just try it.

OE
 
Status
Not open for further replies.

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