I want to use the QoS (Quality of Service) Round Trip sensor to monitor the quality of the network connection between two of my probes. In the documentation for the QoS (Quality of Service) Round Trip sensor, I see the following note:
Note: You must ensure that firewalls, NAT rules, etc. will allow the UDP packets to reach the target probe. The Windows firewall on the target system will be automatically opened by the probe.
I have a few questions regarding this note:
- Which firewall settings are required exactly?
- Is this saying that the firewall configuration that already allows my PRTG core server to communicate with all of my remote probes is insufficient for the operation of the QoS (Quality of Service) Round Trip sensor?
- If I configure a QoS (Quality of Service) Round Trip sensor on my local probe, do I need to configure the firewalls on remote probes to allow inbound UDP traffic for this sensor?
- Firewall configuration is a hassle. Paessler could probably have avoided that by defining remote probes to automatically open those NAT rules by initiating testing to my local probe, right? This means having sensors on both ends.
- If all of this is necessary, would it not be simpler if I opened a single inbound port on my local firewall and configured QoS (Quality of Service) Round Trip sensors on the remote probes pointing at the local probe? It seems to be a lot of work given that they can already reach my core server.
- Also, I am looking for better ways to monitor non-VoIP connection quality. Would you say that the QoS (Quality of Service) Round Trip sensors are good for that as well?