And I'll be completely honest which you. We're getting ready to dump usin a public CA for 802.1x. Comodo in particular has been a pain. Androids don't always have a complete certificate chain for comodo, and Windows Pcs seem to randomly get an intermediate cert set in third party store as a trusted root (I'm pretty sure it's a few installers/apps doing it). So between the 2 problems, you can make all of one or all of the other work with no problems but you'll always have to screw with the other. Private CA is the way to go imho.
Sent from my iPhone On Apr 5, 2016, at 6:05 AM, Nathan, Josh <[email protected]> wrote: Hello, So I'm trying to get Radius to supply a valid cert. Even though I've got my PacketFence server, itself, using my Comodo Wildcard certificate, I can see when logging into my wireless AP via 802.1X that I'm still getting the self-signed Radius cert. I renamed the certs directory according to the README file located in it, and then I created a symbolic link to my PF ssl directory. I then did a packetfence-config restart and a packetfence restart, but my iPad still shows that I'm getting the self-signed test Radius cert. What documentation did I miss? Thanks, Joshua Nathan Level 3 IT Support and Development Black Forest Academy +49 (0) 7626-9161-630 ------------------------------------------------------------------------------ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
