From: David Sommerseth <dav...@openvpn.net>
The IV_HWADDR description was only partially correct, as there are more
implementations using other values than the MAC address of the default
gateway.
The intention of this value is to provide a unique identifier of the
client and on some platforms this is not possible to retrieve other than
to generate this information.
The 64 bytes limitation is an arbitrary value, it is not enforced by
OpenVPN 2.x. But it was considered a good idea to at least have some
reasonable upper limit of how long this string can be, at least for
those implementing support for this information.
Signed-off-by: David Sommerseth <dav...@openvpn.net>
---
doc/man-sections/server-options.rst | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/doc/man-sections/server-options.rst
b/doc/man-sections/server-options.rst
index 047f2270..b026ac7b 100644
--- a/doc/man-sections/server-options.rst
+++ b/doc/man-sections/server-options.rst
@@ -467,8 +467,13 @@ fast hardware. SSL/TLS authentication must be used in this
mode.
When ``--push-peer-info`` is enabled the additional information consists
of the following data:
- :code:`IV_HWADDR=<mac address>`
- The MAC address of clients default gateway
+ :code:`IV_HWADDR=<string>`
+ This is intended to be a unique and persistent ID of the client.
+ The string value can be any readable ASCII string up to 64 bytes.
+ OpenVPN 2.x and some other implementations use the MAC address of
+ the client's default gateway. If this string is generated by the
+ client, it should be consistent and preserved across independent
+ session and preferably re-installations and upgrades.
:code:`IV_SSL=<version string>`
The ssl version used by the client, e.g.
--
2.27.0
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
