Daniele Mannocchi

I'm working with AWSIoT. After understanding that is not useful set the CA cert path, I have encountered your same problem. Looking on called callbacks I have on_disconnected called with...

Same problem... any update?

ZeroTier Center: openwrt device has fixed ip (172.25.0.1) and "allow ethernet bridging" enabled Openwrt dev: zerotier ip: 172.25.0.1 lan ip: 192.6.21.194 ``` root@OpenWrt:~# ip route default via 192.6.21.254 dev br-lan...

ok, now I have ``` root@OpenWrt:~# ip route default via 192.6.21.254 dev br-lan proto static src 192.6.21.194 172.25.0.0/24 dev ztr4nq3plz proto kernel scope link src 172.25.0.1 192.6.21.0/24 dev br-lan proto...

I'm trying to ping and trace from an android device with Fing as app... i can reach 192.6.21.194 with both tools but no one of other lan ip

> From what you say it seems that the problem is that your android client is not receiving correctly the route that tells him that to reach the network 192.6.21.0/24...

The strange thing is that the traceroute knows that the end device is under the openwrt dev, so from the phone the route reaches the openwrt router but after that...

This morning I have done this test: phone hotspot > linux wifi (?.?.?.?)> shared ethernet connection (10.42.0.1) > openwrt (eth 10.42.0.21, zt 172.25.0.1) from another pc on another net, connected...

OK WORKS!!! **Before**: I have canceled the whole configuration; after that I have re-created the config as in the tutorial. phone (zt)> zerotier cosmos > (zt) openwrt (lan) > pc...