Alex Feiszli

We do not currently have any logic to check if IP behind an FQDN changes, though it makes sense to implement something for this.

yes, this is fixed specifically for 0.0.0.0/0. When you add egress with 0.0.0.0/0, the route will not be added to the server.

This is a known issue in 0.14.4, egress behind relay is currently non-functional. We are working to have this fixed in 0.14.5.

Closing as per #1443

Is this perhaps an issue with 2012 compatibility? that's a rather old system. We only test on Windows 10/11. Also, new certificates only get added if the connection fails as...

I dont think we're going to be spending much time on 2012 compatibility, it's a bit out of scope for us. Have you tested on a newer system and seen...

Closing, since issue was resolved

The issue with our previous implementation is, it would only work for linux devices with systemd-resolve installed. It did not work for windows, mac, and a subset of linux devices....

Hi @schmorrison, trying to understand your diagram more fully, is the extent of the issue just the 1 ext client (with red line) unable to access 1 egress gateway (other...

Hi @schmorrison are you still experiencing this issue? Ext clients should get all egress gateways in their AllowedIPs