doesn't work reliably yet in 64bit Win7. So I'm back to trying
to get mschapv2 working with peap. This seems impossible.
On May 30, 2012 2:43 AM, Phil Mayers p.may...@imperial.ac.uk wrote:
On 05/29/2012 10:28 PM, Steve Hopps wrote:
So I'm confused, what's the right way to handle this situation
wrote:
On 30/05/12 13:44, Steve Hopps wrote:
IPhones work with a custom config profile that's easily installed.
However, our most significant hurdle is windows machines. Who would have
guessed??? For some stupid reason Microsoft doesn't care about
supporting all modern encryption standards
. So
thanks for that. :)
On Wed, May 30, 2012 at 8:55 AM, Alan DeKok al...@deployingradius.com wrote:
Steve Hopps wrote:
The reasons you stated are why I think this is near impossible. Our
passwords are stored with md5... I'm not fond of the idea that in
order to get this to work, we have
The only computer in our office which causes certificate errors is a
Windows 7 machine. So I attempted to connect using EAP/TTLS and
MSCHAPv2 using my linux machine and my Android phone. Now I get a
different error.
I also tried using PEAP on my Android phone, and received no
certificate errors.
But according to the configuration file:
# The suffix module takes care of stripping the domain
# (e.g. @example.com) from the User-Name attribute, and the
# next few lines ensure that the request is not proxied.
#
# If you want the inner tunnel request to be
I've got authentication with Android and Linux clients working using
EAP/TTLS and PAP, however Windows and OSX clients dont seem to work.
This is a log of a Windows 7 client. I was able to get iphones working
with a special config, but the same method doesn't seem to work for
OSX. Any help you
I was able to get this working, thanks for all your help everyone
On Mon, May 14, 2012 at 4:51 PM, alan buxey a.l.m.bu...@lboro.ac.uk wrote:
Hi,
Well I've been trying to follow the advice here and also what I've
found online and in the configs. I attempted to revert to the
'default' config
We are using the correct password. There must be something broken
causing the passwords not to match. That is what I'm looking for help
to determine.
On Fri, May 11, 2012 at 3:02 PM, Alan DeKok al...@deployingradius.com wrote:
Steve Hopps wrote:
I'm trying to use FreeRadius with OpenLDAP
+4
Ready to process requests.
On Mon, May 14, 2012 at 9:29 AM, Phil Mayers p.may...@imperial.ac.uk wrote:
On 14/05/12 15:07, Steve Hopps wrote:
We are using the correct password. There must be something broken
causing the passwords not to match. That is what I'm looking for help
to determine
/05/12 15:58, Steve Hopps wrote:
I'll post the full log. It should be pulling from OpenLDAP. I had to
It's not. You haven't configured it to do that.
Module: Instantiating module ldap from file
/etc/freeradius/radiusd.conf
ldap {
server = localhost
port = 389
Ok, you
I'm trying to use FreeRadius with OpenLDAP for authentication of some
Nanostation M2 access points, but have had no luck getting it to work.
When using rad_eap_test to experiment, I logged the following:
Found Auth-Type = PAP
# Executing group from file /etc/freeradius/sites-enabled/inner-tunnel
11 matches
Mail list logo
