Em 15-04-2014 14:43, Peter N. M. Hansteen escreveu: > Giancarlo Razzolini <[email protected]> writes: > >> Because using radius you can have a control per user, and accountability >> per user, not per IP. > Yes, of course, for the per user or per customer case I agee totally. > For the OP's scenario it seems the IP address was the primary key, so > pflow would be ideal, but in environments where IP addresses are not > necessarily kept unique per customer, you will need radius or > something equivalent. > > - P That is why it is more "robust" in that sense. As I mentioned, it was probably not what the OP meant. But, for instance, I only became aware of the pflow + nfsen functionality in OpenBSD 6 months ago. Now I can't imagine network management without it. Of course you don't need to know every possible solution to your problem, but the odds are, if you know enough off them, you might do things differently right from the start. Once you start doing things one way, it's hard to change. In this sense, it's good to know your options beforehand. Now let the OP re-join the discussion so we can know more.
Cheers, -- Giancarlo Razzolini GPG: 4096R/77B981BC
