Hi James, > I’ve upgraded our 2.1.0 setup to 2.2.0, since then I’ve noticed that the > getNormalVlan in custom.pm isn’t being called any more. I’ve put logger > statements in and they don’t appear when a vlan is assigned. The logger > statements in vlan.pm do appear in packetfence.log.
I'm surprised to be honest. I've seen upgrades with pf::vlan::custom modules work. > > Anyone got any thoughts how to track down the source of this problem? > Does your custom module compile? PERLLIB=/usr/local/pf/lib perl -c /usr/local/pf/lib/pf/vlan/custom.pm Although we specify to keep the custom.pm file in our RPM spec, can you verify that it happened correctly? That your custom is not in an .rpmsave instead? Then, I would use the perl debugger to trace a getNormalVlan call.. What access type are you using? RADIUS based or SNMP traps based (port-security)? -- 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) ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
