-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/07/16 13:53, Rafael Gava wrote:
[...snip...]
> Your request not to use 'localhost' is ok. So I changed
> 'client-ip'. But since we have so many clients already configured
> with the 'localhost' keyword, we would like to gradually make the
> tran
Hi Arne,
I left both options available, at least for now. Either 'client-ip', or
'localhost' as an undocumented alias.
This patch to 'client-nat' is necessary to allow it to work properly on a
Windows client (not necessary on Linux) of client/server configuration when
server issues OVPN DHCP add
Am 05.07.16 um 15:13 schrieb Rafael Gava:
> Hi Arne, sorry for replying so late.
>
> Below is the NAT client-ip patch fixing the messed up whitespaces.
> The only difference from the previous patch, besides the whitespaces,
> is that I'm considering both strings 'client-ip' and 'localhost' as
>
Hi Arne, sorry for replying so late.
Below is the NAT client-ip patch fixing the messed up whitespaces.
The only difference from the previous patch, besides the whitespaces, is
that I'm considering both strings 'client-ip' and 'localhost' as valid
options.
Please, whatever problem let me know.
B
Reapplying client-ip NAT patch fixing the following issues raised by Arne
Schwabe:
- Fixing TABs and whitespaces;
- Added comments to the Client IP Marker.
Thanks
Rafael
>From 6bc85f6ef89f27771c48e1e6d837302d5dad0910 Mon Sep 17 00:00:00 2001
From: vntraol
List-Post: openvpn-d
Am 28.04.16 um 04:01 schrieb Rafael Gava:
> Hi Arne,
>
> what a surprise I thought that the NAT patch had been dropped. :-)
More or less forgotten. IIrc the active FTP part was controversal. This
part is okay.
> So, please, should I change the code based on your comments and resend
> the patch?
>
> + if (network && !strcmp(network, "client-ip"))
> +{
> + msg (M_INFO, "*** client-nat client-ip detected...");
> + e.network = 0x;
> +} else {
I am not sure that this message is useful. It does not provide any
additional information to the user. Also please add a
Allow the user to use the string 'client-ip' on the client-nat network
configuration as a convenient way to use the leased IP address received
from OpenVPN server. Usage Example:
client-nat snat client-ip 255.255.255.255 172.20.1.15 # replaces the
'client-ip' string with the leased IP address re
