"usb0", "usb1", …: USB interfaces, see CaptureSetup/USB "nas0", "nas1": ATM bridging as in RFC 2684 (used e.g. "gre0", "gre1": GRE tunneling (Cisco), see "tunl0", "tunl1": IP in IP tunneling, see "br0", "br1", …: Bridged Ethernet, see Ethernet Bridge + netfilter Howto "team0", "bond0": Combined interfaces (i.e. "wlan0", "wlan1", …: Wireless LAN, see CaptureSetup/WLAN "ppp0", "ppp1", …: PPP interfaces, see CaptureSetup/PPP "eth0", "eth1", …: Ethernet interfaces, see CaptureSetup/Ethernet "lo": virtual loopback interface, see CaptureSetup/Loopback "any" : virtual interface, captures from all available (even hidden!) interfaces at once Other names: other types of interfaces, with names that depend on the type of hardware see the appropriate page under CaptureSetup "ppp0", "ppp1", etc.: PPP interfaces, see CaptureSetup/PPP "lo0": virtual loopback interface, see CaptureSetup/Loopback On most systems you can get a list of interfaces by running "ifconfig" or "ifconfig -a".
Wireless interfaces can usually be detected with names containing: "Wireless", "WLAN", "Wi-Fi" or "802.11", see CaptureSetup/WLAN for capturing details. "Generic NdisWan adapter": old name of "Generic dialup adapter", please update Wireshark/WinPcap! "Generic dialup adapter": this the name of the dialup interface (usually a telephone modem), see CaptureSetup/PPP WinPcap provides some special interface names: The interfaces names are provided by the network card manufacturer, which can be helpful to identify an interface. There are some common interface names which are depending on the platform. even completely hide an interface from the capture dialogs.In the Wireshark preferences (Edit/Preferences/Capture), you can: If you are unsure which interface to choose this dialog is a good starting point, as it also includes the number of packets currently rushing in. The "Capture/Interfaces" dialog provides a good overview about all available interfaces to capture from. Required interface not listed (or no interfaces listed at all).
0 kommentar(er)
