2

I have two xbee S1s that successfully communicate with each other. But I am trying to get one of them to receive IEEE 802.15.4 frames from an Atmel transceiver. The goal, of course, is to "trick" an xbee into thinking it is talking to another xbee, when in reality it will be talking to the Atmel transceiver. The only way, as far as I can tell, to do this is to monitor the packets transmitted by an xbee using a sniffer and clone them on the Atmel transceiver.

And here are my findings:

The packet sniffer shows the following traffic when entering a single ASCII character "m" from an xbee S1:

enter image description here

The sniffer shows the following when sending a single ASCII character "k":

Sending single ASCII character "k"

The sniffer shows the following when sending the same ASCII character "k" 3 days ago:

enter image description here

Aside from time stamps, why would the payload have "ad" one day and "a**23*" another day?

Would appreciate if the wireless network experts from the community could weigh in.

user1068636
  • 1,871
  • 7
  • 33
  • 57

1 Answers1

1

Try to get a hex dump of those payloads. I would guess that some of the * characters are unprintable ASCII and vary as well. The payload probably has different header fields, possibly including an incrementing transaction ID. Does the target device's 64-bit IEEE address appear in those bytes? How about it's 16-bit network address? Maybe sender address? You'll need to figure out the packet format, and my guess is that it contains more variable data than just the character you're sending.

tomlogic
  • 11,489
  • 3
  • 33
  • 59
  • I took your suggestion and it got me closer. Looking at the hexdump I was able to notice bytes that stayed the same and bytes that change (incrementing by 1 modulo 256). I cloned these packets on the transceiver and the xbee successfully received 1 byte correctly, but all others bytes did not reach the xbee. I think I'm almost there. – user1068636 Aug 31 '13 at 16:52