Hi, After more investigation, I have found that the netns system on our debian wheezy 7.8 x64 is unstable, and this is probably why I have had so many issues starting with pf 5.2.
In kern.log, I see that, without an obvious reason: > Jun 24 13:25:12 pf kernel: [ 7764.341917] ADDRCONF(NETDEV_UP): ournetns-a: > link is not ready > Jun 24 13:25:13 pf ntpd[2547]: Deleting interface #8 ournetns-b, > 169.254.0.2#123, interface stats: received=0, sent=0, dropped=0, > active_time=1712 secs > Jun 24 13:25:13 pf ntpd[2547]: peers refreshed (I have no idea where ip 169.254.0.2 comes from, and I also find it strange that it mentions outnetns-A and ournetns-B?) But anyway: the result of this is, that after this happens, the pf-domain membership is (obviously) no longer working. I am currently reinstalling, using different nics (this time intel 82576 / ibg) to see if behaviour is caused by the network driver / nic itself. Any tips here? I guess for others here this is not happening..? (as I haven't read any complaints like the above...) MJ ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
