[RADIATOR] ipv6::: bind results in no match on IPv4 client

[Mueller, Jason C]

Heikki,

> When BindAddress is set to ipv6::: and request comes in from an IPv4
> address 172.20.3.170 you'll get this in the logs:
> 
> DEBUG: client_addr:
> <0><0><0><0><0><0><0><0><0><0><255><255><172><20><3><170>
> 
> When BindAddress is commented out and defaults to IPv4 0.0.0.0 you'll
> get this in the logs when using the same client 172.20.3.170
> 
> DEBUG: client_addr: <172><20><3><170>
> 
> The former needs:
> <Client ipv6:::ffff:172.20.3.170>
> 
> and the latter can be caught with
> 
> <Client 172.20.3.170>

I am still using ipv6:::, since I have not yet convinced system administrators to change the bindv6only attribute to 1.

The example above (which a couple of others also suggested) works for a single address (i.e., ipv6:::ffff:128.255.90.90). However, it does not look like you support CIDR notation for IPv6, which you do support for IPv4. I need the support of CIDR notation to avoid putting in many hundreds of client entries.

Here is what comes in from the logs:
Fri Jun 28 07:01:46 2013: ERR: Could not resolve address ipv6:2620:0:e50:100::/64 for Client ipv6:2620:0:e50:100::/64
Fri Jun 28 07:01:46 2013: ERR: Could not resolve address ipv6:::ffff:128.255.100.0/120 for Client ipv6:::ffff:128.255.100.0/120

The first line above is an error for a standard /64 IPv6 subnet.
The second line above shows an error for an IPv6 representation of the IPv4 address range of 128.255.100.0/24 subnet.

Any help is appreciated.

-Jason