Running nat-detection on a simple computer returns NAT status has been found to be: UPnP
Running nat-detection in a container (incus) returns NAT status has been found to be: Private
Both machines are behind the same router (OpenWRT) and have an ip-address from the same subnet on the same network. The container has a macvlan interface, so there’s no extra routing going on.
What could be the reason for the difference? Can I somehow get more verbose output from nat-detection?
Looking at the routers active dynamic port mappings, UPnP, NAT-PMP, PCP, all work from containers using other software and from computers running antnode or other software. So there’s something with containers and autonomi. antnodes in containers make connections - using hole-punching I suspect - but data storage remains empty.
Could antnode / nat-detection require extra privileges/capabilities in order to work?