Gabi
The first implementation will be naive and simply have this problem, it will be solved with #4789 Ideally, we can add a warning when there are overlapping resources in the...
@AndrewDryga I just realized that now we can get some filters with messages "all", does it still mean that empty filters means allow all or allow none?
> > @AndrewDryga I just realized that now we can get some filters with messages "all", does it still mean that empty filters means allow all or allow none? >...
> I think this is what's causing #4521 -- if DNS mappings fail to be refreshed before TURN credentials expire that would explain this behavior With#4548 we can fix this,...
> @conectado Yeah I think we can maybe save this issue for the explicit case for handling Gateway restarts, which will kill the application-layer connection anyway, so DNS will be...
Hmm why would we need additional functionality on the headless client to support this?
> Also need the ability to allow users to disable Resources, otherwise this can cause unexpected consequences with Policy conditions. > > This can work as follows: > > *...
Listing full list of requirements for this feature: - [ ] #5797 - [ ] #5840 - [ ] #5819 - [ ] #5852 - [ ] `update_resources` FFI to...
> @conectado Yes, the related issue is #4899. I couldn't find a way to make Windows automatically delete the DNS rules when we exit, and this was causing problems when...
I was planning to set this on the `set_resources` call. There are still a few questions. * When do we count a "resource" as connected? When we request and succeed...