The rlm_ippool module appears to rely on the NAS IP address and the NAS-Port parameter to mark down IP addresses as being used. This makes sense to me if you are using something like a modem bank or some NAS that actually has ports but what if your NAS is something that doesn't rely on ports in that way?
For instance a router that is sending radius auth requests for VPN users, there is no physical port like a modem bank would have. In my specific case I am using radius auth requests from a piece of equipment which doesn't care about port and specifies a NAS-Port-Type = Virtual . This obviously doesn't work with rlm_ippool since it requires NAS-Port. I was unable to find a way around this issue, I thought maybe I could rewrite parameters but I don't think that would work. I do receive a Calling-Station-ID which could be used as a unique identifier if I could get rlm_ippool to use this parameter instead but short of changing the source code I couldn't find a way. I'm a little confused as to the necessity of having the NAS-Port because wouldn't a normal accounting Stop packet have the IP address in it anyway which would tell rlm_ippool which IP to free up. -Jeff - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
