Hi Maikel, Note: CC'ed -devel list.
Maikel van der Roest wrote: > Hi Olivier, > > I’ve being playing a lot with PF trunk lately and I was wondering. With > now node categories, aint it possible to link the vlan to the > categories, so a lot of custom.pl stuff is not needed anymore? > Yes, we plan on doing something more automatic regarding categories and VLANs but we don't want to rush it, we feel it should do the 'right thing'. For example: - A straight VLAN # won't cut it for VLAN-per-building type of setups. So VLAN given by categories should be a per-switch VLAN so we won't refer a VLAN # but a VLAN name which will be looked up in switches.conf (ex: right normalVlan for switch X). But if we want to migrate to VLAN names* (we've been thinking about this for some time) then we need to differentiate between VLAN strings meant for switches.conf's lookup and VLAN strings meant for a VLAN name defined in the switch itself. So, for now, we recommend using pf::vlan::custom and letting us know what would work for you and when we have more experience about what people are doing 80% of the time, we'll make VLAN categories fulfill that. * Relying on named VLANs instead of dot1q tags for all VLAN operations with switches. -- Olivier Bilodeau obilod...@inverse.ca :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Packetfence-devel mailing list Packetfence-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-devel
