You are here

Home » Forums » Hardware

DNS Name Resolution

9 posts / 0 new
Log in or register to post comments
Last post
Tue, 08/06/2019 - 16:09
#1
W2JCL
DNS Name Resolution

I'm running a simple setup with a NanoBeam connected to a wireless Access Point (TP-Link TL-WR802N).  There is no WAN access.  The Access Point allows me to monitor the node from a laptop or cell phone via WiFi.  The problem I am having is that I can only access the node or its services by using its LAN address.  I cannot use the name of the node, as there appears to be no DNS name resolution.  Is there a way to solve this problem without adding hardware or WAN access?

Thank you,

Jeff W2JCL
 

Top
Tue, 08/06/2019 - 21:14
AE6XE
AE6XE's picture
Jeff, can you clarify the
Jeff, can you clarify the senario?   Is the "mesh rf" disabled, and a WAN wifi client enabled, and connected to this tp-link AP?   "no WAN access" means the tp-link is not connected to anything else, except other AP clients, like your laptop?

Joe AE6XE
Top
Tue, 08/06/2019 - 21:38
W2JCL
DNS Name Resolution

The mesh rf is enabled, as I intend to connect the node in the field to other nodes.  Because it will be used in the field, there is no available WAN.  The Access Point is used so I can monitor the node and see and utilize the rest of the mesh through either a laptop or mobile phone.

Top
Tue, 08/06/2019 - 21:49
AE6XE
AE6XE's picture
You have a cat5 cable between
You have a cat5 cable between the tplink AP and the mesh node?      If so, then put the tplink AP in 'bridge' mode.  The devices connecting to the AP, will then receive an IP address from the mesh node and receive route information to talk to mesh devices. 

Joe AE6XE
Top
Tue, 08/06/2019 - 21:59
W2JCL
DNS Name Resolution
That's correct.  The mesh node is connected directly to the Access Point via cat5 cable.  I will try bridge mode on the AP and let you know what happens.
Top
Tue, 08/06/2019 - 23:14
W2JCL
DNS Name Resolution
My TP-Link device (TL-WR802N) does not have a bridge mode.  The closest mode appears to be Access Point.  This is the mode I have been using.  I've tried it with the AP's DHCP on and off.  With it on, it is functioning as I originally described.  With it off, it doesn't work at all.  Perhaps I need a different router?
Top
Wed, 08/07/2019 - 09:12
KD2EVR
KD2EVR's picture
I have one of those and it
I have one of those and it seems to work most reliably when I follow a staged power-up sequence.  I power up the node, let it finish booting, power up the TP-Link in access point mode, then finally connect the wifi device to the TP-Link.  If I don't it's hit and miss.  Maybe the TP-Link defaults to another mode if it doesn't see the DHCP server immediately.   
Top
Wed, 08/07/2019 - 11:46
W2JCL
DNS Name Resolution
That's an interesting observation.  I tried it, and it works!  DNS is working, and I'm able to open other nodes on the mesh and access services such as Winlink gateways.  I also note that the mesh is now passing internet access to my laptop, which it did not do before.  The internet access is coming from some other node on the mesh.  This might be why DNS is working.  Still, it does show that the power up sequence matters.

Thanks again, Jeff
 
Top
Wed, 08/07/2019 - 12:06
AE6XE
AE6XE's picture
I've seen this with some
I've seen this with some ipCams too.   The device will look to receive via DHCP an IP address and DNS server addresses from the mesh node.  But if the mesh node doesn't respond in a timeout period, the device falls back to a default static configuration (so the device  still has a path to be accessed).      It's painful when the ipCam is up 100' on the tower and  can't be communicated with, if the power  up sequence isn't right, and you don't know why :) .     I've changed the fallback settings on the device to be the same as what the mesh node would provide, so that it always works. 

Joe AE6XE
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer