netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: cpw@lanl.gov, netdev@vger.kernel.org
Subject: Re: 2.6.18-rc6 memory mapped pcap truncates outgoing TCP packets, but not icmp
Date: Wed, 13 Sep 2006 20:44:21 +0200	[thread overview]
Message-ID: <45085185.2060904@trash.net> (raw)
In-Reply-To: <20060913112307.GA1374@outpost.ds9a.nl>

bert hubert wrote:
> Hi people,
> 
> I like to use memory mapped pcap (PACKET_MMAP) since off the shelf, linux is
> a tad prone to drop packets while capturing these days. It used to be lots
> better at it, but right now memory mapped pcap is the only way to get things
> working a bit. I've noticed this on many machines.
> 
> However, memory mapped pcap has started to truncate outgoing packets for me
> recently, and interestingly, I only see this with locally generated TCP
> packets, not with locally generated ICMP packets. I haven't yet tried UDP,
> nor actual sniffing, this is all locally generated packets going out on
> eth0.

Are you using TSO on the outgoing device? If so please try to log the
packet using iptables to see if it really is a TSO packet.


  reply	other threads:[~2006-09-13 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 11:23 2.6.18-rc6 memory mapped pcap truncates outgoing TCP packets, but not icmp bert hubert
2006-09-13 18:44 ` Patrick McHardy [this message]
2006-09-14  8:56   ` bert hubert
2006-09-14 10:02     ` Patrick McHardy
2006-09-14 10:52       ` Alexey Kuznetsov
2006-09-15 12:02       ` bert hubert
2006-09-15 20:16         ` Patrick McHardy
2006-09-18  7:00           ` David Miller

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=45085185.2060904@trash.net \
    --to=kaber@trash.net \
    --cc=bert.hubert@netherlabs.nl \
    --cc=cpw@lanl.gov \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).