Hello, On Wed, 03 Jun 2009 08:24:53 +0100 Arran Cudbard-Bell wrote:
[more uniqueness for accounting packets] > Example policy for this would be something like : > [snip] Thanks a bundle for that, I was about to whack my head against the screen here and type "man unlang". ;) > > If you're still getting duplicates, check that the NAS is actually > sending the value of the Class attribute. Vendors are notoriously bad > for ignoring the RFC in this area. > Yeah, never mind that we are talking to proxy servers upstream which in turn may talk to other proxy servers (nobody knows) which ultimately talk to the NAS (BRAS) in question. I have seen those quickly recycled Acct-Session-Id's only with one location it seems, other people with twice the connects never had their IDs re-used in the same sample period. So my bet is that this particular NAS will also happily ignore the Class attribute. ^o^ But nevertheless, a very useful configuration snippet that would do well in a future sample configuration. Thanks again for the quick and comprehensive response, Christian -- Christian Balzer Network/Systems Engineer NOC ch...@gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/ https://secure3.gol.com/mod-pl/ols/index.cgi/?intr_id=F-2ECXvzcr6656 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html