Skip to content
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

[Suggestion] Notification that an incoming connection was blocked #1350

Closed
soleofthesea opened this issue Oct 22, 2023 · 2 comments
Closed
Labels
suggestion TYPE: idea for new feature or improvements

Comments

@soleofthesea
Copy link

I will admit this is mostly me being dumb and forgetting I have a firewall enabled, but I think not only will this be a good QoL improvement, it'll also help in instances where users were incorrect about how the program works.
I spent way too long figuring out why Android debug bridge was hanging before discovering that Portmaster blocks localhost incoming by default and that 'allow LAN' doesn't include localhost.

@soleofthesea soleofthesea added the suggestion TYPE: idea for new feature or improvements label Oct 22, 2023
@github-actions
Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

@Raphty
Copy link
Member

Raphty commented Oct 23, 2023

There would have to be a smart filter applied because so nanny connections are inbound which are just junk, and getting a notification for each would get annoying super fast.
And most people don't need any Incoming connections

I get that an alert for specific connections would be great, but implementing this will be a lot of work and the benefits for most people is low.

@Raphty Raphty closed this as not planned Won't fix, can't repro, duplicate, stale Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion TYPE: idea for new feature or improvements
Projects
None yet
Development

No branches or pull requests

2 participants