Hi, On Thu, Aug 10, 2017 at 7:59 AM, Balz <Sebastian.balz@xxxxxxxxxx> wrote: > Hi, > > as mention the packages seems to be valid expected the package size of 143. > I tried to manipulate the kernel module so that is read the SRAM but I've > trouble with reading the correct frame length. For me that is to deep into > kernel programming (I have no knowledge with the Linux kernel). > so you mention that you got a frame length which is not valid. It can't be large than 127. This is an on the air field (PHR), so it could be that somebody while transmitting is wrong. _IMPORTANT_ this (PHR) field is not part of CRC (FCS). Also we filter on such frame length and read the whole framebuffer then and trim it to 127 bytes (for monitoring could be interesting)... I would check with an e.g. ATUSB if you receive the same frames... I would only trust other sniffer devices if you know how they filter or simple drop such frames or do whatever their policy is. btw: I bet many other drivers doesn't check on valid PHR field and so far they run into bufferoverflows... - Alex -- 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
