On Mar 4, 2014, at 6:51 PM, forbmsyn <[email protected]> wrote: > > However after about10 minutes, the switch port which the device was plugged > in was changed to vlan 9 automatically. I did not make any changes on > PacketFence, and did not get a chance to update the client device yet. I > think the device should still stay at vlan 3 until the problem is fixed. How > come the vlan of the switch port was changed?
[snip] > Mar 04 14:53:46 pfmon(0) INFO: running expire check (main::cleanup) > Mar 04 14:53:46 pfmon(0) INFO: checking registered nodes for expiration > (main::cleanup) > Mar 04 14:53:46 pfmon(0) INFO: checking violations for expiration > (main::cleanup) > Mar 04 14:53:46 pfmon(0) INFO: violation 1100001 force-closed for > dc:0e:a1:8a:d4:8f (pf::violation::violation_force_close) It appears that your violation had an expiration date/time when set... -Arthur ------------------------------------------------------------------------- Arthur Emerson III Email: [email protected] Network Administrator InterNIC: AE81 Mount Saint Mary College MaBell: (845) 561-0800 Ext. 3109 330 Powell Ave. Fax: (845) 562-6762 Newburgh, NY 12550 SneakerNet: Aquinas Hall Room 11 ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
