I also noticed that I never received the "pfcmd service pf watch" notifications, because of:
Undefined subroutine &pf::cmd::pf::service::pfmailer called at /usr/local/pf/lib/pf/cmd/pf/service.pm line 293. Then the script stops, and it never gets to the restart section. If I disable email notifications, the script continues, and does restart services. (including the pfdhcplistener mentioned earlier) MJ On 4/22/2015 17:25, Fabrice DURAND wrote: > Hi > > Does pfdhcplistener is running ? > What about ipset -L ? > > Regards > Fabrice > > Le 2015-04-22 10:02, heupink a écrit : >> Hi, >> >> Packetfence 5.0, inline mode. >> >> This morning I used a dhcp pool like 172.16.0.0/16 with a lease length >> of a year. This never worked out: somehow nat did not work, traffic >> never left the natted network. (yes, ip_forward enabled) >> >> Then I changed back to 192.168.42.0/24, and this does work. But one >> thing remains: /admin/nodes is still showing 172.16.222.41 for _one_ of >> my devices. Checking the dhcpd log/leases confirms that also this device >> was provided an expected 192.168.42.0 ip, and that the device (a >> blackbox accesspoint, cannot locally logon to is) does in fact have a >> 192.168.42.x address. Rebooted everything multiple times. >> >> However, this accesspoint cannot 'go out': red light, no connectivity. >> (tried it on a different network: green light immediately, so it is able >> to use a dhcp server, and connect outside) >> >> The device is showing "registered" in /admin, but it still shows the OLD >> 172.16.222.41 ip address, with a startime, without an endtime. (plus >> additional greyed ip's in the 192.168.42.0 range) >> >> Perhaps the one-year lease length from this morning was too long for >> packetfence... and I wonder why 172.16.0.0/16 never worked, but for now >> the question is: >> >> How to get rid of this wrong, old ip address in /admin? Is there an >> option to completely purge all info in packetfence for a certain mac >> address, so that it will see the device as completely new? Clicking the >> 'delete button' says: Error! The node can't be delete because it's still >> active. >> >> Clues..? >> >> ------------------------------------------------------------------------------ >> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT >> Develop your own process in accordance with the BPMN 2 standard >> Learn Process modeling best practices with Bonita BPM through live exercises >> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ >> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF >> _______________________________________________ >> PacketFence-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/packetfence-users > > > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > > > > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users > ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
