You are here

Nano Loco M2 not providing master mesh node info

6 posts / 0 new
Last post
VA7NIC
VA7NIC's picture
Nano Loco M2 not providing master mesh node info

Recently upgraded a Nano Loco M2 to 3.18.9.0.   It will not provide the info to Winlink Express to obtain WL2k post office info.

All the other nodes on the mesh (Bullets, Air Grids, Rockets) running 3.18.9.0 do provide the info.

If I swap out the LocoM2 for an AirGrid (which isn't practical for permanent install) then the issue goes away, so its got to be LocoM2 related. 


Winlink would report:  Error getting master node info.  Unable to get info from master node ve7ahe-ecommtrailer.local.mesh
Your computer must be connected to an AREDN MESH node running firmware version 3.17.1.0RC1 or later.

Here is the JSON file output it makes.
{
   "lon": "",
   "sysinfo": {
     "uptime": "0 days, 8:26:21",
     "loads": [
       0,
       0.029999999999999999,
       0
     ]
   },
   "interfaces": [
     {
       "name": "eth0.1",
       "mac": "68:72:51:5D:4A:F5"
     },
     {
       "mac": "68:72:51:5C:4A:F5",
       "name": "wlan0",
       "ip": "10.92.74.245"
     },
     {
       "mac": "68:72:51:5D:4A:F5",
       "name": "eth0",
       "ip": "10.137.94.161"
     },
     {
       "mac": "68:72:51:5D:4A:F5",
       "name": "eth0.2",
       "ip": "10.93.74.245"
     }
   ],
   "api_version": "1.5",
   "services": [
     {
       "name": "WINLINK POSTOFFICE",
       "protocol": "tcp",
       "link": "http:\/\/VE7URC1-oldPO-POSTOFFICE:0\/"
     },
     {
       "name": "POSTOFFICE",
       "protocol": "tcp",
       "link": "http:\/\/AARC-PO:0\/"
     },
     {
       "name": "WINLINK POSTOFFICE",
       "protocol": "tcp",
       "link": "http:\/\/AARC-PO:0\/"
     },
     {
       "name": "POSTOFFICE",
       "protocol": "tcp",
       "link": "http:\/\/POSTOFFICE:0\/"
     },
     {
       "name": "Admin",
       "protocol": "tcp",
       "link": "http:\/\/VA7NIC-ER-X:80\/"
     },
     {
       "name": "WINLINK POSTOFFICE",
       "protocol": "tcp",
       "link": "http:\/\/POSTOFFICE:0\/"
     },
     {
       "name": "FILES",
       "protocol": "tcp",
       "link": "ftp:\/\/POSTOFFICE:21\/"
     },
     {
       "name": "HELP",
       "protocol": "tcp",
       "link": "http:\/\/POSTOFFICE:80\/"
     },
     {
       "name": "Admin",
       "protocol": "tcp",
       "link": "http:\/\/VE7URC-Switch:80\/"
     },
     {
       "name": "WINLINK POSTOFFICE",
       "protocol": "tcp",
       "link": "http:\/\/Library1:0\/"
     },
     {
       "name": "Admin",
       "protocol": "tcp",
       "link": "http:\/\/HP-G60-230CA:3389\/"
     },
     {
       "name": "Admin",
       "protocol": "tcp",
       "link": "http:\/\/VA7PAM-ER-X:80\/"
     }
   ],
   "meshrf": {
     "chanbw": "20",
     "ssid": "BroadbandHamnet-20-v3",
     "channel": "-2"
   },
   "tunnels": {
     "active_tunnel_count": "0",
     "tunnel_installed": false
   },
   "lat": "",
   "grid_square": "",
   "node": "VE7AHE-ECommTrailer",
   "node_details": {
     "firmware_version": "3.18.9.0",
     "board_id": "0xe0a2",
     "firmware_mfg": "AREDN",
     "model": "NanoStation Loco M2 "
   }
 }

K5DLQ
K5DLQ's picture
Can you confirm the AirGrid
Can you confirm the AirGrid is running 3.18.9.0 also?   This is very odd.
VA7NIC
VA7NIC's picture
Yes, all 18 nodes on our mesh

Yes, all 18 nodes on our mesh have been upgraded to 3.18.9.0 (which I might add is running really well except this hiccup)

 

k1ky
k1ky's picture
Nano Loco M2 not providing master mesh node info
I think there may have been some changes to the .json file output?  This may have affected the MESH P.O. listings.  I believe this has been a "work in progress" anyway and would highly suggest that you just publish the hard I.P. addy of the post office for best results.
I have discussed this with the Winlink developer and may review it again to see where we are on this.
VA7NIC
VA7NIC's picture
The json output appears to
The json output appears to work fine on the other nodes in the mesh if I point Winlink at them, the issue appears to be localized at this point to a Nano Loco M2.    

 
VA7NIC
VA7NIC's picture
An update to this thread...
An update to this thread... the Nano Loco M2 didn't have the gps co-ordinates programmed in, as the unit isn't always in one spot (Mobile comms trailer).

Once I put the co-ordinates in, the Winlink Postoffice services detection started working. 

I have 1 other node to test this theory against.

 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer