What's new

Migrate from AX68U (3004.388) to BE86U (3006.102)

FoxyBadger

New Around Here
Good evening everyone.
Long time lurker, first post. Apologies in advance if this question has been asked before, I have had a search, couldn't find what I was after.

I have FTTH (950 Mbps up/down) and for the past couple of years I have been utilising an RT-AX68U router with Merlin firmware installed. As the product is EOL, I purchased a BE86U over the December sales as a replacement.
This is still boxed and needs to be set up and configured.

The majority of my home network is wired, and I will later upgrade the network switch to fully utilise speeds faster than 1Gbps.

Things about my existing network that I must retain (ideally without manually reconfiguring it all again):

- I have two different Guest Networks on WiFi (one 2.4Ghz and one 5Ghz) that are used only for work devices.
- There are a number of work devices (on Guest WiFi) that run on a time schedule (so they do not have network connectivity outside of working hours - this helps me remain disciplined as I WFH not to work too late)
- There are a couple of wired clients (both Now TV/Roku boxes) that have an IP address and DNS server manually assigned (the Now TV box itself doesn't allow you to do this). This allows them to use my Pi-Hole (virtual, hosted on NAS), for DNS - so all adverts on ITV/Channel 4 catch up apps are blocked.
- I run one OpenVPN server for a handful of trusted clients to log onto (each with separate username/password) when we're out and about
- There are a number of wireless clients (mobile phones, tablets) that have static IP addresses assigned on the LAN (I manage a spreadsheet, lol) - so they too can use the Pi-Hole for DNS.
- There are a number of wired clients on the LAN - 2 x NAS, printer, TV, pi-hole, etc... that have static IP addresses assigned on the LAN.

Things I'm not running today (and/or do not care for right now):

- Anything from the AiMesh section
- Anything from the AiProtection section
- Anything from the Parental Controls section (apart from the time schedules for work devices)
- Anything from the Adaptive QoS section
- Anything from the AiCloud section

Things that I may be interested in the future (but not currently doing):
- Keeping both devices and starting a mesh network
- Creating one or more dedicated network segments (e.g. one for IoT devices only, one for work devices only, etc...)

My network will probably have about 20 devices simultaneously connected at any one time, with around 40-50 different clients in total. (Most of them remain switched off unless they're in use).

My questions:

1) What is the easiest way for me to open the new BE86U and retain/transfer the settings/config over from the AX68U to the new device? [Is it even possible?]
2) What are the main pitfalls/things to consider with any other methods (the "less easy" methods).

If you need any more info please let me know!
Thanks in advance.
 
You need to setup your new router manually from scratch. Make screenshots of your settings if you like. Don't re-use the old router as AiMesh node if this node is not needed. It won't make your Wi-Fi better and your old router doesn't support new VLAN related AiMesh features like Guest Network Pro. Not sure why Search didn't work for you. We have perhaps >100 threads with similar questions here on SNB Forums.
 
Apologies in advance if this question has been asked before, I have had a search, couldn't find what I was after.

My questions:

1) What is the easiest way for me to open the new BE86U and retain/transfer the settings/config over from the AX68U to the new device? [Is it even possible?]
2) What are the main pitfalls/things to consider with any other methods (the "less easy" methods).
There have been quite a few past discussions on exporting a router.cfg file from one router model and importing it into another different router model. Here are a few of them...

Bottom line. Pretty much everyone is going to suggest you manually configure the new BE series router and DO NOT import the router.cfg file from the old AX series router. There are various ways to copy the information from the old router; screen grabs, print to PDF, copy/paste, split screen, write down the changes, etc. There are various ways to transfer over information like manual DHCP reservations between routers including possibly using Asus-Merlin Addon Scripts like YazDHCP and for other settings BACKUPMON.

Could you import a different model router's.cfg file? Yes, but because of different hardware, firmware and settings you could end up spending ages trying to run down weird router behavior or the router simply crashing. Almost always its faster to just manually copy your changes from the old router and manually put them into the new router than spend the time trying to track down weird router issues from failed router.cfg import. Unless one has a very complex configuration with lots of addon scripts a manual configuration shouldn't take more than 15 to 30 minutes for most people.
 
Your best choice is to keep your AX router. Wait for WIFI 7 to mature a bit unless you really can use the features that WIFI 7 presents. But, be prepared for disappointments.
 
Pretty much everyone is going to suggest you manually configure the new BE series router and DO NOT import the router.cfg file from the old AX series router.
Just echoing what @bennor said 100%.

Take the opportunity to make a clean start, otherwise you'll be back here asking this and that (which is fine) but the first question (and recommendation) to those questions will invariably be, after you get your new Router and upload the latest FW, "did you do a factory (hard) reset, did you input the settings manually from saved schreeshots, not a cross Router cfg?".
 
You need to setup your new router manually from scratch. Make screenshots of your settings if you like. Don't re-use the old router as AiMesh node if this node is not needed. It won't make your Wi-Fi better and your old router doesn't support new VLAN related AiMesh features like Guest Network Pro. Not sure why Search didn't work for you. We have perhaps >100 threads with similar questions here on SNB Forums.
Thank you for your response. I think I was using search terms that were too specific/restrictive to my exact models.
 
There have been quite a few past discussions on exporting a router.cfg file from one router model and importing it into another different router model. Here are a few of them...

Bottom line. Pretty much everyone is going to suggest you manually configure the new BE series router and DO NOT import the router.cfg file from the old AX series router. There are various ways to copy the information from the old router; screen grabs, print to PDF, copy/paste, split screen, write down the changes, etc. There are various ways to transfer over information like manual DHCP reservations between routers including possibly using Asus-Merlin Addon Scripts like YazDHCP and for other settings BACKUPMON.

Could you import a different model router's.cfg file? Yes, but because of different hardware, firmware and settings you could end up spending ages trying to run down weird router behavior or the router simply crashing. Almost always its faster to just manually copy your changes from the old router and manually put them into the new router than spend the time trying to track down weird router issues from failed router.cfg import. Unless one has a very complex configuration with lots of addon scripts a manual configuration shouldn't take more than 15 to 30 minutes for most people.
Many thanks for the information provided. I'll definitely check out the Addon Scripts mentioned. 👍
 
Just echoing what @bennor said 100%.

Take the opportunity to make a clean start, otherwise you'll be back here asking this and that (which is fine) but the first question (and recommendation) to those questions will invariably be, after you get your new Router and upload the latest FW, "did you do a factory (hard) reset, did you input the settings manually from saved schreeshots, not a cross Router cfg?".
Thanks for taking the time to respond. I'll definitely be starting from scratch! Hopefully I'll get a chance to give it a go this coming weekend.
 

Latest 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!
Back
Top