tcpdump mailing list archives
Sniffing inbound ethernet frames only
From: Jost-DVSB () t-online de
Date: Fri, 20 Oct 2006 18:24:36 +0200
Dear tcpdump experts, I have a Linux box with two Fast Ethernet interfaces. In two separate windows on the desktop I want to see all inbound ethernet frames (from the wire), but not the ethernet frames coming down the local network stack. In the left window tcpdump should run to catch all incoming ethernet frames from interface eth0. In the right window tcpdump should run to catch all incoming ethernet frames from interface eth1. All outgoing ethernet frames must not be displayed. Both tcpdump processes must run in parallel. The keyword inbound cannot be used with link level. Which tcpdump expression solves the problem? Any solution appreciated. jojo - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
Current thread:
- Sniffing inbound ethernet frames only Jost-DVSB (Oct 21)
- Re: Sniffing inbound ethernet frames only Jefferson Ogata (Oct 21)
- Re: Sniffing inbound ethernet frames only Jost-DVSB (Oct 23)
- Re: Sniffing inbound ethernet frames only Jefferson Ogata (Oct 23)
- why not filtering at driver level ? madhuresh (Oct 23)
- Re: why not filtering at driver level ? Guy Harris (Oct 23)
- Re: why not filtering at driver level ? madhuresh (Oct 23)
- Re: why not filtering at driver level ? Guy Harris (Oct 23)
- Re: why not filtering at driver level ? madhuresh (Oct 23)
- Re: why not filtering at driver level ? Guy Harris (Oct 23)
- Re: why not filtering at driver level ? Guy Harris (Oct 23)
- Re: Sniffing inbound ethernet frames only Jost-DVSB (Oct 23)
- Re: Sniffing inbound ethernet frames only Jefferson Ogata (Oct 21)