> > Please explain what are they doing each one process? > Their running mechanism？
First, this is all documented perl code so you can perldoc or vi in the file to see the documentation. ex: perldoc /usr/local/pf/sbin/pfredirect > PFREDIRECT(1) User Contributed Perl Documentation PFREDIRECT(1) > > NAME > pfredirect - IMAP and POP3 redirectors > > SYNOPSIS > pfredirect [options] > > Options: > -d Daemonize > -h Help > -v Verbose ... > > pfdetect parses snort alerts and trigger violations to isolate misbehaving users > pfdhcplistener listens to dhcp traffic, populate dhcp fingerprints for nodes and does more in inline enforcement. Triggers OS violations. > pfmon maintenance daemon, database cleanup mostly > pfredirect usually not used (I never saw it in action), it says it performs IMAP and POP redirection (kind-of email-based captive portal) > pfsetvlan Act on SNMP traps and set switch port VLAN. Central piece of PacketFence's enforcement technique. -- 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) ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
