Re: (RADIATOR) 802.1x Authentication Unsuccessful - Could not find a handler for...

2003-10-04 Thread Hugh Irvine
Hello Terry - You are correct, in many situations a single Handler is fine. The reason there are two options is because some people want to process the outer authentication in one fashion (usually a simple file), and the inner authentication with something like an SQL or LDAP database. The Rad

Re: (RADIATOR) 802.1x Authentication Unsuccessful - Could not find a handler for...

2003-10-04 Thread Terry Simons
I actually tried it with *just* the clause, and it worked... so apparently the "TunneledByTTLS=1" portion isn't required... Should I be using both handler portions? If so, why? It seems really redundant to do things that way, and it is somewhat confusing. I'm just trying to understand what's

Re: (RADIATOR) 802.1x Authentication Unsuccessful - Could not find a handler for...

2003-10-03 Thread Hugh Irvine
Hello Terry - You will need to have two Handlers in your configuration file: Foreground LogStdout LogDir /usr/local/var/log/radius.log LogFile %L/logfile DbDir /usr/local/etc Trace 4 AuthPort 1812 AcctPort 1813 NoIgnoreDuplicates Access-Challenge

(RADIATOR) 802.1x Authentication Unsuccessful - Could not find a handler for...

2003-10-03 Thread Terry Simons
Mike, I stripped my configuration down to a bare-bones one, and I'm still having the issue I mentioned before (listed at the bottom of this E-mail) I've also done the following: Upgraded to Radiator 3.7.1 w/patches as of October 3 2003. Using D-Link DWL 900AP+, which worked with Radiator 3.6