-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 forbmsyn wrote: > Then I found the vlan nubmer of the switch port had been changed back > to #4.
Are you using the example vlan numbering from the network guide? Just trying to figure out what each vlan is in your system. > From the PF Web UI, I could see the mac address of the laptop had > been changed from unregistered to registered. The act of logging into the captive portal did that. That sounds correct. > Packetfence.log gives me some message like below: > > Jul 14 12:35:11 register.cgi(0) INFO: re-evaluating access for node > 00:15:c5:cf:0f:12 (manage_register called) > (pf::enforcement::reevaluate_access) Jul 14 12:35:11 register.cgi(0) > INFO: 00:15:c5:cf:0f:12 is currentlog connected at 192.168.1.12 > ifIndex 10001 in VLAN 2 (pf::enforcement::_should_we_reassign_vlan) Ok, this part indicates that you successfully registered and it's determining if you need to be put into a different vlan. > Jul 14 12:35:11 register.cgi(0) WARN: No parameter defaultVlan found > in conf/switches.conf for the switch 192.168.1.12 > (pf::SNMP::getVlanByName) Jul 14 12:35:11 register.cgi(0) WARN: > Resolved VLAN for node is not properly defined: Replacing with > macDetectionVlan (pf::vlan::fetchVlanForNode) It looks like you don't have a defaultVlan defined for this switch, so it's falling back to the macDetectionVlan instead. > Jul 14 12:35:11 register.cgi(0) INFO: MAC: 00:15:c5:cf:0f:12, PID: > admin, Status: reg. Returned VLAN: 4 (pf::vlan::fetchVlanForNode) Jul > 14 12:35:11 register.cgi(0) INFO: VLAN reassignment required for > 00:15:c5:cf:0f:12 (current VLAN = 2 but should be in VLAN 4) > (pf::enforcement::_should_we_reassign_vlan) And here we see that the system believes that VLAN 4 is the macDetectionVlan and that it needs to issue a VLAN change. > Jul 14 12:35:14 pfsetvlan(3) INFO: reAssignVlan trap received on > 192.168.1.12 ifIndex 10001 (main::handleTrap) Jul 14 12:35:14 > pfsetvlan(3) INFO: security traps are configured on 192.168.1.12 > ifIndex 10001. Re-assigning VLAN for 00:15:c5:cf:0f:12 > (main::handleTrap) And here we see that PF has issued the VLAN change. > Can you please let me know what I should do next? Thanks. It would appear that the config for this switch is missing something. Can you post the configuration you have from /usr/local/pf/conf/switches.conf? Just the section for the 192.168.1.12 switch should be sufficient. > Regards, Jacky - -- - --------------------------- Jason 'XenoPhage' Frisvold [email protected] - --------------------------- "Any sufficiently advanced magic is indistinguishable from technology." - - Niven's Inverse of Clarke's Third Law -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlHjKJUACgkQ8CjzPZyTUTRbwwCcDF5jvJa1q7zFmEuXEv7gD3+7 0YEAnA+qKHpBQ9CQkwinUzxDXEm2PZm+ =Zcs/ -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
