-
-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Higher Priority Rules or LAN Exceptions When "Force Block Incoming Connections" is Enabled #1562
Comments
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 issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
Duno but in my opinion this should not be just an "suggestion" |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
This issue has been automatically closed because it has not had recent activity. Thank you for your contributions. If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord. |
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.
The text was updated successfully, but these errors were encountered: