Many thanks for answers :)
Sorry for the attachments, @Oleg - thanks for CloudShark.
I made two tests, first using CC1101 set and second using CC1125 set.
Test was very simple CC1101 node and CC1101 sniffer, then CC1125 node
and CC1125 sniffer (I wrote the driver basing on CC1101 driver). In bo
Hi!
There's actually quite a nice service to share Wireshark dumps at
https://www.cloudshark.org/
Using this page, you won't run into size restrictions on this mailing list the
next time.
Cheers,
Oleg
On Mon, Jan 04, 2016 at 01:49:17AM +0100, Mateusz Kubaszek wrote:
> Forgotten attachments...
>
Hi Mateusz,
as Kaspar already pointed out: the cc110x device is not a 802.15.4 device,
but has both different physical and link-layer from 802.15.4. However, our
sniffer script assumes the connected device is 802.15.4 device, so the PCAP
data you are receiving in wireshark are marked as 802.15.4 fr
Hey,
On 01/04/2016 01:46 AM, Mateusz Kubaszek wrote:
> A few days ago I ran a sniffer application using CC1101 transceiver.
The cc110x doesn't support 802.15.4 natively, so I wrote the driver to
"pretend" to be 802.15.4 to the upper layers, so we can re-use 6lowpan
and the rest of the network sta
Hi Mateusz,
could you please tell us, which board (and radio) you were using to send
out the 802.15.4 frames? Seems to me that you discovered a bug in RIOT,
which leads to a faulty address mode configuration somehow... Also would
you mind to attach your wireshark dump (as you forgot it in your
Hi everyone!
A few days ago I ran a sniffer application using CC1101 transceiver.
Sniffing device is connected via UART<->USB adapter to PC. A python sniffer
application redirects the frames to Wireshark (v. 2.0.0).
Sniffer was gathering frames from one node programmed with gnrc-networking
example
