# Revision history [back]

I assume from "when I type ifconfig" that this is a UN*X, not Windows.

Wireshark attempts to find "friendly names" for interfaces. On macOS, for example, the en0 interface on my machine shows up as "Wi-Fi" in, for example, the Network pane of System Preferences; that's its "friendly name". That's different from the "UN*X name" of the interface, which is what shows up in ifconfig.

In the welcome pane (what you see if you fire up Wireshark by clicking on a Wireshark launch icon, for example), on my machine it shows an interface named "Wi-Fi: en0". That's displaying both the "friendly name" and the UNX name of the interface. If it can't find a "friendly name", it just shows the UNX name.

So, if you're seeing this on macOS, Wireshark should be showing both of the names.

As for tshark -D, it should also display the "friendly name" if it can determine it; however, what it shows is the UN*X name, followed by the "friendly name" in parentheses.

So, at least on macOS, you should still be seeing the UN*X names in Wireshark - and you should be seeing the "friendly names" in tshark -D, and thus this problem shouldn't show up.

Are you on some other UN*X, such as a Linux distribution, a *BSD OS, Solaris, AIX, etc.?

In any case, if this isn't Windows, and you're not seeing the UN*X names after the "friendly names" in Wireshark, that's a bug. Please give more details on what you're seeing, or report this as a bug on the Wireshark issue list.

(If this is Windows, then Windows hasn't really had the equivalent of "UNX names" since NT 4.0; it has "friendly names" (which may vary in how "friendly" they are - sometimes they are names such as "Local Area Connection", but sometimes they are names such as "Ethernet0", which are not much more friendly than UNX names. The names used by WinPcap/Npcap, which is what Wireshark uses to capture on Windows, are Really Ugly meaningless strings, so Wireshark doesn't show those to you at all. The "friendly names" also show up in the output of ipconfig /all, and that might also show a string indicating the type of adapter.)

I assume from "when I type ifconfig" that this is a UN*X, not Windows.

Wireshark attempts to find "friendly names" for interfaces. On macOS, for example, the en0 interface on my machine shows up as "Wi-Fi" in, for example, the Network pane of System Preferences; that's its "friendly name". That's different from the "UN*X name" of the interface, which is what shows up in ifconfig.

In the welcome pane (what you see if you fire up Wireshark by clicking on a Wireshark launch icon, for example), on my machine it shows an interface named "Wi-Fi: en0". That's displaying both the "friendly name" and the UNX name of the interface. If it can't find a "friendly name", it just shows the UNX name.

So, if you're seeing this on macOS, Wireshark should be showing both of the names.

As for tshark -D, it should also display the "friendly name" if it can determine it; however, what it shows is the UN*X name, followed by the "friendly name" in parentheses.

So, at least on macOS, you should still be seeing the UN*X names in Wireshark - and you should be seeing the "friendly names" in tshark -D, and thus this problem shouldn't show up.

Are you on some other UN*X, such as a Linux distribution, a *BSD OS, Solaris, AIX, etc.?

In any case, if this isn't Windows, and you're not seeing the UN*X names after the "friendly names" in Wireshark, that's a bug. Please give more details on what you're seeing, or report this as a bug on the Wireshark issue list.

(If this is Windows, then Windows hasn't really had the equivalent of "UNX "UN*X names" since NT 4.0; it has "friendly names" (which may vary in how "friendly" they are - sometimes they are names such as "Local Area Connection", but sometimes they are names such as "Ethernet0", which are not much more friendly than UNX UN*X names. The names used by WinPcap/Npcap, which is what Wireshark uses to capture on Windows, are Really Ugly meaningless strings, so Wireshark doesn't show those to you at all. The "friendly names" also show up in the output of ipconfig /all, and that might also show a string indicating the type of adapter.)