Ok, first let me apologize for my messages earlier... for some reason I JUST
received the announcement message (God! I hate Exchange!).
Anyway, so I've applied the update (using "yum update" to keep my RPM db
consistent - seems to have worked ok) and sure enough the fix I posted earlier
is in there and working as advertised.
So I went into my test node and applied a "Generic" violation (just turned it
on, it was already there from earlier testing) and it worked great, moving the
node's interface to the isolation VLAN. HOWEVER, turning the violation back
off did NOT move it back over the "default" VLAN.
I've flipped it several times and no change in behavior. Any suggestions?
Could this be something held over from when I was messing with this earlier? I
didn't do a LOT of changes, but without doing a fresh install (again) I can't
be 100% sure. Any pointers on where to look to see if I fouled things up
somehow (can't imagine how I could have screwed this up). I've checked
"Configuration->Advanced" and everything in "Reevaluate access reasons" is
turned on. I also added a new "Generic" and then deactivated it and that did
not trigger a return to "default".
Rolls appear to be set correctly on the switch and the node.
Thanks!
Don
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
