A bit of radsniff and even raddebug (just capturing accounting packets) via
radmin might be enough to capture the badness they are sending?
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Brian Candler wrote:
> The reason: vendors have bugs in their accounting implementations, and we
> want to be able to show them the original raw packets to prove it's not our
> accounting collectors which are mis-interpreting the data.
My $0.02 is that you should name && shame the vendors. This
> There's no module to do this. There are very few reasons to do this,
> IMHO.
The reason: vendors have bugs in their accounting implementations, and we
want to be able to show them the original raw packets to prove it's not our
accounting collectors which are mis-interpreting the data.
The pr
Brian Candler wrote:
> I would like to put accounting logs into some sort of database, but store
> the entire raw binary packet as well as some decoded attributes.
I'd suggest using tcpdump for raw packets.
> I can think of plenty of options for the storage: e.g. mysql Blob column,
> CouchDB bi
I would like to put accounting logs into some sort of database, but store
the entire raw binary packet as well as some decoded attributes.
I can think of plenty of options for the storage: e.g. mysql Blob column,
CouchDB binary attachment, MongoDB etc. But I can't see how to get at the
raw packet
5 matches
Mail list logo
