From: Ben Greear <greearb@candelatech.com>
To: netdev@sc-software.com
Cc: netdev@vger.kernel.org
Subject: Re: Outbound pktgen pkts missed by tcpdump/pcap
Date: Fri, 15 Sep 2006 10:22:38 -0700 [thread overview]
Message-ID: <450AE15E.1070006@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0609151000360.9994@sc-software.com>
netdev@sc-software.com wrote:
>
> Kernels 2.6.13, 2.6.17.7 & 2.6.17.13...
>
> I've been unable to capture outbound packets from local eth2,
> generated by pktgen using the just previous and latest releases
> of tcpdump & libpcap. All incoming pktgen pkts are seen just fine.
> Pkts are UDP.
>
> Any clues to save me some time fixing this, would greatly appreciated.
Pktgen sends below the packet capture hooks, so you cannot sniff out-going traffic.
If you changed the code to do a dev-queue-xmit instead of hard_start_xmit, it
might be captured then, but would probably decrease pktgen performance.
Ben
>
> Thnx much.
> johnh
> .
> ===========================================================
> John Heil
> South Coast Software
> Custom firmware, device drivers and board bring up services
> Ph: 1-714-774-6952
> Fx: 1-714-774-7053
> www.sc-software.com
> email: johnhscs@sc-software.com
> ===========================================================
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2006-09-15 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 17:08 Outbound pktgen pkts missed by tcpdump/pcap netdev
2006-09-15 17:22 ` Ben Greear [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=450AE15E.1070006@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@sc-software.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.