Stefan Winter wrote:
Hm, while you're at it: I also added
MS-MPPE-Recv-Key =* ANY,
MS-MPPE-Send-Key =* ANY,
MS-CHAP-MPPE-Keys =* ANY,
because Wireless LAN encryption keying material often accompanies EAP
requests
in these attributes. Is that another candidate?
But I would like to suggest to add at least EAP-Message and State in the
default attrs file that's shipped. This was really an ugly caveat.
Fixed, thanks.
Hm, while you're at it: I also added
MS-MPPE-Recv-Key =* ANY,
MS-MPPE-Send-Key =* ANY,
MS-CHAP-MPPE-Keys =*
Hi Alan,
Where's the State attribute? It's *required* to be there for EAP to
work. Either the client is dropping State, or one of the proxies is
dropping it.
All in all, I think one of the proxies is broken. If it's Radiator,
discuss it with them, and we can hash it out.
Actually,
Stefan Winter wrote:
Problem is: the shipped $raddbdir/attrs file strips off EAP conversations
completely, so I had to edit it to allow EAP-Message to go through. While
doing that, I forgot the State attribute (and wasn't even aware that it is so
crucial; time for a little RTFRFC). Now
4 matches
Mail list logo
