{"id":9228,"date":"2024-12-12T00:57:11","date_gmt":"2024-12-12T00:57:11","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=9228"},"modified":"2025-05-12T17:28:58","modified_gmt":"2025-05-12T17:28:58","slug":"release-3_17_00-changes","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/release-3_17_00-changes\/","title":{"rendered":"Release 3_17_00 Changes"},"content":{"rendered":"

What is new in the SNIP<\/span> 3_17_00 release<\/strong> – released December 12th, 2024
\n(updating the prior release of 3_16_00 issued on October 9th, 2024)<\/p>\n

This is the next production release of SNIP<\/strong><\/span> following the Rev 3_16 release.\u00a0 This release contains both major and <\/em>minor<\/em> improvements in response to user requests.\u00a0 This release supports both 32-bit and 64-bit installations on all Windows Platforms from Windows 7 to the current editions.<\/p>\n

It is recommended that all Windows SNIP<\/strong><\/span> installations now update to using this release.<\/p>\n

Changes in this release include<\/strong><\/h2>\n

IP Ban and Blocking Logic Improvements <\/strong><\/h3>\n

A new control has been added that allows blocking specific NTRIP Clients<\/a> based on matching a full or partial text string to the NTRIP Agent string which they use (this is generally the product name and model being used).<\/p>\n

The control used for blocking specific emails<\/a> in the user account names has been reworked to make it easier to block an entire domain name.<\/p>\n

The layout of the IP blocking dialog has been reworked to reflect a better grouping of the various controls.\u00a0 A knowledge base article on the general use of IP blocking and the various control can be found here<\/a>.<\/p>\n

\"\"<\/a><\/strong><\/p>\n

NEAR Stream Improvements<\/strong><\/h3>\n

The functionality of the Verbose<\/strong> checkbox in the NEAR Stream tab<\/a> has been reworked and significantly increased. When checked, it now shows additional helpful information about the process of accepting<\/em> or rejecting<\/em> streams for the active NEAR pools<\/a>.\u00a0 For example, if a stream is not used in a given NEAR pool, the reason for this is now shown in the console logs.\u00a0 \u00a0Use this feature when debugging your NEAR streams.\u00a0 This checkbox always defaults to unchecked when SNIP<\/strong><\/span> is re-started, because it can produce large console logs.<\/p>\n

As a side effect of the improved filtering process for broadcast orbital messages (see PFAT<\/strong> below), the NEAR logic used to include<\/em> or exclude<\/em> a given base station stream was revised to ignore both the presence or the filtering of ephemeris messages when considering a given stream for use in a NEAR pool.<\/p>\n

Web API Improvements <\/strong><\/h3>\n

Improvements were made to the security model for the Web API<\/a> when used by Customer Accounts<\/a>.\u00a0 In the User account section are two buttons which can be used get a report of:<\/p>\n