[RADIATOR] issue with IPv6 clients via FQDN

[Hugh Irvine]

Hello Heikki, Hello Alan -

Correct.

regards

Hugh


On 26 Aug 2009, at 19:07, Heikki Vatiainen wrote:

> Alan Buxey wrote:
>
>> the addresses were all faked for the post - the IPv4 and IPv6 are  
>> both real
>> global addresses published in DNS
>
> Ok, I believe I have an idea what is happening. This interests me too,
> since we also work with IPv6. I took a look at the code to see how the
> address resolving works.
>
> As far as I can tell, DNS names for Clients are resolved with  
> inet_aton.
> This is an IPv4-only function, so this is the reason I believe the
> Client will only be recognized with its IPv4 address. The knowledge
> about its IPv6 address never gets configured for the newly  
> instantiated
> Client.
>
> -- 
> Heikki Vatiainen, Arch Red Oy
> +358 44 087 6547
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator



NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
Have you checked the RadiusExpert wiki:
http://www.open.com.au/wiki/index.php/Main_Page

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.