Our core mission is driving the future of distributed cloud computing. The infrastructure of the internet is siloed and byzantine. We can do better.

GRAVITL

I created a new /24 v0.10.0 network with UDP hole punching disabled
and one client node. I verified that the client could `ping` the
server and then used the administrative console to change the
listening port of the client. After waiting a few minutes, I executed
`wg show` on the client and found that its listening port had not been
changed. Executing `netclient checkin` on the client did update the
listening port to the new value. Is this the intended behavior?