Or if you are running recent nightlies somewhere after Production 3.23.8 and after Nightly 0922 (which does work) to current Nightly 20231018 which does NOT publish on the map. Not sure when it broke, but I think somewhere after Nightly 0922 or so.
I've set up two devices in the past week and neither has appeared in the map. Grid Square and coordinates report as being updated at the top of the setup page. I am entering known good coordinates as I'm a CWOP reporter to the NWS. The interesting thing is the map does not appear to function within the setup page. I try to zoom out for a larger perspective and nothing - just gray. I've attached a screenshot. I'm running firmware 3.23.12.0 DNS resolution is functioning and I have my LAN plugged into the WAN port of my MikroTik RB952-5AC2nD. This is the same issue on my first node which is a GL-AR300M16.
Any help in getting my two nodes to appear is welcomed.
Thanks, Chuck. My post wasn't clear. In addition to the small setup map my nodes were not appearing in the main Aredn map that you sent the link to. I thought maybe the condition between the two map views was maybe related. I have done the 'Apply Location Settings', 'Upload data to AREDN Servers' many times over a few days but the nodes do not appear on the main Aredn map. It would be easy to find my nodes on the map as they would appear almost dead center in the middle of the state of Vermont and Vermont appears to have no other nodes on the map at this time.
I'll take a different tack here by starting with ... "so what?"
I took a look at the map that is on arednmesh.org linked above, and it is woefully out of date. It shows last update for nodes in our region from last June. It shows nodes that have gone offline and been physically removed months ago, but does not show new nodes proudly added in the last month.
So what? We have local versions of Mesh Map hosted here that are up to date. One of our mesh members even has two versons on his server, one that updates to show what was active in the last 2 hours and one that shows everything that was on the mesh in the last 31 days. Both are local, relevant, and useful. I don't need a nationwide map, it's not like I bring aredn hardware with me when I travel.
BTW ... the procedure that Chuck outlined DOES WORK. Doing that gets nodes onto our local maps just fine. You're just IMHO using the wrong map installation.
It's true that the AREDN Mesh map is not being maintained as it should. Plans are being made to correct that.
And it's true that if there's a mesh map locally, that can provide most of the utility of the AREDN map.
They both have their places, and hopefully the AREDN map will be brought current soon.
Now that I have your attention - if a node hasn't been maintained or is likely out of date, it should be removed from the map. But how far back should we retain nodes? Two years? Three years? Or??
It might be nice if the AREDN firmware would publish the location (if it has been entered) say once a week. Then nodes could be purged off the map after say 30 days of not updating their location. That would keep the map more up to date and not have the problem of nodes that have not been online for years showing up on the map.
73
Gerard, WT0F
after say 365 days of not updating their location.
Hi, Gerard:
I have > 15 active nodes without internet access.
When I add, delete, or make a significant change in their host name:
I enable sharing WAN on a home node, reboot,
visit changed remote nodes and click 'Upload data to AREDN Server',
disable sharing WAN on that home node, reboot.
;-) I would rather not do this weekly. ;-)
It shows nodes that have gone offline and been physically remove
"It shows nodes that have gone offline and been physically removed months ago"
Hi, Ed:
Of course it does!
How would it know that a node was added, updated, or removed?
Only by using the 'Upload data to AREDN Servers' tool or the Windows(c) off-line update tool.
The data is static, not dynamic.
Orv, my comments were two fold, one to encourage people not to keep hitting the wall with their head, and to point out the true utility of local mesh maps.
No doubt the larger mesh map has a purpose and I did not mean to imply otherwise. It is more of a fun and informational thing instead of a useful em management tool imho. I would not expect a tool that covers such a large area and so many networks to be perfectly up to date and accurate. Your question about when to drop nodes I believe is why locally K1RKS made the 2 hr map. I can see a conversation where we ask if the map should show nodes with firmware older than ????
Or if you are running recent nightlies somewhere after Production 3.23.8 and after Nightly 0922 (which does work) to current Nightly 20231018 which does NOT publish on the map. Not sure when it broke, but I think somewhere after Nightly 0922 or so.
I've set up two devices in the past week and neither has appeared in the map. Grid Square and coordinates report as being updated at the top of the setup page. I am entering known good coordinates as I'm a CWOP reporter to the NWS. The interesting thing is the map does not appear to function within the setup page. I try to zoom out for a larger perspective and nothing - just gray. I've attached a screenshot. I'm running firmware 3.23.12.0 DNS resolution is functioning and I have my LAN plugged into the WAN port of my MikroTik RB952-5AC2nD. This is the same issue on my first node which is a GL-AR300M16.
Any help in getting my two nodes to appear is welcomed.
Carmine K1VL Shrewsbury, Vermont
My 'http://localnode.local.mesh/cgi-bin/setup' click 'Show Map' also does not work same as yours.
When I recall it working (maybe a few years ago) it only showed itself...never other nodes.
I think that map is to be used to check that you are entering correct values.
I recommend that you 'Apply Location Settings', 'Upload data to AREDN Servers', then
view the AREDN map here: http://usercontent.arednmesh.org/K/5/K5DLQ/livemap2.html#3/39.83/-98.58
73, Chuck
Carmine K1VL
I took a look at the map that is on arednmesh.org linked above, and it is woefully out of date. It shows last update for nodes in our region from last June. It shows nodes that have gone offline and been physically removed months ago, but does not show new nodes proudly added in the last month.
So what? We have local versions of Mesh Map hosted here that are up to date. One of our mesh members even has two versons on his server, one that updates to show what was active in the last 2 hours and one that shows everything that was on the mesh in the last 31 days. Both are local, relevant, and useful. I don't need a nationwide map, it's not like I bring aredn hardware with me when I travel.
BTW ... the procedure that Chuck outlined DOES WORK. Doing that gets nodes onto our local maps just fine. You're just IMHO using the wrong map installation.
73, Ed
It's true that the AREDN Mesh map is not being maintained as it should. Plans are being made to correct that.
And it's true that if there's a mesh map locally, that can provide most of the utility of the AREDN map.
They both have their places, and hopefully the AREDN map will be brought current soon.
Now that I have your attention - if a node hasn't been maintained or is likely out of date, it should be removed from the map. But how far back should we retain nodes? Two years? Three years? Or??
Or maybe purge all and start fresh?
Orv W6BI
Two years? Three years? Or??
Or maybe purge all and start fresh?"
How about an archive through 2023 and starting 2024 anew?
73, Chuck
73
Gerard, WT0F
I have > 15 active nodes without internet access.
When I add, delete, or make a significant change in their host name:
I enable sharing WAN on a home node, reboot,
visit changed remote nodes and click 'Upload data to AREDN Server',
disable sharing WAN on that home node, reboot.
;-) I would rather not do this weekly. ;-)
73, Chuck
Hi, Ed:
Of course it does!
How would it know that a node was added, updated, or removed?
Only by using the 'Upload data to AREDN Servers' tool or the Windows(c) off-line update tool.
The data is static, not dynamic.
73, Chuck
No doubt the larger mesh map has a purpose and I did not mean to imply otherwise. It is more of a fun and informational thing instead of a useful em management tool imho. I would not expect a tool that covers such a large area and so many networks to be perfectly up to date and accurate. Your question about when to drop nodes I believe is why locally K1RKS made the 2 hr map. I can see a conversation where we ask if the map should show nodes with firmware older than ????
Ed