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!

XT12, XT9, EBM68

Phillips39

Occasional Visitor
Hey,

My current set up is 2x XT12 and 2x XT9 running in AiMesh. Main router is XT12. XT12's run latest @RMerlin firmware, the XT9's on the lates stock firmware as unfortunately no Merlin support. Everything has been rock solid and works well.

My network has been expanding to the point at which I'm now considering running a separate IoT network for my ring devices, locks, Hue bulbs and the like. I'm aware this cannot be done via the current Merlin build as it is on 3004, so am looking at the possibility of flashing the XT12's to the latest stock 3006 firmware.

Off the back of that I realise that I may get compatibility issues with the Mesh with the XT12s being on 3006 and the XT9s being on 3004. As such, I am looking into replacing the XT9s with either their business counter part the EBM68 (as these run 3006) or 2 more XT12s. Even though the EBM68s would be more aesthetically pleasing replacing the currently wall mounted XT9s, I'm leaning towards the XT12. Rationale being that the XT12s are more powerful (and my current 2 I have been really pleased with), and also because if I find it all goes south on 3006, I can flash them all back to Merlin. Plus, hopefully, Merlin may release a version of 3006 before long which I could then apply to all 4 XT12.

I have also considered upgrading to Wi-Fi 7 as main router and putting the XT12s into secondary nodes. However, from researching, Wi-Fi 7 routers still seem to be problematic. Plus only a handful have Merlin support of which the majority are the ROG style which won't go down well at home!

Would appreciate any input and advice here. TIA.
 
Hey,

My current set up is 2x XT12 and 2x XT9 running in AiMesh. Main router is XT12. XT12's run latest @RMerlin firmware, the XT9's on the lates stock firmware as unfortunately no Merlin support. Everything has been rock solid and works well.

Given the 3.0.0.6.vlan ASUSWRT is being re-engineered and is overdue for hardware already sold... you might want to wait and see what firmware/models unfold over the coming months/year (an AiMesh upgrade with multiple models and uncertain ASUSWRT is always an experiment whether you want it or not).

OE
 
Given the 3.0.0.6.vlan ASUSWRT is being re-engineered and is overdue for hardware already sold... you might want to wait and see what firmware/models unfold over the coming months/year.

OE
Thanks for the reply. How stable is the 3006 version currently? I notice from your signature, you use it? I doubt there would be support for the EBM68s from Merlin if the XT8s or XT9s have never been supported?

I've also noticed that the XT12's are now out of stock via Asus directly. Are they likely to be discontinued before long would you know?
 
Thanks for the reply. How stable is the 3006 version currently? I notice from your signature, you use it? I doubt there would be support for the EBM68s from Merlin if the XT8s or XT9s have never been supported?

I've also noticed that the XT12's are now out of stock via Asus directly. Are they likely to be discontinued before long would you know?

3006 is stable here as long as you don't twiddle it much... the vlan bit is betaware, imo, for Pro models only, and does not feel very solid... presumably why they are reworking it.

Sorry, I don't have answers to your specific questions.

The key point in this discussion is "Everything has been rock solid and works well." So I can only suggest that making a change now may be premature... I would be patient and continue planning while the current state of affairs will likely change. I'm hoping to see the next/second draft of ASUSWRT's vlan support before June(?).

OE
 
Understood. Thanks. Is it worth swapping out the XT9s for EBM68s in that case to give me an option - or will the mix of 3004 and 3006 firmwares likely cause more issues than its worth?

Is there any way I can separate out my IoT devices now, whilst still allowing their dedicated apps to control them? I'm fairly savvy but not hugely experienced in vlans, hence why the guest network pro feature was intriguing. Happy to play with it as long as I don't end up screwing everything up because it isn't a fully baked implementation.

Also, further down the road, if I were to 'upgrade' to BQ16's (non pro in the UK), would 2 of these work well with the 2 XT12s as nodes? I'm reading on some sites this mix of hardware can be problematic, but then others say it is fine. Assuming all were on same firmware architecture.

I should add here that all nodes are wired and on ethernet backhaul.
 
Understood. Thanks. Is it worth swapping out the XT9s for EBM68s in that case to give me an option - or will the mix of 3004 and 3006 firmwares likely cause more issues than its worth?

I chose to make the jump to all Pro models to at least avoid the obvious incompatibily between vlan support vs no vlan support. Now I'm holding with vlan betaware.

Is there any way I can separate out my IoT devices now, whilst still allowing their dedicated apps to control them? I'm fairly savvy but not hugely experienced in vlans, hence why the guest network pro feature was intriguing. Happy to play with it as long as I don't end up screwing everything up because it isn't a fully baked implementation.

Just the usual unless you are more clever than me... put those clients on a guest WLAN or a dedicated 2nd network(?)

Also, further down the road, if I were to 'upgrade' to BQ16's (non pro in the UK), would 2 of these work well with the 2 XT12s as nodes? I'm reading on some sites this mix of hardware can be problematic, but then others say it is fine. Assuming all were on same firmware architecture.

Someone here familiar with those models will have to comment.

OE
 
Thanks again.

So if I understand you correctly, having XT12 Pro's may well be a better longer term investment than the EBM68s, as they're likely to be involved in developments longer due to their 'pro' denomination?

OK, that's what I thought about the current guest network options in 3004. The thing that's always confused me though is if say my ring doorbell is on the guest network, my phone is on the main network, can the ring app on my phone still communicate with the doorbell?

Thanks for your help here, much appreciated!
 
So if I understand you correctly, having XT12 Pro's may well be a better longer term investment than the EBM68s, as they're likely to be involved in developments longer due to their 'pro' denomination?

I try not to make purchase recommendations, especially with ASUS marketing... when I do, it is for an obvious choice that I have some experience with. As for ASUS' so-called Expertware, there has to be better business class vendors/solutions to consider. For consumer equipment, I try to separate a main stream segment from ASUS's marketing and stick with those... N66U (the hook), AC68U (the winner), AC86U (the lemon), AX86U/Pro, AX88U Pro, all dual band.

For specific models, find recent discussion here by owners to see how it's going for them. You can also look at a model's firmware history on its Support page to judge how much love they get from ASUS. The level of love is down lately while ASUS beavers away on vlan draft2 code.... recent firmware releases have mostly been minor updates and to patch significant issues.

OK, that's what I thought about the current guest network options in 3004. The thing that's always confused me though is if say my ring doorbell is on the guest network, my phone is on the main network, can the ring app on my phone still communicate with the doorbell?

The two default possibilities are i) all clients are on the same network so that they can intra-communicate, or ii) the admin tool on one network is able to communicate with the IoT device isolated on another network by going out and back through the vendor's Internet cloud service, or similar for remote access without having to setup remote access to your network yourself.

Anything more clever locally is beyond my experience and would likely require more network admin overhead than I care to adopt.... keep it simple, it will all get complicated enough on its own. Others here may offer some tricks.

OE
 

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