Opened 14 years ago
Closed 11 years ago
#113 closed Bug / Defect ( fixed )
Partially implemented --push-peer-info option
| Reported by: | Samuli Seppänen | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Generic / unclassified | Version: | OpenVPN 2.3-beta / 2.3-RC (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | push-peer-info server |
| Cc: |
Description
The client-side part of
push-peer-info
option is finished and the man-page is updated, but there server-side support is missing.
Change History (3)
comment:1 Changed 12 years ago by
| Keywords: | push-peer-info server added |
|---|
comment:2 Changed 12 years ago by
| Priority: | major → minor |
|---|
This is what partially implemented means (quoting cron2 at #openvpn-devel):
push-peer-info on the server side is ONLY exported to management-interface, not to normal environment, logfile, or client-connect script
Some additional nuggets from
plaisthos
at #openvpn-devel:
It [push-peer-info] sends version, platform, mac of the default gw and all environment variables that begin with UV_ to the server
...and from
cron2
at #openvpn-devel:
Seems ppi is relayed to management interface, and AS will then know "ah, this is iOS client -> can do snappy" (part of the [push-peer-info] patch set is "always send a sub-set of push-peer-info data, even if not explicitely turned on")
comment:3 Changed 11 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The data is now exported to the client via environment variables. Closing.
What exactly does "server-side support is missing" mean?