Installing New AX86u Pro - few basic questions please

[Rizwan]

Hi All
Sort of a checking my checklist and trying to make sure I get things right

I've had an AC86u for ages and actually bought the AX86uPro a long while ago but just never found time to make the switch/upgrade and the longer I left it the more daunting it seemed as more and more devices (heating, AC etc etc) all connect to the WiFi setup

So:
1. Get latest stable AX86uPro firmware
2. Swap out routers and immediately flash to the d/l 3.0.0.6 firmware for the new router and do a factory reset then start setting it up
2a. Do QIS and add in the settings for the static IP I have for this router from my ISP

3. My current set-up has separate SSIDs for 2.4 & 5Ghz but now I should just use 1 SSID and use smart connect is that correct? Searching the forum I seem to find conflicting advice on this? I'm nervous because some of my devices (heating control and aircon wifi) connect only to 2.4Ghz
I figure in principle when using new tech with a new network better to try the modern way of doing things rather than legacy approach but advice welcomed

4. Do I really need to manually set the channels for 2.4/5Ghz ? Happy to play around if problematic but if I'm giving myself time to srt it up "properly" from the off just useful to know what can predominantly be left to default and which you need to tweak for optimL performance (improving wifi range definitely a desire)

5. Then add in MAC for the various devices so they maintain the fixed IPs i set them up with and away we go

6. I'll probably see how I go with this wifi performance but probably next step will be connect the AC86u upstairs via a network switch in spare room to establish a MESH network

Any obvious silly things I've overlooked please? It's been a LONG while since I've messaged around with any of this

 

[Tech9]

It's your router and your decision how you want it set up. Connect it to your ISP, update the firmware on it, reset if after if you like, set it manually the way you like. Don't add your old router as node if single router coverage is good enough.

 

[bbunge]

3. Sure, use a single SSID and Dual Band SmartConnect. As for the clients you mentioned, set up an IoT Guest WIFI on just the 2.4 GHz band with WPA2-Personal. Most of those devices are connected to a remote server that the phone app connects to so you really do not need them on your main LAN. My thermostat, garage door opener and etc connect this way.

4. No, you do not need to manually set the channels in most cases. In my case I set both bands to Auto Channel but set the 2.4 GHz to 20 MHz and the 5 GHz to 80 MHz with DFS disabled. This works well for me as the router seems to be smart enough to select the beat channels even with close neighbors.

5. Using the Manual Assignment of IP addresses can get to be a pain. I start the DHCP assignment of addresses (IP Pool Starting Address) at 192.168.50.30. This gives me plenty of addresses between 192.168.50.2 and 192.168.50.29 to assign as static addresses at the client (cams, managed switch, NVR, NAS, printers and etc.). This is a one time effort and when I have to factory reset the router I need to only change the IP Pool Starting address. Save yourself some work!

6. The AC86U will work as an AiMesh node but will restrict the bandwidth you can use on the AX86U Pro. Try it to see if you really need it. Above I recommended using 80 MHz on the 5 GHz band as this will slightly increase the WIFI range and may work better for you. Pushing 160 MHz can be done but you will likely have some connection issues/ WIFI dropouts.

You may want to keep an eye on the progress of the new Merlin firmware for this router. It is in beta now but is working well for me!

 

[Tech9]

The AC86U will work as an AiMesh node but will restrict the bandwidth you can use on the AX86U Pro

This statement is incorrect, @bbunge. I can demonstrate RT-AX86U with 5GHz radio set at 160MHz with wireless RT-AC68U node (even older model) using the same radio as shared backhaul plus client connected to RT-AX86U at 160MHz with 2400Mbps link speed and actually saturating Gigabit LAN port with file transfer. The node is just a repeater or access point and doesn't restrict main router's own capabilities. It can affect the total network performance needing more airtime when connected clients to it are actively using it, but this is valid for any other slower AP using the same channels including on neighboring networks.

 

[Rizwan]

3. Sure, use a single SSID and Dual Band SmartConnect. As for the clients you mentioned, set up an IoT Guest WIFI on just the 2.4 GHz band with WPA2-Personal. Most of those devices are connected to a remote server that the phone app connects to so you really do not need them on your main LAN. My thermostat, garage door opener and etc connect this way.

##Brilliant thank you. I could potentially even keep the same (current) SSID/password for the IoT Guest Wifi to save me having to add each one of those again?
Ill read up how to set up IoT guest

4. No, you do not need to manually set the channels in most cases. In my case I set both bands to Auto Channel but set the 2.4 GHz to 20 MHz and the 5 GHz to 80 MHz with DFS disabled. This works well for me as the router seems to be smart enough to select the beat channels even with close neighbors.

##Excellent. Will do

5. Using the Manual Assignment of IP addresses can get to be a pain. I start the DHCP assignment of addresses (IP Pool Starting Address) at 192.168.50.30. This gives me plenty of addresses between 192.168.50.2 and 192.168.50.29 to assign as static addresses at the client (cams, managed switch, NVR, NAS, printers and etc.). This is a one time effort and when I have to factory reset the router I need to only change the IP Pool Starting address. Save yourself some work!

##Please could I trouble you to explain this a little more. If I'm still going to manually assign static IPs to those devices where is the work saving? I've clearly not understood something here

6. The AC86U will work as an AiMesh node but will restrict the bandwidth you can use on the AX86U Pro. Try it to see if you really need it. Above I recommended using 80 MHz on the 5 GHz band as this will slightly increase the WIFI range and may work better for you. Pushing 160 MHz can be done but you will likely have some connection issues/ WIFI dropouts.

##Yes I recall reading something about this in the past so will try. Kids bedrooms are pretty much opposite side of the house through lots of brick so currently it's limited but if I can without great. Otherwise setting up the AIMesh will really extend range for the other side if needed.

You may want to keep an eye on the progress of the new Merlin firmware for this router. It is in beta now but is working well for me!

##will do. I've always used Merlin on the AC86 so this will be 1st time on stock

Thank you again for the really helpful comprehensive replies to help me understand better

 

[bbunge]

#5 - Static IP addresses. Lets clear up some terminology. Static addresses are assigned within the clients configuration or setup and never change unless you change it. Manually reserved addresses are assigned by DHCP (usually the router) and if different from the DHCP/MAC address algorithm assigns the address can change.
I mentioned that I set the DHCP starting address at 192.168.50.30 which gives me a range of IP addresses that the DHCP will not assign. My IP cams and other clients are assigned a static address within this range. These addresses never change and when I reset the router I do not have to worry about going through the manual drill of adding their MAC addresses to a list of manually assigned or reserved addresses.
Some IoT clients can not be set up with static addresses. You can let them get an addresses from DHCP and not worry about them as the DHCP assigned address will seldom change.
Whatever way you go is OK. I feel that using static IP addresses is work saving for me as I have been known to switch firmware frequently just to try things....

 

[Rizwan]

#5 - Static IP addresses. Lets clear up some terminology. Static addresses are assigned within the clients configuration or setup and never change unless you change it. Manually reserved addresses are assigned by DHCP (usually the router) and if different from the DHCP/MAC address algorithm assigns the address can change.
I mentioned that I set the DHCP starting address at 192.168.50.30 which gives me a range of IP addresses that the DHCP will not assign. My IP cams and other clients are assigned a static address within this range. These addresses never change and when I reset the router I do not have to worry about going through the manual drill of adding their MAC addresses to a list of manually assigned or reserved addresses.
Some IoT clients can not be set up with static addresses. You can let them get an addresses from DHCP and not worry about them as the DHCP assigned address will seldom change.
Whatever way you go is OK. I feel that using static IP addresses is work saving for me as I have been known to switch firmware frequently just to try things....

AHA! Thanks for clarifying that terminology. Makes sense now as what I was referring to as "Static IPs" I actually meant 'Manually Assigned IP around the DHCP list'
Saying that I can't see in the router where I would assign static IPs in the way you describe?

Just on the point of the DHCP addresses - do I have to leave the LAN-IP as 192.168.50.1 or can I change it to 192.168.0.1 and are there any ramifications to doing this? I figured if I keep the same LAN IP as current and assign the Guest IoT Wifi the same SSID/password I currently use it should allow most of the heating etc tech to stay connected?

 

[Rizwan]

#5 - Static IP addresses. Lets clear up some terminology. Static addresses are assigned within the clients configuration or setup and never change unless you change it. Manually reserved addresses are assigned by DHCP (usually the router) and if different from the DHCP/MAC address algorithm assigns the address can change.
I mentioned that I set the DHCP starting address at 192.168.50.30 which gives me a range of IP addresses that the DHCP will not assign. My IP cams and other clients are assigned a static address within this range. These addresses never change and when I reset the router I do not have to worry about going through the manual drill of adding their MAC addresses to a list of manually assigned or reserved addresses.
Some IoT clients can not be set up with static addresses. You can let them get an addresses from DHCP and not worry about them as the DHCP assigned address will seldom change.
Whatever way you go is OK. I feel that using static IP addresses is work saving for me as I have been known to switch firmware frequently just to try things....

Thank you very much also for being patient with me and helping with replies - its been so long since I played with stuff I forgot many of these things and simple things suddenly seemed more daunting than they should hence I put it off for so long!
Really appreciate it

 

[Rizwan]

@bbunge having done some more reading as I understand it you've assigned the static IPs on the devices themselves NOT on the router (which is why I can't see that option )
That's correct right?