Good Afternoon,
Though I'm not new to AREDN, we have now taken the deep-dive and have set up several nodes at various sites as well as a few that are based in residences. Some are RF...some are not; however, all have Internet access.
I'm trying to wrap my head around how access to specific nodes & services is done...especially to one's own nodes. Normally on a typical network, setting up shared access is pretty straightorward but my understanding of how AREDN approaches access and "sharing" is unclear.
Is there a guidance document that might shed some light on this?
Thank you.
Though I'm not new to AREDN, we have now taken the deep-dive and have set up several nodes at various sites as well as a few that are based in residences. Some are RF...some are not; however, all have Internet access.
I'm trying to wrap my head around how access to specific nodes & services is done...especially to one's own nodes. Normally on a typical network, setting up shared access is pretty straightorward but my understanding of how AREDN approaches access and "sharing" is unclear.
Is there a guidance document that might shed some light on this?
Thank you.
If you're not on the mesh but have internet, then you need to have someone with a tunnel server give you credentials. I just setup a Gl.i device that fits in my travel laptop bag. It connected me via hotel wifi to the tunner server on my local mesh (OR) and I was on the mesh and able to look things over from 3K miles away.
You have to learn about setting up tunnel clients, then learn how to connect via wifi if no ethernet port is available to you where you are.
Ed
if that is the case, then you have to either access one of the nodes via Ethernet at one of the nodes or enable wifi access on one of the nodes and access it that way. this will allow you to explore the network/access the other nodes.
there might be another way to do this once you access the node from the WAN but i haven't be able to figure it out myself.
More information please.
Does 'Some are RF' mean 'Some are RF connected' ?
Does 'some are not' mean 'Those that are not RF connected are tunneled'?
IOW, are all these AREDN nodes 'connected' via RF or tunnel?
"how access one's own nodes"
Commonly, a node is 'accessed' via a computer with a web browser application.
The computer is ethernet connected to the LAN port of the POE injector powering the node.
The web browser uses the address 'http://localnode.local.mesh' and navigates the web pages of the nodes to configure settings.
"how access to specific nodes"
Once the above is available, navigating the other 'connected' nodes is with the web browser
from http links on the local node's web pages.
"on a typical network"
The world wide web is a typical network and there are bazillions of shared resources.
My home LAN shares resources with me.
My AREDN nodes share resources with others on the local AREDN network.
'"sharing" is unclear.'
It is unclear to me what 'sharing' you seek.
"Is there a guidance document that might shed some light on this?"
Start here:
https://docs.arednmesh.org/en/latest/
Especially:
https://docs.arednmesh.org/en/latest/arednServicesGuide/services_overvie...
I hope this helps,
Chuck
OK, so you have a Mikrotik hAP-ac2 and a Mikrotik hAP-ac3.
How are they connected?
via RF ? If yes, then both must be configured as 'mesh'...not Wi-Fi client nor Wi-Fi Access Point.
What channel and bandwidth?
DtD ? If yes, then the nodes may be Access Points or 'Ad Hoc' network devices.
Your computer is (ethernet) or (Wi-Fi client) connected to which node...ac2? ...ac3?
73, Chuck
If you have several nodes installed in your home with proximity such that you can/should be able to maintain RF connections between those nodes, then simply type "localnode:8080" to gain access to what your computer sees as your directly connected node.
This should bring you to the home/management screen of that node. There is a lot of useful info there, but just take a look at the lower right corner of that scrren. You should see something like this:
"host entries: 238 nodes / 684 total devices"
This should say something more than "1 node" and more than "1 total devices".
Also check out this entry: "signal|noise|SNR: no RF links "
If your's says "no RF links" like in this example above, that certainly suggests that you don't have RF links established between the node you are accessing and other nodes in your proximity.
This would be a better indication: "signal|noise|SNR: -48 | -95 | 47 dB "
In this example, the node is indeed reporting a connection to some node with the values as indicated.
From there, if you click on "mesh status", you should see all the other nodes you have/are connected to. Simply click on the link to any of the nodes listed and you should be whisked away to that node's home screen.
If you don't see other nodes, then either you are out of range of the other nodes or you don't have them configured correctly (that is, using the same SSID, same freq and bandwidth parameters, etc.
I hope this helps.
Regards,
Kent, KL5T
I'm digging in to your suggestions right now. :-)
Gary
I discovered something interesting. Using the "localnode:8080" URL, I got the following results via the node's wi-fi SSID: AK4ZX-AC2-AREDN
Macbook Pro - brought up the localnode via wi-fi but red links, etc., result in "can't find messages".
Macbook Pro direct connected via Ethernet and wi-fi off; results in can't find site. However, if I use the localnode's IP address, I can get to the dashboard but red links don't work.
ASUS Laptop - brought up the localnode via wi-fi and all red links work!
ASUS Laptop direct connected via Ethernet and wi-fi off; success and all red links work.
Lenovo Laptop - brought up the localnode via wi-fi and all red links work!
Lenovo Laptop direct connected via Ethernet and wi-fi off; success and all red links work.
My MacBook Pro is my daily driver and I see no settings that would explain its lack of success. I even did a full DNS flush.
Still digging...Thank you again.
Gary
Can you provide any screen shots of your home screen on any of your nodes?
Regards,
Kent
Is a tunnel required?
I see them on Mesh Status but clicking any red link results in a "can't find" message when I connect to a node via its wi-fi SSID. If I plug into it via Ethernet, it works.
That seems to reinforce my first comments, you do not use both rf AND a switch to connect one device to a network.
Changing Advanced Configuration settings doesn't seem to make it work either via wi-fi. Using a node's (ac2 or ac3) wi-fi allows me to get to the Internet but not use most of the links here and there to other nodes elsewhere "within the mesh"
You're fiddling with stuff that should not matter. Internet and AREDN mesh are two completely different things, they are NOT cross connected unless you are making serious mistakes or doing some highly advanced stuff that requires a high level of knowlege re firewalls and protocols. Go back to the basics and start over is what I'd recommend.
Ed
First of all, welcome to the AREDN community. It sounds like you have multiple nodes connected in varying methods. Might be useful to post a drawing of what all is there and how the various nodes are connected. I am in the same condition. At this moment there are 10 nodes at my house. Let's see if this image posts correctly. The image did not post, so here is a direct link to it: http://k6ccc.org/images/Home%20AREDN%20network.png
My non-consumer grade router connects to a LAN port on the hAPac3 and gets a 10.x.y.z address. My home computer gets to the AREDN network by way of my router since the router knows that 10.0.0.0/8 is reachable via the hAPac3. The DNS server knows that any url ending in .local.mesh is reachable via the hAPac3. This is one of several ways to connect, but not the most common. The black links are DtD, purple-ish is 2.4 GHz, blue is 3 GHz, and orange is 5 GHz.
One note I will make is there are times where it is VERY useful to know what the IP addresses are for each node. I have bookmarks for mesh node name, mesh IP, LAN IP, and if there is one the WAN IP for every one of my nodes (and some others). The node IPs are available from the main status page. The image did not post so here is a direct link to it: http://k6ccc.org/images/AREDN%20IPs.png
I think you should be able to ping the various parts of you network to determine connectivity. Several of us here have scripts of ping commands to evaluate network capability/stability. I like
ping -R -c5 <node name> or
ping -R -c5 <IP address>
because it gives a Route Report to see how the ping got from sending end to prescribed destination and back. -R does not report every stop on the path, but is a powerful tool when the ping goes through. The ping is repeated five time (-c5).
After some experimentation, we use CAT5 to connect computers to local radios, and CAT 5 cable with dtd hubs (like MikroTik hEX POE lite) to connect several radios at one location. We are using Wireguard tunnels because here in the North Texas flat lands, trees and buildings make problematic seeing "hub" nodes even on 200 ft structures unless you have a tower in your yard.
--Tim K5RA
Orv W6BI
I need to try mtr. Sounds interesting.
We have a script we run on our R-Pi machines that uses these command-line tools:
arp - Address Resolution Protocol
netstat - Network Statistics
nmap - Network Mapper
All have a lot of options. There are stories about them in Wikipedia, on Internet, and in your computer with MAN <app name>
--Tim K5RA