[PacketFence-users] 答复: why node become unreg

[平嘉伟 <jia...@le...>]

Hi Fabrice:
       Thanks for your reply!
       the result of query you asked is:
[cid:image005.jpg@01DC6824.E20C98E0]

Although I can not find out if “unreg” is empty or not before this happening, But I am pretty sure it is “empty”.
Because there are many nodes like X, have “bypass role” setting, and  the “unregistration” settings of them are same(“empty”)
[cid:image007.jpg@01DC6824.E20C98E0]

[cid:image009.jpg@01DC6824.E20C98E0]
They are all good, for now;

I know that the “security event engine” will “unreg” node if the “unreg date” reached, but the value of that is “null”;
Is there any other setting like “Time Expiration” which is able to “unreg” the node?

发件人: Fabrice Durand <oeu...@gm...>
发送时间: 2025年12月6日 4:20
收件人: pac...@li...
抄送: 平嘉伟 <jia...@le...>
主题: Re: [PacketFence-users] why node become unreg

Hi Joel,

To help narrow this down, could you please check the unreg_date column for the node in the database?

A query similar to this should provide the necessary detail:
select * from node where mac='c8:5a:cf:06:d7:73';

Thanks,
Fabrice

Le ven. 5 déc. 2025 à 15:14, 平嘉伟 via PacketFence-users <pac...@li...<mailto:pac...@li...>> a écrit :
Hi all:
       I am using pf 11.2 for wire / wireless authentication with eap and no-eap;
       The setup works fine for years;
       Today, one node(X) became “unreg” with no reason, I check all logs I can find and can not find out why, here is the details:
1      check web ui right after client reported, the bypass-role of X is “OA-USER-NO-WAN”, the status is “unregistered”, the unregistration is “empty”; change status to “registered”, do “reevaluate”, all good.
2     X works fine before “2025-12-02 10:52:08”(T0)
3     the audit log show “disconnect-ack” at T0
4     latest log before T0 of X is “accept” at “2025-12-02 10:29:25”(T1)
5     the “access duration” of authen policy for bypass role “OA-USER-NO-WAN” is 6 month.
5       packetfence.log shows
Dec  2 10:52:07 nac01 packetfence_httpd.webservices[1285279]: httpd.webservices(1187) WARN: [mac:c8:5a:cf:06:d7:73] Unable to pull accounting history for device c8:5a:cf:06:d7:73. The history set doesn't exist yet. (pf::accounting_events_history::latest_mac_history)
Dec  2 10:52:07 nac01 packetfence[1382039]: pfperl-api(1311921) INFO: Request to /api/v1/dhcp/mac/c8:5a:cf:06:d7:73 is unauthorized, will perform a login (pf::api::unifiedapiclient::call)
Dec  2 10:52:07 nac01 packetfence[1382039]: pfperl-api(1311921) INFO: re-evaluating access (manage_deregister called) (pf::enforcement::reevaluate_access)
Dec  2 10:52:07 nac01 packetfence[1382039]: pfperl-api(1311921) INFO: Instantiate profile CP-DOT1X (pf::Connection::ProfileFactory::_from_profile)
Dec  2 10:52:07 nac01 packetfence[1382039]: pfperl-api(1311921) INFO: is currentlog connected at (10.155.99.156) ifIndex 32798 OA-USER-NO-WAN (pf::enforcement::_should_we_reassign_vlan)
Dec  2 10:52:07 nac01 packetfence[1382039]: pfperl-api(1311921) INFO: is of status unreg; belongs into registration VLAN (pf::role::getRegistrationRole)
Dec  2 10:52:07 nac01 packetfence[1382039]: pfperl-api(1311921) INFO: VLAN reassignment required (current VLAN = 30 but should be in VLAN 2) (pf::enforcement::_should_we_reassign_vlan)
Dec  2 10:52:07 nac01 packetfence[1382039]: pfperl-api(1311921) INFO: switch port is (10.155.99.156) ifIndex 32798connection type: Wired 802.1x (pf::enforcement::_vlan_reevaluation)
Dec  2 10:52:07 nac01 packetfence[1382039]: pfperl-api(1311921) INFO: modified c8:5a:cf:06:d7:73 from status 'reg' to 'unreg' based on unregdate colum (pf::node::nodes_maintenance)
Which component changed “status”? and why?

Any advice is appreciated.

BR

joel
_______________________________________________
PacketFence-users mailing list
Pac...@li...<mailto:Pac...@li...>
https://lists.sourceforge.net/lists/listinfo/packetfence-users