IPv6 subnet as client ipaddr
Hi, we just wanted to configure an IPv6 subnet as client with the variable ipaddr. Found out that only a single IPv6 IP address is working with the variable ipaddr. With ipv6addr subnet is working, too. Does not work: client test { ipaddr = fd76:70:6e:1::/64 secret = XXXXXXXXXXXXXXXXXXXXXXXXX } Does work: client test { ipaddr = fd76:70:6e:1::1 secret = XXXXXXXXXXXXXXXXXXXXXXXXX } Does work: client test { ipv6addr = fd76:70:6e:1::/64 secret = XXXXXXXXXXXXXXXXXXXXXXXXX } Error log message: Failed to parse IPv4 address string "fd76:70:6e:1::/64" /etc/freeradius/3.0/clients.conf[270]: Error parsing client section Is it a bug? Tested in freeradius 3.0.12 and 3.0.16. Same behaviour. Thank you Klara
On Feb 12, 2018, at 5:00 PM, Klara Mall <klara.mall@kit.edu> wrote:
we just wanted to configure an IPv6 subnet as client with the variable ipaddr. Found out that only a single IPv6 IP address is working with the variable ipaddr. With ipv6addr subnet is working, too.
Does not work:
client test { ipaddr = fd76:70:6e:1::/64
The "ipaddr" is intended to be used mainly for hostname lookups. As a result, it's not overly good at parsing raw IPv6 addresses.
secret = XXXXXXXXXXXXXXXXXXXXXXXXX }
Does work:
client test { ipaddr = fd76:70:6e:1::1
That's just an IPv6 address...
Does work:
client test { ipv6addr = fd76:70:6e:1::/64
i.e. when you force it to be IPv6, it works.
Error log message: Failed to parse IPv4 address string "fd76:70:6e:1::/64" /etc/freeradius/3.0/clients.conf[270]: Error parsing client section
Is it a bug? Tested in freeradius 3.0.12 and 3.0.16. Same behaviour.
It's a bug. I've pushed a fix for the v3.0.x, which should be in the 3.0.17 release. Alan DeKok.
participants (2)
-
Alan DeKok -
Klara Mall