>> >> read_dhcp_fingerprints_conf is one of the ugly piece I've yet to dig >> into, I'm afraid there's nothing I could do in a timely fashion and we >> are pretty busy right now.. > > Thanks for looking into it. > As I said, I don't quite understand the meaning of the code snipplet in > trigger.pm in the bigger context of packetfence. Could you quickly > explain what it is good for?
It's possible in violations.conf to specify a range of IDs as triggers, ex: OS::1200-1300 would mean all 1200 to 1300 OS would trigger that violation. If you don't use ranges then you won't see ranges in the trigger table thus this range code is not useful to you. > >> Would you mind filing a bug report and maybe moving forward commenting >> out that feature? In the future I'll look more closely at your problem. > > Yes, sure. Where? packetfence.org/bugs -- 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) ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
