Hello Fabrice,
Thank you for your explanation.
Regards,
Irvan.
On Fri, Nov 4, 2022 at 7:37 PM Fabrice Durand wrote:
> 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-i
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 wrote
Hello Irvan,
It looks pretty normal that the windows sends the computer account because it’s
the default behavior.
What is not normal, is that if you have at least one successful authentication
on the wifi with a username password, it should keep that one and not re-ask
again.
All that can be
Hello Everyone,
We have strange behaviour with Windows Client connecting to dot1x WiFi on
Packetfence using AD Authentication source.
The symptoms are :
- When the first time Windows client connect to SSID, it was asked for
username and password for login.
- But if client forget the SSID and tr
