Support for outbound interface selection about xh HOT 5 CLOSED

All good, the build out of interface-option works exactly as I would expect curl --interface to work. Thanks for the feature!

from xh.

What value would you like to pass to --interface? from cURL docs, I see that it accepts either interface name, IP address or host name.

We can add support for --interface <ip-address> by making use of reqwests's hyper's set_local_address. However, --interface <interface-name> is yet to be supported by hyper-rs. See hyperium/hyper#3076 and seanmonstar/reqwest#1336

from xh.

I am okay with any of those. If I had option to choose I'd go with interface name, but setting the outbound local IP also works for me. iproute2 does have --json output so I can hack some script that I could use like xh --interface $(if-to-ip wg-relay4) .... that would just go over JSON from ip --json address show to figure out what local IP has the given interface, and return the IP.

The GNU wget also only supports binding to IP via --bind-address and have no smarts to specify interface instead, I think this is fully sufficient feature, though in this case perhaps --bind-address makes more sense than --interface as the switch unless you want later to add the interface selection, once those are supported by hyper bindings.

from xh.

I am leaning more towards mimicking cURL and only having the --interface option.

I can hack some script that I could use like xh --interface $(if-to-ip wg-relay4) .... that would just go over JSON from ip --json address show to figure out what local IP has the given interface, and return the IP.

Actually, we could let xh handle the interface to local IP mapping. Of course, this is a temporary solution since some users will sooner or later run into seanmonstar/reqwest#1336.

from xh.

@slashbeast I would like to know if #307 works for your use case (CI is failing due to MSRV policy which we can ignore for now)

$ cargo run -- --interface wg-relay4 https://ipinfo.io/ip

from xh.