martin-ger

Yes, they all will use the 192.168.1.245 as DNS. As long a requests from somewhere in the chain go outbound to 192.168.1.xx or further to the Internet - no problem.

Starting point should be the https://github.com/martin-ger/esp32_nat_router . It contains all the required features aside from mesh. The mesh state mashine should be added - best from scratch. A detailed description...

Locally from the NAT routers from their local subnets. You cannot access these adresses from the outside (as usual with NAT).

This is done automatically "... Also the IP address of the internal network is adjusted to the mesh level: 10.24.m.0." https://github.com/martin-ger/esp_wifi_repeater#automesh-mode There is no need to cofigure this - or...

Yes, each ESP give out its local 10.24.m.x addresses. ESPs on the same mesh level will use the same addresses in their local nets, but due to NAT, this is...

Locally you can see the assignment on the serial CLI with "show status". Remote login via port 7777 is not so easy in a multilevel mesh setup, as you cannot...

Guess, the easiest way would be, to connect it upstream via the ESPs to an MQTT broker and control it via MQTT topics.

It is a completely independent approach.

Other measurements have shown, that the performance can be much better. Problems may occur with buffer space: if too many packets come in at the same time, the repeater has...

"NAT table full" means: too many connections at the same time (or in the last seconds). Currently there is limit of 512 entires in that table and I already drop...