NTRIP streaming can be enabled in the configuration by entering the following command: enabled=1 This setting should be changed to: enabled=0 No information should be sent over NTRIP until a server is configured to receive it. To enable NTRIP on the server, add the following code to the NTRIP.conf file: enabled=1 To enable NTRIP on the clients, add the following code to the ntrip.conf file on each client: enabled=0 To disable NTRIP on the server, remove the enabled=1 code in NTRIP.conf or comment it out. To disable NTRIP on the clients, delete the enabled=0 code in ntrip.conf or comment it out.

Detect Network Outage

First, a general troubleshooting method:
To detect if there is an NTRIP network outage, use the following command. If the output of this command is "NO", then there is no issue with the server or client. The output will be "YES" if the server cannot receive data from the clients:
/usr/sbin/ntrip -v
If you want to detect if NTRIP is enabled and sending packets, run this command:
/usr/sbin/ntrip -v | grep enabled
Now that we have discovered that NTRIP is sending data on the server and receiving it from clients, let's troubleshoot by looking at some specific information about the network connection. NTRIP has two types of connections:
- Server connection communication: This type of connection uses UDP to send packets. This type of connection uses RAW sockets.
- Client connection communication: This type of connection uses TCP to send packets. This type of connection uses RAW sockets.

Timeline

Published on: 11/17/2022 05:15:00 UTC
Last modified on: 11/21/2022 19:41:00 UTC

References