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

--bind option doesn't accept interface name #450

Closed
bam80 opened this issue Aug 12, 2016 · 4 comments
Closed

--bind option doesn't accept interface name #450

bam80 opened this issue Aug 12, 2016 · 4 comments

Comments

@bam80
Copy link

bam80 commented Aug 12, 2016

It's more like a feature request, because now I have to write tricky scripts to get IP address of the interface, instead of just passing it by name in the -B option

@bmah888
Copy link
Contributor

bmah888 commented Apr 6, 2017

We note this is a little tricky because an interface can have multiple IPv4/IPv6 addresses and picking the right one might be hard.

@hoang-tranviet
Copy link
Contributor

hoang-tranviet commented Apr 7, 2017

This at least requires getting the right protocol family from specified server (-c). Maybe I did it already in my local branch...

@bam80
Copy link
Author

bam80 commented Apr 8, 2017

Can this feature be implemented at least for the case when an interface has only one IP address? It is far more convenient and straightforward to specify interface by name

@bmah888
Copy link
Contributor

bmah888 commented Dec 22, 2020

This is not likely to happen for reasons I cited above, but #1089 and #1097 are somewhat related to this.

@bmah888 bmah888 closed this as completed Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants