150 likes | 230 Views
An Implementation of Real Time Internet Traffic Charging. Alan Benson. Bishop Grosseteste College. Presentation Plan. What is the problem? What is my solution? How does it work? Shortcomings!. The Problem. An increase in the number of users An increase in the number of uses
E N D
An Implementation of Real Time Internet Traffic Charging Alan Benson Bishop Grosseteste College
Presentation Plan • What is the problem? • What is my solution? • How does it work? • Shortcomings!
The Problem • An increase in the number of users • An increase in the number of uses • An increase in the number of connected sites • Insufficient funding
Objectives of the System • To identify chargable traffic • To identify the user generating the traffic • To identify a method to make the charge • To prevent internet access where necessary
System Parameters • Automatic • As simple as possible • As cheap as possible • As portable as possible • Scalable
Identifying Chargable Traffic • Global routing table held locally • Monitor Gateway interface • Traceroute • RIPE/RADB
The “buildastable” script • Run regularly as a cron job • Use RIPE aware whois • Builds list of all peer networks
Identifying who to charge The Problem • Dynamic, mobile users • Dynamic IP address assignment The Solution • Log user on login • DHCP executes external script
The “setaccess” script • Matches an assigned IP addess to a User • Checks the Account balance of that User on the Novell server • Grants or denies access through the Linux gateway notifing user when appropriate. • Builds database on Users and IP Addresses
Monitoring and Charging the Traffic • Netramet monitors all traffic • NeMaC collects that traffic at specified intervals and executes external charge script
The “charge” script • Checks for traffic since last collection • Charges the user for any traffic they received • Checks User balance and disables route if appropriate with a message.
Bugs/Features • Accuracy of RIPE/RADB databases • Internet routing discrepancies • Central email hubs • Advance charging • Scalability
Portability • Modular setup • Third Party programs run on many platforms. • System written in Perl, therefore very portable.