Thanks Nikos. I patched 0.10.4 with git master code, but
NAS-IP-Address recorded on radius is still the private one.
BTW, I encountered below error when building binary, not sure if I was
wrong, I solved this problem by changing it to ws->dtls_session.
worker-vpn.c:674:44: error: session undeclared (first use in this function)
ws->conn_mtu = gnutls_dtls_get_data_mtu(session);
^
Regards,
Di
On Sat, May 9, 2015 at 3:39 AM, Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote:
> On Thu, 2015-05-07 at 22:55 +0800, Teki Ri wrote:
>> Hi Nikos,
>>
>> My ocserv server is running on a Amazon EC2 instance, as you may know
>> EC2 instances have 2 kind of IP address assigned, private IP and
>> public IP. Commands executed from inside the OS such as ifconfig just
>> return the private IP, on the other hand when you communicate with the
>> internet, the public IP will be used. The NAS-IP-Address info of
>> radius account data received from ocserv is always the private IP, but
>> this NAS-IP-Address sending from other VPN services such as PPTP or
>> L2TP is always the public IP.
>
> It seems that the NAS-IP-Address was set by freeradius-client itself
> using the IP used to connect with the radius server. I have some
> untested patch in git master if you want to try.
>
> regards,
> Nikos
>
>
