Hi cg, > In fact, if I may, can I contact you directly via email - while > posting all technical dialogue to the list, of course ? I can attach > preliminary versions of my docs, if you'd like them now.
Yes, please do. > After several restarts, without any intervention on my part, the > warnings disappeared ... cosmic rays ? Actually, I've been loading > various Perl modules even if I'm not certain that they're absolutely > required. I've probably overdone it, but at least the above glitch was > taken care of. I'm not quite sure what's the root cause but I've seen warnings often in that spot of the code and it's because it's doing array/hash merges and sometimes the values are undef in one of them (thus the warnings). I haven't been able to reliably reproduce and restarting always seems to fix it so I never really looked into it. > It *seems* to be ok - > and there are no complaints or error messages of any sort ; however > I'm not getting any graphs on the admin screens. As it's possibly a > lurking Debian PHP issue, I've left it for later - until after I get > all the basic ops working. Check apache's error logs for hints maybe? Or pf's own admin_debug_log. > > I'm working with 3 vlans and an HP Procurve 2600 switch at the > moment. PF now sees a plugged in client and issues an IP address to > it, but that's as far as it gets. I've not yet been able to get a > 'captive portal' screen on the client pc. Have you setup the DNS? Look for instructions in the install guide. In the registration VLAN, you need *any* DNS query to answer pf's IP in that VLAN. > Am combing daily through the > PF configs and continue to find things to fix ? I am *not* confident > of the current switch setup but have been unable to get pfcmd_vlan to > return any info - pfcmd_vlan doesn't log anything in logs/packetfence.log... It's an annoyance.. There's a bug already filed for that: http://www.packetfence.org/bugs/view.php?id=874 You can run it by hand and with -verbose 4 it'll give you tons of stuff. > eg, my uplink= setting for the various vlans in > switches.conf is dubious ... (Currently I have it set to > uplink=dynamic everywhere - not certain that that's viable.) Should be ok to start with. If you see in the logs stuff like "Won't take action because it is an uplink port" or "Dynamic uplink unimplemented" then start worrying about it. > In the event, thanks for both the attention and for PF itself - it's a > terrific product and shows great promise for becoming a standard (if > it isn't that already). > Thanks, help spread the word! :) Have a good one! -- Olivier Bilodeau obilod...@inverse.ca :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Packetfence-users mailing list Packetfence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
