Hi Ludovic, I'm using the Inline configuration, although with a slight difference that should work the same with regards to the networking (two interfaces: eth0 is my management/outside network, eth1 is my internal).
After taking another look at it, I believe I was able to resolve the activation link problem. It was indeed the Apache permission error as described in this bug ticket (http://www.packetfence.org/bugs/view.php?id=1302). I added in the suggested change in apache.pm, as well as simply allowing all connections to /html/cative-portal/ in httpd.conf.d/captive-portal-common.conf and was able to register the node. Now I just need to understand why the nodes are marked as "registered" before even needing to hit the activation link... ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
