Jamil
Jamil
Hmm I need to think about this one. I'm not sure it is good to completely detach from upstream here.
> > Hmm I need to think about this one. I'm not sure it is good to completely detach from upstream here. > > Last time we talked about this...
Careful not to spam this - might to limit it to 1x per week.
Just a thought - might be good to have these also in Weekly Report scorecard email. - Gateways out of date - Clients out of date - Metrics - etc
@bmanifold correct
> Looks like non-resource DNS are still resolved correctly when the bug is manifesting It could be because this is a single request-reply that doesn't require holding the port open...
> The bit that I don't understand is why a NAT would do this. There is no reason why traffic originating from the same IP + port going to different...
> We can restore the behaviour prior to #6181 by creating a dedicated UDP socket for DNS queries (see [#6297 (comment)](https://github.com/firezone/firezone/issues/6297#issuecomment-2290031063)). Should we just do that and close this issue...
I'll move #6297 to TODO