I updated my ippool table to increase the length of the varchar. Then I set the Pool-Name attribute to an IPv6 pool. I set up this in mysql base: radcheck 6 | testadsl-sagem-ds-1 | Pool-Name | := | poolipv6 radippool 5 | poolipv6 | 2a0a:8e80:0400:0202::/64 | | | | NULL | | | | 6 | poolipv6 | 2a0a:8e80:0400:0203::/64 | | | | NULL | | | | 7 | poolipv6 | 2a0a:8e80:0400:0204::/64 | | | | NULL | | | | 8 | poolipv6 | 2a0a:8e80:0400:0205::/64 | | | | NULL | | | But I got this result [sqlippool] Invalid IP number [2a0a:8e80:0400:0202::/64] returned from database query. Should I change the Pool-Name attribute ? Is there a attribute trigger for IPv6?
William DELORAINE wrote:
I updated my ippool table to increase the length of the varchar.
Then I set the Pool-Name attribute to an IPv6 pool. ... [sqlippool] Invalid IP number [2a0a:8e80:0400:0202::/64] returned from database query.
OK. The module checks if the returned data is an IPv4 address. That can be fixed. But also: [2a0a:8e80:0400:0202::/64] isn't a valid IPv6 address. That's a prefix. If you're familiar with C, you can try editing the rlm_sqlippool source. All it needs is: - a check to allow the returned IP to be AF_INET6 - creation of a Framed-IPv6-Address attribute, instead of a Framed-IPv4-Address. Alan DeKok.
participants (2)
-
Alan DeKok -
William DELORAINE