Sorry, me again, already.. > Do you run 2.0.0? If you do, I'm concerned that I don't see the > pfcmd_vlan entries in your log..
Just answered myself on that one by looking at the email subject.. doh! The flip call (below) *should* cause a reaction in pfsetvlan. Jan 11 10:52:18 flip.pl(0) INFO: flip.pl called with mm:mm:mm:mm:mm:mm (main::) Jan 11 10:52:18 flip.pl(0) INFO: switch port for mm:mm:mm:mm:mm:mm is ap.ap.ap.ap ifIndex 259 connection type: WiFi MAC Auth (main::) ... (expected pfsetvlan picking up on the trap here) To communicate between the two processes we send a local trap to a fake 127.0.0.1 switch. I'm thinking that maybe something in your debian port is causing problems.. - Do you have the [127.0.0.1] switch of type packetfence defined in your conf/switches.conf? - Do you see the local trap in logs/snmptrapd.log? - Can you do a tcpdump on the loopback and see if the trap is correctly sent by flip? Thanks, -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
