Hi,
questions regarding the BABEL settings:
According to the documentation, "Mesh Station" defines a station that can communicate to either type of AP (PtP or PtMP) - and to other "Mesh Stations" too? Does it replace the old "Mesh" mode?
If one radio is set to PtP mode, can/should the second one be in PtP mode, too?
Thanks 73s
Kurt
HB9XCL
questions regarding the BABEL settings:
According to the documentation, "Mesh Station" defines a station that can communicate to either type of AP (PtP or PtMP) - and to other "Mesh Stations" too? Does it replace the old "Mesh" mode?
If one radio is set to PtP mode, can/should the second one be in PtP mode, too?
Thanks 73s
Kurt
HB9XCL
"and to other "Mesh Stations" too?"
No.
The documentation does not state nor imply that.
-----
https://docs.arednmesh.org/en/latest/arednGettingStarted/node_admin.html...
About halfway down the page...
https://docs.arednmesh.org/en/latest/arednGettingStarted/node_admin.html...
"
Mesh:
Normal AREDN® mesh mode which uses ad hoc peer-to-peer networking to create a mesh.
PtP/PtMP:
Uses infrastructure mode (point-to-point or point-to-multipoint) to limit communication between a single access point (AP) and one or more specified stations.
Mesh PtP defines an AP that communicates with a single station.
Mesh PtMP defines an AP that can communicate with multiple stations.
Mesh Station defines a station that can communicate to either type of AP defined above."
I think a 'mesh station' cannot communicate with a 'mesh' station as that station is in 'ad hoc' mode
nor another 'mesh station'...only a PtP or PtMP node.
IOW...only exactly one other specific SSID (PtP/PtMP) node.
-----
I cringe each time I see the word 'mesh' used.
I would like to see 'Wi-Fi ad hoc protocol' or 'Wi-Fi infrastructure protocol' used instead.
IMHO, 'mesh' is a topology, not a protocol.
:-|
73, Chuck
Indeed, to have a "mesh" station and a "mesh station" is confusing. Last one should be renamed, as you said.
At our club meeting yesterday evening, we decided to avoid the new modes for the time being, and to also recommend that to our users (which are mainly non-IT people). To have limited connections does not reflect our understanding of an emergency mesh network in general. Additionally the new modes are still far too poorly documented (for example, can a PtMP also communicate with another PtMP? If so, under what topological conditions would this constellation make sense? and so on...).
73s
Kurt HB9XCL
"can a PtMP also communicate with another PtMP? If so, under what topological conditions would this constellation make sense? and so on...)."
"can a PtMP also communicate with another PtMP?"
Not via RF. Although since 'PtMP' indicates RF, then no.
"under what topological conditions would this constellation make sense? "
Logical sense, 'Mesh' topology.
Practical sense, up to 3 stations and all 3 can hear the other 2.
73, Chuck
I also would assume that PtP means both stations would need to enter the other station into their list. I just haven't tried this yet as I don't want to goof up links remotely managed. Can a PtMP station have multiple Mesh Stations ... or multiple PtP stations in it's approved list?
Ed
PtP/PtMP:
Uses infrastructure mode (point-to-point or point-to-multipoint) to limit communication between a single access point (AP) and one or more specified stations. Mesh PtP defines an AP that communicates with a single station. Mesh PtMP defines an AP that can communicate with multiple stations. Mesh Station defines a station that can communicate to either type of AP defined above.
Orv W6BI
"Can a PtMP station have multiple Mesh Stations"?
Hi, Ed:
Following the documentation...when you say 'Mesh Stations' do you mean
'mesh' station or 'mesh station'?
"multiple PtP stations in it's approved list?"
Following Access Point (and AREDN PtMP) infrastructure mode...
a 'mesh station' is a client to a 'PtMP' (access point), so no,
a client cannot have multiple 'access points'.
73, Chuck
What is a specified station and how exactly does a operator enter this into the node info? I don't want to do this on an actual node unless I understand how it's done, by Node Name, by MAC address ... how?
I assume PtP and PtMP does not affect existing dtd connections?
PtP & PtMP have no relationship to DtD.
If node A is set PtMP and node B is set Mesh ... and I want to add B to A's whitelist ... will I be able to see the MAC address of node B even though I'm not taking any traffic from it? Or do I have to put node A into Mesh node long enough to see and link with B, then put A back to PtMP and add B's MAC address?
Ed
Orv
Does your 'PtMP server' act identical to a Wi-Fi 'Access Point'?
Linking is done by SSID.
73, Chuck
"If node A is set PtMP and node B is set Mesh"
Node B must be 'mesh station' not 'mesh'.
73, Chuck
PtMP and PtP use the unique SSID of each node (I assume that is the node name?) rather than MAC address.
Your post refers to PtMP server. I guess that is how one PtMP node controls which Mesh nodes can connect. If using PtP do both nodes need to be setup as PtP for it to work? I would assume the node that is PtP would be restricted access but a Mesh node not restricted.
Ed
The PTmp server has a unique SSID that the mesh stations need to be configured with. The mesh stations need to be configured as Mesh Stations.
Hope that's clear.
Orv
the query was about link class(infrastructure) and not about link routing(BABEL).
Most of this discussion is about the new station classes available in the new AREDN firmware releases
which now have the BABEL routing protocol.
Wi-Fi has two(?) classes; 'ad hoc' and 'infrastructure'.
The default home Wi-Fi router operates in 'infrastructure' class and in 'Access Point' mode.
The default home device (workstation, thermostat, doorbell, mobile phone, smart TV,...) operates in
Wi-Fi infrastructure class and 'client' mode.
Previously (<2025-12-01?) the only routing protocol was OLSR and the only Wi-Fi class was 'ad hoc'.
Recently Wi-Fi infrastucture classes added were PtP(?), PtMP (think Access Point), and 'mesh station' (think client).
73, Chuck