Re: [tcpdump-workers] Link-Layer Header Type request for Linux Kernel Messages

Hi, I guess area what I am working blur the boundaries of existing tools. So what about feature? (maybe it is time to little extend tool boundary) Linux Kernel Messages and Android Logs are similar to "syslog", ok, but think about wide perspective. The question are: 1. What can be supported by

[tcpdump-workers] website not updated

If tcpdump 4.4.0 and libpcap 1.4.0 are done should the webpage be updated or are they in some kind of beta form? I'll happily fix it on github if that's the right place to do it. -- WXS ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org h

[tcpdump-workers] radiotap header retry

Hi all, I have a question about the radiotap header 802.11. Is there in tcpdump a corresponding filter as wlan.fc.retry==1 in wireshark? Thanks a lot Ilaria ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelma

Re: [tcpdump-workers] Link-Layer Header Type request for Linux Kernel Messages

Hi, Ok. Let start thinking only about: LINKTYPE_DEV_KMSG_LINUX & DLT_DEV_KMSG_LINUX, other can be ignored because /dev/kmsg is only one which can be used easy and powerfully. Implementation on two sides is ready (libpcap and Wireshark) Pozdrawiam / Best regards ---

Re: [tcpdump-workers] website not updated

> "Wesley" == Wesley Shields writes: Wesley> If tcpdump 4.4.0 and libpcap 1.4.0 are done should the webpage be Wesley> updated or are they in some kind of beta form? I'll happily fix it on Wesley> github if that's the right place to do it. They are done, the web page isn't updat