Changeset 7152 in ntrip for trunk/BNC/src


Ignore:
Timestamp:
Jul 27, 2015, 3:25:22 PM (9 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/src/bnchelp.html

    r7151 r7152  
    591591
    592592<p><a name="ssl"><h4>3.2.2 SSL - Transport Layer Security</h4></p>
    593 <p>Communication with an NTRIP Broadcaster over SSL requires the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known NTRIP Server certificates. You may also just try communication via SSL to check out whether this is supported by the involved NTRIP Broadcaster. </p>
    594 <p>SSL communication may involve queries coming from the NTRIP Broadcaster. Tick 'Ignore SSL authorization errors' if you don't want to be bothered with this. Note that SSL communication is usually done over port 443.</p>
     593<p>Communication with an NTRIP Broadcaster over Secure Sockets Layer (SSL) as well as the download of RINEX skeleton files when available from HTTPS websites require the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known NTRIP Server certificates. You may also just try communication via SSL to check out whether this is supported by the involved NTRIP Broadcaster. </p>
     594<p>SSL communication may involve queries coming from the NTRIP Broadcaster or from a HTTPS website hosting RINEX skeletons. Such a query could show up under BNC's 'Log' tab as follows:
     595<pre>
     596SSL Error
     597Server Certificate Issued by:
     598GNSS Data Center
     599BKG (Bundesamt fuer Geodaesie und Kartographie)
     600Cannot be verified
     601
     602The issuer certificate of a locally looked up certificate could not be found
     603The root CA certificate is not trusted for this purpose
     604No certificates could be verified
     605</pre>
     606 Tick 'Ignore SSL authorization errors' if you generally trust the server and don't want to be bothered with this. Note that SSL communication is usually done over port 443.
     607</p>
    595608
    596609<p><a name="general"><h4>3.3. General</h4></p>
    … …  
    739752<p><a name="rnxskl"><h4>3.4.5 Skeleton Extension - optional</h4></p>
    740753<p>
    741 Whenever BNC starts generating RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. A HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <u>http://www.epncb.oma.be:80/stations/log/skl/brus.skl</u> for an example of a public RINEX header skeleton file for the Brussels EPN station.
    742 </p>
    743 <p>
    744 However, sometimes public RINEX header skeleton files are not available, their contents is not up to date, or you need to put additional/optional records in the RINEX header. For that BNC allows using personal skeleton files that contain the header records you would like to include. You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog. A file in the RINEX Observations 'Directory' with a 'Skeleton extension' suffix is interpreted by BNC as a personal RINEX header skeleton file for the corresponding stream.
     754Whenever BNC starts generating RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. A HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <u>http://www.epncb.oma.be:80/stations/log/skl/brus.skl</u> for an example of a public RINEX header skeleton file for EPN station Brussels. Note that the download of RINEX skeleton files from HTTPS websites requires the exchange of client and/or server certificates. Clarify 'SSL' options offered in panel 'Network' for details.
     755</p>
     756<p>
     757Sometimes public RINEX header skeleton files are not available, their contents is not up to date, or you need to put additional/optional records in the RINEX header. For that BNC allows using personal skeleton files that contain the header records you would like to include. You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog. A file in the RINEX Observations 'Directory' with a 'Skeleton extension' suffix is interpreted by BNC as a personal RINEX header skeleton file for the corresponding stream.
    745758</p>
    746759<p>
    … …  
    33973410Some limitations and deficiencies of the NTRIP Version 1 stream transport protocol are solved in NTRIP Version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are:
    33983411</p>
    3399 <p>
    3400 &nbsp; 1:&nbsp; NTRIP Version 1, TCP/IP.<br>
    3401 &nbsp; 2:&nbsp; NTRIP Version 2 in TCP/IP mode.<br>
    3402 &nbsp; 2s:&nbsp; NTRIP Version 2 in TCP/IP mode via SSL.<br>
    3403 &nbsp; R:&nbsp; NTRIP Version 2 in RTSP/RTP mode.<br>
    3404 &nbsp; U:&nbsp; NTRIP Version 2 in UDP mode.
    3405 </p>
     3412
     3413<p>
     3414<table>
     3415<tr></tr>
     3416<tr><td><b>Option &nbsp;  &nbsp; </b></td><td><b>Meaning</b></td></tr>
     3417<tr><td>&nbsp; &nbsp; 1</td><td>NTRIP Version 1, TCP/IP</td></tr>
     3418<tr><td>&nbsp; &nbsp; 2</td><td>NTRIP Version 2 in TCP/IP mode</td></tr>
     3419<tr><td>&nbsp; &nbsp; 2s</td><td>NTRIP Version 2 in TCP/IP mode via SSL</td></tr>
     3420<tr><td>&nbsp; &nbsp; R</td><td>NTRIP Version 2 in RTSP/RTP mode</td></tr>
     3421<tr><td>&nbsp; &nbsp; U</td><td>NTRIP Version 2 in UDP mode</td></tr>
     3422</table>
     3423</p>
     3424
    34063425<p>
    34073426If NTRIP Version 2 is supported by the broadcaster:
    … …  
    34093428<ul>
    34103429<li>Try using option '2' if your streams are otherwise blocked by a proxy server operated in front of BNC.</li>
    3411 <li>When using NTRIP Version 2 via SSL (option '2s') you need to specify the appropriate 'Caster port' for that. It's usually port number 443.</li>
     3430<li>When using NTRIP Version 2 via SSL (option '2s') you need to specify the appropriate 'Caster port' for that. It's usually port number 443. Clarify 'SSL' options offered in panel 'Network'.</li>
    34123431<li>Option 'R' or 'U' may be selected if latency is more important than completeness for your application. Note that the latency reduction is likely to be in the order of 0.5 sec or less. Note further that options 'R' (RTSP/RTP mode) and 'U' (UDP mode) are not accepted by proxy servers and a mobile Internet Service Provider may not support it.</li>
    34133432</ul>
Note: See TracChangeset for help on using the changeset viewer.