When I set the provisioners to use EAP-TLS (only tested with a mspki) I get
the following error:
-----
Caught exception in captiveportal::Controller::Root->dynamic_application
"Can't locate object method "current_module" via package
"captiveportal::DynamicRouting::Module::Provisioning" at
/usr/local/pf/html/captive-portal/lib/captiveportal/PacketFence/DynamicRouting/Module.pm
line 236."
-----

When I set the provisoner to PEAP, I do not get an error, but devices never
connect after loading the configuration. I have tested this on iOS and
Android. I see no other errors in the logs. Following th MSPKI guide I
successfully tested everything in the debugging section.

Here is my (privacy filterd/sanitized) pki_provider.conf:
----
[App-CA]
country=US
server_cert_path=/usr/local/pf/conf/ssl/tls_certs/pf_domain_edu.cer
ca_cert_path=/usr/local/pf/conf/ssl/tls_certs/ca.cer
locality=City
state=State
organizational_unit=Information Technology Services
url=http://10.1.1.136/CertSrv/mscep/
type=scep
cn_attribute=pid
organization=ORG
----

Here is a sanitized provisioners.conf (android):
----
[android]
eap_type=13
can_sign_profile=0
security_type=WPA
description=Android
broadcast=1
server_certificate_path=/usr/local/pf/conf/ssl/tls_certs/pf_domain_edu.cer
oses=
type=android
category=
pki_provider=App-CA
ssid=ITS Testing
----

I have setup portal modules following the guide section titled "Mixing
login and Secure SSID on-boarding on the portal".

Ideas?
------------------------------------------------------------------------------
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. http://sdm.link/zohodev2dev
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to