Hi friends,
I am an AREDN newbie and stuck with following:
I got 3 pcs. Gl.inet AR150, put aredn Vers. 3.20.3.1 on those and did the recommended basic setup.
In the wifi scan I can well see al of it as foreign networks without name but on the status page I find only my own local node which is connected by cable to my laptop.
Both the other 2 nodes which should connect via RF are not visible / connected.
Sorry, I searched almost the complete web but didn't find a source explaining to me what I am doing wrong and how I can make the 2 other nodes connect via RF?
:-(
Can someone give me a hand where to find some howto information and / or how to proceede forward?
Many tahnks &73
Manuel DO5MSH Hamburg, Germany
I am an AREDN newbie and stuck with following:
I got 3 pcs. Gl.inet AR150, put aredn Vers. 3.20.3.1 on those and did the recommended basic setup.
In the wifi scan I can well see al of it as foreign networks without name but on the status page I find only my own local node which is connected by cable to my laptop.
Both the other 2 nodes which should connect via RF are not visible / connected.
Sorry, I searched almost the complete web but didn't find a source explaining to me what I am doing wrong and how I can make the 2 other nodes connect via RF?
:-(
Can someone give me a hand where to find some howto information and / or how to proceede forward?
Many tahnks &73
Manuel DO5MSH Hamburg, Germany
just to be sure! Are all the nodes set on the same frequency and bandwidth?
When did you say status page do you meant Mesh Status?
Ciao
Leo, I3RKE/AC2OG
Thanks, Yes all three are on the same frequency and bandwidth and yes I meant mesh status.
When I connect the nodes via cable they see each other but not via RF :-(
(Well, use 10 and 20 MHz bandwidths. Avoid 5 MHz bandwidths as they have some issues.)
Are all devices scanning the same channels?
RF will not link unless the channel, bandwidth, and SSID matches.
Chuck
While I don't think I've heard of this issue with GL.inet, I have heard of (and actually seen with bluetooth modules) some brands recycling MAC addresses between multiple pieces of hardware. If they find themselves in the same broadcast domain, they can cause some pretty strange problems...