Re: freeradius retransmit of EAP-TTLS start packet with incorrect packet id

2012-11-20 Thread Phil Mayers
On 19/11/12 16:27, Alan DeKok wrote: There are patches going into 3.0 which will detect RADIUS retransmits over multiple proxy hops. That is a rare case, but more likely in the case of eduroam. Fixing it is good. Ooh, really? What solution did you hit on? - List

Re: freeradius retransmit of EAP-TTLS start packet with incorrect packet id

2012-11-20 Thread Alan DeKok
Phil Mayers wrote: Ooh, really? What solution did you hit on? Cache reply by State. authorize { cached_reply ... } post-auth { ... cached_reply } It returns handled in the authorize section if it finds a matching State. On authorize it does:

freeradius retransmit of EAP-TTLS start packet with incorrect packet id

2012-11-19 Thread list
Hi, I am still waiting on the freeradius logs from the customer experiencing this problem, but I was wondering if anyone had ever seen the following before or have any ideas what may be causing it: 1. EAP-TTLS client sends the EAP-Identity (packet id 2) 2. EAP-TTLS client receives the

Re: freeradius retransmit of EAP-TTLS start packet with incorrect packet id

2012-11-19 Thread Alan DeKok
l...@securew2.com wrote: Furthermore this does not happen all the time leading me to believe this might be a retransmit issue between the access point and freeradius, maybe during high load. That's likely. And since it's EAP retransmit after a long time, odds are that the RADIUS packet

Re: freeradius retransmit of EAP-TTLS start packet with incorrect packet id

2012-11-19 Thread list
Hi Alan, it still seems strange that it would respond with a packet id that was never sent by the client. I guess this could only happen if the AP somehow thought it should retransmit the identity request. I am hoping the radius server logs will help so i can see the missing packet causing

Re: freeradius retransmit of EAP-TTLS start packet with incorrect packet id

2012-11-19 Thread Alan DeKok
l...@securew2.com wrote: it still seems strange that it would respond with a packet id that was never sent by the client. I guess this could only happen if the AP somehow thought it should retransmit the identity request. Yes, maybe. I am hoping the radius server logs will help so i can