But I don’t think I can run AstroMesh on Brume3 yet, correct?
What I have today is the ISP’s modem, then the Brume3, an unmanaged switch connecting 3*Flint3 (I used to have Flint3 as the entry point, instead of the Brume3, and the other 2**Flint3 were APs).
If I can’t install AstroMesh on the Brume3 today (running 4.9.0 Beta and not 4.10 is published), so how do I make best use of it (don’t want the Flint3 to do a double NAT)?
That's not supported just yet, but it's definitely on our roadmap for a future update.
I think you can set up one Flint 3 as your AstroMesh Main Router, configure the other two as Mesh Nodes, and then run the Brume 3 as a drop-in gateway connected behind the Main Router.
Down the line, once the Brume 3 gets AstroMesh support, you can easily switch things up—make the Brume 3 your Main Router and use all three Flint 3s as Mesh Nodes.
Thanks! That’s what I was thinking but the Brume3 is the entry point of my network to do the DPI, and I wasn’t sure if the traffic can enter a Flint3, get forwarded to the Brume3 as a drop-in, do the DPI, and then go back to the Flint3 and the rest of the AstroMesh.
Sorry for the confusion. I just double-checked with my team: currently, DPI doesn't inspect or track incoming WAN traffic, so it's not working as expected in drop-in mode. We’re already working on a fix for this, and I’ll keep you in the loop!
We're currently in the public beta phase! You can follow the steps outlined in this post to grab the firmware and give it a spin. The stable build is expected to drop in late August.
Great, I thought it was a closed beta. I was able to load the firmware and start testing it. Is there a way to be notified when there are firmware updates for the beta testing?
We’ll keep you posted on beta firmware updates right here in this thread. For stable releases, you’ll get a direct heads-up right inside your admin panel.