Hello Pedro,
so it's an inline setup, if you do ipset -L , you should be able to see
the mac of your device in the registration set.
Also did you enabled ip_forward on the Packetfence server, and what is
the dns server on your testing device ?
Regards
Fabrice
Le 2017-11-20 à 09:13,
Hello Yohann,
you need to do that:
cat conf/ssl/MyCERT.crt conf/ssl/MyPRIVKEY.key > conf/ssl/server.pem
and restart haproxy
Regards
Fabrice
Le 2017-11-21 à 09:07, LE GALL Yohann a écrit :
Hi Fabrice,
I’m actually trying to fix my bug about certificates. I did the same
thing as said in
Hello Jason,
sorry for the delay to answer, i was a little bit busy these last days.
Can you enable normalize_radius_machine_auth_username in advanced
section and retry ?
Because as you say, the username is stripped and it's probably because
PacketFence use the TLS-Client-Cert-Common-Name
Hi Fabrice,
I’m actually trying to fix my bug about certificates. I did the same thing as
said in previous mails.
My administration’s board ( https://server:1443/admin/ ) is certificated but my
portal board is not.
How can I do the trick to fix it ?
Regards,
Yohann
I manually changed the "unregistered" VLAN for the switch, to return the
vlan for "corp-machines" (10 instead of 91) and this worked as expected so
the dynamic vlan assignment configuration and subsequent DHCP are working
as expected. The question remains, how do I get the 802.1x EAP-TLS requests
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
I found this lovely little nugget here:
https://sourceforge.net/p/packetfence/mailman/message/33699954/ which
pointed me in the right direction. Looks like I needed auto-register ticked
on my profile and all was right in the world.
