Apparently you misunderstood the guide... PacketFence can either run as an *out-of-band* solution (VLAN enforcement) or as an *inline* solution.
- out-of-band: Probably what you want... PacketFence will only be managing both registration and isolation VLANs. Other VLANs (your production ones) will be handled by your production network stuff and PacketFence will only assign VLANs ID. - inline: Probably what you *don't* want. All of the traffic is handled by PacketFence itself since it is the gateway of the secured network. Enforcement is made with iptables. On 2013-02-18 3:01 PM, Josh Bitto wrote: > What I gathered from it is that pf can either work as your firewall or inline > from your firewall -- [email protected] :: +1.514.447.4918 (x110) :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
