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!
Any word on when this will be in public beta? I have both supported devices and Iâm excited to test this out.
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.
Hello,
i have set up the mesh with 3 Flint3
and 1 Slate7 how can I change the host name of the Nodes not only the Node name ?
also no of my WLAN Dives use the slate 7 still they near by them then by the Flint 3 devices.
I use MLO any idea ?
thanks
I have set this up using 2 x Flint 3s and it seems to be running ok since initial 4.10 rollout.
My config is astromesh local as both routers are in one location at home
logread.tar (552.5 KB)
Have been seeing this error in the logs
(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=beerocks_contro,pid=27381,uid=0
[793821.379611] Out of memory: Killed process 27381 (beerocks_contro) total-vm:235108kB, anon-rss:210256kB, file-rss:2424kB, shmem-rss:0kB, UID:0 pgtables:488kB oom_score_adj:0
When this happens the node disconnects from using the lan connection and to goes to wifi.
Only way to fix is reboot the node.
Seems to happen at least once in a 24hr period
For context
The functionality still seems to work and does not appear to affect performance
Adguard Home is running with just one filter
HaGeZi Multi PRO++ mini
I have attached logs
As the quote below this works for me SSH into the node :-
This works for me:
uci set system.@system[0].hostname='insert-hostname'
uci commit system
/etc/init.d/system reload
Or go to and click on the node :-1
Click the Edit button:-
and edit the name:-
Is that what you are looking for?
Sorry about currently MLO doesn't support fast roaming just yetâonly the main network has it supported for now. MLO fast roaming is on our roadmap for future updates.
Based on the logs you shared, it seems that the device ran out of memory, which triggered the OOM (Out of Memory) killer. It ended up killing beerocks_controllerâa core component of the Mesh moduleâsince it was hogging the most RAM at the time. That's what caused the crash, and a reboot fix it.
To help us dig deeper and try to reproduce this in our lab, could you share the following details?
Thanks a ton for your help!
Okay, Iâve been running AstroMesh for about 5 days now and Iâve ran into a couple of issues:
I have a theory. This device was close to the mesh node when I was setting this up and I believe it was stuck on the secondary device.
The client tab shows no clients. It did this when I first set it up and I rebooted it. The client tab worked for a while but then the tab is clear again. See the screenshot.
Is there a list of known bugs and features that shouldnât be working while in mesh mode? Also, is there any estimate on when the next beta version will be released?
I also got a 3-Flint3-nodes mesh, keeping it local for now.
Every time I change the name of one of the SSIDs, the mesh drops the 2 nodes - they show offline. If I manually reboot one of the nodes, it comes up with the blue light blinking slowly.
Isnât chaning an SSID âthe most basic taskâ I should expect from a mesh to see that it propagates fine across all mesh nodes and the new devices steer to the best node? Anything Iâm doing wrong?
Also, as someone already reported, I moved my WiFi7 devices to a 5G/6G -MLO SSID and they seem to get stuck on the main node and drop when I move up the floors in the house. Whatâs the right way to roam on MLO in beta1?
Not supported right now according to this reply:
Beta 4.10.0 beta 1 firmware.
I lack understanding why when the FLINT 3 node shows as being off-line, I can still access the devices that are ethernet connected to the ethernet connected node?
Update
I was also unable to log into the Node GUI.
Not unexpectedly, a power off/on reboot restored full functionality. Maybe I should schedule a reboot - I do that on the master to help prevent the OOM with ADGH.
So the iPhone 15 Pro still isnât roaming correctly, it stays connected to the mesh node even when mostly out of range.
Your AdGuard Home filter setup/rules.
Number of clients
I am having the same issue
