[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1349034330.12401.210.camel@edumazet-glaptop>
Date: Sun, 30 Sep 2012 21:45:30 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Chris Clayton <chris2553@...glemail.com>
Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
gpiez@....de
Subject: Re: Possible networking regression in 3.6.0
On Sun, 2012-09-30 at 16:26 +0100, Chris Clayton wrote:
> Hi Eric,
>
> On 09/28/12 12:26, Eric Dumazet wrote:
> > On Fri, 2012-09-28 at 10:22 +0100, Chris Clayton wrote:
> >
> >> No, the WinXP guest is configured with a fixed IP address
> >> (192.168.200.1). Subnet mask is 255.255.255.0, and default gateway is
> >> 192.168.200.254. DNS is 192.168.0.1.
> >>
> >
> > I have no problem with such a setup, with a linux guest.
> >
> > Could you send again a tcpdump, but including link-level header ?
> > (option -e)
> >
> > Ideally, you could send two traces, one taken on tap0, and another taken
> > on eth0.
> >
> Below are two more traces that I think may well be more useful than
> those I sent on Friday. They are taken with tcpdump directly (after some
> reading up on that application) rather than tcpdump translations of pcap
> files captured with netsniff-ng. Also, they are taken concurrently, so
> they show the traffic on tap0 and eth0 at the time of an unsuccessful
> attempt to ping the router from the WinXP KVM client. The command was:
> sudo tcpdump -nev -i eth0 -Z chris >eth0.trace
Could you send "netstat -s" before/after your tests ?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists