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

Kill Switch and Web UI #3

Open
jmh530 opened this issue Jun 28, 2020 · 5 comments
Open

Kill Switch and Web UI #3

jmh530 opened this issue Jun 28, 2020 · 5 comments

Comments

@jmh530
Copy link

jmh530 commented Jun 28, 2020

I have followed the directions here, but I am not able to access the Web UI for qBittorrent when the kill switch is on.

@danjacques
Copy link
Owner

The instructions specifically target Transmission. I haven't tried setting up qBittorrent. You are able to access the UI when the firewall rules are disabled?

The kill switch rules themselves allow total local access, so the specific client shouldn't be an issue. That said, I don't really have any addition insights to offer other then maybe whack one rule at a time and see which one is causing you problems, then figure out why and report back?

@jmh530
Copy link
Author

jmh530 commented Jun 28, 2020

I used add_fw allow ip from [defaultgatewayip] to [jailip/jailnetmask] 8080 keep-state.

@danjacques
Copy link
Owner

danjacques commented Jun 28, 2020

Interesting. Perhaps qBittorrent binds local and Transmission binds all by default? I'll have to test this theory. I'll add your fix to the notes for future readers.

@jmh530
Copy link
Author

jmh530 commented Jun 28, 2020

Actually the above doesn't work with [defaultgatewayip]. It works with any.

@jmh530
Copy link
Author

jmh530 commented Jun 28, 2020

Not sure if that is safe, I'm not really familiar with ipfw.

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

2 participants