Thank you all for your help. I added two more listen blocks in radiusd.conf and I updated detail { ... with the following: %{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}} and it works but ..... (there's always a but). if we use an IPv6 address, then Packet-Src-APv6-Address value will be, for instance, 0:0:0:0:0:0:0:0, and the path becomes : ${radacctdir}/0:0:0:0:0:0:0:0/detail-%Y%m%d.log but FR crashes since it cannot create a folder with that name. Is there any way of overcoming this issue? replace : with . or so??? Thanks again for your help. Sergio.
Date: Mon, 31 Oct 2011 08:52:46 +0000 From: A.L.M.Buxey@lboro.ac.uk To: freeradius-users@lists.freeradius.org Subject: Re: IPv6 ready?
Hi,
Just wondering if FR supports IPv6 addresses since I'm unable to start the server when using IPv6.
yes. we use it fine with IPv6 - both receiving and sending RADIUS packets.
Another question is: are you aware of any (client) tool for testing FR when using IPv6 addresses? eapol_test doesn't seem to know anything about :: or ::1
eapol_test - use hostnames (eg in /etc/hosts ?) ?
Do the below lines from radiusd.conf require any change when IPv6?
... ... detail { detailfile = ${radacctdir}/%{Client-IP-Address}/detail-%Y%m%d.log
yes, Client-IP-Address doesnt exist in IPv6 world - you can use one of the source address attributes instead
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html