Hello Thomas,
you can do this kind of configuration but via the pfdhcp api
(https://github.com/inverse-inc/packetfence/tree/devel/go/dhcp).
Per example you can add this option 43 for a specific network.
Also there is a new feature that is not yet merged in PacketFence that
will allow you to add options based on the device parameter (mac, dhcp,
fingerprint, ...).
But to use it you will need to apply a patch and recompile the dhcp
server. (not complicate, take a look at
https://github.com/inverse-inc/packetfence/tree/devel/go )
The code if you want to try:
https://patch-diff.githubusercontent.com/raw/inverse-inc/packetfence/pull/3784.diff
Regards
Fabrice
Le 19-01-22 à 16 h 08, Thomas, Gregory A via PacketFence-users a écrit :
All,
My campus is in the process replacing a mass of access points across
campus. Some happen to be behind Packetfence. Those behind Packetfence
are unable to connect to the control. As these are Cisco Aps, they are
advising implementing option 43 on the DHCP server.
I am currently running 8.3.0 and have no idea on how to do this.
Any help?
Gregory A. Thomas
Student Life Support Specialist
University of Wisconsin-Parkside
[email protected]
<https://mail.uwp.edu/owa/redir.aspx?C=PJoLX1MXo0SU0MLM7GrPmwxJzaMkdtAIgi4jkK-AXpCwJ307G0bt2lvFPw4WGoqQ06Tt1qwrKAA.&URL=mailto%3athomasg%40uwp.edu>
262.595.2432
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
