@rain Please confirm that in local mesh network in home we can use ethernet to establish the link between main router and node, I guess that if ethernet connection is present that would automatically be the priority connection. Donāt know if there is a visual clue for that in the configuration page.
Andā¦ if so, and in local mesh only, what are the main differences between having the node in mesh mode or AP mode like I have right now? I guess the mesh mode will inherit all network configuration from the main router, including all wifi vlans like main and IoT, that in the AP mode does not happen. Correct me if Iām wrong.
We actually have no intention of collecting user data. That said, some of our cloud featuresālike device management and remote networkingāneed to tag and differentiate devices just to make sure everything functions properly.
Anyway we always do our best to keep data collection to an absolute minimum, using it solely to keep features running. We highly appreciate your oversight and welcome everyone to keep reviewing and monitoring our practices.
Exactly.
Ethernet networking is fully supported and will be prioritized when establishing the connection.
In Mesh mode, the entire network operates as a unified setup; all Wi-Fi and network configurations are synced from the main router, and fast roaming is supported.
1 Like
Thanks for the info, I will check tomorrow.
- Re LUCI on the node, I would like to change the name of the node / router. Before ASTROMESH I went in to LUCI to change it. Can I still change the name of the router?
- Edit I found where to change the name of the node....
BUT it does not change the name of the node on the node Admin / login page.... It is only changes on the Node Info page on the master......
The other use for LUCI was in ACCES POINT I offloaded the SearXNG / docker onto that router to relieve the workload on the main /master router. I do not know if that was or was not a good idea but it was possible.
Thanks. 
does this also include additional networks like guest and IoT?
That makes sense, and thanks so much for the feedback! We will bring LuCI back in a future release.
Yes, both Guest and IoT networks are included as well.
1 Like
Are you release an extra mesh device like the Fritz Mesh system? Or I can only buy āTravel Routersā for the mesh?
Tank you
Yes, we do have plans to introduce dedicated mesh node devices, which are expected to launch in Q4 of this year.
2 Likes
Really great!
you should already be able to use normal astrowarp clients with the astromesh. You can already do this with other GL routers that support astrowarp but not astromesh. the big kicker is that astrowarp only devices cant use the split tunnel feature of astromesh, if you join a regular astrowarp client to the astromesh its a full tunnel home only currently
once you join the node to astromesh you can edit the name. in the astromesh controller you can click on a node and on the pop out there is a little pencil icon, you can change the node name here.
if you want to change the hostname you can do that via ssh
mesh mode is far superior to AP mode. for one all your SSIDās are synced across all the routers in the mesh topology.
3 Likes
Yes I have done that, but as I said above that does not transfer to the node admin page.
I am sure you can if you have intimate knowledge of the command line commands - it is much easier to use LUCI for people less familiar with the full command line commands.
And with LUCI you have so many other options / System monitoring monitoring / memory usage etc, or is that irrelevant for a (MESH) Node?
On another topic - VLANs / SUBNETs on the node
should I be able to create a VLAN / SUBNET on one of the Flint 3 (or Flint 4 when available) node ports just as I can on the master? Is it a feature that is not possible on a node by design?
I see on the node there is no "network" menu choice and so no VLAN / SUBNET option (I am using a Flint 3 ethernet as the node) and as such you cannot configure a VLAN / SUBNET
I could create a VLAN / SUBNET on the Master ethernet port to which the Flint 3 is connected but that would then make anything that connects to the Flint 3 node on a VLAN / SUBNET not ideal I would imagine?
But it does, I just reset mine and tested it. I have custom hostnames and my node names are different than my hostnames. Setting the node name shows the name in the node admin panel
I donāt think full vlan support has been implemented over the mesh backhaul yet
Any thoughts of allowing end-users to point connected devices to the mesh node of their choice in the future? For example, I always want my stationary smart TV to connect to my Flint 3 main mesh node vs the Slate 7 AP mesh node (if I so desired) - so I could go in and say āSmart TV ALWAYS connect to Flint 3 with Slate 7 as auto-back-upā?
1 Like
When will you guys release the preliminary specs? I tried submitting feedback, but encountered issues. Hopefully, it's not too late to still potentially influence the specs of the upcoming MeshNode.
I'm modernizing my home network at the moment. I already have the Slate 7 and Brume 3. I just sold the Flint 2 because I'm getting ready to get the Flint 4. I have decommissioned the Beryl AX and will want to replace the Slate 7 with the Slate 7 Pro once v4.9 is available! I hope the MeshNode will be tightly integrated with your newer products!
You mean the upcoming MeshNode? What other details can you provide?