{"id":8884,"date":"2023-10-24T21:59:35","date_gmt":"2023-10-24T21:59:35","guid":{"rendered":"https:\/\/www.use-snip.com\/kb\/?post_type=ht_kb&p=8884"},"modified":"2023-10-30T21:27:24","modified_gmt":"2023-10-30T21:27:24","slug":"release-3_12_00-changes","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/release-3_12_00-changes\/","title":{"rendered":"Release 3_12_00 Changes"},"content":{"rendered":"

What is new in the SNIP<\/span> 3_12_00 release<\/strong> – released October 30th, 2023
\n(updating the prior release of 3_11 issued on September 08th, 2023)<\/p>\n

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

Reports<\/strong><\/h3>\n

All requests for any report, GIS map, or various other summaries are now processed in different ways based on \u00a0the callers source IP.\u00a0 This provides two important benefits, improved security, and correct IP use in linkages in the report. \u00a0This also has value with SNIP<\/strong><\/span> hosted on \u00a0virtual machines (VMs, such as an AWS hosted deployments) whenever local loop-back rules prohibit the machine from asking for web pages from itself.\u00a0 In more detail\u2026\u00a0\u00a0 When the request is made from inside<\/em><\/strong> SNIP<\/strong><\/span> (using the document viewer<\/a> or various menu commands), the local IP of the host machine is used in the replies and the request is always granted admin rights. \u00a0When the request is made from inside<\/em><\/strong> the machine using any local browser, the host machine local IP is used in the replies and the request may be granted admin rights depending on the report.\u00a0 When the request is made from outside<\/em><\/strong> the machine (from an IP that is not the host or the public IP of the machine) the request is processed as usual, complete with security checks for the requesting parties privileges. \u00a0Various links found in the report are adjusted to follow this process as well.<\/p>\n

As a result of the above most \u201cs-reports\u201d (SNIP<\/strong><\/span> reports) are now only used with inside the SNIP<\/strong><\/span> document viewer<\/a>.<\/p>\n

In Rev 3.11 Base Station reports were providing details regarding connected users (NTRIP Clients<\/a>) when they should not have. These reports should ONLY<\/strong> provide such details when a user with Admin rights has requested the report. This has now been corrected.<\/p>\n

A few additional map display reports also now make use of the newer display style and format that was introduced in Rev 3.11 \u00a0\u00a0The older map style has not yet been removed, this will occur in a future release.<\/p>\n

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

A minor bug was found and corrected in serial port<\/a> data streams when this type of stream was used in any NEAR streams<\/a>.\u00a0 Short lapses in data resulting in no observational message content were not being detected as they are in other stream types<\/a>. \u00a0As a result of this, any users (NTRIP Clients<\/a>) which were connected to serial stream by way of a NEAR stream were being starved and were not being automatically switched to a more suitable data stream. \u00a0The operation is now working correctly; should there be any data starvation events, after ~5 seconds, the base station serial stream is removed from the NEAR pool and any connected users are then automatically connected to the best alternative stream.\u00a0 The offending base station may rejoin the after a period of correct operation has again elapsed.<\/p>\n

IP Processing<\/strong><\/h3>\n

This release corrects a bug where URL strings with \u201c4-part\u201d names (in other words, a domain with two<\/em> levels of sub-domains like \u201cpositionz-rt.linz.govt.nz\u201d) were not being resolving into the correct IP value.<\/p>\n

Also corrected a bug where some newly blocked IP values, when the value was \u00a0entered using the menu command:\u00a0 Setup<\/strong> \u21d2 IP Ban\/Block Settings<\/strong> \u21d2 Block an IP<\/strong> were not always being saved to the settings file.<\/p>\n

Map and GIS Displays <\/strong><\/h3>\n

The simple \u201cmap it\u201d link (used in base station reports and tool tips) was not shown at all times for some base stations.\u00a0 This has been corrected. Pressing this link will open the default browser on the host machine and open a “plain Jane” Goggle map which is centered at the base station location.\u00a0 \u00a0This allow general GIS browsing of the nearby area, while some of the other map produce specialty maps which are centered on the base station along with coverage circles and also show other nearby base stations and any connected users \u2013 each with detailed pop up reports.<\/p>\n

In tables for several reports the country of origin has now been added to the display even when the specific city is not known.<\/p>\n

SNIP<\/span> Service Monitor Update
\n<\/strong><\/h3>\n

The Service monitor tool has been updated to Rev 1.3<\/strong> with this release.\u00a0 The new release is installed automatically with the update (the program is called: \u201cSNIPserviceMon.exe<\/strong>\u201d).\u00a0\u00a0 This update was promoted by a Danish deployment that reported that the tool falsely presumed that the “fall back” the seasonal change in the local time (daylight saving time) was a stalled copy of SNIP<\/strong><\/span> needing a restart.\u00a0 The new tool correctly detects system time changes and processes them correctly.<\/p>\n

 <\/p>\n

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