Hey guys,
I use an Ansible playbook to generate packetfence networks.conf and
switches.conf (to add new remote switches).
On pf 4.5.1, after the config change, I used the following commands to make
sure that all services take the new parameters :
pfcmd configfiles push
/etc/init.d/packetfence restart
Initally I was using the following:
pfcmd configfiles push
pfcmd configreload
pfcmd service dhcpd restart (to get new dhcpd subnet from networks.conf)
pfcmd service pfdns restart (not sure why)
pfcmd service radiusd restart (to get new switches from switches.conf)
But the configreload part was a bit too long to run, as my switches.conf is now
around 35000 lines long, so a full restart of packetfence is slightly more
efficient.
However, on version 4.6.1, it seems that even after " pfcmd configfiles push"
and a packetfence restart, the dhcpd server still have the old configuration
without the new networks, and I have to run pfcmd dhcpd restart to get the new
dhcpd.conf running.
So I'm wondering what would be the minimal set of commands to run after a
config change in networks.conf and switches.conf, on pf 4.6.x, considering I
use only radius method for auth&deauth ?
Thanks & R egards,
--
Frederic Hermann
Neptune Internet Services
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
