On Sun, Nov 14, 1999 at 02:08:10PM -0000, subb3 at ibm.net wrote:
>> I have 2 interfaces on my linux system. They are modem and ethernet.
> When I use tcpdump to capture info, I cannot get any information
> from the ethernet interface. tcpdump just waits and waits.
>> Here is how, I am invoking tcpdump
>> $ tcpdump -a -v -l -S -i ppp0 <= works fine
> $ tcpdump -a -v -l -S -i eth0 <= No output of any type from my LAN
>> What am I doing wrong here? Is this anything to do with ppp0 being
> the default routing device?
It should have nothing to do with the routing table.
Add -n to prevent DNS reverse lookups for stuff on your LAN. If your
DNS is not setup correctly, these lookups can take quite a while to
timeout.
Try dropping the -a. It might be causing slow DNS lookups. Shouldn't be
though...
Also, stupid question, but are you sure there is traffic on your ethernet?
Later,
Kenn
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
