Re: [RADIATOR] Alvarion Breezemax & Radiator

2017-06-07 Thread Tuure Vartiainen
Hi,

> On 7 Jun 2017, at 16.27, Michael Tipton  wrote:
> 
> And here is the telrad configs that they provided. 
> 

both logs you sent only contain retransmissions of 
a same EAP-Identity response (in a packet dump the line "EAP-Message = 
<2><1>username” which is the first RADIUS Access-Request in EAP 
authentications) so either your NAS is not receiving 
replies or it ignores them.


BR
-- 
Tuure Vartiainen 

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.

___
radiator mailing list
radiator@lists.open.com.au
http://lists.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Alvarion Breezemax & Radiator

2017-06-07 Thread Michael Tipton
And here is the telrad configs that they provided.


telrad_provided.log
Description: Binary data


telradprovided.cfg
Description: Binary data
___
radiator mailing list
radiator@lists.open.com.au
http://lists.open.com.au/mailman/listinfo/radiator

Re: [RADIATOR] Alvarion Breezemax & Radiator

2017-06-05 Thread Tuure Vartiainen
Hello,

> On 5 Jun 2017, at 17.28, Michael Tipton  wrote:
> 
> I have been trying to get radiator to work with Alavarion Breezemax 3000 
> series wimax CPEs, but have not had any success in even getting a TTLS tunnel 
> established. 
> 
> The CPEs are configured to use EAP-TTLS for phase 1 and MSCHAPv2 for phase 2. 
> 
> I am trying to get it to work with a flat file, I found the following via the 
> mailing list and google 
> https://lists.open.com.au/pipermail/radiator/2009-December/015946.html
> 
> ​It looks like from this freeradius mailing list post that Alavarion violated 
> the wimax specifications. 
> ​http://lists.freeradius.org/pipermail/freeradius-users/2011-October/056593.html
> 
> ​That did not seem to function either in opening the TTLS tunnel. I then 
> engaged Telrad who apparently bought out Alavarion. They were able to provide 
> with with the last known config that worked for them using RAdmin.
> 
> I edited it to make it work with a flat file, but even that failed to 
> establish the TTLS tunnel. 
> 
> Our customer is currently using freeradius and I have had a hard time 
> converting them over to radiator to work with our systems. 
> 

please see an example config goodies/eap_ttls.cfg which comes with Radiator, 
it should work just fine and gives you a good starting point.

> I've attached the configs I've tried with no success and well as the trace 
> logs. ​Any help would be greatly appreciated. I have tried several changes of 
> each to no avail. 
> 

At least the mail which came to the list didn’t include any config nor a trace 
log?


BR
-- 
Tuure Vartiainen 

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.

___
radiator mailing list
radiator@lists.open.com.au
http://lists.open.com.au/mailman/listinfo/radiator