Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From a transport layer perspective, there is no different for UDP between a local network and the internet. However, there are various factors that can come into play:</p> <ul> <li>UDP lacks reliability. Performing a single write and synchronously blocking waiting for a response will have good results on a LAN with minimal noise the majority of the time. However, it may be worth modifying the client to expect data loss when going across the internet. If the applications are going to need a high degree of reliability, then consider a different transport layer protocol, such as TCP.</li> <li>If the server and client are on the same network, but the client is trying to connect to the server through the network's external IP, then verify that the gateway supports looping back internal traffic destined to the external IP.</li> <li>Perform a traceroute to verify the IP packet's <a href="http://en.wikipedia.org/wiki/Time_to_live" rel="nofollow">time to live</a> field is higher enough for routing between the client and server.</li> <li>Verify proper NAT support for routing devices between the client and server. <a href="http://tools.ietf.org/html/rfc4787" rel="nofollow">RFC 4787</a> describes UDP and NAT requirements in detail. <a href="http://en.wikipedia.org/wiki/UDP_hole_punching" rel="nofollow">UDP Hole Punching</a> may be required if the server is not actually publicly accessible.</li> </ul> <p>In most cases, if the client and server work on a LAN, then it is often a networking issue. It may be worth debugging networking with basic tools like <a href="http://en.wikipedia.org/wiki/Netcat" rel="nofollow">netcat</a> and using reliable connection-based protocol, such as TCP. Once connectivity has been observed, then swap to using the UDP client and server.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload