I was set up the chili (Proxy) connected to the radius and then it was
attribute Colubris-AVPair := max-input-rate=4096 and Colubris-AVPair +=
max-output-rate=4096 so I cannot control bandwidth because my proxy accept
only WISPr-Bandwidth-Max-Down.
How to modify it.
The reason why radius
it is not really a captive portal
situation. Is this something that is achievable using Freeradius?
I've seen lots of talk about using WISPr-Redirection-URL as an attribute in the
Access_Accept but I'm unsure whether this is an attribute specific to a certain
NAS. I'm using Cisco switches, so would I
, so it
is not really a captive portal situation. Is this something that is
achievable using Freeradius?
No. RADIUS does authentication, not routing, and not HTTP. You need
a captive portal.
I’ve seen lots of talk about using WISPr-Redirection-URL as an attribute
in the Access_Accept
...@lists.freeradius.org
[mailto:freeradius-users-bounces+amorris=cardiffmet.ac...@lists.freeradius.org]
On Behalf Of Alan DeKok
Sent: 17 February 2012 16:11
To: FreeRadius users mailing list
Subject: Re: WISPr-Redirection-URL with Cisco 3550 switch
Morris, Andi wrote:
I would like to have the ability
Hey al, iread that i can rate limit on a per user basis with the
WISPr-Bandwidth-Max-Down and Up.. correct?
Can someone please tell me how i can do this? I have freeradius running
on Ubuntu server, with mysql atabase and daloradius for web management.
My users connect to the freeradius
Bandwidth Limit greatly depends on NAS. If yous NAS supports it then it can
be done !
On Wed, Sep 14, 2011 at 7:29 PM, Luke Hammond l...@dezignbrasil.com wrote:
Hey al, iread that i can rate limit on a per user basis with the
WISPr-Bandwidth-Max-Down
and Up.. correct?
Can someone please
!
On Wed, Sep 14, 2011 at 7:29 PM, Luke Hammond l...@dezignbrasil.com
mailto:l...@dezignbrasil.com wrote:
Hey al, iread that i can rate limit on a per user basis with the
WISPr-Bandwidth-Max-Down and Up.. correct?
Can someone please tell me how i can do this? I have freeradius
it then it can
be done !
On Wed, Sep 14, 2011 at 7:29 PM, Luke Hammond l...@dezignbrasil.comwrote:
Hey al, iread that i can rate limit on a per user basis with the
WISPr-Bandwidth-Max-Down
and Up.. correct?
Can someone please tell me how i can do this? I have freeradius running
on Ubuntu
WISPr-Bandwidth-Max-Down / UP is indeed the Attribute which you are looking.
But you need search the mailing lists and find out how to add those into
radreply/radgroup reply.
Hint : Read http://wiki.freeradius.org/Rlm_sql
Regards
Suman
On Wed, Sep 14, 2011 at 9:34 PM, Suman Dash sumand
Thanks Suman. WIll take a look.
On 14/09/2011 1:11 PM, Suman Dash wrote:
WISPr-Bandwidth-Max-Down / UP is indeed the Attribute which you are
looking. But you need search the mailing lists and find out how to add
those into radreply/radgroup reply.
Hint : Read http://wiki.freeradius.org
As described previously, the access point or device which the client
is directly connected to must be a NAS capable of acting on the
WISPr-* parameters sent to it by your RADIUS server.
http://wiki.freeradius.org/NAS
CoovaChilli, for example, is an open-source solution for NAS that runs
under
Hello,
What is the difference between WISPr-Bandwidth-Max-Down and
ChilliSpot-Bandwidth-Max-Down ?
Thank you,
Mickael
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Wed, Jul 6, 2011 at 5:28 AM, becoco beca...@gmail.com wrote:
Hello,
What is the difference between WISPr-Bandwidth-Max-Down and
ChilliSpot-Bandwidth-Max-Down ?
You should really ask chillispot-related forum/list about this. As far
as freeradius concerned, both are just attributes, nothing
Hi Guyz,
Using freeradius with mysql for authentication 'n accounting and it works well.
Clients get authenticated and kicked when time is up.
Now need to send bandwidth control parameters (WISPr-Bandwidth-Max-Up +
WISPr-Bandwidth-Max-Down) to my NAS
My NAS supports traffic shapping
Hi,
Today I did some test with radreply.WISPr-Session-Terminate-Time and
radcheck.Expiration.
It is supposed both attributes do the same, but Expiration is from AAA server
side, meanwhile Session-Terminate-Time is from NAS side.
However, there is a difference if you want to to set
kevin wrote:
IOW, when using WISPr-Bandwidth, does that modify the client connection
at the client computer or does that occur at a proxy or firewall device?
The RADIUS client (NAS) that receives the WISPr-Bandwidth attribute is
responsible for enforcing it.
What I'm getting
On Thu, 2008-12-18 at 15:05 +0100, Alan DeKok wrote:
kevin wrote:
IOW, when using WISPr-Bandwidth, does that modify the client connection
at the client computer or does that occur at a proxy or firewall device?
The RADIUS client (NAS) that receives the WISPr-Bandwidth attribute
can see, zeroshell offers a lot of extra, low-level control. As
mentioned in another part of this thread, being able to manage office
users using WISPr-Bandwidth and similar controls, allowing me to
aggregate all bandwidth with a single point of authentication which is
what I'm looking at. My own
, when using WISPr-Bandwidth, does that modify the client connection
at the client computer or does that occur at a proxy or firewall device?
What I'm getting at is, is a captive portal necessary or can a person
simply have client authentication via freeradius and the client network
card handle
will be
done by MAC for initial ease of setup) but I'm trying to figure out
where the Bandwidth attributes actually are used.
IOW, when using WISPr-Bandwidth, does that modify the client connection
at the client computer or does that occur at a proxy or firewall device?
What I'm getting
IOW, when using WISPr-Bandwidth, does that modify the client connection
at the client computer or does that occur at a proxy or firewall device?
When you use bandwidth control attributes they are used by your NAS (AP,
router, switch, captive portal ...). You should read NAS documentation
to find
moving to using freeradius to authenticate (which
ultimately will be
done by MAC for initial ease of setup) but I'm trying to
figure out
where the Bandwidth attributes actually are used.
IOW, when using WISPr-Bandwidth, does that modify the client
- Original Message -
From: Alan DeKok [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, January 06, 2005 10:58 AM
Subject: [radius] Re: WISPr Attributes and freeradius
Nick Marino [EMAIL PROTECTED] wrote:
When using the WISPr-Session-Terminate-Time
Nick Marino [EMAIL PROTECTED] wrote:
Here is the definition for the attribute, do you have anymore info on it and
FR.
As I said, I don't know anything about the attribute.
FreeRADIUS has no code to interpret that attribute.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
!
The Wispr dictionary has been included in the freeradius distribution, but
that's it and probably nothing more will ever be done.
--
Regards,
Thor Spruyt
E: [EMAIL PROTECTED]
W: www.thor-spruyt.com
M: +32 (0)475 67 22 65
Bestel nu uw exemplaar van Operationele verkoop (Walter Spruyt -
Liesbeth
- Original Message -
From: Thor Spruyt [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Friday, January 07, 2005 2:16 PM
Subject: Re: [radius] Re: WISPr Attributes and freeradius
Alan DeKok wrote:
Nick Marino [EMAIL PROTECTED] wrote:
Here is the definition
When using the WISPr-Session-Terminate-Time in the radreply table should FR
send a rejection based on the time set in that attribute if the time is in
the past or is that supposed to be handled by the NAS and is just sent to it
in the access-accept packet?
Nick Marino - IT Solutions
-
List
- Original Message -
From: Alan DeKok [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, January 06, 2005 10:58 AM
Subject: [radius] Re: WISPr Attributes and freeradius
Nick Marino [EMAIL PROTECTED] wrote:
When using the WISPr-Session-Terminate-Time
Nick Marino - IT Solutions
- Original Message -
From: Alan DeKok [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, January 06, 2005 10:58 AM
Subject: [radius] Re: WISPr Attributes and freeradius
Nick Marino [EMAIL PROTECTED] wrote:
When using the WISPr-Session
Nick Marino wrote:
WISPr-Session-Terminate-Time 14122, 9
String
X
The time when the user should be disconnected in ISO 8601 format
(-MM-DDThh:mm:ssTZD). If TZD is not specified local time is
assumed. For example a disconnect on 18 December 2001 at 7:00 PM UTC
would be specified as 2001-12
- Original Message -
From: Thor Spruyt [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, January 06, 2005 12:07 PM
Subject: Re: [radius] Re: WISPr Attributes and freeradius
Nick Marino wrote:
WISPr-Session-Terminate-Time 14122, 9
String
X
The time when the user
Nick Marino wrote:
Ok then how did you implement your server to work like that?
I run an external auth script which looks up the expiration timestamp of the
user and...
- either accepts the user and delivers the timestamp in the
Wispr-Session-Terminate-Time attribute
- either rejects the user
- Original Message -
From: Thor Spruyt [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, January 06, 2005 1:23 PM
Subject: Re: [radius] Re: WISPr Attributes and freeradius
Nick Marino wrote:
From: Thor Spruyt [EMAIL PROTECTED]
So it's not specified how
33 matches
Mail list logo
