Sallee, Jake wrote: > I agree with XenoPhage, I will add a few things though. > > 1) Unless there is a compelling reason use the VLAN deployment option. It is > the best option for performance and scalability in my opinion.
Agreed. Inline would require beefier machines as well since all network traffic passes through the packetfence system. Packetfence also becomes a single point of failure in that scenario. > 2) If you deploy using VLans you will need to add 2 more VLans, one for > registration and one for isolation. Depending on how you deploy, you don't really *need* the isolation VLAN and it can merely exist on the packetfence server, but not be on any switches. > 3) Take is slow, set it up in the simplest way possible and then layer on the > extra things. Start with a single switch and a single client. Read and > follow the Admin Guide VERY carefully. And always feel free to post you > questions to the list. Or, do it in your development network first.. You have a dev network, right? :P > Jake Sallee > Godfather of Bandwidth > System Engineer > University of Mary Hardin-Baylor -- --------------------------- Jason 'XenoPhage' Frisvold [email protected] --------------------------- "Any sufficiently advanced magic is indistinguishable from technology.\" - Niven's Inverse of Clarke's Third Law ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
