----- Original Message ----- From: "Oliver Graf" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 29, 2003 7:52 AM Subject: Re: missing acct attributes
> On Fri, Aug 29, 2003 at 01:28:38AM +0200, Chris Knipe wrote: > > This is very interesting, and for many months looked more than fine to me. > > HOWEVER, Freeradius is now complaining (especially radutmp and rlm_ippool) > > that there is no NAS-Port-ID specified (which, I can COMPLETELY understand). > > The problem is, I cannot "force" PPPD to send this attribute - they are all > > hard coded by the FreeBSD Developers.... > > [...] > > So the question really, is how / where can I add a default NAS-Port-ID acct > > attribute to freeradius, so that the attribute is only added on my specific > > huntgroup, and only if it is not already specified? The VPN services makes > > [...] > > rlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, > > unique ID MAY be inconsistent > > Why not just tell acct_unique in its config that it should not look > for NAS-Port-ID or substitute something else for it? > > And the second solution is nearly as obvious: patch pppd to do it > right. There should be source code for it... Because it's not the only type of connection that the pppd server or the radius server will serve? It's only for this one specific service that I don't really need the port-id... There are allot of other services served by the same radius server that I depend on the port-id... I'll see if I can get acct_unique to only disregard the attribute on the single huntgroup, but I'm not to hopeful... A quick browse through freeradius' source showed that rlm_ippool specifically looks for the attributes... I may be wrong though. -- me - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
