On Fri, Jan 20, 2012 at 12:18 PM, Alan DeKok <aland@deployingradius.com> wrote:
Oscar Remírez de Ganuza Satrústegui wrote:
> I am having some problems using huntgroups to identified the origin of a
> request.
> I have simplified the test trying to find out the problem, but I do not
> understand what it is happening:
> (The "notworking log" is appended at the end of the message. I had toIt would have been better to follow the instruction in the FAQ,
> trim it to make it shorter)
README, "man" page, web pages, and daily on this list: "radiusd -X".
Using "radiusd -xX" produces 2x the output, and is NOT needed.
Because it's checking the user *inside* of the TLS tunnel. Go read
> I can see in the "not working log" that on the first requests the
> huntgroup is been recognised ok. I just do not understand why it tries
> again to check it, until it fails (request #9).
raddb/sites-available/inner-tunnel. You will probably need to modify
your huntgroup check.
That's how 802.1X works. It sends lots of packets.
> I also do not understand why it needs so many requests (12!) to work ok.
Alan DeKok.