Just to share heads up. I was able to fix this issue by disabling the
enable command, below is how my aaa config looks like.
aaa authentication login default local group NAC-Packetfence
aaa authentication login console group NAC-Packetfence
*aaa authentication enable default none*
aaa
Hello,
I want to change the ip address from 192.168.X.X to 10.10.X.X, but no matter
how I tried, it still not work.
The files I have modified are /usr/local/pf/cong/pf.conf and
/etc/network/interfaces.
And I have also run /usr/local/pf/bin/pfcmd configreload ,
/usr/local/pf/bin/pfcmd
Hello,
I ran the configurator quiet some time back and dont remember which
enforcement mode I selected. Is there a way to determine the enforcement
mode and make changes to it, e.g: switching between vlan mode to inline,
etc.
Regards
Misbah
___
Thanks a lot James. It worked. searches are blazing fast now.
- Arun
On Wed, Dec 15, 2021 at 7:47 PM Rouzier, James wrote:
> Hi Arun,
>
> There is fix for this.
>
> However it requires you to apply a patch manually as it cannot be applied
> through maintenance.
> Since it requires an update to
Hi Ludovic,
Yes with the pf test utility I can test the right user name syntax and I
have recreated the catch all rule. The radius request is accepted now!
Thanks!
Best regards,
Albert Yung
On Tue, 14 Dec 2021 at 10:17 PM, Zammit, Ludovic wrote:
> Hello Albert,
>
> As the logs say:
>
> Dec
Hi,
i have a question regarding mab and packetfence.
My idea is to check allowed mac-addresses against ldap instead of import the
macs by csv to the database.
Because our ldap is the only valid and complete source of information.
My understanding is that i must configure an authentication
please open your browser console tools and try to login. There should be some
data pointing you into the right direction.
Or login via ssh and give all the services a restart with the pfcmd command.
Rein
December 13, 2021 2:11 PM, "IS AppSec (IT/Chennai) via PacketFence-users"
