title: Fragmented UDP packets not received by application
body: <p>Very strange behavior...</p>
  
  <p>I have 3 machines:</p>
  
  <pre>
   -----------     ------------     -----------
   | A (x86) |-----| B (x86)  |-----| C (arm) |
   | sender  |     | receiver |     | sender  |
   -----------     ------------     -----------
  </pre>
  
  <ul>
  <li>A and B are Linux (Ubuntu 12.04) machines, kernel 3.2;</li>
  <li>C is an android (ICS) machine, kernel 3.0.8;</li>
  <li>All are connected via RJ45 cables;</li>
  <li>Connections are OK, network is set up correctly;</li>
  </ul>
  
  <p><strong>Issue is:</strong> when machine C (ARM-android) sends a UDP packet which payload size is over 1472 bytes (maximum payload before packet gets fragmented), server application on machine B is never able to receive it, ... regarding that:</p>
  
  <ul>
  <li>Source/Dest IP addresses are correct: I can receive all the datagrams I send if I set the payload size less or equal to 1472;</li>
  <li>On machine B (receiver), if I dump network traffic with Wireshark, I can see each fragment, and then re-assembled message => from Wireshark point of view, it's all good!</li>
  <li>Comparing each fragment header as well as re-assembled message with what I can dump when the same message is sent from machine A (which is always received OK), everything seems perfect (only differences are IP addresses, and checksum, since UDP header checksum takes in account IP address fields).</li>
  <li>There is no MTU issue, packets are fragmented as expected.</li>
  <li>There is no router/switch between the machines</li>
  <li>ifconfig shows neither packets drop, nor overflows, nor any other classical error!</li>
  <li>... this is so weird!!</li>
  </ul>
  
  <p>I've spent some time on Internet, but never found any topic like this one. Each time people has troubles with UDP, either their MTU discovery was not correct, or they did some mishandling in the testing procedure, or they could not dump message on receiver host, ... this is not the case here!!</p>
  
  <p>For sure, I know issue is on sender end (machine C), but maybe is could be easier to enable some logs (at kernel level?) on receiver end to understand why UDP datagram disappears!? Any advice? Are there specific files I could check in /proc/sys/net, or kernel options I should enable?</p>
  
  <p>Thanks a lot.</p>