R80.30 B08 & B20 SmartConsole - Inspection Settings GUI bug?

[Howard_Gyton]

Hi,

I've just come across a possible GUI bug.

1. Go into "Inspection Settings"

2. Ensure Settings is sorted.  The top entry is probably "Aggressive Aging".

3. Right click and 'Edit' this and you should see its page pop up.

4. Scroll down the list, the method doesn't matter, to an entry a page or two down.

5. Repeat step 3 and you should see you will not see the right page:

It's not specifically stated when sorting on the "Settings" column, that it is alphabetical, but its fairly safe to assume that at least should be but doesn't seem to work like that.

Below is the point where it fails, and editing any beyond this point, points to the wrong protection.

Howard

[G_W_Albrecht]

Nice - but: Effective October 6th 2019, SmartConsole package has been updated (Build 20).

[Howard_Gyton]

Hey!

Yes, I saw that, but I haven't had a chance to try that yet.

A workaround for that issue is to use the search box.  That seems fairly robust, and you can view the correct protection.

EDIT:  Just removed, rebooted, and installed Build 20 for R80.30 SmartConsole and the bug persists.  It's actually weirder that first appears.  Sort by "Settings" so that "Aggressive Aging" is at the top of the list, then just scroll up and down with the mouse wheel but don't click on anything.  You should see that it is no longer at the top of the list, but "Block H.323 Multicast Connections" has now replaced it.  Double clicking on this now brings up the "Aggressive Aging" page!

It seems like the list when first sorted may be correct. 8th down on the list is "Block MGCP Fax", and is correct when viewed.

Scroll up and down the list and you will see that cosmetically the lists order has changed, but crucially, the contents of the list behind this has not changed.

Scrolling up and down also randomly re-sorts the visual list of protections, but the 8th one will always be "Block MGCP Fax" when viewed, regardless of what the actual list entry presents itself as.

At first glance, you may be forgiven for thinking this doesn't seem too serious, as a workaround already exists i.e. search, but if you don't notice you could potentially enable or disable the wrong protection.  Try explaining that one to your higher ups when the proverbial hits the fan.

[G_W_Albrecht]

I would report that to TAC !

[Howard_Gyton]

Done!

Howard