This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 5 and 6
Revision 5 as of 2005-05-18 07:23:58
Size: 1886
Editor: UlfLamping
Comment: tweak text format
Revision 6 as of 2005-05-18 19:37:40
Size: 1885
Editor: GuyHarris
Comment: Get rid of excess ).
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 * [ Microsoft: How To Install Microsoft Loopback Adapter in Windows 2000])  * [ Microsoft: How To Install Microsoft Loopback Adapter in Windows 2000]

Loopback capture setup

The following will explain capturing on loopback interfaces a bit.

If you are trying to capture traffic from a machine to itself, that traffic will not be sent over a network interface, even if it's being sent to an address on one of the machine's network adapters. This means that you will not see it if you are trying to capture on, for example, the interface device for the adapter to which the destination address is assigned. You will only see it if you capture on the "loopback interface", if there is such an interface and it is possible to capture on it; see the next section for information on the platforms on which you can capture on the "loopback interface".

Supported Platforms

See [ Ethereal: Supported Capture Media] page for Ethereal capturing support on various platforms. Summary: you can capture on the loopback interface on Linux, on various BSDs including Mac OS X, and on Digital/Tru64 UNIX, and you might be able to do it on Irix and AIX, but you definitely cannot do so on Solaris, HP-UX, or Windows.


There is a Microsoft Loopback Adapter available from Microsoft:

... which is quite different than the ones available for various UN*X systems. This adapter is a virtual network adapter you can add, but it will not work on the IP address interfaces; it will take its own IP address. You won't see any internal traffic until you direct it through that adapter.

CaptureSetup/Loopback (last edited 2020-01-30 19:15:46 by ChristopherMaynard)