You are here

Home » Forums » Hardware » Nodes

Can not connect wifi to New TP-link 210 nodes

5 posts / 0 new
Log in or register to post comments
Last post
Sun, 11/18/2018 - 14:29
#1
K3MMB
Can not connect wifi to New TP-link 210 nodes
Two brand newly configured 210v2 nodes see and play nice with each other. 

Computer connected to switch can access either unit. Computer trying wifi connect gets: Can Not Connect to this Network.

What did I do wrong? It has to be a simple error.

73 de mike
Top
Sun, 11/18/2018 - 15:42
K6AH
K6AH's picture
PCs are going to connect via

PCs aren't going to connect via wifi to a mesh node unless you have setup a wifi access point specifically for that purpose.

Andre

Top
Sun, 11/18/2018 - 16:03
(Reply to #2)
K3MMB
HW exchanged and better
Thanks Ande,
I traded out (apparently bad ap) with new tplink set up and connected node2 with static ip, made dhcp reservation.

Connecting to both nodes, but only using node base ip. so if I want to connect with node name, what do I need to change?

again, thanks
73 de mike
Top
Sun, 11/18/2018 - 20:18
(Reply to #3)
K6AH
K6AH's picture
Full Qualified Node Name
The node you are Ethernet-connected to is http://localnode.local.mesh and all other nodes use the convention, nodename.local.mesh and for services, servicename.local.mesh.  Note that servicename must be unique across the mesh, so each service should be preceded with your callsign (ex: callsign-servicename.local.mesh).

Andre
Top
Mon, 11/19/2018 - 09:42
(Reply to #4)
K3MMB
localnode.local.mesh will not connect, but
nodename.local.mesh:8080 will -- must have port to access.

node is connected to cisco switch. laptop is connected to switch. laptop gets 10. address from node. node name works.

connected to AP on the second node, and only the node 10. base addr works. AP is configured with static from dhcp pool on node.
 so if I want to control remote node via wifi, is that correct?

 
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer