On Mon, Jul 15, 2002 at 11:33:38AM -0500, Beatriz Silva wrote:
> As I told before I am trying to write a program to capture OSPF
> packets in Windows. I know that the network interface names in Unix are
> eth0, eth1 and so on.
No, the interfaces in Linux are eth0, eth1, and so on.
They may have different names in other UNIX systems; the interfaces on
the Solaris machine I use at work have names like "hme2", "ge2", and
"ge3", and the interface on my home machine is named "fxp0" on FreeBSD
and "iprb0" on Solaris, and the interfaces on HP-UX will probably have
names like "lan0", "lan1", and so on..
> We can see that in the ethereal window when we start a capture. But
> what would be the interface names for Windows ? I see big names in
> ethereal and I hope it is not that.
Unfortunately, on Windows 2000 and later, it *is* that; it's some name
that includes a printable version of some unique ID for the interface,
not anything particularly nice. (NT 4.0 used names that were more like
the sort of names you have on UNIX systems. I don't know what Windows
95, 98, and Me use.)
> In tcpdump you have to enter with these interface names as parameters
> in the comandline and I do not know what to write.
WinDump and Tethereal both have a "-D" flag; if you run them with the
"-D" flag, they'll list the interface names.
