You are here

new node, no name resolution

14 posts / 0 new
Last post
kg7kmv
new node, no name resolution

I just picked up a second GL750 (creta) device and loaded aredn 3.22.8.0 FW. Got it setup and configured, just like I did the first one (working great, love it!)

But this one doesn't seem to resolve names!

  • It is setup stand alone: no ethernet connections, Wifi access, and 2G mesh to my hAP, which is sharing WAN and working great. I can see all the meshed nodes on Mesh Status and I verified it is configured exactly like my other Gl750 (which is working perfectly). No special configuration, mostly defaults.
  • While on the GL750 wifi, I can only access the node via 'localnode.local.mesh', not by it's name 'KG7KMV-GL750-2.local.mesh'. I cannot access any other nodes it is connected to by their names or IPs.
  • I can access the node from the mesh.

Any thoughts here? I've tried a few things, but I'm not a "power user". Should I try the Reset to Firstboot button and start over?

nc8q
nc8q's picture
new node, no name resolution

Maybe another set of eyes might find a difference.
Please, instead of using words, show us your configuration
73, Chuck

 

K5DLQ
K5DLQ's picture
Do you have a custom DNS

Do you have a custom DNS configuration on your computer, perhaps?  
 

kg7kmv
no custom DNS that I know of.

no custom DNS that I know of. Same issue on PC, phone, and tablet, only on this node.

now some screenshots!
I had installed the blockkonwnencryption package, but removed it many reboots ago
(pasted screenshots didn't stick when I saved.. trying again)






Image Attachments: 
nc8q
nc8q's picture
kg7kmv-gl750-2 -> kg7kmv-router 100% 60%

KG7KMV:
I am concerned with the 60% NLQ and tunneled neighbors sharing WAN.
You should strive to achieve 100% LQ and NLQ.
"Location Not Available" !
Are both GL750s and kg8kmv-router in the same building or on the same property?

Trouble shooting:
From a computer on the LAN of your kg7kmv-gl750-2,
I would like to see the results of a PING with a destination node.
example:
gelmce@nc8q-mesh:~$ ping -c 1 kf8mz-ar150
PING kf8mz-ar150.local.mesh (10.9.116.210) 56(84) bytes of data.
64 bytes from KF8MZ-AR150.local.mesh (10.9.116.210): icmp_seq=1 ttl=61 time=21.9 ms

--- kf8mz-ar150.local.mesh ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 21.913/21.913/21.913/0.000 ms
gelmce@nc8q-mesh:~$

(Windows OS has a slightly different syntax)

If the PING is successful, I would like to see a traceroute.
example:
gelmce@nc8q-mesh:~$ traceroute kf8mz-ar150
traceroute to kf8mz-ar150 (10.9.116.210), 30 hops max, 60 byte packets
 1  localnode.local.mesh (10.174.162.33)  0.551 ms  0.536 ms  0.845 ms
 2  dtdlink.NC8Q-hAP.local.mesh (10.218.93.193)  1.947 ms  1.934 ms  1.922 ms
 3  mid2.KF8MZ-MTIK5G (172.31.187.121)  19.434 ms  19.880 ms  34.906 ms
 4  KF8MZ-AR150.local.mesh (10.9.116.210)  34.894 ms  35.134 ms  35.122 ms
gelmce@nc8q-mesh:~$

(Windows OS command is 'tracert')

- Why are kg7kmv-router and KI0E-HAP-4 sharing their internet connection with the entire local AREDN network?
- I am concerned that tunneled nodes may have multiple tunnels/routes and there may be some 'looping'.
There was a bug-fix in the nightly to ensure that tunneled nodes do not link via exposed WAN sharing.

Aside:
- I see some 'not so unique' hostnames on your network.
(example: raspberrypi, which is the default hostname of all Raspberry Pis.)
(https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/advanced_config.html#port-forwarding-dhcp-services-and-dns-aliases):
The hostnames of computers connected to the mesh at large must be unique.
Typically you should prefix your amateur radio callsign to the computer’s hostname in order to have the best chance of it being unique on the mesh network.


Expand to: The hostnames of computers, devices, cameras, IP phones, PBXs,... connected to the mesh at large must be unique.

73, Chuck

kg7kmv
Thanks for all the

Thanks for all the recommendations!

- The link between kg7kmv-gl750-2 and kg7kmv-router is across my house, in a temporary testing situation while I sit at my work bench to get it setup.
- I didn't set the location on the 750 because I don't know where it will end up. I loan them out to other hams interested in trying it before buying. 
- We have a very small network over here with 3 hams, very early stages of experimenting and learning AREDN. I just turned off my WAN sharing, but it's helpful sometimes getting new nodes connected which otherwise have no WAN connection.
- I can address the hostnames with the other operator. As of now there are only two of us with any services on our network.

On the issues with my gl750:
- I did a reset to firstboot. Then had a heck of a time getting it to take the new node name. when I clicked save settings the page would 404 error. Long story short, I eventually got it to take the name/password. Still not doing hostnames for me when connected to the 5G wifi.

ping and traceroute tests (from PC connected to kg7kmv-router meshed to kg7kmv-gl750-2):

root@KG7KMV-GL750-2:~# ping kg7kmv-router.local.mesh
PING kg7kmv-router.local.mesh (10.5.13.64): 56 data bytes
64 bytes from 10.5.13.64: seq=0 ttl=64 time=12.384 ms
64 bytes from 10.5.13.64: seq=1 ttl=64 time=4.959 ms
64 bytes from 10.5.13.64: seq=2 ttl=64 time=1.635 ms
64 bytes from 10.5.13.64: seq=3 ttl=64 time=1.645 ms
64 bytes from 10.5.13.64: seq=4 ttl=64 time=1.946 ms
64 bytes from 10.5.13.64: seq=5 ttl=64 time=3.317 ms
^C
--- kg7kmv-router.local.mesh ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 1.635/4.314/12.384 ms
root@KG7KMV-GL750-2:~#
root@KG7KMV-GL750-2:~# traceroute kg7kmv-router.local.mesh
traceroute to kg7kmv-router.local.mesh (10.5.13.64), 30 hops max, 38 byte packets
 1  KG7KMV-router.local.mesh (10.5.13.64)  2.447 ms  1.966 ms  3.911 ms
root@KG7KMV-GL750-2:~#


pretty much the same result with a PC connected to the LAN on kg7kmv-gl750-2.

I discovered that while my PC is on the LAN of kg7kmv-gl750-2 I have name resolution. It's only when connected to its WiFi that names don't work for the connected client.
 

nc8q
nc8q's picture
It's only when connected to its WiFi that names don't work for t

"It's only when connected to its WiFi that names don't work for the connected client."

KG7KMV:

Then, perhaps, the same test 'when connected to its WiFi'.

"when I clicked save settings the page would 404 error."
This is likely because, when the node rebooted, your PC dropped its DHCP client address.
'404 error' was likely generated by your web browser.
Wait 1 to 3 minutes and do a  'page refresh'.
Sometimes I do a
ping -i 9 <nodename>
and watch for a response. "-i 9" wait 9 seconds between PINGs
(Windows OS argument syntax may be different)

Earlier:
"No special configuration, mostly defaults."
er, uh, in Advanced Configuration, what is not default?

I see in your images that you have 2 outdoor rated radios and
everyone else is a tunnel.

Which 'names' don't work for the connected client.
Can you PING them 'when connected via AR750's WiFi'?

73, Chuck
 

kg7kmv
Sadly, we are mostly tunnel

Sadly, we are mostly tunnel connections right now. Our network is young and we don't have a good hilltop node yet nor tall towers to get over all the trees. The 3 active ops are loaning out devices for other hams to try out, who are not tech-savvy.

"Mostly defaults" means the only things I changed were:
- node name
- root password
- enable 5G wifi

 

kg7kmv
here are some screenshots

here are some screenshots from my PC connected via cable to the gl750 LAN.
the gl750 is connected to my home network via cable on the WAN port.
the gl750 has a (poor) mesh connection to kg7kmv-router.
I expect that my PC should have full mesh access AND full internet access like this, and I get that with other nodes in this same setup.
 

Image Attachments: 
nc8q
nc8q's picture
gl750 is connected to my home network via cable on the WAN - not

Your image in #4 indicates that gl-ar750-2 does not have a WAN connection.
This may need to be fixed.

The bottom image in #9 indicates that 'router' is not offering DNS for internet names.
This may need to be fixed.

I advise against sharing internet access across the network --- full time.

If you want internet access, it may be best to enable it on one of your home devices
(hAP, GL-AR750-1, GL AR750-2) then connect to that device via its 5 GHz Wi-Fi.

Can you use your mouse and cut-n-paste the text from your windows cli into your post?

73, Chuck

 

kg7kmv
I've changed up the setup

I've changed up the setup several times. I started fresh here.
GL750 is plugged in WAN <-> home LAN.
Screenshot shows it has a WAN IP and Default gateway on my LAN.
I SSH to the GL750 and ran a few commands. The output is attached, including the node ifconfig report.
Summary:
- traceroute to another node is successful
- traceroute to google.com is successful
- Node has mesh and internet access!

on my PC, which is attached to the GL750 wifi, it can reach mesh nodes but has no internet access.
Here is the ipconfig output:

 
Wireless LAN adapter Wi-Fi:
 
   Connection-specific DNS Suffix  . : local.mesh
   Link-local IPv6 Address . . . . . : fe80::b047:15db:645f:3717%7
   IPv4 Address. . . . . . . . . . . : 10.245.77.147
   Subnet Mask . . . . . . . . . . . : 255.255.255.248
   Default Gateway . . . . . . . . . :

No other connections. I noticed that the default gateway is blank. That seems like the issue why my PC can't get on the node WAN.

Can a hardware issue cause this? I got the node open box on ebay.

debug file attached as well.
Image Attachments: 
File Attachment: 
nc8q
nc8q's picture
Windows user please help.
Reference:
Wireless LAN adapter Wi-Fi:
 
   Connection-specific DNS Suffix  . : local.mesh
   Link-local IPv6 Address . . . . . : fe80::b047:15db:645f:3717%7
   IPv4 Address. . . . . . . . . . . : 10.245.77.147
   Subnet Mask . . . . . . . . . . . : 255.255.255.248

   Default Gateway . . . . . . . . . :

KG7KMV:

All looks good to me regarding your kg7kmv-ar750-2.
The output from your unknown Windows CLI command does not seem correct to me.
I cannot advise as I don't do Windows.

73, Chuck

 

KK6BML
KK6BML's picture
Updated hAP - same name resolution problem.

I have 2(or now 3) hAP lite' - one sits fixed in my house attached toan nm2, a nm5 and a rPi - backup server for Laguna Niguel ACS services. this hAP was updated to 3.22.8.0 10/16/22. I have a second (and now 3rd thinking 2nd might be damaged - plus "one is noe, two is one" redundancy adage) that I deply mobile with a switch, NM5 & NM2 node and ip cameras (Summple &a Foscam) for Emergency and other events. I upgraded the second one 11/20/22 or there about. basic Setup, Port forwading page, advanced configuration look the same. however, the second node is displaying all the symptoms described in this thread. I reserve an ip address for a camera,and publish it as alwasy - appears on mesh status correctly yet clicking on link give a response of not connected to the internet (isn't resolving the name), can't ping by name, but can ping by direct ip address and can connect to the camera (or other services) by keying ip address directly into browser. This is across the board - any Mac os or ios device and my windows machine. doesn't matter if connected by ethernet or wifi or remotely via mesh rf.  Further - get the same result trying to click through to ANY name (node or service) on the Mesh Status page. And yes, I've emptied my cache (and cleaned my cookies and restarted the browser and tried several different browsers and rebooted my devices) - to no avail.
Main thing I note in common in the thread and it sparked interest - when I check DHCP configuration (ipconfig in windows terminal or network adapter setting on MAC) the connection is configured with a proper ip address and subnet mask from the DHCP setup on the hAP but NO Primary Gateway(windows speak) / Router(Mac speak) address in the DHCP assignment. All other devices I have that can be connected to as DHCP server all have this value (it is always the LAN address of the DHP Server device).

It is driving me crazy trying to prepare for our major annual event in 2 weeks. I'm working with KK6LZB in Laguna Niguel to see that the nodes & cameras are all configured and accessable by our main control module (ZoneMinder on the LNACS mesh server) for the Laguna Niguel christmas parade. BTW - this node worked completely correctly under ther 3.21 build

Bob Evans KK6BML

PS - I've been at this for 4 hrs tonight on top of about 12 the last week so don't have energy or time to create and upload screen shots or device log files at this point

kg7kmv
I did end up getting mine

I did end up getting mine working by enabling "aredn.@wan[0].lan_dhcp_defaultroute". 

Just very strange that one device needed that and the other one does not.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer