Manual detention does not pursue client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Network Administration Visualized |
Fix Released
|
Low
|
John-Magne Bredal |
Bug Description
The "manual detention" function in Arnold does not pursue client if it moves to a new switchport.
NAV version 3.5.1
Excerpt from t1000.log:
<...>
[2009-03-12 09:55:01,665] [INFO] [t1000] 00:00:de:ad:be:ef is quarantined, checking for activity...
[2009-03-12 09:55:01,874] [DEBUG] [t1000] {'sysname': 'sw1.net.
[2009-03-12 09:55:01,875] [INFO] [t1000] Mac not active.
<...>
[2009-03-12 10:10:02,355] [INFO] [t1000] 00:00:de:ad:be:ef is quarantined, checking for activity...
[2009-03-12 10:10:02,367] [DEBUG] [t1000] {'sysname': 'sw1.net.
[2009-03-12 10:10:02,368] [INFO] [t1000] Found active mac
[2009-03-12 10:10:02,398] [INFO] [t1000] Ip not in activeonvlans
<...>
description: | updated |
Changed in nav: | |
assignee: | nobody → john-m-bredal |
Changed in nav: | |
milestone: | none → 3.13.0 |
Changed in nav: | |
status: | Fix Committed → Fix Released |
There is currently a limitation when using predefined detentions: if you manually detain a computer with the same reason that the predefined detention uses, it will assume that you want the detention to be confined to the vlans (if any) that the predefined detention uses.
In this example you try to detain a computer with the same reason as a predefined detention uses. As this computer is not currently in the defined vlans for the predefined detention, it will not detain it.
The solution here is to make the reasons for detaining separate for manual and predefined detentions. This will be done in an upcoming patch.