Hello Irvan,
yes it's normal, we did some unlang to mimic the way the realm is set when
packetfence receives a machine authentication.
https://github.com/inverse-inc/packetfence/blob/devel/raddb/policy.d/packetfence#L36
Regards
Fabrice
Le ven. 4 nov. 2022 à 08:34, Irvan via PacketFence-users
Hello Ludovic,
Thank you for your explanation.
How about the realm? According to log, when windows sends computer account
as login, Packetfence put it on Realm = "binus.local". But we never stup
that realm.
Is it normal to?
Regards,
Irvan.
On Thu, Nov 3, 2022 at 12:16 AM Zammit, Ludovic
I have a working 11.2 install on Rocky Linux 8.6.
I have made several attempts to upgrade to 12.0 using the recommended automated
method.
/usr/local/pf/addons/upgrade/do-upgrade.sh runs through without obvious errors,
however when I restart pf, either directly after the upgrade or by a reboot,