Hi Alan, I did try and re-use the config files. That's how I got the PEAP and MD5 protocols working.
I'm running the same client on a different box and the updated freeradius version on another box as well. That's all that changed. I'm testing a product which is acting as the authenticator and unfortunately my radius knowlegde is quite limited. Thanks for your help. I'll read up on the inner-tunnel configurations and see what I can find there. Thanks. /Matt On Thu, Mar 3, 2011 at 5:24 PM, Alan Buxey <[email protected]> wrote: > Hi, > >> csahwreg4:/users/mboyle/ws/gash_main/testsuites/dot1x[84]> radtest -d >> /users/mboyle/ws/gash_main/testsuites/dot1x/raddbs/default/ testuser >> whatever localhost 1812 testing123 >> Sending Access-Request of id 4 to 127.0.0.1 port 1812 >> User-Name = "testuser" >> User-Password = "whatever" >> NAS-IP-Address = 138.120.210.28 >> NAS-Port = 1812 >> rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=4, length=20 >> csahwreg4:/users/mboyle/ws/gash_main/testsuites/dot1x[85]> > > > ..but that is plain PAP test. recent versions of FreeRADIUS let you query the > inner-tunnel directly too - to ensure that what you are doing works...look > at the inner-tunnel config to see the listening port...then use that instead. > > that might show something. > > ..and why not just clone/copy your working config? > > alan > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
