On Tue, 27 Jan 2004, George Heeres wrote: > Based on the above problem, the simple solution would be to do > everything inside of FreeRadius. Theoretically, I could even use the > EXEC module to punch holes in the firewall and setup the traffic > shaping. Sounds good to me. But so far I'm not having any luck with > the IP address pools. During the EAP session, the rlm_ippool module > returns NOOP with an error that the nas port was not found. I've
rlm_ippool depends on the NAS-IP-Address(or NAS-Identifier) and NAS-Port-Id attributes to be present in the incoming access/accounting requests in order to allocate/deallocate the corresponding ip entries. So you must make sure that the NAS-Port-Id attribute is present in the incoming requests. > tried to add that information with the users attribute, but the > information I've added ends up being contained within the internal > tunnel and the rlm_ippool module still complains about no nas port. > What am I doing wrong? Here is the ippool that I currently have > setup in radius.conf: -- Kostas Kalevras Network Operations Center [EMAIL PROTECTED] National Technical University of Athens, Greece Work Phone: +30 210 7721861 'Go back to the shadow' Gandalf - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
