Date: Wed, 10 Apr 96 14:03:00 MET DST From: Greg Lehey <lehey.pad@sni.de> To: branson@longstreet.larc.nasa.gov (Branson Matheson) Cc: lehey.pad@sni.de, freebsd-questions@freebsd.org Subject: Re: Violently pulling out my hair Message-ID: <199604101206.OAA27198@nixpbe.pdb.sni.de> In-Reply-To: <199604101204.IAA12187@longstreet.larc.nasa.gov>; from "Branson Matheson" at Apr 10, 96 8:04 am
next in thread | previous in thread | raw e-mail | index | archive | help
>>> Allright so next i tried... >>> >>> branson@garion #tcpdump ether host 08:00:09:d4:65:ff >>> tcpdump: ethernet address used in non-ether expression >>> >>> This is really frustrating.. can any one help? >> >> This looks to me like tcpdump is going for the wrong interface. The >> message tells you that you can only use this option on an Ethernet >> or FDDI interface. Assuming that you are really trying to trace an >> Ethernet interface (say, ed0), try: >> >> tcpdump -i ed0 ether host 08:00:09:d4:65:ff > > That did work.. thanks... I am not sure why it needs the ethernet > interface to be specified... but I will do it in the future. RTFM. By default, tcpdump goes for the first network interface it finds. In almost every installation, this is the only ethernet interface. In your case, it obviously isn't. Try: $ netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 <Link>00.00.c0.bc.55.7d 27876404 0 33199370 0 1359110 ed0 1500 204.216.27 freefall.FreeBS 27876404 0 33199370 0 1359110 lo0 16384 <Link> 69899 0 69899 0 0 lo0 16384 your-net localhost.cdrom 69899 0 69899 0 0 ppp0* 1500 <Link> 0 0 0 0 0 ppp1* 1500 <Link> 0 0 0 0 0 sl0 552 <Link> 427566 29 423782 5 0 sl0 552 204.216.27. jkh-sl0-f.cdrom 427566 29 423782 5 0 sl1* 552 <Link> 0 0 0 0 0 The example is from freefall. I'd guess that your system will show another interface before the internet interface. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604101206.OAA27198>