* TCP: Peer messages
@ 2009-04-19 1:03 Stephen Hemminger
2009-04-19 11:19 ` Ilpo Järvinen
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Hemminger @ 2009-04-19 1:03 UTC (permalink / raw)
To: Ilpo Järvinen, David Miller; +Cc: netdev
Running some log-term tests of (using bittorrent of latest Ubuntu releases).
I see no problems with firewall rules (or sky2 driver), but I do several of these:
[28286.893945] TCP: Peer <ip scrubbed>:63659/51413 unexpectedly shrunk window 414881290:414894358 (repaired)
[47312.851937] TCP: Peer <ip scrubbed>:43793/51413 unexpectedly shrunk window 888816585:888823785 (repaired)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: TCP: Peer messages
2009-04-19 1:03 TCP: Peer messages Stephen Hemminger
@ 2009-04-19 11:19 ` Ilpo Järvinen
2009-04-20 3:11 ` Stephen Hemminger
0 siblings, 1 reply; 3+ messages in thread
From: Ilpo Järvinen @ 2009-04-19 11:19 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: David Miller, Netdev
On Sat, 18 Apr 2009, Stephen Hemminger wrote:
> Running some log-term tests of (using bittorrent of latest Ubuntu releases).
> I see no problems with firewall rules (or sky2 driver), but I do several
> of these:
>
>
> [28286.893945] TCP: Peer <ip scrubbed>:63659/51413 unexpectedly shrunk window 414881290:414894358 (repaired)
> [47312.851937] TCP: Peer <ip scrubbed>:43793/51413 unexpectedly shrunk window 888816585:888823785 (repaired)
This is what was earlier the Treason uncloacked message until somebody
was scared to death because of it and we had to change the wording.
And it's what the old kernels do for us (and there are plenty of such
kernels around), and possibly broken middleboxes too. Unless you have a
tcpdump of a specific case or can clearly say that its frequency is much
larger than it used to be in some between kernel versions consistent test
setup, I'm not going to waste my time on debugging obsolete remote ends.
But, now that I think it a bit more, we could possibly but a WARN_ON
somewhere if we ever sent past advertized window to make a distinction
between our and their bugs.
--
i.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: TCP: Peer messages
2009-04-19 11:19 ` Ilpo Järvinen
@ 2009-04-20 3:11 ` Stephen Hemminger
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Hemminger @ 2009-04-20 3:11 UTC (permalink / raw)
To: Ilpo Järvinen; +Cc: David Miller, Netdev
On Sun, 19 Apr 2009 14:19:36 +0300 (EEST)
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> wrote:
> On Sat, 18 Apr 2009, Stephen Hemminger wrote:
>
> > Running some log-term tests of (using bittorrent of latest Ubuntu releases).
> > I see no problems with firewall rules (or sky2 driver), but I do several
> > of these:
> >
> >
> > [28286.893945] TCP: Peer <ip scrubbed>:63659/51413 unexpectedly shrunk window 414881290:414894358 (repaired)
> > [47312.851937] TCP: Peer <ip scrubbed>:43793/51413 unexpectedly shrunk window 888816585:888823785 (repaired)
>
> This is what was earlier the Treason uncloacked message until somebody
> was scared to death because of it and we had to change the wording.
>
> And it's what the old kernels do for us (and there are plenty of such
> kernels around), and possibly broken middleboxes too. Unless you have a
> tcpdump of a specific case or can clearly say that its frequency is much
> larger than it used to be in some between kernel versions consistent test
> setup, I'm not going to waste my time on debugging obsolete remote ends.
>
> But, now that I think it a bit more, we could possibly but a WARN_ON
> somewhere if we ever sent past advertized window to make a distinction
> between our and their bugs.
>
12 over 3 days is not enough to worry about.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-04-20 3:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-04-19 1:03 TCP: Peer messages Stephen Hemminger
2009-04-19 11:19 ` Ilpo Järvinen
2009-04-20 3:11 ` Stephen Hemminger
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.