2015-07-24 18:24 GMT+02:00 Stefan Schmidt <stefan@xxxxxxxxxxxxxxx>: > Hello. > > On 24/07/15 17:14, Baptiste Clenet wrote: >> >> 2015-07-24 16:51 GMT+02:00 Stefan Schmidt <stefan@xxxxxxxxxxxxxxx>: >>> >>> Hello. >>> >>> On 24/07/15 16:45, Baptiste Clenet wrote: >>>> >>>> 2015-07-24 15:07 GMT+02:00 Alexander Aring <alex.aring@xxxxxxxxx>: >>>>> >>>>> On Fri, Jul 24, 2015 at 02:53:52PM +0200, Baptiste Clenet wrote: >>>>> ... >>>>>> >>>>>> Yes if SAC = 1, SAM should be 0 I agree. >>>>>> >>>>>> Is that somehow possible that I send ihpc of 7b39 (taken at the end of >>>>>> lowpan_header_compress) and I receive and iphc of 7bf9 (taken at the >>>>>> begginning of lowpan_header_decompress) every time?? >>>>>> >>>>> So far I know that is not possible. I think you need to debug it, do >>>>> you >>>>> have maybe some kind of monitor interface to see what on the air? >>>>> >>>> Here is what tcpdump gives me when I receive a message: >>>> >>>> 13:15:40.253868 P ethertype Unknown (0x00f6), length 82: >>>> 0x0000: 41c8 13ef beff ff56 7863 ed54 89a7 cffb A >>>> ......Vxc.T.... >>>> 0x0010: f93a 0201 ff34 1234 8700 a5ee 0000 0000 >>>> .:...4.4........ >>>> 0x0020: fe80 0000 0000 0000 1234 1234 1234 1234 >>>> .........4.4.4.4 >>>> 0x0030: 0102 cfa7 8954 ede3 7856 0000 0000 0000 >>>> .....T..xV...... >>>> 0x0040: 05c7 >>>> >>>> There is neither 7b39 or 7bf9. >>>> Can't use tshark on openwrt. >>> >>> >>> That makes it harder as neccassary for debugging. Either try to use >>> something like netcat to bring the stream to you host and look at it with >>> wireshark or save it as pcap file, transfer it to your host and look at >>> it >>> with wireshark. >>> >>> Doing it like above is really error prone. Why would you make your life >>> harder as you should? :) >> >> Ok, will try with netcat as soon as I can, thanks. > > > Cool. >>>> >>>> Btw, why can't I add lowpan0 on top of monitor0? >>>> root@OpenWrt:/# ip link add link monitor0 name lowpan0 type lowpan >>>> RTNETLINK answers: Invalid argument >>> >>> >>> Hmm, why would you want to do that? A monitor interface should give you >>> all >>> the information you need during sniffing. For what do you want to add a >>> lowpan interface on top? >> >> I would like to send IPV6 packet (ping6) through the interface lowpan0. >> >> I think I misunderstood something here about sniffing packet and >> interface. Should I have lowpan monitor interface instead of the wpan >> monitor? > > > You want to use the same interface for sniffing normal data transfer? Yes this is what I wanted. Not > really a good idea imho. While sniffing you should keep that interface "read > only". Ok, thanks. > > If I got you right the case you want to debug is that you receive the SAM > value message on one device when sending a ping from another device, > correct? Yes, exactly. Thanks to some printk I can see the SAM value in lowpan_header_decompress and lowpan_header_compress (receiving and sending) but maybe sniffing the wpan0 will give me different results? >In this case you should use the mintor interface on the receiving > side and ping6 from the other device. That should give you the packet send > over the air which you can dissect in wireshark. Ok, will do that tomorrow with nc Thanks > > regards > Stefan Schmidt -- Baptiste -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
