Hi ! I'm trying to set up Freeradius (1.1.0) to proxy ms-chap-v2 and when I get the "accept" from ms-win2k3-ias server, then i want to assign a static ip address. Reading the doc/proxy file, i read that the user file is processed as usual after accept is received ms radius server. users : DEFAULT Service-Type == Framed-User, User-Name == "username" Framed-IP-Address = 192.168.1.100 Running radius in debug mode i alway get this : Error: Warning: Found 2 auth-types on request for user 'username@domain' Is it possible to assign a ip address after a ack (accept) is received from the proxy radius server ? If yes, anybody have a config example for me ?
Hi !
I'm trying to set up Freeradius (1.1.0) to proxy ms-chap-v2 and when I get the "accept" from ms-win2k3-ias server, then i want to assign a static ip address.
Found a odd solution : radius.conf : ippool pool-ip { range-start = 192.168.1.100 range-stop = 192.168.1.101 netmask = 255.255.255.255 cache-size = 10 session-db = ${raddbdir}/db.ippool ip-index = ${raddbdir}/db.ipindex override = no maximum-timeout = 0 } huntgroups : group NAS-IP-Address == 192.168.1.1 users : DEFAULT Huntgroup-Name := "group", Pool-Name := "pool-ip" Debug: rlm_ippool: Allocating ip to nas/port: vpn.domain.com/0 Debug: rlm_ippool: num: 1 Debug: rlm_ippool: Allocated ip 192.168.1.100 to client on nas vpn.domain.com,port 0 Debug: modsingle[post-auth]: returned from pool-ip (rlm_ippool) for request 0 Debug: modcall[post-auth]: module "pool-ip" returns ok for request 0 I'm able to give a "static" ip address, but i have to allocate two ip addresses for each user. :-(
Hi !
I'm trying to set up Freeradius (1.1.0) to proxy ms-chap-v2 and when I get the "accept" from ms-win2k3-ias server, then i want to assign a static ip address.
Reading the doc/proxy file, i read that the user file is processed as usual after accept is received ms radius server.
users :
DEFAULT Service-Type == Framed-User, User-Name == "username" Framed-IP-Address = 192.168.1.100
Can anybody help ?
Hi !
See post_proxy_authorize in proxy.conf.
Yes, "post_proxy_authorize = yes" was the solution and some hacking in the user file.
See also "postproxy_users", which is I think what you want.
This file/function "postproxy_users" wasn't documented, maybe someone can do that for the 1.1.1 verision ?
participants (2)
-
Alan DeKok -
VannMann32 .