I may have been too quick to call this good.
The devices are now self registering which I thougth was going to sole all
my problems but the approprite role is still not getting returned. What
appears to be the problem is the realm is coming up null. I've followed the
setup guide and configured realms that match both the netbios domain name
as well as the AD domain name and tied them back to the AD source. In the
portal profile I have allowed auto-registration and filtered on EAP (Wired
& Wireless) and set the source to machineAuth, the AD source I defined. I
bound machine auth to both the realms defined above + default. The rule at
the end of machine auth is to set the role to corp-machine (assigns vlan
10).
The radius info from the audit page looks great except the authentication
is coming through as realm "null" and the response is not setting a role as
configured in the rules of machineAuth.
The Profile being hit is the EAP-Test profile i built, which I've tried
with reusing dot1x credentials and without. The only source is the
machineAuth - I think I might be missing something to force a realm or
proper detection of the realm? Thoughts on how to test or further
troubleshoot?
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
