{"id":9119,"date":"2024-07-29T19:35:15","date_gmt":"2024-07-29T19:35:15","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=9119"},"modified":"2024-08-14T21:56:43","modified_gmt":"2024-08-14T21:56:43","slug":"release-3_15_00-changes","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/release-3_15_00-changes\/","title":{"rendered":"Release 3_15_00 Changes"},"content":{"rendered":"

What is new in the SNIP<\/span> 3_15_00 release<\/strong> – released July 30th, 2024
\n(updating the prior release of 3_14 issued on April 12th, 2024, final update August 14th 2024)<\/p>\n

Release 3_15_14 Update Note<\/strong><\/span><\/h3>\n

We had three deployments that reported a problem with the original Rev 3_15_00 release (out of hundreds who has download and installed at that time).\u00a0 Push-In<\/a> connections caused a strange (and fatal) race condition in the way base station resources were being allocated on these machines.\u00a0 The 3_15_14 release corrects this problem but is otherwise is the same.<\/p>\n

This is the next production release of SNIP<\/strong><\/span> following the Rev 3_14 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

Major IP Ban \/ Block Logic Changes<\/strong><\/h3>\n

Major changes have been made to the logic that monitors and detects connection abuse and then temporarily bans \/ blocks the offending IPs from connecting to the Caster.\u00a0 Please read this article<\/a> for a review of all the controls and their uses.<\/p>\n

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

Three new controls and associated logic were created to augment the existing controls as follows:<\/p>\n

Max Connections \/per User<\/strong>
\nThis control detects devices that repetitively make too many re-connection attempts in any one minute period.<\/h4>\n

Max Connections \/per IP<\/strong>
\nThis control detects devices that create multiple TCP\/IP sockets without correctly closing their prior sockets.<\/h4>\n

Max Input Data Rate<\/strong>
\nThis control detects devices that send in way too much data to be valid.<\/h4>\n

These new controls can be disabled by Unchecking<\/strong> the associated check box for each. For more details see this article<\/a>.<\/p>\n

The display of banned \/ blocked IPs was also reworked into a more concise table summary.\u00a0 Pressing List<\/strong> on any category of entry will produce a full list of those IPs in the console display.\u00a0 The resulting entries hyperlink to a full report about each IP as well.<\/p>\n

Important:<\/strong><\/span> In prior releases of SNIP<\/strong><\/span> (prior to Rev 3.15) the IP Ban \/ Block Logic functionality was NOT present in the Lite<\/em><\/strong><\/span> models of SNIP<\/strong><\/span>, and had various restrictions in the Basic<\/em><\/strong> <\/span>models of SNIP<\/strong><\/span>.\u00a0 This has now been changed. All models of SNIP<\/strong><\/span> now have the full functionality of the Ban \/ Block Logic.\u00a0 If you are a Lite<\/em><\/strong><\/span> or Basic<\/em><\/strong><\/span> model user, please be sure to update your copy and then enable this dialog to take advantage of these new features.<\/p>\n

These changes were largely motivated by events during the Spring 2024 planting season for the Northern Hemisphere.\u00a0 One of our public casters (www.RTK2go.com<\/a>) suffered from degraded service for nearly three weeks. This was due to some new NTRIP Client devices with multiple software problems connecting to the service.\u00a0 Less than a dozen users damaged access for over a thousand other users and had to be removed.\u00a0 These devices have now been blocked. The above logic should detect anything similar if it occurs again. \u00a0If you are developing NTRIP Client<\/a> software, please follow the guidance you will find published by RTCM<\/a> to avoid such problems.\u00a0 Read the (free) NTRIP Best Practices Guide<\/a> you can find on the RTCM site.<\/p>\n

 <\/p>\n

Improved Map Displays<\/strong><\/h3>\n

Use of the built in copy of Chrome within SNIP<\/strong><\/span> has been almost entirely eliminated in favor of using the local browser of the host machine.\u00a0 This is most evident in the Map display commands.\u00a0\u00a0 This speeds up the display of the map while also making the Caster more responsive to core requests.\u00a0 The maps can be displayed using a base map provided by either Goggle or Open Street Maps (OSM).\u00a0 This is controlled by the Map Preferences<\/a> dialog.<\/p>\n

When a map is invoked from SNIP<\/strong><\/span> itself from the Windows desktop, additional private details about the connected User Accounts and the Base Station is often shown.\u00a0 This information is NOT shown if the map was requested externally by a web page (such as the SNIP<\/strong><\/span> STATUS<\/a> command) to protect privacy. The general presumption is that any person sitting at the desktop should be treated as an Admin user because they have access to the entire Caster from that position.\u00a0 Requests coming into the Caster from the Web API<\/a> may or may not be treated as admin accounts depending the way you have setup the rights for the log-in account that is being used.\u00a0 See the knowledge base articles on customer accounts<\/a> and staff accounts<\/a> for further details.<\/p>\n

Near Streams<\/strong><\/h3>\n

When creating a collection of Base Stations to be used in a NEAR stream<\/a> by using a preset list<\/a>… \u00a0 A right-click<\/em> “Remove” menu item has now been added for each entry in the list.\u00a0 Combined with the existing Add All<\/em><\/strong> and Remove All<\/em><\/strong> buttons in the dialog, this should provide better functionality when editing long lists.\u00a0 [Added in Rev 3_15_14]<\/p>\n

Misc.<\/strong><\/h3>\n