Threat Prevention New TP Update

[Jan Janowski]

EBAY 2600 now running a revised patch!

Edit: 5/14/26 Reporting daily the 2x different patches dot activity and access, to Support... They check my accuracy, and forward to Tier 2

 

[Jan Janowski]

EBAY 2600 received another 'visit' last PM....
TP 7 and 30 day Map- as well as 'ALL' dot displays reacting differently than the same did yesterday.
SANDY 2600 (With older patch version) still working as well.

 

[Jan Janowski]

End of week 1 with 3x identically configured (other than WIFI, QC, and default port#) 2600's online simultaneously to Modem: 2x different 2600's running different patch revisions on TP.... 1.3.2 and one 2600 with TP 1.3.2 un-patched.
I don't see a difference between the 2 patches operationally.... Both doing as intended (Patched 2600's See events as dots on map on 7, 30, & ALL...., and un-pached only seeing dots on ALL- blank on 7 & 30)... I'm Still reporting to support daily with test results as requested... Nothing shared with me other than one patch is later version than other....

 

[Jan Janowski]

Update on TP “PATCH” that fixes Event dots on Map Statistics:

A new fellow joined the Support thread, saying he tried to call me, but I didn’t answer, and they wanted to know if all units had been fixed, as I had been giving them daily updates on the 2600’s indicating so. (I was asked to provide daily updates by them… had he not read the support thread??)

First: The thread was filled with others who had indicating that a new TP V1.3.3 was going to include map updates, and that support (and I too) wanted me to hold off on ‘Main 2600’ my 3rd 2600, keeping unpatched 1.3.2, allowing for that to be 3rd unit to test 1.3.3, when it came out. That direction made total sense - and I was willing to do that and agreed to it. I’m awaiting it now!

Second; not only does my phone store records of calls attempted, but not answered... I have a Verizon phone app that logs any blocked telemarketer calls. No calls were logged anywhere. That in itself was strange..

So I answered No, I have 3x 2600’s, only 2 are patched, and per earlier in support thread, per Synology support it was decided not to patch main 2600..

That was answered with form from this new guy… inficating they wanted access to main 2600. This new thread direction sounds very strange.

Today I rejected that offer…. I’m awaiting (as I was asked to do) for the TP 1.3.3 release, that had the patch and revision to MAP, and the plan support suggested was: to install TP 1.3.3 first on Sandy 2600, as it had oldest revision “Patch”, Then after testing, install TP 1.3.3 on EBAY 2600, and test….. Then and only then, install TP 1.3.3 on my main 2600, and, because I have spare units I offered (again) to pre-test the release code on oldest patched 2600.

I await their answer. Wierd new direction!

 

[Jan Janowski]

An answer was given for that confusing comment.

Since the patches work, Synology is closing the ticket. When later TP update is released I can then try it.

Don’t you want to leave ticket open until new TP is released”???

No, they don’t. !!

So ….. For the second time, I’m shutting down the 2x patched 2600’s, and returning them to a: “Spare on the shelf” status — for this software issue.
As, for the second time a “solution” has been reached. My feelings: a Solution isn’t a Solution, with a: COMPLETE TESTED SOLUTION. I guess I expect too much?

Once TP 1.3.3, or whatever it will be called, is released, THEN they will be pulled back out.
Main 2600 remains at Un-Patched TP 1.3.2 for now.

Don’t know how they can track issues afterward when results are scattered across different tickets. If in the submission area there was a place to add reference or previous ticket number… but that doesn’t help the first post. Kinda counter productive