On 08/03/2012 07:25 PM, Tony Cheneau wrote: >>> - UDP header compression is broken: the header is compressed >>> correctly, however both compressed and uncompressed header are sent >>> on the air. Because the code is broken on the sender and the >>> receiver, it still works. I have a patch for that (saves a few >>> bytes in the packet). >>>
Hi Tony, As far as UDP goes, I made a simple UDP client/server to see if I can get one packet across the link that wasn't ICMP6. The packet[1] is sent and looks good in wireshark, but the receiver bounces it back with an ICMP6 packet which Wireshark dissects as saying "Parameter Problem, unrecognized next header encountered." That seems different than the UDP issue you described. Is this something you've seen before? Alan. [1] http://www.signal11.us/~alan/next-header.pcap.gz ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
