raiden00pl opened a new pull request, #21003:
URL: https://github.com/apache/nuttx/pull/21003

   ## Summary
   
   6LoWPAN read packets held in the device's IOB chain as one flat buffer, so 
the payload of any packet longer than one IOB (for example, ping6 above 56 
bytes) was read past the first IOB. Like the rest of the network stack, 6LoWPAN 
now keeps the packet in the IOB chain and copies it out with iob_copyout(). The 
socket send paths fill the IOB with devif_send(), as the UDP and TCP send paths 
do. The reply to a received packet is converted from the IOB in the 
netdev_input() callback, before the reassembly buffer is freed. 
     
   ## Impact
   
   Packets larger than one IOB can now be sent and replied to.
   
   ## Testing
   
   nRF52840-DK - nRF54LM20-DK pair:                                             
                                                                                
                                                                                
                                
   - ping6 at 56, 300, 1000 and 1232 bytes in both directions                   
                                                                                
                                                                                
                                
   - nettest TCP transfer of 4096 bytes                                         
                                                                                
                                                                                
                                
   - UDP datagrams of 96 and 1000 bytes                                         
                                                                                
                                                                                
                                
   - an ICMPv6 reject reply generated by ip6tables 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to