tcpdump mailing list archives
Re: [Wireshark-users] Filtering both vlan-tagged as untagged frames with an ip-filter
From: Joerg Mayer <jmayer () loplof de>
Date: Wed, 2 May 2007 09:46:55 +0200
From a thread at wireshark-users, but this concerns libpcap.
On Tue, May 01, 2007 at 11:38:26PM -0700, Guy Harris wrote:
Does it count as a bug if it's documented to work that way? :-) To quote the OS X 10.4.9 tcpdump man page (this isn't WinPcap-specific - it's common to all libpcap/WinPcap implementations):
Well, it's not a bug per se, but I really think that the capture syntax manpage should be part of libpcap and not of tcpdump. I know of a few systems that have wireshark installed but not tcpdump. Also, it is possible to build tcpdump with older versions of libpcap where the capture syntax might be different. Would a patch to move the capture syntax into its own manpage and into the libpcap package be acceptable? If so, I'm willing to produce one. ciao Joerg -- Joerg Mayer <jmayer () loplof de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Current thread:
- Re: [Wireshark-users] Filtering both vlan-tagged as untagged frames with an ip-filter Joerg Mayer (May 02)
- Re: [Wireshark-users] Filtering both vlan-tagged as untagged frames with an ip-filter Michael Richardson (May 02)
- Re: [Wireshark-users] Filtering both vlan-tagged Guy Harris (May 02)
- Re: [Wireshark-users] Filtering both vlan-tagged Joerg Mayer (May 02)
- Re: [Wireshark-users] Filtering both vlan-tagged Luis Martin Garcia (May 02)