Jamil
Jamil
`expire_flows` is what ends up pushing `reject_access` down (I am working to clean all of these up) ```elixir # Resource is updated, eg. traffic filters are changed def handle_info({:update_resource, resource_id},...
This might be a case of the gateway missing the `reject_access` message then?
I know what happened here. Might be better to discuss in realtime.
This may not be an immediate issue, since I believe the correct behavior still happened regardless of the ordering of the `update_resource` and `expire_flows` message here. See https://firezonehq.slack.com/archives/C04HRQTFY0Z/p1749016177340049
Fixed by moving the remaining message broadcasts to the ordered stream. This was just a bug due to being in limbo between the old and new side effect system.
This is reproducible for me on Windows 10: 1. Connect Firezone 2. Update the DNS server of the primary interface adapter to manual, set it to 1.1.1.1 3. Observe all...
Logs from the above session [firezone_logs_2025_06_05-04-52.zip](https://github.com/user-attachments/files/20602717/firezone_logs_2025_06_05-04-52.zip)
``` Edition Windows 10 Pro Version 22H2 Installed on 1/30/2025 OS build 19045.5917 Experience Windows Feature Experience Pack 1000.19061.1000.0 ```
Can't seem to reproduce the above on Windows 11 Pro.
[firezone_logs_2025_06_05-07-12.zip](https://github.com/user-attachments/files/20604697/firezone_logs_2025_06_05-07-12.zip)