{"id":869,"date":"2016-03-22T11:03:29","date_gmt":"2016-03-22T11:03:29","guid":{"rendered":"\/?post_type=ht_kb&p=869"},"modified":"2019-10-09T18:46:02","modified_gmt":"2019-10-09T18:46:02","slug":"how-to-read-a-mountpt-string","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/how-to-read-a-mountpt-string\/","title":{"rendered":"How to read a MountPt string"},"content":{"rendered":"

A MountPt<\/strong> (or a “mount point” when the term is fully spelled out) is the specification by which an NTRIP client connects to a data stream on an NTRIP Caster.\u00a0 Often the term refers to just the unique string name, and most NTRIP clients think in terms of that string.<\/p>\n

Very Important to remember:<\/strong><\/span> MountPt strings that determine what data stream to use in the Caster Table are ALWAYS<\/strong> case sensitive.\u00a0\u00a0 They are always one word<\/span>.\u00a0 They do not have leading or trailing spaces, nor do they have odd characters (!@#$%^&*();:'”,etc.) \u00a0 They are always a unique string in the table.\u00a0 They tend to start with a letter.<\/p>\n

For example:\u00a0 If a user entered a “close” mountPt in his NTRIP Client software (say one that varies only by the capitalization), then SNIP<\/strong><\/span> will warn you the owner\/operator about it on the console.\u00a0 But the end user will simply see a disconnect and the current caster table returned.<\/p>\n

Hint<\/span><\/strong>:\u00a0 You can always take a quick look at what any caster table looks like by pointing your favorite browser to it.\u00a0 That is a good way to confirm that what you think might be there really is.<\/p>\n

Each “full” mountPt consists of several distinctive parts and is commonly expressed as a string.\u00a0 SNIP<\/strong> <\/span>uses a common format style shared by many tools to display this data.\u00a0 These strings appear in log reports and other places. The article describes how to read these strings.\u00a0 The term mountPt<\/em> refers to either the unique Caster table entry or the full specification, depending on the context of us.<\/p>\n

A mountPt string consists of up to five<\/span> separate parts,
\nseparated by four<\/span> single character delimiters [ ; @ ; \/ ]<\/p>\n

UserName\u00a0 <\/strong>:\u00a0 Password\u00a0 <\/strong>@\u00a0 casterURL\u00a0 <\/strong>:\u00a0 Port\u00a0 <\/strong>\/\u00a0 mountPt<\/strong><\/p>\n

The user portion is optional (it may be absent) and it may be encoded in a Base64 <\/a>format (in which case the first “:” is missing). In most SNIP<\/strong> <\/span>reports, an encoded user and password are shown as XX:XX to protect privacy.<\/p>\n

As an example, if you wished to connect to a caster at 12.34.56.78 operating at port 8080 and a mount point called “test,” then the examples below are all valid mountPt strings:<\/p>\n