curl/docs/cmdline-opts/interface.d

Long: interface
Arg: <name>
Help: Use network INTERFACE (or address)
See-also: dns-interface
---

Perform an operation using a specified interface. You can enter interface
name, IP address or host name. An example could look like:

 curl --interface eth0:1 https://www.example.com/

If this option is used several times, the last one will be used.

On Linux it can be used to specify a VRF, but the binary needs to either
have CAP_NET_RAW or to be ran as root. More information about Linux VRF:
https://www.kernel.org/doc/Documentation/networking/vrf.txt
cmdline-docs: more options converted over 2016-11-15 17:44:58 -05:00			`Long: interface`
			`Arg: <name>`
			`Help: Use network INTERFACE (or address)`
			`See-also: dns-interface`
			`---`

			`Perform an operation using a specified interface. You can enter interface`
			`name, IP address or host name. An example could look like:`

			`curl --interface eth0:1 https://www.example.com/`

			`If this option is used several times, the last one will be used.`
--interface: add support for Linux VRF The --interface command (CURLOPT_INTERFACE option) already uses SO_BINDTODEVICE on Linux, but it tries to parse it as an interface or IP address first, which fails in case the user passes a VRF. Try to use the socket option immediately and parse it as a fallback instead. Update the documentation to mention this feature, and that it requires the binary to be ran by root or with CAP_NET_RAW capabilities for this to work. Closes #2024 2017-10-26 14:42:55 -04:00
			`On Linux it can be used to specify a VRF, but the binary needs to either`
			`have CAP_NET_RAW or to be ran as root. More information about Linux VRF:`
			`https://www.kernel.org/doc/Documentation/networking/vrf.txt`