Path measurement: Difference between revisions

Path measurement (view source)

1 byte added , 23 April 2020

no edit summary

1,775

edits

Revision as of 06:56, 23 April 2020 (view source) Soumar (talk \| contribs) No edit summary ← Older edit		Revision as of 06:56, 23 April 2020 (view source) Soumar (talk \| contribs) No edit summary Newer edit →
Line 130:		Line 130:

	# Due to technical reasons, large clock adjustments cannot be filtered out so if that happens, a very large two-way-latency is measured. Both devices does not need to be time synchronized but large adjustments shall not happen. That means that time synchronization (for example via NTP) should be enabled on both devices or disabled on both devices for best results. However, such clock adjustment miss-measurements are one-time events and will not lead to false values for the following packets.		# Due to technical reasons, large clock adjustments cannot be filtered out so if that happens, a very large two-way-latency is measured. Both devices does not need to be time synchronized but large adjustments shall not happen. That means that time synchronization (for example via NTP) should be enabled on both devices or disabled on both devices for best results. However, such clock adjustment miss-measurements are one-time events and will not lead to false values for the following packets.

	# The maximum supported packet size for the path measurement is currently 2048 bytes. Larger packets are truncated for the measurement.		# The maximum supported packet size for the path measurement is currently 2048 bytes. Larger packets are truncated for the measurement.