Re: Any interoperability issues with Aruba and Freeradius

2013-02-10 Thread Alex Sharaz
Thanks for this one Alan, fixes one of my outstanding issues Rgds Alex Sent from my iPhone On 8 Feb 2013, at 17:59, a.l.m.bu...@lboro.ac.uk wrote: Hi, * there is one problem that FreeRADIUS doesn't return the inner ID into the outer one when using EAP-TTLS (but does when using EAP-PEAP),

Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread Alex Sharaz
Hi All, I'm sure the answer to this is nope, but ... At a recent Aruba training course in amongst the documentation supplied to us were a couple of presentation slides showing different types of eap authentication against recommended RADIUS servers for use with Aruba equipment (Just to be

Re: Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread Alan DeKok
Alex Sharaz wrote: At a recent Aruba training course in amongst the documentation supplied to us were a couple of presentation slides showing different types of eap authentication against recommended RADIUS servers for use with Aruba equipment (Just to be sure the slide heading said Aruba

Re: Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread Phil Mayers
On 08/02/13 16:19, Alan DeKok wrote: If it requires tweaking for Aruba, then Aruba has failed to implement the standards correctly. Was it Aruba who we had all the issues with terminating PEAP/TTLS locally on the controller, then transforming the inner EAP-MSCHAPv2 to plain MSCHAPv2 and

Re: Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread Alex Sharaz
Aruba now say they only support eap-tls and eap-peap when you offload eap onto their mobility controllers. Rgds Alex On 8 Feb 2013, at 16:46, freeradius-users-requ...@lists.freeradius.org wrote: Re: Any interoperability issues with Aruba and Freeradius - List info/subscribe/unsubscribe? See

Re: Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread Alan DeKok
Alex Sharaz wrote: Aruba now say they only support eap-tls and eap-peap when you offload eap onto their mobility controllers. That is a stupid response from them. If they follow the specs, they should pass EAP straight through to the RADIUS server. If they do anything else, they are

Re: Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread Alex Sharaz
I have to say that in their defence, the eap offloading is switched off by default and you do actually have to switch it on. A On 8 Feb 2013, at 17:27, Alan DeKok al...@deployingradius.com wrote: Alex Sharaz wrote: Aruba now say they only support eap-tls and eap-peap when you offload eap onto

Re: Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread Alex Sharaz
* there is one problem that FreeRADIUS doesn't return the inner ID into the outer one when using EAP-TTLS (but does when using EAP-PEAP), but this is nothing Aruba-specific and probably a configuration error in FreeRADIUS on our part. I've got a strange thing here as well. In the

Re: Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread A . L . M . Buxey
Hi, * there is one problem that FreeRADIUS doesn't return the inner ID into the outer one when using EAP-TTLS (but does when using EAP-PEAP), but this is nothing Aruba-specific and probably a configuration error in FreeRADIUS on our part. stick something like this into your 'inner-tunnel

Re: Any interoperability issues with Aruba and Freeradius

2013-02-08 Thread Phil Mayers
On 08/02/13 17:14, Alex Sharaz wrote: Aruba now say they only support eap-tls and eap-peap when you offload eap onto their mobility controllers. Well, don't do offload - it's a pretty bad idea anyway, and vendors have a history of mangling it. - List info/subscribe/unsubscribe? See