I also just noticed that the feature seems to exist in the 4.0 GUI. Maybe I'll test that as well...
I just tested it in 4.0 and that's affected by the bug as well... I managed to re-produce it 2/2 times with 2m and proxy and sys-net as netvm.
What is interesting:qvm-firewall in dom0 lists a change (i.e. removes the "allow all" rule) after the timer runs out and even in the qubes-vm-settings GUI the checkbox is unchecked again, but the VM still has full Internet access... So whatever timer is there triggers, but the follow-up actions seem to be inappropriate.
Btw in 4.0 "no access" seems to mean that DNS and ICMP is still allowed which seems somewhat weird, but at least it's mentioned in the GUI. So "no access" != "no network access" in 4.0.
-- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to email@example.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7b495527-2b2e-4e20-5e24-a78daae3f924%40hackingthe.net. For more options, visit https://groups.google.com/d/optout.
Description: S/MIME Cryptographic Signature