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

App "KDEConnect" cannot be allowed/bypassed #1507

Closed
marscher opened this issue Jun 4, 2024 · 5 comments
Closed

App "KDEConnect" cannot be allowed/bypassed #1507

marscher opened this issue Jun 4, 2024 · 5 comments

Comments

@marscher
Copy link

marscher commented Jun 4, 2024

App "KDEConnect" cannot be allowed/bypassed in Rethink.

Symptoms:

  • No connection possible on a local and trusted (within KDEConnect) wifi.
  • "Bypass Universal" + "Bypass app from all Proxies" does not make it possible to connect.
  • "Bypass DNS & Firewall" + "Bypass app from all Proxies" does not make it possible to connect.
  • Adding a "universal firewall" rule to allow (bypass) broadcast traffic to 255.255.255.255

Solution/Workaround:
pause or disable Rethink seamlessly works until re-activation of the firewall.

Desired:
Do not stop/pause the firewall to make local connections.

@ignoramous
Copy link
Collaborator

ignoramous commented Jun 4, 2024

KDE Connect likely uses P2P/LAN? If so, try enabling:

  • Either: Configure -> Network -> Do not route Private IPs.
  • Or: Configure -> Apps -> (search for KDE Connect, tap on it) -> Choose Exclude.

Some prev refs:

@marscher
Copy link
Author

Thanks, excluding private IPs did do the trick.

@alexanderadam
Copy link

I think that there should be some FOSS apps which should be on the exclude list by default or have at least some rules to have them working by default.

What do you think?

@ignoramous
Copy link
Collaborator

Imposing allowlists/whitelists on unsuspecting users is a landmine.

The ones who use apps like KDE Connect or Syncthing already know enough to look for and understand the workarounds, imo.

@alexanderadam
Copy link

The ones who use apps like KDE Connect or Syncthing already know enough to look for and understand the workarounds, imo.

I didn't and I guess the others in this issue as well in #577 or #1159 did neither.

How about a middle ground where the first blocked request of a well-known FOSS app that's logged will cause a notification saying something like "Hey, it looks like you're using $app and we blocked the request for you which will lead to some functions not working." and then having two options "Allow request for $app" "Dismiss and don't ask again".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants