https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3096
--- Comment #50 from Michael Tüxen <tuexen@xxxxxxxxxxxxx> 2012-02-14 14:43:45 PST ---
(In reply to comment #49)
> (In reply to comment #48)
> > (In reply to comment #46)
> > > so it explicitly speaks of multiple IDBs. (Arguably, "dumpcap -i any -w
> > > file.pcapng" should write IDBs for the real interfaces rather than the "any"
> > > interface, but that's a bit more work; what's really wanted there is some help
> > > from libpcap.)
> > I think dumpcap -i any -w file.pcapng should only use a single IDB specifying
> > the any interface (only on Linux, of course). Since this is what the user
> > specifies
>
> What the user specified is "capture on all interfaces", not "capture on the
> 'any' interface"; there is no network interface named "any".
>
> Think of it as being like "ls *". "ls *" doesn't just print "*", it prints the
> names of all files it matches; similarly users might want - and at least some
> *do* want, as expressed by messages to tcpdump-workers and libpcap/tcpdump bugs
> - to know which particular real interface packets came in on.
OK...
But if i remember it correctly, you get some specific linux cooked (pseudo)
header and
so on. So if we translate -i any to an explicit list, the user can't get
anymore what he
gets now. That is why I suggest to use a different way.
However, if we don't want to continue this functionality, we can interpret any
in the
suggested way.
Best regards
Michael
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.