Hi Fabrice,
Thanks very much for your quick answer and I'm sorry to take so long to get
back to you, I went O/S on a very busy trip, plus I missed the original msg -
apologies.
Sorry also since I didn't receive your original reply via the list (I'd posted
then, subscribed, maybe something happened out of sequence) so I've had to
start a new msg here..
To answer your questions (in reverse order :)
I've now changed the password in Advanced to plaintext (it was bcrypt) and
re-tested but I'm still getting exactly the same result.
I noticed the comment next to the Database passwords hashing method control
that reads 'The algorithm used to hash the passwords in the database. This will
only affect newly created or reset passwords'.
It seems that this does not refer to passwords stored in the
/usr/local/pf/raddb/users file, but I thought I would check with you that this
is the case?
I don't think that this should affect passwords used over Wifi authentication?
The contents of my raddb/sites-enables/packetfence-tunnel are just below.
(Thanks again for your help).
# This file is generated from a template at
/usr/local/pf/conf/radiusd/packetfence-tunnel
# Any changes made to this file will be lost on restart
server packetfence-tunnel {
authorize {
suffix
ntdomain
# packetfence-multi-domain not activated because no domains configured
eap {
ok = return
}
files
####Activate local user eap authentication based on a specific SSID ####
## Set Called-Station-SSID with the current SSID
set.called_station_ssid
if (Called-Station-SSID == 'Open-Wrt') {
## Disable ntlm_auth
update control {
MS-CHAP-Use-NTLM-Auth := No
}
## Check password table for local user
pflocal
if (fail || notfound) {
## Check password table with email and password for a sponsor registration
pfguest
if (fail || notfound) {
## Check password table with email and password for a guest registration
pfsponsor
if (fail || notfound) {
## Check activation table with phone number and PIN code
pfsms
if (fail || notfound) {
update control {
MS-CHAP-Use-NTLM-Auth := Yes
}
}
}
}
}
}
expiration
logintime
}
authenticate {
Auth-Type MS-CHAP {
packetfence # increment the StatsD counter
if(PacketFence-Domain){
chrooted_mschap
}
else{
mschap
}
}
eap
}
session {
radutmp
}
post-auth {
exec
update control {
PacketFence-RPC-Server = ${rpc_host}
PacketFence-RPC-Port = ${rpc_port}
PacketFence-RPC-User = ${rpc_user}
PacketFence-RPC-Pass = ${rpc_pass}
PacketFence-RPC-Proto = ${rpc_proto}
}
packetfence
sql
Post-Auth-Type REJECT {
sql
attr_filter.access_reject
}
}
pre-proxy {
}
post-proxy {
eap
}
}
Hello Evan,
can i have the content of raddb/sites-enables/packetfence-tunnel and
what did you configured for the password in Advanced ? (it must be
plaintext instead of bcrypt)
Regards
Fabrice
Le 2016-05-23 11:02, Evan Linwood a écrit :
>
> Hello,
> I'm having a problem getting WPA2-EAP working with my OpertWRT
> wireless router, and hoping that someone could please help.
>
> Some background:
>
> My router is a Linksys unit running OpenWRT Chaos Chalmer.
>
> (I've already configured this with a local RADIUS server and confirmed
> that WPA2-EAP works as expected against the local radius server).
>
> I'm having problems when I reconfigure the router to use the
> Packetfence server as the RADIUS auth server.
>
> The PF server is release 5.7.0, running on Ubuntu 12.04.5 LTS.
>
> According to the PacketFence Administration Guide v4.1.0,
> Configuration/FreeRADIUS Configuration, Option 3. Local
> Authentication, it is only necessary to configure the raddb/users file.
>
> The contents of my /usr/local/pf/raddb/users file is as follows:
>
> username Cleartext-Password := "password"
>
> I'm seeing errors appear in my RADIUS Audit Log as follows:
>
> MAC Address xxx
> Auth Status REJECT
> Auth Type EAP
> Auto Registration no
> Calling Station ID xxx
> Computer name
> EAP Type MS-CHAP-V2
> Event Type Radius-Access-Request
> IP Address
> Is a Phone no
> Node status
> Domain
> Profile
> Realm default
> Reason mschap: External script says
> NT_STATUS_CANT_ACCESS_DOMAIN_INFO (0xc00000da)
> Role
> Source
> Stripped User Name username
> User Name username
> Unique ID
>
>
> I've seen the thread in the Packetfence mailing list re the
> NT_STATUS_CANT_ACCESS_DOMAIN_INFO error, but don't think I can apply
> the same approach because I am not running an Active Directory server
> in my configuration (hence why I'm using Option 3 for local auth as
> described above).
>
> I have configured a RADIUS Realm called 'default'. This has no domain
> configured, and is configured with Source 'local'.
>
> I haven't created any RADIUS Domains.
>
> If anyone could offer any help or thoughts it would be much appreciated!
>
> Thanks Evan
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users