Ed Stevens wrote: > > I would like to know how to start tcpdump 3.6 listening on all > interfaces such that the name of the interface is printed on each line > of output. > In tcpdump 3.4, this is easy: just start up without specifying an > interface. I expected that starting 3.6 with the 'any' interface > specified would do the same thing, but it doesn't. I really need to be > able to listen to all interfaces, AND to know which interface each > packet belongs to. > Here's an added note: I downloaded and built tcpdump 3.4.19, and I don't see the device names on output there either. Is this a compile-time option? Or should I be looking at an earlier version, say, 3.4.1? > A related (but less important) question: When tcpdump 3.4 listens on a > VLAN trunk on eth1, the interface names are reported as "if120", "if148" > and so on, the number varying according to which port on the switch the > source host is connected on. Where do these names come from? (The > numbers relate neither to the vlan ID of the port, nor to the virtual > interface device name assigned by ifconfig.) > > --- > Ed Stevens > Senior Software Designer, Atreus Systems Corporation > (613) 233-1741 x226 > http://www.atreus-systems.com -- Ed Stevens Senior Software Designer, Atreus Systems Corporation (613) 233-1741 x226 http://www.atreus-systems.com - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
