#371 closed Bug / Defect (notabug)
manpage speaks of the ifconfig tool
Reported by: | kcodyjr | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | |
Component: | Generic / unclassified | Version: | OpenVPN 2.3.2 (Community Ed) |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
Cc: |
Description
As I've just been pyroclastically informed in #openvpn, this tool is so thoroughly deprecated that anyone still having latent nostalgic thoughts of it should be chastised and castigated until they stop demanding evidence of its deprecation, and simply accept that the wisdom of their overlord is beyond their understanding.
Despite this, the manpage mentions that a recent ifconfig tool is required for subnet mode to work properly.
Please resolve the inconsistency and either repair the manpage, or pekster.
Note: See
TracTickets for help on using
tickets.
OpenVPN is multi-platform. ifconfig is current on BSD, Solaris, and others. Linux has deprecated most of net-tools in favor of iproute2, but in favor of general support of both non-Linux and very-outdated Linux, ifconfig support remains.
This said, even the 2.2/2.4 kernel methods ifconfig provides generally work for OpenVPN; features such as true secondary IPs on interfaces aren't supported (directly) by OpenVPN and are a non-issue. Old tooling therefore continues to be supported. iproute2 is available as a compile-time option.
Do note that it is currently impossible to change the runtime path to the ifconfig binary (a recompile is needed.) iproute2-enabled builds have a runtime flag to change this. Beyond this, the OpenVPN support for both remains functionally identical.