Hi All,
PostAuthHook to replace the default Tunnel-Private-Group-ID in the
reply-packet with the generated ID now runs OK.
I placed the PostAuthHook after the AuthBy clause in the handler for the
outer tunnel. A first glance learns that it works.
But we assume that a re-authentication - for whate
On 12/20/2010 05:25 PM, Patrick Renkens wrote:
> PostAuthHook to replace the default Tunnel-Private-Group-ID in the
> reply-packet with the generated ID now runs OK.
>
> I placed the PostAuthHook after the AuthBy clause in the handler for the
> outer tunnel. A first glance learns that it works.
>
Seeing this thread, I was reminded that I had once submitted a desired patch,
but not sure it was ever implemented (?).
http://www.open.com.au/pipermail/radiator/2007-June/014065.html
It was to resolve my issue with Clients (routers) with multiple A records and
the fact that Client's addresses
