Hi
there is a lot of AREDN equipement in function in Quebec / Canada.
why is most of it not shown on the worldmap?
thanks
there is a lot of AREDN equipement in function in Quebec / Canada.
why is most of it not shown on the worldmap?
thanks
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
See https://docs.arednmesh.org/en/latest/arednNetworkDesign/network_topology... for more info.
Orv W6BI
'Once several local or regional networks have been created, there may be a need for access between these “mesh islands.” '
+1 with Orv w6bi.
As far as I can tell, neither VE2CCK nor Quebec, Canada, has a local nor a regional network.
I recommend that VE2CCK/Quebec 1st build a network, then a 'supernode'
could be considered.
IMHO, a stand-alone 'supernode' will not help grow from a non-existing network into
an existing network.
IMHO, a 'supernode' is not well suited to be the beginning of a local network.
I recommend starting with 'regular' nodes to build a local network.
If any existing AREDN node in Quebec would link with ve2lfo-halow, then
this existing Quebec network would be advertised on the AREDN world map.
I think this advertising may help grow an AREDN network in Quebec.
Hierarchical/Geographical, I would have suggested that you link with
VA2RLM-SuperNode-YND,
but that node does not seem well configured.
Closer, perhaps, but not in Quebec is
which appears to be a well configured AREDN node.
A link with this node would also put your 'network' on the AREDN World Map.
73, Chuck
First, you may be taking a humble approach, but I totally agree with your statements about building the network first with regular nodes (RF/Tunnels) and then considering linking isolated groups of nodes using Supernodes if required.
Second, you mentioned that the va2rlm-supernode-ynd "does not seem to be well configured". Could you elaborate on that?
If I missed something in the setup of the Supernode, I would like to correct it.
I also host a regular tunnel server with many tunnels to others in Québec and Ontario. I recently made changes to my home network, where I needed to temporarily stop the regular tunnel service for a few days. The tunnel service has since been restored.
Of course, no map updates would have been possible during the maintenance.
Thank you for taking the time to answer this and other messages in the forum. Your help is appreciated.
73,
...luc
- Supernodes must not RF link with other nodes.
- Supernodes may only tunnel with other supernodes
73, ChuckCheck.
k1vl, va3iq, ve6vh. Check.
and may only DtD link with local nodes.
va2rlm-g3-t, va2rlm-g7-t, va2rlm-ns-2397-ne, va2rlm-ns-5910, va2rlm-vm-t, and ve2cro-ns-5910-pret05
appear to be tunneled 1.3 miles away.
Those nodes should appear under 'LOCAL NODES'.
DtD links are physically limited to 100 meters (~0.05 miles).
Perhaps you 'fudged' on the lat/lon values to spread them out on a local map.
The AREDN firmware is assuming those nodes are tunneled instead of DtD'ed.
You are correct. I did "fudge" the lat/lon values as part of a test and never gone back to reset the values.
Had I realized this would cause the node to interpret the distance as being linked by tunnel instead of DtD. I would have corrected it sooner.
Regardless, it's an easy fix.
Are there any other correction(s) or suggestions for improvements, I could be making here ?
Thanks,
73,
...luc
Your /a/status page looks good.
We both have an issue with our tunnel with Lawrence, VA2IQ.
I have no clue what might be amiss with that.
73, Chuck