tag:blogger.com,1999:blog-4359208343555922820.post221077632327867733..comments2024-01-12T06:26:30.504+00:00Comments on Random Tech Stuff: The STM32W-RFCKIT as a 802.15.4 network analyzer on LinuxJoeDhttp://www.blogger.com/profile/02413638198679968289noreply@blogger.comBlogger14125tag:blogger.com,1999:blog-4359208343555922820.post-16875863713715637352012-11-01T16:30:09.492+00:002012-11-01T16:30:09.492+00:00I believe the Contiki project is close to implemen...I believe the Contiki project is close to implementing 6LoWPAN on that hardware. I don't have the details right now, but I'm sure there is some tool to flash the devices there.Joe Desbonnethttps://www.blogger.com/profile/01861293299381288570noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-44007283405721056412012-11-01T16:07:35.974+00:002012-11-01T16:07:35.974+00:00Has anyone figured out how to flash these devices ...Has anyone figured out how to flash these devices under Linux?Brianhttps://www.blogger.com/profile/07071260460245753757noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-27918372253885818832012-11-01T16:06:59.317+00:002012-11-01T16:06:59.317+00:00Has anyone figured out how to flash these devices ...Has anyone figured out how to flash these devices under Linux?Brianhttps://www.blogger.com/profile/07071260460245753757noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-43722131068852847692012-04-27T21:17:32.708+01:002012-04-27T21:17:32.708+01:00Thank you very much for this tool,
a 802.15.4 / Zi...Thank you very much for this tool,<br />a 802.15.4 / ZigBee sniffer in Linux is very cool :-)<br /><br />I'm using it with a fifo/ named pipe as follows, works really well here.<br /><br />1) mkfifo snifferout<br />2) ./stm32w-wireshark /dev/ttyACM2 15 > sniffout<br />3) sudo wireshark -k -i sniffoutManuel Pietschmannhttps://www.blogger.com/profile/11965785941668635815noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-67787080932195113692012-04-27T01:56:24.571+01:002012-04-27T01:56:24.571+01:00I got it working this time.
I think I was using th...I got it working this time.<br />I think I was using the dongle with out it being flashed.studenthttps://www.blogger.com/profile/11237128679757489609noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-18938847949039441142012-04-26T11:03:00.280+01:002012-04-26T11:03:00.280+01:00Try leaving out Wireshark for the moment. Just spe...Try leaving out Wireshark for the moment. Just spew hex to the screen:<br />./stm32w-wireshark -f hex /dev/ttyACM0 15<br /><br />One side effect of invoking Wireshark the way I mentioned is that when you close it the stm32w-wireshark process does not automatically go away. You may need to check if existing processes are already running:<br />ps -auxw | grep stm32w-wireshark<br /> and kill them:<br />killall stm32w-wireshark<br /><br />I must come up with a better way of invoking this tool + Wireshark together.Joe Desbonnethttps://www.blogger.com/profile/01861293299381288570noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-1622550861107627892012-04-26T04:37:00.996+01:002012-04-26T04:37:00.996+01:00This comment has been removed by the author.studenthttps://www.blogger.com/profile/11237128679757489609noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-54433805659777543172012-04-26T04:33:47.533+01:002012-04-26T04:33:47.533+01:00I got to see zigbee frames using windows. And I tr...I got to see zigbee frames using windows. And I try to get it working on Linux but wireshark just says "Waiting for capture input data..." even though i have a device transmuting zigbee back and forth. <br />I am thinking there is an error because when i enter the command to run wireshark like so:<br /><br />wireshark -k -i <( ./stm32w-wiresharkv2 /dev/ttyACM0 15 -d 9 )<br />device=/dev/ttyACM0<br />channel=15<br />DEBUG: debug level 9<br />Writing command 0x10 (set channel),<br /><br />I think the last line is an error but I don't know lots of c.studenthttps://www.blogger.com/profile/11237128679757489609noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-20737551447153176072012-04-21T12:04:47.800+01:002012-04-21T12:04:47.800+01:00@legodude: No, the name you give the key doesn'...@legodude: No, the name you give the key doesn't matter. With the latest version of Wireshark you can enter multiple keys and it will try them all until one works. So if in doubt plug in a few variations. The "ZigBeeAlliance09" key is default for Home Automation, but I'm not sure about Smart Energy.<br /><br />Is this a meter installed by a utility company? If so, it's possible the key is not public (after all, do you want anyone near your home knowing how much electricity you're consuming, when you are at home etc).Joe Desbonnethttps://www.blogger.com/profile/01861293299381288570noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-15860509350656822852012-04-20T22:17:38.988+01:002012-04-20T22:17:38.988+01:00Hi Joe,
Poking around more, I realised that packet...Hi Joe,<br />Poking around more, I realised that packets I am interested in are encrypted. I actually found your message about Zigbee NWK decryption key, but I don't know if I have it working correctly.<br /><br />You wrote:<br />Security Level: AES-128 Encryption, 32-bit Integrity Protection<br />Network Key: 39:30:65:63:6E:61:69:6C:6C:41:65:65:42:67:69:5A<br />(that's the ASCII values of ZigBeeAlliance09 *in reverse*)<br /><br />I put this into the ZigBee NWK setting, as a preconfigured key with 'normal' byte order. Does keyname matter?<br /><br />I can't seem to get it to decrypt any data payloads, any hints?<br /><br />thanks<br />mikelegodudehttps://www.blogger.com/profile/08075536653478667201noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-9317213119324231162012-04-20T21:12:17.679+01:002012-04-20T21:12:17.679+01:00Hi,
Got your software working and am receiving dat...Hi,<br />Got your software working and am receiving data from my Itron electic meter, pretty neat. Thanks! I'm going to play around with it some more and let you know if I come up with any improvements<br />*mikelegodudehttps://www.blogger.com/profile/08075536653478667201noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-12013689289763036802012-04-17T18:10:57.626+01:002012-04-17T18:10:57.626+01:00hi, please write to me to rekrios@hotmail.com , i ...hi, please write to me to rekrios@hotmail.com , i have the question about com-sniffering, thxDrozdovhttps://www.blogger.com/profile/09204263962529513338noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-91027820583836461262012-04-13T14:06:19.844+01:002012-04-13T14:06:19.844+01:00@Graham: Oh, that's interesting. I wasn't ...@Graham: Oh, that's interesting. I wasn't aware of DLT. I must implement that. Let me google it first and I'll get back to you if I need help.Joe Desbonnethttps://www.blogger.com/profile/01861293299381288570noreply@blogger.comtag:blogger.com,1999:blog-4359208343555922820.post-79784337561850328442012-04-13T13:21:33.701+01:002012-04-13T13:21:33.701+01:00That looks interesting. I'm a Wireshark comit...That looks interesting. I'm a Wireshark comitter, although this isn't an area I've worked on I'd like to help you out.<br /><br />To include the RSSI data (and the channel and clock info if you wish), yo need a new encapsulation type (a DLT) and then just pass the extra data prepended onto the 802154 packet. When Wireshark reads that type it can call the appropriate dissector that strips the preamble, decodes it and adds it to the display and then passes the remaining 802154 packet over to the regular dissector.<br /><br />Email if you want some help.Grahamhttps://www.blogger.com/profile/01479835043774003824noreply@blogger.com