Qube firewall traffic blocked when resolving hostname in "Firewall rules" fails #7499
Labels
affects-4.1
This issue affects Qubes OS 4.1.
affects-4.2
This issue affects Qubes OS 4.2.
C: networking
needs diagnosis
Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed.
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
ux
User experience
Qubes OS release
Qubes 4.1
Brief summary
If one hostname which is defined under "Firewall Rules" fails to resolve, the network is not accessible. All network traffic is blocked, even when using an IP. The packets are filtered by (according to "ping" output) the "Net qube".
It does not matter if "Allow all outgoing connections", "Limit outgoing connections to..." or "Allow full access for ,,," is selected.
Steps to reproduce
At least one hostname is specified as "Address" under "Firewall Rules" and such a hostname cannot be resolved
Expected behavior
Upon launching the Qube a notification is displayed for each hostname that cannot be resolved (alternative: "multiple hostnames cannot be resolved" instead of single hostname).
The network remains accessible, the failed hostname obviously not.
Actual behavior
Upon launching the Qube a notification is displayed for the first hostname that cannot be resolved. This notification will show only once even if multiple hostnames fail.
It does not matter if "Allow all outgoing connections", "Limit outgoing connections to..." or "Allow full access for ..." is selected: all network connections are blocked.
The text was updated successfully, but these errors were encountered: