What's new

AC66U-B1 Firmware version 3.0.0.4.384_32738

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

Ken Atkinson

Regular Contributor
Firmware version 3.0.0.4.384_32738
- Release Note -

AiMesh new features:
- Supported creating mesh system with new router, BlueCave.
- Added Roaming block list in Advanced Settings --> Wireless.
You can add devices into block list and this device will not be roamed between AiMesh nodes.
- Supported ethernet onboarding. User can use ethernet cable.
You can use ethernet cable to connect AiMesh router LAN port and AiMesh node WAN port first and run the adding node process to build the mesh system.

Security fixes:
- Fixed Reflected XSS vulnerability.
- Fixed CSRF vulnerability.
- Fixed command injection vulnerability.
- Fixed stack buffer overflow vulnerability.
Thanks for Rick Ramgattie contribution.

Bug fixed and Enhancements:
- Fixed USB hard drive over 2TB compatibility issues.
- Fixed Samba/FTP folder permission issues.
- Added USB3.0/2.0 mode switch setting in Administration --> System --> USB Settings.
 
Thanks, running well so far on my 68U, device list seems to be more stable now.
 
Still no SMB2.

Sent from my P01M using Tapatalk
 
sure, as I said, they are all bit-ident, only different names, you could name it 123.trx as well for upload, absolutely of no relevance.
 
About roaming block list, what happen if the device connect to a weak signal AP first? I think the roaming block list will be more useful if we can lock down which AP the device can connect to.
 
Hopefully the rest of the AiMesh routers will receive update soon.

soon

Many models will get new updates soon. So far to my understanding there should be updates on
- USB control (Thanks to the contribution of forum user DolfG)
- Updates on AiMesh
- Enhancements on "SIP Passthrough" function

Time frame varies with the release schedule and test results.

regards,

Jack Cheng, ASUS Australia
 
About roaming block list, what happen if the device connect to a weak signal AP first? I think the roaming block list will be more useful if we can lock down which AP the device can connect to.
Agreed. You should be able to select the device Mac addresses and assign it to a specific node. This would help a few of my clients connect to specific nodes that get a great signal, use MuMiMo (as only my main router supports it) and load balance the network a little. This would be especially useful for clients that stay in one spot and do not physically move around the network.

Sent from my LG-US998 using Tapatalk
 
About roaming block list, what happen if the device connect to a weak signal AP first? I think the roaming block list will be more useful if we can lock down which AP the device can connect to.

Pretty much what many of us have been asking for since the early days of the AIMesh beta releases, so either Asus just don’t “get it” or they can’t or don’t want to do it?
 
Why device connect to a "week signal" AP first? When you locked down, your specified device can't connect to other AP anymore.
 
Why device connect to a "week signal" AP first? When you locked down, your specified device can't connect to other AP anymore.
Because you come home and first floor node got better outdoor coverage and so you're locked to this while you only stay downstairs where you want to be connected all the time!

I see really no need for disabling roaming but a large need for locking devices to a defined nodes,
mostly for stationary devices.

Or more simple case, you are in the kitchen connected to 2G, turn on microwave ofen and loose connection but still see weak first floor router 5G, so you are locked to the other node no chance to go back.
 
For the microwave case, how do you think to disable the 2G service? BTW, it's a simple case study.

For the locked device with specific nodes, the device can't connect with other nodes (none specific nodes), correct?
If the specific nodes crashed, the device can't connect anymore. Correct?
 
2G is needed for coverage, so usually needed all the time.
And as each band is limited to an amount of clients we need it to put them on different channels.

Yes would be correct, then one or the other wont have connection anymore, but the rest still working well.
If they would roam to the other node this will crash because too many clients want to connect.

This are advanced features of course and not standard implementation of Aimesh!

How would you describe the usage of the new feature to disable roaming?
What are the benefits of it?
In which case and how would you use it?
 
If they would roam to the other node this will crash because too many clients want to connect.
I think this is roaming case with load balance.

How would you describe the usage of the new feature to disable roaming?
What are the benefits of it?
In which case and how would you use it?
Client Device can handle his wifi connectivity without AiMesh roaming control.
 
How would you describe the usage of the new feature to disable roaming?
What are the benefits of it?
In which case and how would you use it?
WiFi calling with AiMesh in your home makes WiFi calling unusable because the call drops when the device switches access points. I changed all my ASUS devices back to repeaters with separate SSID's just to resolve this WiFi calling issue. In theory, now that I can isolate our cell phones to our primary main floor access point this should resolve the dropped call issue. The only problem this doesn't fix is now the phones won't connect to my basement access point to have great coverage behind my house at our pool. So it fixes one issue and introduces a new one. I'm thinking I may just leave my configuration the way it is, keeping the family happy at the moment.
 
WiFi calling with AiMesh in your home makes WiFi calling unusable because the call drops when the device switches access points. I changed all my ASUS devices back to repeaters with separate SSID's just to resolve this WiFi calling issue. In theory, now that I can isolate our cell phones to our primary main floor access point this should resolve the dropped call issue. The only problem this doesn't fix is now the phones won't connect to my basement access point to have great coverage behind my house at our pool. So it fixes one issue and introduces a new one. I'm thinking I may just leave my configuration the way it is, keeping the family happy at the moment.

iOS?

OE
 

Similar threads

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