Manual detention does not pursue client

Bug #341703 reported by Steinar Otto Sjøholt
8
This bug affects 1 person
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.example.test', 'camid': 881653, 'ip': '0.0.0.0', 'start_time': <DateTime object for '2009-02-26 13:41:09.81' at b76a6608>, 'module': '1', 'mac': '00:00:de:ad:be:ef', 'netboxid': 11, 'end_time': <DateTime object for '2009-02-27 10:41:10.18' at b76a6640>, 'starttime': <DateTime object for '2009-02-26 13:41:09.81' at b76a66b0>, 'ifindex': 7, 'endtime': '2009-02-27 10:41:10', 'port': 'FastEthernet0/7', 'misscnt': None}
[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.example.test', 'camid': 896401, 'ip': '0.0.0.0', 'start_time': <DateTime object for '2009-03-12 09:56:09.03' at b768b5d0>, 'module': '1', 'mac': '00:00:de:ad:be:ef', 'netboxid': 11, 'end_time': <DateTime object for '999999-12-31 00:00:00.00' at b768b4f0>, 'starttime': <DateTime object for '2009-03-12 09:56:09.03' at b768b678>, 'ifindex': 7, 'endtime': 'Still Active', 'port': 'FastEthernet0/7', 'misscnt': 0}
[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
<...>

Tags: arnold
description: updated
Changed in nav:
assignee: nobody → john-m-bredal
Revision history for this message
John-Magne Bredal (john-m-bredal) wrote :

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.

Changed in nav:
status: New → Confirmed
Revision history for this message
Morten Brekkevold (mbrekkevold) wrote :

John-Magne, is there any progress on this issue?

Revision history for this message
John-Magne Bredal (john-m-bredal) wrote :

Fixed in rewrite by making reasons/justifications for predefined detentions/detention profiles not usable for manual detenions.

Changed in nav:
status: Confirmed → In Progress
importance: Undecided → Low
Changed in nav:
milestone: none → 3.13.0
Revision history for this message
John-Magne Bredal (john-m-bredal) wrote :

Fixed in 3.13

Changed in nav:
status: In Progress → Fix Committed
Changed in nav:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.