Noob Connect to an esp32

[Grey-Lancaster]

I have a GL.iNet GL-MT300N-V2(Mango) running OpenWrt 22.03.4 r20123-38ccc47687 / LuCI openwrt-22.03 branch git-23.093.57104-ce20b4a

It is behind my main router 192.168.1.213 and gets an ip of 192.168.1.213 It hands out 192.168.8.x dhcp clients My esp32 that I would like to connect from afar is 192.168.8.202 (edited)

It appears that I may have misunderstood how this works. I thought the esp would show up as a device at ZT.com, but now I believe that if I am on my windows 11 box connected to ZT, I should be able to ping// access 192.168.8.202 webserver. Correct?

My openwrt router does show on zt.com and I can access it from my win 11 box.

The only strange thing is see is "ip a" shows /16 instead of /24 ??

14: ztxyzxxx: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2800 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether f6:a7:19:58:25:63 brd ff:ff:ff:ff:ff:ff
    inet 172.26.240.1/16 brd 172.26.255.255 scope global ztxxxxxx
       valid_lft forever preferred_lft forever
    inet6 fe80::5825:21ff:fe9e:c89d/64 scope link
       valid_lft forever preferred_lft forever

Also I am correct to add 192.168/8.0/24 to the ip's

Thanks, Grey

[ogarcia]

I don't quite understand your question. You say that you have a router (where I understand that you have ZeroTier installed) and an esp32 device, but both in the same network 192.168.1.x. The first one with the IP 192.168.1.213 and the second one with the IP 192.168.1.202. Therefore ZeroTier does not intervene there at all since they have direct communication.

On the other hand, I see that you have defined a ZeroTier 172.26.0.0/16 network to which you have put a route to the 192.168.8.0/24 network through the IP 172.26.240.1. This is correct if you want to reach the 192.168.8.0/24 network via the IP 172.26.240.1.

As for the network being /16 instead of /24 it is because of how you have defined it. The initial IP is 172.26.0.1 and the final one is 172.26.255.254, therefore it is a /16. If you want a /24 you have to choose a range within 172.26. For example for the 240 you would have to set the initial IP to 172.26.240.1 and the final IP to 172.26.240.254.

[Grey-Lancaster]

Thanks, I made a typo. I am so used to 1.1, not 8.1. The esp device is 192.168.8.202

The Wan IP of the router is 192.168.1.213 The Lan IP is 192.168.8.1 The ZT IP is 192.168.193.1

I messed up and delete my managed route 172... <> Lan and could not figure out how to put it back so I created a new network and added the stuff back. Now myip a does not have an inet 6 scope link ?

14: ztxyz: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2800 qdisc fq_codel state UNKNOWN group default qlen 1000 link/ether 56:84:bb:c3:68:31 brd ff:ff:ff:ff:ff:ff inet 192.168.193.1/24 brd 192.168.193.255 scope global ztxyz valid_lft forever preferred_lft forever

From My Phone which is a ZT client, I can open 192.168.8.1 just fine. But 192.168.8.202 is actually working sometimes. From my windows PC ping

Ping 192.168.193.1 works perfect

New network

Thanks again for your help Grey

[ogarcia]

I messed up and delete my managed route 172... <> Lan and could not figure out how to put it back so I created a new network and added the stuff back. Now myip a does not have an inet 6 scope link ?

If you do not enable IPv6 in the ZeroTier central you do not have IPv6, in any case you do not need it so you can have it disabled without problems.

From My Phone which is a ZT client, I can open 192.168.8.1 just fine. But 192.168.8.202 is actually working sometimes.

This may be because you are using too much bandwidth in other traffic (e.g. some Torrent downloads) and there is not enough available to the ZeroTier network. Anyway the ping to and from Android devices on ZeroTier is usually not very stable, do not worry about that, the important thing is that you see that you are able to access the services you have deployed.

[Grey-Lancaster]

Well I thought it was just bad code on my esp as I loaded something diff and it looked perfect. Now it is back to hit or miss. Appears that anything on the lil router wifi is hit or miss It just may not have enough horsepower to run it. Oh well, I suppose it is doing the best it can :)

Thanks again Grey

[Grey-Lancaster]

So confusing. This am it was working perfectly, until I rebooted it ....

[ogarcia]

Note that problems with ESP32 can come from poor WiFi coverage. Try placing the ESP32 closer to the router to check this.