> Richard,
>
> Thanks for that input, it sounds very straightforward to me. I'll try
> your patches on Tuesday (Monday is a holiday here). Have you brought
> this up with Cisco? If not, I will open a case next week. I'd like to
> know whether Cisco's leap/eap developers intended for the ID to not
> increment-- or whether they've made a mistake against their own
> standard.
>
Ok, nice if you open a case to Cisco. Their leap-software of WLSE is buggy,
(not the same as their access points) :-)
> I'd like to use the same freeradius server for WLSE/APs as for other
> non-LEAP clients, such as TLS/PEAP. Since your patch to rlm_eap.c
> should only kick in when reply->type.type == PW_EAP_LEAP, there should
> be no problem, wouldn't you say?
>
Ok, if you have only non-LEAP clients. But you need to path every new relese of
freeradius you need...
Bests regards.
+--------------------------------------+
| ??? |
| {O-O} Richard Timsit |
| ^_ SIC STI |
| / T \_ EPFL Lausanne |
| '` I " 1015 Ecublens,SUISSE |
| M (021) 693 22 35 |
| | | [EMAIL PROTECTED] |
| I I |
+--------------------------------------+
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
