On 17/11/10 12:31, hans.bornem...@tu-dortmund.de wrote:
Hi,
I have 2 freeradius server: 1 as proxy server, 1 as authentication
server. Everything is working fine (Auth. for WPA2, MSCHAPv2 ) until I
implement the postproxy function:
Post the debugging output, as advised frequently on this list:
radiusd -X | tee log
post-proxy {
post_proxy_log
#attr_rewrite
attr_filter.post-proxy
You're probably filtering the EAP-Message and other required attributes out
/etc/freeradius/attrs:
tu-dortmund.de
Tunnel-Private-Group-ID :=8,
Fall-Through = Yes
DEFAULT
Tunnel-Type := VLAN,
Tunnel-Medium-Type := IEEE-802
This filter is insufficient. Please study the examples - you need at least:
Reply-Message =* ANY,
Proxy-State =* ANY,
EAP-Message =* ANY,
Message-Authenticator =* ANY,
MS-MPPE-Recv-Key =* ANY,
MS-MPPE-Send-Key =* ANY,
MS-CHAP-MPPE-Keys =* ANY,
State =* ANY
...to be sure of EAP working.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
