Prevent certain ip ranges from accounting
Hi I'm busy setting up a community network. I'm using freeradius and mysql to authenticate users and do accounting. After the users authenticated to the freeradius system, i only want to do accounting for any internet services. All the free community services, like local chatting within the community network, local voice over ip, etc, should not be billed. All of this traffic will flow between the local network on a class B range. Is it possible to exclude this range from accounting on the radius system and only do accounting for any other ip address (to only bill actual internet traffic) ? Thanks NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard NMMU eMail disclaimer which may be found at: <http://www.nmmu.ac.za/disclaimer/email.htm>> NOTICE: Please note that this eMail, and the contents thereof, is subject to the standard NMMU eMail disclaimer which may be found at: http://www.nmmu.ac.za/disclaimer/email.htm
Van Der Westhuizen, Eldridge (Mr) (Summerstrand Campus North) wrote:
for any/ internet/ services. All the free community services, like /local/ chatting within the community network, local voice over ip, etc, should not be billed. All of this traffic will flow between the local network on a class B range. Is it possible to exclude this range from accounting on the radius system and only do accounting for any other ip address (to only bill actual internet traffic) ?
This is not a radius issue / feature. Your network devices will have to be able to differentiate local versus internet traffic for you. If they can, they *may* be able to just put the internet counter values in radius accounting packets, but I don't know of any NAS that does. Radius accounting packets just contain a single one-dimensional list of packets/bytes in/out. What your NAS puts in them is a NAS issue. If you're assigning fixed IPs, you might look at netflow. Packets like "ipfm" and similar can be used to monitor traffic by IP from a port mirror. All depends on your network architecture.
Phil Mayers wrote:
If you're assigning fixed IPs, you might look at netflow. Packets like "ipfm" and similar can be used to monitor traffic by IP from a port mirror. All depends on your network architecture.
You can also use netflow with dynamic IPs, if you script up something to match the IPs and timestamps in the netflow data against the timestamps, IPs and usernames in your radius accounting. -- James Wakefield, Unix Administrator, Information Technology Services Division Deakin University, Geelong, Victoria 3217 Australia. Phone: 03 5227 8690 International: +61 3 5227 8690 Fax: 03 5227 8866 International: +61 3 5227 8866 E-mail: james.wakefield@deakin.edu.au Website: http://www.deakin.edu.au
participants (3)
-
James Wakefield -
Phil Mayers -
Van Der Westhuizen, Eldridge (Mr) (Summerstrand Campus North)