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

command line option to bind to specific network interface #778

Closed
allefeld opened this issue Aug 15, 2016 · 3 comments
Closed

command line option to bind to specific network interface #778

allefeld opened this issue Aug 15, 2016 · 3 comments

Comments

@allefeld
Copy link

What version of WebTorrent Desktop? (See the 'About WebTorrent' menu)
Version 0.10.0 (0.96.0)

What operating system and version?
Linux 3.16.0 (Debian 8.5)

This is not a bug report, but a feature request.

Please include a command line option (not just a preference, to be scriptable) to bind WebTorrent Desktop to a specific network interface. Like the -i --bind-address-ipv4 and -I --bind-address-ipv6 options of transmission-daemon.

@feross
Copy link
Member

feross commented Aug 18, 2016

I'm not sure I understand why this needs to be a command line option. None of the other options in WebTorrent Desktop are currently exposed via a command line option. How are you using WebTorrent Desktop in a script? Can webtorrent-cli work for you?

@allefeld
Copy link
Author

@feross, the reason is that the interface is not always the same one, and reconfiguring manually is tedious. So I'd like to write a shell script wrapper that figures out the interface and then starts WebTorrent Desktop.
webtorrent-cli, maybe, I'll check it out. Thanks!

@feross
Copy link
Member

feross commented Aug 19, 2016

Thanks for explaining. If you're interested in sending a PR for this, I'll take a look at it. But I think this kind of advanced feature probably should be added to webtorrent-cli.

@feross feross closed this as completed Aug 19, 2016
@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants