Threat Prevention TP V1.3.3 Has been Released!

[Jan Janowski]

Updated SANDY 2600 to SRM -2 and find the new TP has Not been attached to SRM Update script file yet — so manually downloaded it and manually updated it on SANDY 2600.

It will take some hours before things will be confirmed operational with Threat Prevention and events as indicated on map (Which I hear may have an update as well.

I’ll be all over it testing. And will report here.

Once Sandy is deemed updated successfully will do same to EBAY 2600……

And then the MAIN 2600.

I’ll report on all 3, each starting from a different SRM version.

 

[Jan Janowski]

All my custom Self Defined Rules and Settings seem to have been kept... Events starting over from none... So far 7 events... See dots on 7 and 30 days, but not ALL... yet

 

[Jan Janowski]

HMMM..... Seeing events, as dots, under the 7, 30 day Map selection.. But nothing (no dots) on ALL .... To make sure this was not a fluke on just one 2600 (SANDY 2600) loaded SRM -2 and TP 1.3.3 on EBAY 2600.... That is doing the same thing (Displaying Dots on 7 & 30 day, but nothing on ALL....

Again... TP 1.3.2 WITH either of the 2 PATCHES SOFTWARE SUPPORT WROTE, DID DISPLAY ON: 7, 30, & ALL - on Both of same 2600’s: that ran on both 1.3.2 & Patch - and now with 1.3.3 dots seen on 7 & 30, but not ALL.
Original problem with TP 1.3.2: No dots on 7 & 30, but showed dots on ALL...

Asked Support what THEY SEE????? (Main 2600 remains: SRM 1.3.2-2 and UN-PATCHED TP 1.3.2)
ongoing with other tests..

Regarding the possibility of a MAP Change.... I don't see any... It is not obvious..

At least all 2600's are now at 1.3.2-2!!!!

Darn! Why I offered to test the software before release! I wonder if they actually tested this on a system?

 

[Jan Janowski]

Support has asked for, and been given, access to: SANDY 2600 and EBAY 2600 again...

Both are at: SRM 1.3.2-2 and TP 1.3.3 Both see dots on Map: 7 day, and Map: 30 day, and no dots on Map: ALL

 

[Jan Janowski]

12-13 hours After TP 1.3.3 install..... Some dots are finally showing up in ALL !!!
But ALL shows less than what 30 is showing... and 30 is showing same as 7 is showing.... !!!!
Both are acting identical, so there must be a delay of some type going on... nothing in Release Notes.



Anybody else seeing this?

 

[Jan Janowski]

So since not getting any immediate answer, and finding nothing warning me NOT to Update to TP 1.3.3.... MANUALLY INSTALLED TP 1.3.3 on my MAIN 2600!!!

Getting the EXACT SAME RESULTS.... 7 day and 30 day immediately Updating... But ALL at present (Fully installed 1.3.3 at 4PM Local time)... Nothing as yet on ALL!!! I bet it will be there tomorrow morning!!!

ALL 3X 2600'S TP V1.3.3 ARE ACTING IDENTICALLY!!!! And nothing in release notes to warn you about it!!! Synology has access to 2 of 3 2600's... Will be interesting to see what they say about this DELAY in displaying!

WIERD!!!!

 

[Jan Janowski]

Almost 715PM. 3.25 hours since upgrade. Still nothing on ALL on main 2600.. though identical numbers on 7 & 30.
Both EBAY & SANDY Still have less numbers of dots in ALL than either 7 or 30. Which both have same amounts.

It sure looks like a built in delay that All sees that 7 & 30 doesn’t see, as I’m seeing same confusing info on 3 separate 2600’s.

Then there is the question: why does ALL NOT MATCH 7 & 30? Since they should ALL be Identical?? (Pun Intended!)

Just before bed- At 945 still nothing from ‘all’ on main 2600. 7 & 30 have events and are identical. Sandy & EBAY 17.5 & 16.5 hours after 1.3.3: ‘all’ is less than 7 & 30

Can’t wait to see what Support says.

 

[Jan Janowski]

Not finding anything totally broke in TP 1.3.3... That would make it un-useable...... But TP 1.3.3 sure does have a limitation in the ALL setting of the MAP Dots...
There seems to be a Delay of about 12-14 hours from the time 7 day or 30 day sees & displays events... and when they are finally displayed on ALL -- BUT EVEN THEN, Not All the events Seen by 7 & 30 are even being displayed by ALL!!! Not sure what could cause only Some Events to display and not all events... ??????

Now you'd think that ALL would, have as many events as 7 or 30 would, within the first 7 days.... and then 30 and All would increase from there after 7 days, and All would increase over 7 and 30 starting after day 30...
With this being DAY 2 of TP 1.3.3, we can only surmise what the first 7 days SHOULD DISPLAY, and it is Not Displaying Correctly!!! WHO KNOWS WHAT day 8 or day 31 will show?????!!!! (Day 8=7/14/26.. Day 31=8/6/26!)

ALL NEVER shows same amount of events as 7 or 30 does.. AT ANY TIME -- SO FAR!

"All" worked fine in TP 1.3.2 and 7 & 30 never displayed at alll.... The '2 Patches' I ran on 2x 2600's (One under SRM 1.3.2 and other under SRM 1.3.2-1) under TP 1.3.2 worked flawlessly for almost 5 months on 7, 30 or ALL -- No Issues!!!
In 1.3.3 they fixed 7 & 30, but broke ALL.. That must be the issue in TP 1.3.3!

All this has been sent to Support in detail... I'm still awaiting them to visit SANDY 2600 or EBAY 2600, that I gave Support access to.... My MAIN 2600 is acting 100% Identical to SANDY & EBAY...

I'm still testing.... looking for good or bad points... This error is not hard to determine from the displays.... It is Quite Obvious. I keep referring to support to look at their router in those areas....

ONGOING.....

They have visited! Saw as I described. Asked if 3rd did same (does).
2nd visit
Ongoing

 

[Jan Janowski]

Day 3 of Update
All 3x are still working identically. The all list dot amount is still less than 7 & 30 day lists, which are identical.

2x different Support IP’s have visited to 2 of 3 2600’s. I see no changes. In past changes were made then I was informed what had happened.

Nothing else unusual in TP 1.3.3 on any of the 3 was found by me. I’m asking support what they saw on my, or other units.

ONGOING

 

[Jan Janowski]

Day 4 since TP 1.3.3 Update install.... some time since yesterday, When: ALL 3 2600's, who's TP ALL Event dot quantity has always lagged behind both 7 and 30 (That were identical), (and for 12 or so hours after initial 1.3.3 Update... 'ALL' had NO Event Dot Display at all)... when 7 & 30 had event dots........

Overnight all 3 2600 TP 'ALL' Display: HAS "CAUGHT UP" TO 7 AND 30 DAY DISPLAY! Now: The 3x display settings: "All", "7", "30" --- On Day 4 -- They now are Identical!

Hey! I'm just the Postman.... Describing what I'm seeing!!! Don't recall this before.... on any prior TP version, ever!

Reported this to Support... Awaiting their, and Software Support's response.

 

[Jan Janowski]

While I await the next Softtware visit, and Support reply to the situation...
The delay I saw on ALL though the dots graphic is indicating identical colors, location, and dot sizes, if I click on the dot graphic, the amount of events it displays is different between 7 & 30 (which match in amount), and ALL... (which often displays an altogether different amount)... Have no idea WHY, but reported it to Support....

So far I see no other operational issues other than the ALL Display....

Monday 7-13, 0600: flurry of failed (blocked login emails!). Confirmed. Tripped auto Block!

Deleted blocks- added allowed IP’s sent support contact of what I found and did to alleviate it! I can login with what I gave them! Wonder if it’s a typo being done?

At least block has been removed and ip in allowed list!

My login email ‘push’ has worked out - and it’s worth confirmed!!!

But still why did they fail ??????

 

[Jan Janowski]

Update from support;
They were using Setting from “Last Time”
they visited!
Not “This time”!

USA Support now passing on: THIS TIME’S
settings!
That should work!!!

Tuesday 7-14. Successful login by software folks

 

[Jan Janowski]

Day 8 since TP 1.3.3 was updated on 3x 2600's! All 3 are acting identically!
Being Day 8.... I would expect that on the 7 day map/dot selection would (now) have less dots than the 30 day Selection does (because it's day 8!) AND IT DOES... IT IS WORKING CORRECTLY (Part of 1.3.3 FIX)

But Being Day 8 I would also expect the ALL Selection would match the 30 day Selection.... BUT IT DOESN'T!! ALL Contains LESS than 30!.... "ALL" is either INCORRECT, or it's being delayed... On day 2-3 I Asked if a delay to display on ALL is 'as intended' (and 7 & 30 has NO DELAY), and have not heard from them yet... (This worked Correctly in TP 1.3.2 & PATCH (No Delay anywhere), but on 1.3.3 ALL appears broken or delayed - not sure which!)

Now if my guess that there is a 12-14 hour DELAY on posting to ALL, that 7 & 30 Doesn't see..... Then Tomorrow... day 9 ALL Should have "Caught Up" with 30.... Like I saw ALL do - compared to 7 & 30 on 1.3.3 Update's first 12-14 hours of operation.. Time will Tell!!

All this relayed to Support... (they visited yesterday and again last night)

 

[Jan Janowski]

Software support has replied, passed it on to Support, and onto me!

The actions that I described in posts above are “As Designed”, and to simplify: has something to do with longitudinal & latitude of the event, and the ‘rings’ based upon amount of event numbers.
Ok.. if: As Designed.. Ok: There is my answer! All 3 doing same thing!

I thanked them for their assistance, and said if no further testing would be required? I would shut down the remote access.

 

[Jan Janowski]

Nothing new heard from Support - Retired the spare 2600’s. Timing is everything! one 2600 on loan again. They do things I don’t. And are 100% DHCP, so this will test my settings in other ways, as I am 95% static IP. Here.