Hello, you should probably have to update packetfence before the end of the lease through the API. Also isn't it possible to do mac-auth , it will be easier to manage.
Regards Fabrice Le mer. 23 juil. 2025 à 07:22, 석태환 via PacketFence-users < packetfence-users@lists.sourceforge.net> a écrit : > Hello, I’m an IT infrastructure engineer currently exploring PacketFence. > > One of our manufacturing clients wants to control *unauthorized routers > (rogue DHCP servers)* and *unauthorized devices*, so we’ve proposed and > are now testing PacketFence. Due to the unstructured nature of their > network, we’ve chosen to implement *PacketFence in inline mode*. > > However, their LAN environment heavily relies on *static IP addressing*. > Critical systems like servers, CCTV, VoIP phones, and printers all use > static IPs, making it difficult to switch to DHCP. > > As I understand, *inline mode in PacketFence requires clients to use DHCP*. > In testing, we encountered the following issue: > > - > > We pre-configured IP-to-MAC bindings using the IP Addresses assigned > feature. > - > > Clients set to DHCP receive an IP and work fine through PacketFence. > - > > After that, we manually set the same IP on the device as a static IP. > - > > But when the DHCP lease expires and the device reboots, PacketFence > fails to recognize the node, and commands like register or unregister > no longer apply. > > Question > > Is there a recommended method to operate *PacketFence inline mode in a > static IP environment*, or is *DHCP with IP assignment bindings* simply > the best option? > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users >
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
