https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1882
--- Comment #5 from Guy Harris <guy@xxxxxxxxxxxx> 2010-11-10 14:22:48 PST ---
There's "interface name" as in "description intended to be human-readable" and
there's "interface name" as in "what gets passed to pcap_open_live(),
pcap_create(), or pcap_open()".
There is, in fact, no guarantee that there *is* a description, and it could
well be a fairly clunky string.
*If* you're capturing on an interface, rather than capturing from a pipe, there
*is* a guarantee that there's a name passed to the pcap routine. From the
example given:
/tmp/wireshark.2007-04-15--1355.eth0.asdfGth
he probably meant the name passed to the pcap routine, e.g. "eth0".
On Windows, the full name in Chris's example would be
\Device\NPF_{7798FBA2-0E70-403F-BFD4-76F44AFB62FD}
("(Intel(R) 82567LM Gigabit Network Connection (Microsoft's Packet Scheduler)"
is the description); we'd probably want to just extract the UUID from that
name, e.g.
{temp
directory}\wireshark.2010-11-10--1355.7798FBA2-0E70-403F-BFD4-76F44AFB62FD.asdfGth
which is a *bit* long. On UN*X, it'd be somewhat simpler, as UN*X interface
names tend to be short and sweet.
If we're capturing on a pipe, we should probably just choose the last component
of the pathname of the pipe.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
