Hi list, I don't remember the ip netns / chroot config from earlier releases, but I have discovered that it was giving us, while we are testing, some problems:
If we turn off the switch, but leave packetfence running, and the next day turn on the switch again, everything seems back to normal, but only the netns part seems to be malfunctioning, causing the domain join to show "test join failed". And many domain related things don't work anymore: > root@pf:~# ip netns exec ournetns host samba.our.domain.com > seting the network namespace failed: Invalid argument > root@pf:~# Sure: "service packetfence-config restart" & "service packetfence restart" cures this. But perhaps it could be made more robust someway? (it's strange that the status page shows only 'started', and yet, things do not work) Perhaps with packetfence 'in production', you will hardly ever turn off the switch it's connected too, but still. 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
