On Sun, Jan 10, 2010 at 6:18 AM, Jon Smirl <[email protected]> wrote: > On Sat, Jan 9, 2010 at 8:06 PM, Dmitry Eremin-Solenikov > <[email protected]> wrote: >> On Sat, Jan 09, 2010 at 07:56:19PM -0500, Jon Smirl wrote: >>> On Sat, Jan 9, 2010 at 7:29 PM, Dmitry Eremin-Solenikov >>> <[email protected]> wrote: >>> > On Sat, Jan 09, 2010 at 07:25:23PM -0500, Jon Smirl wrote: >>> >> >> Why don't these look like 802.15.4 packets in wireshark? >>> >> > >>> >> > Do you use our patched wireshark? We've had to put some minor code >>> >> > changes there. >>> >> >>> >> Where are the changes you made, I don't see a diff in the git tree. I >>> >> already have some patches in my wireshark. >>> > >>> > Please take a look at: >>> > http://sourceforge.net/projects/linux-zigbee/files/linux-zigbee-sources/0.1/libpcap-1.0.0-ieee80215-arphrd.patch/download >>> >>> I added this one and I can decode the packets now >> >> :) >> >>> >>> > https://sourceforge.net/projects/linux-zigbee/files/linux-zigbee-sources/0.1/wireshark-1.0.5-ieee80215.4.patch/download >>> >>> Why can't the kernel code add the correct FCS? >> >> What for? Only for sniffing? That sounds strange. I think there should >> be some way to declare that we are returning via less bytes than we received, >> but I haven't found it at first glance and had no time to dig deeply >> there. In fact I think all libpcap/tcpdump/wireshark integration should >> be reviewed, updated and pushed upstream. However I had no time and >> Sergey (the man who originally did that stuff) also is silent now. > > It would probably be easier to add the FCS than to mess with Wireshark > since it will be present in packets that originate over the air.
Yes. However most (if not all) of simple transeivers (like at86rf230/231, mc1319x/20x, cc2x20 (I I'm not mistaken), etc.) strip it before returning packet to the MCU. Maybe we should just force the stack to extend the packet with two zero bytes in place of FCS? I'll think about this. >> >>> > Those are the changes required for *sharking packets from our stack. >>> > >>> >> >>> >> I'm able to sniff and decode 802.15.4 packets from the air. I use a >>> >> Raven stick. It does the 6lowpan expansion inside the stick since the >>> >> 6lowpan support inside wireshare doesn't match what is in Contiki. >>> > >>> > Hmmm. >>> >>> It would be better to get one of Mar's mc13224 boards going as a >>> sniffer. The Raven code is not able to receive packets at full wire >>> speed, the mc13224 code can. Raven also introduces a bunch of >>> overhead simulating Ethernet packets. >>> >>> Mar has a USB economote in the works with integrated JTAG. >> >> I hope to get mc13224v board RSN (on Monday-Tuesday). It's a custom >> board but according to the author it should be compatible with >> Freescale's USB sniffer dongle. However it will take some time for me >> to get in touch with it. > > What are you planning to run on it? Contiki, Z-stack, other? I'll try Contiki. Also I hope to be able to run Freescale code (to enchance testing of our stack). I don't really know what else. That will be my "experiments" board for the next period of time. > > >> >> -- >> With best wishes >> Dmitry >> >> > > > > -- > Jon Smirl > [email protected] > -- With best wishes Dmitry ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Linux-zigbee-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
