Panagiotis Georgopoulos wrote:
a) Why am I seeing in my radius –X output lines as the following :
[unix] IPv6 is not supported!
The "unix" module stores user login information into a "wtmp" style file. It doesn't support IPv6.
rlm_radutmp: IPv6 not supported!
Same thing here. It stores user login information into a "utmp" style file. It doesn't support IPv6.
What could trigger that “IPv6 is not supported” output? Is there something that might be going wrong, because clients get authenticated successfully as far as I can tell but I am afraid that something else might be broken.
If you don't use "radlast" and "radwho", you can delete the "unix" and "radutmp" entries from the "accounting" section. Nothing else will be affected.
b) My FreeRadius machine has “an easy to remember” IPv6 address e.g. 2001:a::1 and NAS clients are using this to send packets to FR. However it seems that FR is configuring another IPv6 address from the router advertisements that it gets from the access network.
No. FreeRADIUS doesn't configure IPv6 addresses. Your OS does.
The problem is that when this happens FR replies to NAS with packets coming from the autoconfigured address as source and thus breaks the setup as NAS are waiting packets from 2001:a::1. Is there a way to force FR to generate packets coming from the manually configured IP (2001:a::1) ?
Update the "listen" section to bind to that specific IP.
c) Is there a plan to get a dual stack FreeRadius? It would be really advantageous to be able to run FreeRadius in both ipv4 and ipv6 at the same time.
Uh... it's *already* dual stack. You are running it dual stack right now. Alan DeKok.