Open n0one42 opened 4 weeks ago
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
This is how I temporarily resolved it. Or instead of LAN I could define 192.168.122.0/24
which is the default libvirt range.
Affected Rules:
Description:
I am using Portmaster as my main tool for DNS and firewall management on my system. However, I encountered an issue where enabling "Force Block Incoming Connections" blocks incoming traffic necessary for
dnsmasq
andlibvirt
to function properly. This setting currently has higher priority than any custom rules, making it impossible to allow the required traffic without disabling the feature entirely.Steps to Reproduce:
libvirt
with a virtual network usingdnsmasq
.Expected Behavior: There should be a way to create higher priority rules or exceptions for LAN connections that allow necessary traffic for specific services like
dnsmasq
andlibvirt
while still blocking other unwanted incoming connections.Current Behavior: Currently, any rules set to allow this traffic are overridden by the "Force Block Incoming Connections" setting, making it impossible to enable the necessary traffic for
dnsmasq
andlibvirt
without disabling this setting entirely.Proposed Solution:
Conclusion: Implementing one of the proposed solutions will enhance Portmaster's usability by allowing users to maintain strict control over incoming connections while ensuring necessary services can operate without interruption.
Thank you for considering this suggestion. I am happy to provide further information or testing if required.