This doesn't seem like a question about Radiator or even RADIUS. In
order to gather
RADIUS accounting data from the switch -- radius accounting has to be
supported in
the switch's firmware. I don't know of any switch that supports this.
However, if all you're interested in is a count of octets-in versus
octets-out on a port
by port basis, you're probably better off investigating a solution with
SNMP or RMON
as both protocols are commonly available on managed switches and there
are many
monitoring packages that can be used to not only check on the status of
the switch
and the various ports but also to record the traffic data.
On 7/20/2012 10:49 AM, Jeff Kaminski wrote:
We at Urban Networks have Radiator up and running on CentOS, as well
as the built in ServerHTTP.
In particular, we are interested in traffic accounting for users on
Urban's network that do not need Radius authentication. We just need
to collect their traffic usage for billing.
I am currently setting up the /etc/radiator/radius.cfg file and can
create users. What I now need to know is how to collect IP traffic
accounting information for a particular user that is on a particular
port on a smart switch. This Radius accounting information then needs
to be forwarded on to a Platypus 7 server that handles user account
billing.
To summarize, The user is already attached to Urban's network and has
full Internet access. We just want to track their traffic usage.
Something like the number of Megabytes in and out of the port on the
switch that they are on per hour - or something like that?
So Radiator needs to map the user to the switch and port, and then
track port statistics.
Jeff
_______________________________________________
radiator mailing list
[email protected]
http://www.open.com.au/mailman/listinfo/radiator
_______________________________________________
radiator mailing list
[email protected]
http://www.open.com.au/mailman/listinfo/radiator