Per User Bandwidth through Radius.

ncrossley

Anyone willing to start development on this feature. A vital part of PFSense.

craibo

I am looking for the same feature but for Captive portal. per user bandwidth limiting (single limit for Tx and Rx added together) and Disabling of accounts rather then deletion after account Expiration date or limit reached.

I'd post this under bounty but I am South African Student so my money doesn't go very far!!
Let me know if anyone else is looking for similar thing

Thanks guys

tpj

I've set up FreeRadius on an external server, which the captive portal authenticates the users against as well as providing accounting updates.

From there, I'm going to set up some form of script as a cron job on the MySQL server that RADIUS ties into, to compare the amount of data used by the users against the amount of data they have available, and delete the users that have exceeded their limit from the users table.

mdouglas

I have custom chillispot/coova daemon running pfsense. It replaces the CP that comes with pfsense. It has bandwidth, allowed domains, and many other controls. it uses a local Freeradius & mySQL server within pfsense. Not recommended for embedded users due to the mySQL R/W. I would be happy to share.

sullrich

How did you fix the ipfw pfil issues? Try per user bandwidth and let us know if it really works.

mdouglas

With Chillispot/Coova the per user bandwidth is given by the radius and controlled by the chilli deamon. WISPr var. Works great. Each user has it own Upload & Download setting.

sullrich

This is running on top of pfSense? Can you please show me the output of ipfw show?

mdouglas

i am using pf not ipfw.

buraglio

@mdouglas:

I have custom chillispot/coova daemon running pfsense. It replaces the CP that comes with pfsense. It has bandwidth, allowed domains, and many other controls. it uses a local Freeradius & mySQL server within pfsense. Not recommended for embedded users due to the mySQL R/W. I would be happy to share.

Do you have a link I can grab this code from and look at it? Is it documented at all?

mdouglas

as far as the chilli deamon, I havn't created a true pfsense package (I don't know how). Although, I have created a gui integrated into the pfsense web gui for configuring the chilli daemon. as far as FreeRadius, as you know, is apart of the pfsense package list. There are some modifications to the FR setup files to get it to work with mysql instead of flat file structure. There are some how tos on getting mysql installed in pfsense, google "mysql pfsense" again, some custom config for getting it to work with mysql.

all in all, its alittle work. maybe the pfsense dev would like to look into working with me in getting this all added as a CP package.

jahonix

@mdouglas:

maybe the pfsense dev would like to look into working with me in getting this all added as a CP package.

…they are listening already. ;D
SUllrich is THE coding mastermind of pfSense "with a little help of his friends".

buraglio

I don't care if it's a package, I'd still like to see whatever code you have (webgui, etc.). Just tar it up. I'm competent enough to manually get it working. I'm really just interested in your implementation of it. If it's not documented, thats fine. I can reverse engineer whatever you have. No hurry, though, I still need to get my dev environment back up and running.

nb

sullrich

I still want to know how per user bandwidth is working. Call me skeptical but I doubt it's working like you say. Please tell us how it works.

Not trying to sound negative but dummynet which a lot of the captive portal packages use to constrain the bandwidth values does not work with PF currently.

mdouglas

Its been running on my pf platform for months.

Chilli uses RADIUS to provision access and to provide accounting.

Direction of Input and Output
The original ChilliSpot defined input and output as being data uploaded and downloaded by the client respectively. Uses the reverse meaning (per default) making it more compatible with some other commercial access controllers.

In RFC 2866, it says:

Acct-Input-Octets
This attribute indicates how many octets have been received from the port over the course of this service being provided.
Acct-Output-Octets
This attribute indicates how many octets have been sent to the port in the course of delivering this service.

However, this is not very conclusive as it depends on what side of the port you are referring to. In the manual for a popular commercial access controller, is says:

Acct-Input-Octets
Number of octets/bytes received by the customer.
Acct-Output-Octets
Number of octets/bytes sent by the customer.

This is the definition adopted by CoovaChilli - one of the very first changes made to ChilliSpot, for use with back-end systems also supporting commercial access controllers.

Access Provisioning
The following RADIUS attributes are used to place limits on a session authorized by a RADIUS Access-Accept response:

Session-Timeout = seconds
Standard RADIUS attribute (defined in RFC 2865) for setting the maximum session timeout. The user is logged out after this amount of time; session duration.

Idle-Timeout = seconds
Standard RADIUS attribute (defined in RFC 2865) for setting the maximum idle timeout. The user is logged out after this amount of time of inactivity (no traffic).

ChilliSpot-Max-Input-Octets = bytes
ChilliSpot-Max-Output-Octets = bytes
ChilliSpot-Max-Total-Octets = bytes
Chilli vendor specific attributes for setting the max in, out, or total bytes transferred for the session. See above for the meaning of input and output.

WISPr-Bandwidth-Max-Up = bits/second
WISPr-Bandwidth-Max-Down = bits/second
WISPr vendor specific attributes for setting the maximum bandwidth rate in bits per second.

ChilliSpot-Bandwidth-Max-Up = kbits/second
ChilliSpot-Bandwidth-Max-Down = kbits/second
Chilli vendor specific attributes for setting the maximum bandwidth rate in kbits per second. Internally, chilli multiplies this value by 1000 in converting to bits per second.
In all cases, the ChilliSpot vendor specific attributes override WISPr attribute values. However, using the WISPr attributes is perhaps the more standard way to go.

Session Accounting
In RADIUS Accounting, the following attributes are used to report session statistics:

Acct-Session-Time = seconds
Duration of session in seconds.

Acct-Input-Octets = bytes
Acct-Output-Octets = bytes
The lower 32-bit value of the number of bytes of input and output (see above for a discussion of the meaning of input vs. output).

Acct-Input-Gigawords = gigawords
Acct-Output-Gigawords = gigawords
The upper 32-bit value of the number of bytes of input and output; or how many times the above attributes have rolled-over the 32-bit value.

Acct-Input-Packets = num-packets
Acct-Output-Packets = num-packets
The number of packets carrying input or output octets.

sullrich

nevermind, we are obviously speaking on two different wavelengths. I want to know TECHNICALLY how it is pulling off constraining the bandwidth from a FreeBSD perspective (ipfw divert, dummynet, etc).

mdouglas

np, obviously I don't know what your asking, nor is it important. All I know is I have over 200 users, all with different bandwidth restrictions, all of it running through the chillispot/coovachilli daemon running in pfsense. I guess if you want to know more technical info, you might google chillispot and research for the info you are looking for.

Scott, is this a project you would like to see included in pf? After reading the CP Forums, I see there are lots of CP users who are looking for a more robust CP package besides the one included in monowall/pfsense. What dev is the pfsense team doing currently to improve the CP in pf? Is pfsense still following the monowall dev of the CP?

sullrich

A quick google search shows that it is using ipfw. Please type ipfw show from a command shell and post the output if you do not mind.

mdouglas

ipfw show

ipfw: getsockopt(IP_FW_GET): Protocol not available

buraglio

chillispot can also be made to use pf, although to what extent I don't know at this point. There were patches for this under freebsd earlier this year that (I think) were committed. Everything I've seen so far shows only NAT and L3 rules. IT would likely be able to be made to talk to tables using pftabled or perl or something, but I don't see any indication of if that is currently the case.
I think what sullrich wants to know is what mechanism you are using to actually perform the QoS (ipfw, pf, some kind of weird alchemy or magic, etc.).
We understand where you are getting the data from to create the rules (radius). If you post your stuff I'm sure it can be reverse engineered to see what it does.

mdouglas

@mdouglas:

i am using pf not ipfw.