I tried everything I know and suggestions from other posts in this forum but I just can not get PF to set it to the correct VLAN of 237 and hope that someone can provide some insight.
I have a ProCurve 3500yl with the latest firmware K.15.04, copied the perl module for procuve 2600 to a new procurve 3500yl and added the new module to both the switch_add switch_edit web page to have that listed as an options on the WebGui. In the webgui for this switch I have my vlans 1,2,3,4,5,232,236,237 with nomal vlan1, registration vlan 2, isolation 3, MAC 4, Guest 5 Custom1, 237, Custom2 236, Custom3 232. I modified the custom perl module to set the vlan with the Bypass VLAN of 237 and used the same methods as above with my ProCurve 2800 series switches which works fine. In the packetfense.log I am seeing the following log entries: INFO MAC: xx:xx:xx:xx:xx:xx, PID 1, status reg returned vlan 237 (pf::vlan::fetchVlanForNode) INFO authorizing xx:xx:xx:xx:xx at new location <switchIP> ifIndex 2 (main::handleTrap) WARN: new VLAN 237 is not a managed VLAN -> replacing VLAN 237 with MAC detection VLAN 4 (pf::SNMP::setVlan) After checking the vlan 4 on my switch, it has interface 2 untagged, which before the move to vlan 4, I manually untagged it to Guest VLAN 5 so I know that pf is able to work with the SNMP on setting the vlan. Can anyone provide me with some insight please? -Chris M ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
