What's new
  • 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!

Clean Installation Guide for wannabe techies :)

RebornVampie

Occasional Visitor
There is much (outdated) information and I didnt find a step by step manual so I am trying to create one while fixing the network myself. I am trying to summarize it one topic. I have used OTHER peoples information. I am an ICU nurse with an interest in technology and usually am able to fix things with comprehensive reading. I appreciate feedback and recommendations.

Situation:
- Current setup: ONT -> ISP router - AC68U (merlin, wired) as acces point, AX58U (merlin, wired) as second access point.
- New setup: ONT -> AX88U pro (merlin) as main router - AX88u (asus, wired) as node - AX58u (asus, wired) as node.
House is three stories, classical European stone house from 1980s. We laid preproduced high quality CAT6A cables to every floor.

Reason:
My girlfriend and me are moving in together and this is a good moment to have a system overhaul.

Goals:
get an easily managable network running maximum capacity both on WiFi and LAN by using AiMesh. Have a safe protected WiFi.
Devices: 2 synology (DS218+ (externally accessable (VPN, Plex etc)), DS416), Hue lights, google audio x4, google home speaker x2, Somfy Connexoon (Sunshade + Shutters), Honeywell Round WiFi, Toshiba AC, Imou camera's x5, solar panels. Phones, laptops, computers. (Getting them managed in homekit as soon as we are living together :). Everything works individually now.)

Basic setup:
1. download and extract current firmware of every router to PC (ozarkedge, jan 6th). Merlin on main and original Asus on nodes. Advantage: easy update, turn auto update OFF
2. wire the PC to router LAN (ozarkedge, jan 6th)
3. browse to the router's default LAN IP address (ozarkedge, jan 6th)
4. perform the quick internet setup routine, skipping WAN (ozarkedge, jan 6th)
5. upload the current firmware (ozarkedge, jan 6th)
6. Hard Reset that firmware to its default settings (ozarkedge, jan 6th) How To: https://www.asus.com/us/support/faq/1039074/
7. perform the quick internet setup routine for real. (ozarkedge, jan 6th)

AiMesh setup (wired backhaul (main LAN to node WAN) is best performance):
8. login to main router
9. press search (1-2 minutes)
10. click add (2-5 minutes).
Do it one by one.

11. settings

Sources: https://www.snbforums.com/threads/asus-rt-axu88-pro-install-and-setup-questions.93475/
 
Last edited:
New setup: ONT -> AX88U pro (merlin) as main router - AX88u (asus, wired) as node - AX58u (asus, wired) as node.

Firmware 3006/3004 mix, not all main router features will be available to the nodes.
 
The new VLAN related features come with 3006 firmware. Your nodes are locked to 3004 firmware. All routers on 3006 firmware is the only guaranteed compatibility combination. This means something like RT-AX88U Pro main with 2x RT-AX86U Pro nodes… in case you want to invest in AX-class devices and AiMesh. With Ethernet infrastructure available your hardware options extend beyond consumer products.
 
Ah crap, I thought I read well into it. Bought two new routers to be able to have AIMesh with ax6000 😅. Ill try if vlan will work by directly connecting the tv to the ax88u pro. Thank you.
 

Not your fault. Asus marketing is all about AiMesh Compatible without explaining what exactly. What we know is based on user experience and feedback. With 3006 main router and 3004.388 nodes you may have Guest Network propagation to nodes (with some limitations), but not VLAN to node LAN ports. Your main router will have VLAN to LAN port available. Perhaps no big deal for your use case, but disappointing when you start with limitations on a new equipment. For this reason I often suggest identical units on the same firmware (Asus) or lower cost SMB gear (Omada/UniFi) for new installations with Ethernet infrastructure available.
 
Bought two new routers

If the new routers are the above mentioned RT-AX88U and RT-AX58U - they perhaps have 1-2 years before landing on End-of-Life list. Not the best models to purchase in mid 2025. RT-AX86U Pro is the the cheapest option running 3006 firmware and with VLAN support.

Regular forum members @visortgw and @jksmurf have experimented a lot with mixed firmware AiMesh and shared valuable details. You may want to read the previous (quite long) discussions here on SNB Forums for additional information and realistic expectations.
 
Last edited:
Thank you for your input. Ill try and sell the RT-AX88u and buy a GT-AX6000.
Saw one second hand and it also has ax6000 and 3006 firmware.

Ill keep the ax58u for the attic and maybe disconnect it if its a bottleneck.

That would be ok, right?
 
For a new network I would prefer new equipment. Saved money may turn into huge waste of time dealing with hard to diagnose intermittent issues.
 
Hi,
I have a question about VLANs and how to set them up. I really searched in the forum and internet. I need some step-by-step advice.

After configuring everything, I now have a super stable network—thank you! I had to replace some cables, but now the speed is superb.

Sorry for the newbie question, but I have many IoT devices and security cameras (solar panels, Google Chromecast Audio, Somfy shutters, etc.). I’d like to put them on a separate network, segmented from my Synology and other devices, but still be able to access them from the main network.

I noticed the IoT setup in Asus Merlin firmware mentions wired connections, but I can’t choose which devices to assign. I have assigned all devices manual DHCP IP addresses.

I’m using a TP-Link TL-SG108E Light Managed 1Gb switch to add more ports and connect my IoT devices. I also have Asus routers: AX88U Pro, GT-AX6000, and AX58U.

Could you recommend some up-to-date reading material or guides on how to set this up with the latest Merlin 380.06? Most resources I find are outdated or inaccurate—for example, this video (
) doesn’t represent how my router setup looks. I do not have that advanced screen :/.

Thanks in advance for your help!
 

Attachments

  • 2025-07-01 20_27_42-Isolate your smart devices with VLAN and Guest Network Pro (ASUS routers) ...png
    2025-07-01 20_27_42-Isolate your smart devices with VLAN and Guest Network Pro (ASUS routers) ...png
    111 KB · Views: 14
Thank you Tech9. That AX58U is on my attic and doesn't do much. I switch it off when I dont need it.

I am struggling with interVLAN communication. As you've seen its been over a month, I have honestly tried fixing it for a while.
I would like VLAN 1 to be able to communicate with ALL of my network. But VLAN 52 and 53 need to be isolated of the rest. Just so my synology on 192.168.2.10 can read out my solar panels with home assistant AND my Synology Security center can watch the rtsp or even onvif of my imou camera's. I noticed that I communicate over the internet with my IOT devices, not through LAN. When I am on the same VLAN, I can access all streams and devices.

I discovered SSH commands and used chatGPT to help make firewall-start script for firewall rules. I tried masqueredes etc

My network is setup by using Guest Network Pro.
VLAN 1 br0 is my main network where most of my devices are on, my synology's but also because of mDNS apple homepod, google home, hue, ikea dirigera, printer
VLAN 52 br52 is my IoT network which has most IoT devices. My camera's, oven, AC, etc.
VLAN 53 br53 is my guest network, for people who come to visit
VLAN 300 is my ISPs media channel

This is the set of rules I have running at the moment but I cant even ping to my VLAN 52 device from VLAN 1.

Firewall-start
Code:
#!/bin/sh

# NAS can access solar panels
iptables -I FORWARD -i br0 -o br52 -s 192.168.2.10 -d 192.168.52.5 -p tcp --dport 80 -j ACCEPT

# br0 access to br52 and br53
iptables -I FORWARD -i br0 -o br52 -s 192.168.2.0/24 -d 192.168.52.0/24 -j ACCEPT
iptables -I FORWARD -i br0 -o br53 -s 192.168.2.0/24 -d 192.168.53.0/24 -j ACCEPT

# DROP traffic from br52 to br0 and br53
iptables -I FORWARD -i br52 -o br0  -s 192.168.52.0/24 -d 192.168.2.0/24  -j DROP
iptables -I FORWARD -i br52 -o br53 -s 192.168.52.0/24 -d 192.168.53.0/24 -j DROP

# DROP traffic from br53 to br0 and br52
iptables -I FORWARD -i br53 -o br0  -s 192.168.53.0/24 -d 192.168.2.0/24  -j DROP
iptables -I FORWARD -i br53 -o br52 -s 192.168.53.0/24 -d 192.168.52.0/24 -j DROP

What am I doing wrong or missing? I hope I can fix it by making the right firewall-start file.
Alternatively I am thinking to get a wifi dongle to connect to VLAN 52 over wifi, but it beats the purpose of separating everything in the first place.
 
Last edited:
@RebornVampie, if you haven't done so already, see some iptables firewall-start script examples at the following links. ChatGPT sometimes gets things wrong when it comes to scripting.
And this one specifically for communicating between Guest Network Pro profiles (two of them, br52 and br53, in the example script):
Code:
iptables -I FORWARD -i br52 -s 192.168.52.0/24 -d 192.168.53.0/24 -j ACCEPT
iptables -I FORWARD -i br53 -s 192.168.53.0/24 -d 192.168.52.0/24 -j ACCEPT
Edit to add: There are several other iptables scripting in 3006.102.x Asus-Merlin firmware discussions that may be relevant including these:
 
Last edited:
Thank you. I have read the topics. What I did is open all traffic between my synology (192.168.2.10) and br52 (IoT) and br53. To be honest, I wanted my synology not to be visible for guests and my iot but I dont know how to get it working elsewise. My synology has only https and 2fa but still I would have preferred to have it closed off as possible.

steps I did (for future readers). enable SSH in asus GUI (lan only)
open PuTTy -> login
create script file: vi /jffs/scripts/firewall-start
add this in the file (right click):
Code:
#!/bin/sh
iptables -I FORWARD -i br52 -s 192.168.52.0/24 -d 192.168.2.10 -j ACCEPT
iptables -I FORWARD -i br53 -s 192.168.53.0/24 -d 192.168.2.10 -j ACCEPT
iptables -I FORWARD -i br0 -s 192.168.2.10 -d 192.168.52.0/24 -j ACCEPT
iptables -I FORWARD -i br0 -s 192.168.2.10 -d 192.168.53.0/24 -j ACCEPT
save it: escape -> :wq
give rights to access the file: chmod a+rx /jffs/scripts/firewall-start
restart firewall: service restart_firewall
check if the rules are implemented: iptables -L -v -n --line-numbers

Thank you for your help!
 

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!

Staff online

Back
Top