2015-07-27 12:21 GMT+02:00 Alexander Aring <alex.aring@xxxxxxxxx>: > On Mon, Jul 27, 2015 at 12:08:18PM +0200, Baptiste Clenet wrote: > ... >> >> Receiving side: >> [ 176.921637] CID flag is set, increase header with one >> [ 176.931640] NH flag is set, next header carried inline: 02 >> [ 176.942502] SAC bit is set. Handle context based source address. >> [ 176.954397] >> [ 176.957352] ieee802154 phy0 wpan0: SAM value 0x3 not supported >> > > Yes this is not what it was transmitted before from the other node. > That's why I would ask for some sniffing device, somewhere in the lower > layers mac or phy it will fill your frame with garbage. > > I can't tell you now if it's the transmitted node or the receiving node. > You need to debug it there. Yeah, I agree. > > To ensure the transmitted node don't send garbage I would like to check > it with some sniffer device. If you see garbage on the sniffer device > then it's something wrong with the transmitting. Ok, but I did sniffing with monitor0 on the receiver as I mentioned earlier. How may I sniff a packet ont the sender? Because I can't set up lowpan0 on top of monitor0. How may I sniff on lower layers? Also, I would add that even if I change the destination IP, I still receive the message. Shouldn't the transceiver blocks messages which are not addressed to it? > > - Alex -- 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
