public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Speedster <speedster@haveacry•com>
To: Herbert Xu <herbert@gondor•apana.org.au>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki•fi>,
	Netdev <netdev@vger•kernel.org>,
	bugme-daemon@bugzilla•kernel.org,
	"Andrew Morton" <akpm@linux-foundation•org>
Subject: Re: [Bugme-new] [Bug 12327] New: Intermittent TCP issues with => 2.6.27
Date: Wed, 07 Jan 2009 22:49:55 +0900	[thread overview]
Message-ID: <4964B303.4020708@haveacry.com> (raw)
In-Reply-To: <20090107041732.GA22041@gondor.apana.org.au>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

Herbert Xu wrote:
> Can you also attach a dump for connections that do work under
> 2.6.27? That should tell us whether this MAC is genuine.

Done. I also realised my wireshark display filter was dst_host rather 
than simply host - it looks as though replies _do_ come back but for 
some reason are ignored? My apologies.

The 2.6.27 dump contains a connection to a local file mirror 
(203.21.20.200) and an attempted connection to store.apple.com 
(17.149.156.10).

> If it is bogus, can you dump on the other interfaces to see
> who is corrupting it?
> 

I believe the differing MAC addresses on the PPP remote endpoint are due 
to my ISP having multiple layer 2 termination routers for 
load-balancing/redundancy and not a symptom of the issue.

Cheers,
Dean

[-- Attachment #2: whinge-2.6.24_whimper-dump-bidir.cap --]
[-- Type: application/octet-stream, Size: 1406 bytes --]

[-- Attachment #3: whinge-2.6.27_whimper-dump-twohosts.cap --]
[-- Type: application/octet-stream, Size: 2339 bytes --]

  reply	other threads:[~2009-01-07 13:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12327-10286@http.bugzilla.kernel.org/>
2008-12-30  5:41 ` [Bugme-new] [Bug 12327] New: Intermittent TCP issues with => 2.6.27 Andrew Morton
2008-12-31 20:32   ` Ilpo Järvinen
2008-12-31 23:22     ` Speedster
2009-01-02  8:34       ` Herbert Xu
2009-01-05 11:19         ` Speedster
2009-01-06 19:10           ` Ilpo Järvinen
2009-01-06 21:19             ` Speedster
2009-01-07  4:17           ` Herbert Xu
2009-01-07 13:49             ` Speedster [this message]
2009-01-08  3:07               ` Herbert Xu
2009-01-08 13:13                 ` Ilpo Järvinen
2009-01-08 15:04                 ` Speedster
2009-01-08 16:37                   ` Stephen Hemminger
2009-01-08 19:39                     ` Ilpo Järvinen
2009-01-08 19:54                       ` Stephen Hemminger
2009-01-08 21:54                     ` Herbert Xu
2009-01-09  0:14                   ` John Dykstra
2009-01-09  0:30                   ` John Dykstra
     [not found] <e7c4531f0901081558n429f7275w717774dbe9ccd895@mail.gmail.com>
2009-01-09  3:14 ` Herbert Xu
2009-01-09 11:55   ` Herbert Xu
2009-01-09 12:04     ` Herbert Xu
2009-01-12  5:30       ` Patrick McHardy
2009-01-13 10:50       ` Speedster
2009-03-06 10:39       ` Dean Holland
2009-03-25 13:26         ` Ilpo Järvinen
2009-01-12  5:27     ` Patrick McHardy
2009-01-12  5:25   ` Patrick McHardy

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=4964B303.4020708@haveacry.com \
    --to=speedster@haveacry$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=bugme-daemon@bugzilla$(echo .)kernel.org \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=ilpo.jarvinen@helsinki$(echo .)fi \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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