All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Liljeberg <mika.liljeberg@welho.com>
To: Wichert Akkerman <wichert@wiggy.net>
Cc: linux-kernel@vger.kernel.org,
	Maciej Soltysiak <solt@dns.toxicfilms.tv>,
	netdev@oss.sgi.com
Subject: Re: ipv6 stack seems to forget to send ACKs
Date: 10 Jan 2003 00:12:33 +0200	[thread overview]
Message-ID: <1042150352.4688.15.camel@devil> (raw)
In-Reply-To: <20030108170139.GL22951@wiggy.net>

Hi Wichert,

Looking at your trace it seems that the receiving machine is dropping
all packets that do not have traffic class set. Note that all segments
received with [class 0x2] get properly acked. The others probably don't
get to TCP at all. You might want to check your filters and QoS
policies.

BR,

	MikaL


On Wed, 2003-01-08 at 19:01, Wichert Akkerman wrote:
> Previously Maciej Soltysiak wrote:
> > I seem to be getting better results than you, i think that it is not an
> > issue of ipv6 implementation but simply the case of time sensitive
> > traffic fighting with other Internet traffic over tunnels through ipv4
> > networks.
> 
> Actually, I don't follow this. How could any kind of traffic shaping
> result in my client not sending ACKs, which is what the tcpdump
> seems to indicate? I can understand packets being dropped which
> would result in retransmits, but that is not the case here.
> 
> Wichert.
> 
> (usual I'm-no-network-guru-and-might-be-misreading-things disclaimer here)

  parent reply	other threads:[~2003-01-09 22:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 13:08 ipv6 stack seems to forget to send ACKs Wichert Akkerman
2003-01-08 13:26 ` Maciej Soltysiak
2003-01-08 13:30   ` Wichert Akkerman
2003-01-08 13:51     ` Maciej Soltysiak
2003-01-08 13:52       ` Wichert Akkerman
2003-01-08 13:56         ` Maciej Soltysiak
2003-01-08 14:09           ` Wichert Akkerman
2003-01-08 14:43 ` Maciej Soltysiak
2003-01-08 14:52   ` Wichert Akkerman
2003-01-08 15:02     ` Wichert Akkerman
2003-01-08 16:39       ` Maciej Soltysiak
2003-01-08 16:43         ` Wichert Akkerman
2003-01-08 17:01         ` Wichert Akkerman
2003-01-08 17:43           ` Maciej Soltysiak
2003-01-08 19:52           ` Andrew McGregor
2003-01-09 22:12           ` Mika Liljeberg [this message]
2003-01-09 22:21             ` Wichert Akkerman
2003-01-08 15:22 ` Fabio Massimo Di Nitto
2003-01-08 18:05 ` Fabio Massimo Di Nitto
2003-01-08 19:59   ` Andrew McGregor
2003-01-08 20:27     ` Maciej Soltysiak
2003-01-08 20:31       ` [OT] " Fabio Massimo Di Nitto
2003-01-08 20:39         ` Andrew McGregor
2003-01-08 22:43     ` Wichert Akkerman
2003-01-09  7:29       ` Fabio Massimo Di Nitto
2003-01-09  9:38         ` Wichert Akkerman
2003-01-09  9:43           ` Fabio Massimo Di Nitto
2003-01-10 20:59             ` Paul Jakma
2003-01-09 10:32       ` Maciej Soltysiak
2003-01-09 10:40         ` Wichert Akkerman
2003-01-09 22:50     ` Bill Davidsen
2003-01-09  8:32 ` Herbert Xu
2003-01-09 11:38 ` Rogier Wolff
2003-01-09 11:55   ` Andrew McGregor
2003-01-09 15:41   ` Wichert Akkerman
2003-01-09 15:52   ` Wichert Akkerman
2003-01-09 16:03     ` Wichert Akkerman
2003-01-10  1:17     ` Andrew McGregor

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=1042150352.4688.15.camel@devil \
    --to=mika.liljeberg@welho.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=solt@dns.toxicfilms.tv \
    --cc=wichert@wiggy.net \
    /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.