Guy Harris <g...@alum.mit.edu> wrote: >> It would be reasonable to anticipate additional characteristics that >> could make their way into a capture file for received traffic, such as >> RSSI and noise levels, antenna selection, etc. For the requested link >> types, the packet will start with the MAC Layer data (the 4-byte >> HomeID comes first), including an FCS, with no additional data. For >> captures that require RSSI or additional metadata to be associated >> with the packet, RadioTap or PPI could be used similar to what is >> already done for Bluetooth Low Energy and other wireless protocols.
> So presumably new LINKTYPE_/DLT_ values will be requested for the > captures with metadata, once the format for the metadata is specified? (and maybe we'll get to pcapng as default before then...) -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers