This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
playground:wiki3:network_delays [2020/03/19 17:33] dlr [Samples of configuration] |
playground:wiki3:network_delays [2020/03/19 17:39] dlr [Very bad backhaul (>1000ms)] |
||
---|---|---|---|
Line 139: | Line 139: | ||
<code>1200 + 350 + 50 + 1200 = 2800ms</code> | <code>1200 + 350 + 50 + 1200 = 2800ms</code> | ||
- | On each end-device, and on the dashboard configuration of the end-device, the RX1 window delay has to be adjusted to a greater value. For example, setting RX1 to 2000ms (to reach the RX2 window) or 3000ms (to reach the RX1 window) is fine. | + | On each end-device, and on the WMC end-devices configuration interface, the RX1 window delay has to be adjusted to a greater value. For example, setting RX1 to 2000ms (to reach the RX2 window) or 3000ms (to reach the RX1 window) is fine. |
- | Indeed, the delay calculated above is 2800ms, so if RX1 delay is 3000ms, it is reachable. | + | This solution is possible at the cost of provisioning every end-devices of the network, so that it can work with high latencies. This network configuration is useful with satellite backhaul, for example. |
- | + | ||
- | This is possible at the cost of provisioning every end-device on the network so that it can work with high latencies. This can be useful with satellite backhaul, for example. | + | |