On 7 Aug 2013, at 07:51, Dominique Frise <dominique.frise@unil.ch> wrote:
On 08/06/2013 05:29 PM, Alan DeKok wrote:
Dominique Frise wrote:
Is there any other flag/function that would indicate that an Access-Challenge packet was received from the NAS?
A NAS will NEVER send an Access-Challenge to the server.
A proxy will receive an Access-Challenge from a home server. As was said, you need the latest code from the GIT to use that feature.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Did a fresh install from http://github.com/FreeRADIUS/freeradius-server/tree/v2.x.x
./radiusd -v radiusd: FreeRADIUS Version 2.2.1 (git #12be9f6), for host x86_64-unknown-linux-gnu, built on Aug 6 2013 at 21:51:33 Copyright (C) 1999-2013 The FreeRADIUS server project and contributors. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. You may redistribute copies of FreeRADIUS under the terms of the GNU General Public License. For more information about these matters, see the file named COPYRIGHT.
But still no luck :-( --------------------- rad_recv: Access-Challenge packet from host X.X.X.X port 1812, id=101, length=49 Reply-Message = "Enter OTP:" State = 0x38373131 Prompt = No-Echo Proxy-State = 0x313039 # Executing section post-proxy from file /usr/local/etc/raddb/sites-enabled/default +- entering group post-proxy {...} [eap] No pre-existing handler found ++[eap] returns noop ++? if (Response-Packet-Type == Access-Challenge) ? Evaluating (Response-Packet-Type == Access-Challenge) -> FALSE ----------------------
Hmm ok. I thought this was fixed at the same time we allowed modification of Response-Packet-Type. I'll have a look at it. Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team