>>> 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.
>>
> I may be unfairly blaming the upgrade. Looking in my logs, I can't see it
> actually working before on this system.
>
If it never worked, let's take another direction.
In lib/pf/vlan.pm's getNormalVlan, add:
$logger->info("NOT-CUSTOM");
and in lib/pf/vlan/custom.pm's getNormalVlan, add:
$logger->info("CUSTOM");
Restart packetfence, then do another test and check what path did the
code take (you'll see in logs/packetfence.log).
Also, is this a fairly recent install (IOW you first intalled after
1.8.3) or is it a setup that has been ugpraded since the dawn of times?
--
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)
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
