In New England we are looking to grow our mesh networks and connect them over time. With that in mind and experimenting linking Mesh networks together by using tunneling i see a strong need for a standard naming convention and thought I would ask if someone has one? Seems like this should be part of the documentation at ARDEN. Changing the name of a node after the fact is painful so it would be good to get it right the first time.
Ideas:
callsign-type-location#-state (type: H=home, P=portable, BB=backbone and the list could go on...)
example: NG1P-BB-Topsham1-ME (this would be a backbone node and the first node at this location)
Another idea for a standard:
state-location-type-callsign#
example: ME-Topsham-BB-NG1P1 (same as above juts in a different order. (This one might be better if you looking at the mesh status view to see State location first perhaps?)
What are others doing? I guess we may want to include country also? Lets make a standard and document it. I think a standard is key when you grow into other mesh networks. If your stand alone do what works for you.
Thank you Bill NG1P
You are here
Naming Standard?
Fri, 04/29/2022 - 09:29
#1
ng1p
Naming Standard?
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
RTFM:
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/basic_setup.html
...
Node Name
Begin the node name with your callsign, followed by unique identifying information of your choice.
Node names may contain up to 63 letters, numbers, and dashes, but cannot begin or end with a dash.
Underscores, spaces, or any other characters are not allowed.
Node names are not case sensitive, but the case will be preserved on the node status display.
Amateur radio operators are required to identify all transmitting stations.
The AREDN® node name is beaconed automatically by the node every five minutes, so the node name must contain your callsign.
Recommended names follow the (callsign)-(label) format, such as AD5BC-MOBILE or AD5BC-120SE.
As a general rule node names should be kept as short as possible, while clearly and uniquely identifying the node.
(Bold is mine. Chuck)
-----
Location can be placed into latitude/longitude fields and description can be put into 'Node Description' field.
-----
"Changing the name of a node after the fact is painful so it would be good to get it right the first time."
Excuse moi. Change node name, save settings, reboot. Voila!
OK, maybe after a name change, remove node from the local network for 7 minutes.
( I think there is a fix for this coming soon in a nightly build. )
-----
"What are others doing?"
Browse the maps. Hover over node icons.
https://www.arednmesh.org/content/list-aredn-network-maps
-----
I hope this helps,
Chuck
73 Bill NG1P
There's not too much of a naming standard in Southern California. Out here in Ventura County we mostly use "callsign-VC-location-5G". Any other descriptive info can go into the Description field (e.g. "90 degree sector and Rocket M5 servicing east Simi Valley. Antenna bearing approximately 300 degrees"
BTW, you CAN remotely reset the advertised services after a nodename change.
To do so, ssh into the node ("ssh -p 2222 root@<nodename>)
and issue the command
/etc/init.d/olsrd stop;sleep 7m;reboot
Hit enter to execute the command then exit out of the node with the exit command.
This has the effect of shutting off OLSR broadcasts for 7 minutes, then rebooting
NOTE: If you're using Windows 10 but it doesn't know about 'ssh', install the OpenSSH option. Information on it here.
73
Orv W6BI