Hey Thanks for taking time to explain that.
After getting confirmation on all of the above I pulled a Sherlock Holmes and found that using 127.0.0.1 as the ip of the radius server does not work. I had to all the LAN adapter IP there instead.
Now she's ticking away and working.
If you use * as interface IP then radius is listening on all interfaces. Probably the easiest one for testing.
The user speed limit seems to work. Set it to 256K up down and a speed test verified that.
Do you mean the limit set on CP only or do you mean the override freeradius does ?
Now I'll test the usage daily and hope monthly works. I read about a 6 meg counter bug does that still apply with the 2.0.1 version?
This bug is still present on 2.0.1 but as far as I know it is fixed in 2.1. There was a ticket open on redmine which was closed.
When trying to limit the amount of traffic please read the freeradius2 documentation carefully - about accounting updates and so and and read the "KNOWN BUGS" to make sure you know what is going on :-)
I also need to know how it regulates speed as compared to the traffic shaper.
I tested the shaper once regulating speed . All it does is drop packets , making the end user take longer to download . In the end wan usage from the ISP almost doubled in the 2 months I tested this.
Does CP do the same?
Don't know anything about that.
Also If I have a static route 3rd nic going off too different servers will CP limit speed to this lan as well?
All users which use the CP as authentication will be affected by the limits - no matter which destination their traffic has. But you can add a "Pass-through IP address" on CP. So you are able to bypass the CP for specific destination IPs.