I have a persistent Windows 10/11 netlcient with local egress gateway routing issue. It's taken me a while to work out what's going on, but I hope it will be reproducible in different setups. I have tested in different locations with completely different netmaker servers. Would be great if you could test @quiet-continent-24852. Since version 0.16.0 Netclients on Windows Desktops work fine until an egress gateway is added on the local network giving access to their network range. They continue to function over wireguard, but they can no longer make HTTPS or SHH connections to the Netmaker server, or to other nodes running netclient such as a VPS webserver. Disabling the egress gateway or disconnecting the node allows normal comms to continue, e.g. opening the dashboard, connecting to websites on a full client connected webserver, making SSH connections to other nodes using their public IP. The affected nodes cannot make pull requests either, with the timeout error: