FreeRadius working as a ProxyRadius using PAP protocol
Hello, I'm trying to use FreeRadius (server-2.1.1) as a Proxy Radius with PAP protocol. peap,eap,pap pap Client <----------------------> AP <-------------> FreeRadius <--------------> Radius server There's what i have had in my conf files: client.conf: client ***.***.***.*** { secret = pass shortname = LinksysWRT54G nastype = other } proxy.conf: realm NULL { authhost = ***.***.***.***:1645 accthost = ***.***.***.***:1646 secret = pass } users: DEFAULT FreeRADIUS-Proxied-To == ***.***.***.***, Auth-Type := PAP I don't think my proxy radius use the right protocol. I want it to use PAP protocol whe it tries to contact radius server. < radiusd: #### Opening IP addresses and Ports #### < listen { < type = "auth" < ipaddr = * < port = 1645 < } < listen { < type = "acct" < ipaddr = * < port = 1646 < } < Listening on authentication address * port 1645 < Listening on accounting address * port 1646 < Listening on proxy address * port 1647 < Ready to process requests. < < rad_recv: Access-Request packet from host ***.***.***.*** port 1405, id=0, length=180 < Message-Authenticator = 0x1ad77a29ef17ee966a8521f57795f231 < Service-Type = Framed-User < User-Name = "enguyend\000" < Framed-MTU = 1488 < Called-Station-Id = "00-1D-7E-5F-F7-39:SogetiNET" < Calling-Station-Id = "00-16-6F-AA-80-DD" < NAS-Port-Type = Wireless-802.11 < Connect-Info = "CONNECT 54Mbps 802.11g" < EAP-Message = 0x0200000d01656e677579656e64 < NAS-IP-Address = 192.168.1.1 < NAS-Port = 1 < NAS-Port-Id = "STA port # 1" < +- entering group authorize {...} < ++[preprocess] returns ok < ++[chap] returns noop < ++[mschap] returns noop < [suffix] No '@' in User-Name = "enguyend", looking up realm NULL < [suffix] Found realm "NULL" < [suffix] Adding Stripped-User-Name = "enguyend" < [suffix] Adding Realm = "NULL" < [suffix] Proxying request from user enguyend to realm NULL < [suffix] Preparing to proxy authentication request to realm "NULL" < ++[suffix] returns updated < [eap] Request is supposed to be proxied to Realm NULL. Not doing EAP. < ++[eap] returns noop < ++[unix] returns notfound < ++[files] returns noop < ++[expiration] returns noop < ++[logintime] returns noop < ++[pap] returns noop < Sending Access-Request of id 210 to ***.***.***.*** port 1645 < Message-Authenticator = 0x00000000000000000000000000000000 < Service-Type = Framed-User < User-Name = "enguyend" < Framed-MTU = 1488 < Called-Station-Id = "00-1D-7E-5F-F7-39:SogetiNET" < Calling-Station-Id = "00-16-6F-AA-80-DD" < NAS-Port-Type = Wireless-802.11 < Connect-Info = "CONNECT 54Mbps 802.11g" < EAP-Message = 0x0200000d01656e677579656e64 < NAS-IP-Address = 192.168.1.1 < NAS-Port = 1 < NAS-Port-Id = "STA port # 1" < Proxy-State = 0x30 < Proxying request 0 to home server ***.***.***.*** port 1645 < Sending Access-Request of id 210 to ***.***.***.*** port 1645 < Message-Authenticator = 0x00000000000000000000000000000000 < Service-Type = Framed-User < User-Name = "enguyend" < Framed-MTU = 1488 < Called-Station-Id = "00-1D-7E-5F-F7-39:SogetiNET" < Calling-Station-Id = "00-16-6F-AA-80-DD" < NAS-Port-Type = Wireless-802.11 < Connect-Info = "CONNECT 54Mbps 802.11g" < EAP-Message = 0x0200000d01656e677579656e64 < NAS-IP-Address = 192.168.1.1 < NAS-Port = 1 < NAS-Port-Id = "STA port # 1" < Proxy-State = 0x30 < Going to the next request < Waking up in 0.9 seconds. < Waking up in 13.0 seconds. < rad_recv: Access-Request packet from host ***.***.***.*** port 1405, id=0, length=180 < Sending duplicate proxied request to home server ***.***.***.*** port 1645 - ID: 210 < Sending Access-Request of id 210 to ***.***.***.*** port 1645 < Message-Authenticator = 0x00000000000000000000000000000000 < Service-Type = Framed-User < User-Name = "enguyend" < Framed-MTU = 1488 < Called-Station-Id = "00-1D-7E-5F-F7-39:SogetiNET" < Calling-Station-Id = "00-16-6F-AA-80-DD" < NAS-Port-Type = Wireless-802.11 < Connect-Info = "CONNECT 54Mbps 802.11g" < EAP-Message = 0x0200000d01656e677579656e64 < NAS-IP-Address = 192.168.1.1 < NAS-Port = 1 < NAS-Port-Id = "STA port # 1" < Proxy-State = 0x30 < Waking up in 11.0 seconds. < Rejecting request 0 due to lack of any response from home server ***.***.***.*** port 1645 < There was no response configured: rejecting request 0 < Using Post-Auth-Type Reject < +- entering group REJECT {...} < [attr_filter.access_reject] expand: %{User-Name} -> enguyend < attr_filter: Matched entry DEFAULT at line 11 < ++[attr_filter.access_reject] returns updated < Sending Access-Reject of id 0 to ***.***.***.*** port 1405 < Finished request 0. < PROXY: Marking home server ***.***.***.*** port 1645 as zombie (it looks like it is dead). < Waking up in 4.9 seconds. < Cleaning up request 0 ID 0 with timestamp +15 < Ready to process requests. Does anyone have on idea? Thanks Eric NGUYEN
I'm trying to use FreeRadius (server-2.1.1) as a Proxy Radius with PAP protocol.
If you ment to proxy only pap requests, your configuration is not going to work.
proxy.conf:
realm NULL {
authhost = ***.***.***.***:1645
accthost = ***.***.***.***:1646
secret = pass
}
users:
DEFAULT FreeRADIUS-Proxied-To == ***.***.***.***, Auth-Type := PAP
It was an eap request so that didn't match.
< Proxying request 0 to home server ***.***.***.*** port 1645
< Sending Access-Request of id 210 to ***.***.***.*** port 1645
< Message-Authenticator = 0x00000000000000000000000000000000
< Service-Type = Framed-User
< User-Name = "enguyend"
< Framed-MTU = 1488
< Called-Station-Id = "00-1D-7E-5F-F7-39:SogetiNET"
< Calling-Station-Id = "00-16-6F-AA-80-DD"
< NAS-Port-Type = Wireless-802.11
< Connect-Info = "CONNECT 54Mbps 802.11g"
< EAP-Message = 0x0200000d01656e677579656e64
< NAS-IP-Address = 192.168.1.1
< NAS-Port = 1
< NAS-Port-Id = "STA port # 1"
< Proxy-State = 0x30
< Going to the next request .. < Rejecting request 0 due to lack of any response from home server ***.***.***.*** port 1645
< There was no response configured: rejecting request 0
Request was proxied but home server didn't respond. You will have to debug the home server and see did it recieve the request. Ivan Kalik Kalik Informatika ISP
-----Message d'origine----- De : freeradius-users-bounces+eric.nguyen-dang-luan=sogeti.com@lists.freeradius.org [mailto:freeradius-users-bounces+eric.nguyen-dang-luan=sogeti.com@lists.freeradius.org] De la part de tnt@kalik.net Envoyé : mercredi 12 novembre 2008 12:15 À : FreeRadius users mailing list Objet : Re: FreeRadius working as a ProxyRadius using PAP protocol
I'm trying to use FreeRadius (server-2.1.1) as a Proxy Radius with PAP protocol.
If you ment to proxy only pap requests, your configuration is not going to work.
proxy.conf:
realm NULL {
authhost = ***.***.***.***:1645
accthost = ***.***.***.***:1646
secret = pass
}
users:
DEFAULT FreeRADIUS-Proxied-To == ***.***.***.***, Auth-Type := PAP
It was an eap request so that didn't match.
< Proxying request 0 to home server ***.***.***.*** port 1645
< Sending Access-Request of id 210 to ***.***.***.*** port 1645
< Message-Authenticator = 0x00000000000000000000000000000000
< Service-Type = Framed-User
< User-Name = "enguyend"
< Framed-MTU = 1488
< Called-Station-Id = "00-1D-7E-5F-F7-39:SogetiNET"
< Calling-Station-Id = "00-16-6F-AA-80-DD"
< NAS-Port-Type = Wireless-802.11
< Connect-Info = "CONNECT 54Mbps 802.11g"
< EAP-Message = 0x0200000d01656e677579656e64
< NAS-IP-Address = 192.168.1.1
< NAS-Port = 1
< NAS-Port-Id = "STA port # 1"
< Proxy-State = 0x30
< Going to the next request .. < Rejecting request 0 due to lack of any response from home server ***.***.***.*** port 1645
< There was no response configured: rejecting request 0
Request was proxied but home server didn't respond. You will have to debug the home server and see did it recieve the request.
Ivan Kalik Kalik Informatika ISP
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
My request are proxied : i got this the following respond : < rad_recv: Access-Reject packet from host 205.223.235.196 port 1645, id=186, length=23 < Proxy-State = 0x30 In my radius log file: < ******* Incoming RADIUS packet: ******* < radrecv: Packet from host 10.226.66.51, port=24670 < send_reject() < ******* Incoming RADIUS packet: ******* < radrecv: Packet from host 10.226.65.52, port=25433 < send_reject() I think the problem is the protocol I use : PAP. I'm not sure that FreeRadius use PAP protocol to communicate with Radius Server. And is it normal that I can't see any password when I use a sniffer? Regards NGUYEN Eric
NGUYEN DANG LUAN, Eric wrote:
In my radius log file: < ******* Incoming RADIUS packet: ******* < radrecv: Packet from host 10.226.66.51, port=24670 < send_reject()
Your main server is rejecting the request. Fix it. And it isn't FreeRADIUS.
I think the problem is the protocol I use : PAP.
The problem is that you haven't configured the OTHER RADIUS server properly.
I'm not sure that FreeRadius use PAP protocol to communicate with Radius Server.
FreeRADIUS doesn't control the authentication protocol. The end user machine controls it.
And is it normal that I can't see any password when I use a sniffer?
Yes. Alan DeKok.
-----Message d'origine----- De : freeradius-users-bounces+eric.nguyen-dang-luan=sogeti.com@lists.freeradius.org [mailto:freeradius-users-bounces+eric.nguyen-dang-luan=sogeti.com@lists.freeradius.org] De la part de Alan DeKok Envoyé : mercredi 12 novembre 2008 15:48 À : FreeRadius users mailing list Objet : Re: FreeRadius working as a ProxyRadius using PAP protocol
NGUYEN DANG LUAN, Eric wrote:
In my radius log file: < ******* Incoming RADIUS packet: ******* < radrecv: Packet from host 10.226.66.51, port=24670 < send_reject()
Your main server is rejecting the request. Fix it.
And it isn't FreeRADIUS.
I think the problem is the protocol I use : PAP.
The problem is that you haven't configured the OTHER RADIUS server properly.
I'm not sure that FreeRadius use PAP protocol to communicate with Radius Server.
FreeRADIUS doesn't control the authentication protocol. The end user machine controls it.
And is it normal that I can't see any password when I use a sniffer?
Yes.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
My radius server (which is not freeradius) rejects my authentication when i'm using a ProxyRadius (freeradius). But it's ok when I use NTRadping or a cisco ACS. I'm currently using SecureW2 software for the end user machine. Does anyone know where is the problem? NGUYEN Eric
NGUYEN DANG LUAN, Eric wrote:
My radius server (which is not freeradius) rejects my authentication when i'm using a ProxyRadius (freeradius). But it's ok when I use NTRadping or a cisco ACS. I'm currently using SecureW2 software for the end user machine.
Does anyone know where is the problem?
The end RADIUS server. Go fix it. Read it's debugging output (if it has any). Don't ask *us* how to fix it. It's not a FreeRADIUS problem. Alan DeKok.
I think the problem is the protocol I use : PAP. I'm not sure that FreeRadius use PAP protocol to communicate with Radius Server. And is it normal that I can't see any password when I use a sniffer?
No, the protocol you (or should I say the user) are using is eap not pap. Freeradius recieved eap request and proxied eap. It is normal not to have a password in eap packet. Ivan Kalik Kalik Informatika ISP
participants (3)
-
Alan DeKok -
NGUYEN DANG LUAN, Eric -
tnt@kalik.net