I need a script that create email with the amount of up and download traffic every 1st day in month after that action the script resets the traffic counter of each pppoe-user.
Thank you for help!
I hope my English is good enough to understand...
Nobbe
i woul suggest you to use some accounting software to accomplish this. You are welcome to take a look at our application called HotSpot Manager:
http://www.mikrotik.com/download.html#hotspot
Edgars
http://www.mikrotik.com/download.html#hotspot
Edgars
Hotspot Manager
Fine - but there is no download link .... how should I use a software without download?i woul suggest you to use some accounting software to accomplish this. You are welcome to take a look at our application called HotSpot Manager:
http://www.mikrotik.com/download.html#hotspot
Edgars
New Desires to the Online Hotspotmanager
1. Count the traffic and pay for traffic ($ per MB) in the section "hour cost"
2. Count the traffic amount from 00:000 to 23:59 every day (one option is to disconnect all users at midnight)
2. Count the traffic amount from 00:000 to 23:59 every day (one option is to disconnect all users at midnight)
amount a day
2. i've checked that but it is not correct.
example: User1 logged in at 23:00 and have a amount of traffic in the first hour of 100 MB and in the next 1 hour only 1MB
after that hour the user1 logged out.
in the logfile the amount uf 101MB is calculated in the next day and thats not correct because the amount of 100 MB is caused in the day before.
thats my problem
example: User1 logged in at 23:00 and have a amount of traffic in the first hour of 100 MB and in the next 1 hour only 1MB
after that hour the user1 logged out.
in the logfile the amount uf 101MB is calculated in the next day and thats not correct because the amount of 100 MB is caused in the day before.
thats my problem
The reason for this is that normally accouting data is from the Accounting-Stop packets that the NAS (here: RouterOS) sends to the RADIUS server. And this packet does contains the complete user session (i.e. all online time and data transfer) and is timestamped just when the connection is dropped. That is, the RADIUS server (where the accounting data is collected) doesn't get to know anything about the session until it's finished. This leads to the effect you see.
There' not much to do about it, though. You could use Interim RADIUS packets to update the stats while the connection still is active (i.e. every 5 minutes or so), but I'm not sure if this could be easily (i.e. out-of-the-box) used to split accounting data the way you want it.
Basically all ISPs (at least those doing tarifs by data volume) have this effect, but none of those I know do have a problem with it. That's a kind of "jitter" that will level out over some months. It's right that in theory this could lead to users not using up their "free" volumen for a day or so...
While I'm typing this I come up with an idea how you could do accurate accounting, though (at least if you operate your own RADIUS server):
You could set the Session-Timeout for each session so that the session ultimately is closed (forcefully, from the NAS) just before midnight. Then all accounting data is "billed" to the correct day, and the user could instantly login again. If that's a feasible solution, is up to you...
There' not much to do about it, though. You could use Interim RADIUS packets to update the stats while the connection still is active (i.e. every 5 minutes or so), but I'm not sure if this could be easily (i.e. out-of-the-box) used to split accounting data the way you want it.
Basically all ISPs (at least those doing tarifs by data volume) have this effect, but none of those I know do have a problem with it. That's a kind of "jitter" that will level out over some months. It's right that in theory this could lead to users not using up their "free" volumen for a day or so...
While I'm typing this I come up with an idea how you could do accurate accounting, though (at least if you operate your own RADIUS server):
You could set the Session-Timeout for each session so that the session ultimately is closed (forcefully, from the NAS) just before midnight. Then all accounting data is "billed" to the correct day, and the user could instantly login again. If that's a feasible solution, is up to you...
You could remotely execute command removing all the interfaces of your connected users with a cronjob.
Login with ssh/telnet -> remove ifaces and wait for calls from angry customers.
I wrote a shell script for remote login and command execution.
It works with both ssh and telnet.
It's bit fancy since I also included dialog menus (I had some spare time).
The whole thing can be easly changed to make it more suitable for running within a cronjob.
Just read the connect_ssh and connect_telnet functions.
The script is avaliable at:
http://yazzy.yazzy.org/coding/shell/rou ... uteros.txt
I tested it with sh on FreeBSD and Gentoo Linux (where /bin/sh -> bash).
Enjoy.
Login with ssh/telnet -> remove ifaces and wait for calls from angry customers.
I wrote a shell script for remote login and command execution.
It works with both ssh and telnet.
It's bit fancy since I also included dialog menus (I had some spare time).
The whole thing can be easly changed to make it more suitable for running within a cronjob.
Just read the connect_ssh and connect_telnet functions.
The script is avaliable at:
http://yazzy.yazzy.org/coding/shell/rou ... uteros.txt
I tested it with sh on FreeBSD and Gentoo Linux (where /bin/sh -> bash).
Enjoy.
Who is online
Users browsing this forum: No registered users and 66 guests