White III, Joe wrote:
> Based on the debug output down below, could I do the following in the users
> file?:
>
> DEFAULT User-Password == "letmelook"
> Airespace-Wlan-Id = 4
> Fall-Through = No
No. Put the Airespace attribute on the first line. See "man users"
And use "Clearte
Fajar wrote:
>
> In FR-2.x you should be able to use
>
> DEFAULT Client-Shortname == ap-2000-cd6, Auth-type := reject,
> Fall-Through = yes
Turns out the guest network is on a separate wireless VLAN, not on separate
access points as first thought.
Based on the debug output down below, c
On Thu, Jan 26, 2012 at 4:37 AM, White III, Joe wrote:
>> Generally, you can only do this is if the requests from those "certain
>> APs" have something which distinguishes them. Then you can match on this
>> in the users file [using 'DEFAULT'] and set Auth-Type to Reject.
>
>
> If I have three acc
> Generally, you can only do this is if the requests from those "certain
> APs" have something which distinguishes them. Then you can match on this
> in the users file [using 'DEFAULT'] and set Auth-Type to Reject.
If I have three access points I don't want users to access, can I do something
On 25/01/2012 20:35, White III, Joe wrote:
I'm running Freeradius 1.0.1 using MySQL as the database backend.
I need to configure the server so that all users are restricted from using
certain access points (i.e. guest network). It appears I need to use a DEFAULT
user definition in the users
I'm running Freeradius 1.0.1 using MySQL as the database backend.
I need to configure the server so that all users are restricted from using
certain access points (i.e. guest network). It appears I need to use a DEFAULT
user definition in the users file, but I can't find any examples to work f
6 matches
Mail list logo
