From: Richie <listmail@triad.rr.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Gerry Reno <greno@verizon.net>, xen-devel@lists.xensource.com
Subject: Re: pv_ops 2.6.32.12: network problem: Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet
Date: Wed, 19 May 2010 18:22:13 -0400 [thread overview]
Message-ID: <4BF46495.1060208@triad.rr.com> (raw)
In-Reply-To: <4BF456F9.8090606@goop.org>
Is this problem (and fix) also related to the issue described here?
http://wiki.xensource.com/xenwiki/XenFaq#head-4ce9767df34fe1c9cf4f85f7e07cb10110eae9b7
I posted about a checksum problem not to long ago in this xen-users
thread
http://lists.xensource.com/archives/html/xen-users/2010-05/msg00456.html
TIA for any info.
Jeremy Fitzhardinge wrote:
> On 05/19/2010 02:09 PM, Gerry Reno wrote:
>
>> I am using a pv_ops dom0 kernel 2.6.32.12 with xen 4.0.0-rc8. My
>> domU's use 2.6.31-14-server ubuntu.
>>
>> When I try to ping another computer on the network from the domU I
>> still received this error:
>> Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet
>>
>> I thought this error was fixed somewhere around 2.6.32.10 but
>> apparently it is still in 2.6.32.12.
>>
>> How do I get around this problem?
>>
>
> I applied a patch to fix up a checksum bug in netback, but I realized I
> hadn't applied it to stable-2.6.32. Please try again (it will be
> 2.6.32.13) and tell me how it goes.
>
> Thanks,
> J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-05-19 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 21:09 pv_ops 2.6.32.12: network problem: Attempting to checksum a non-TCP/UDP packet, dropping a protocol 1 packet Gerry Reno
2010-05-19 21:24 ` Jeremy Fitzhardinge
2010-05-19 22:22 ` Richie [this message]
2010-05-19 22:53 ` Jeremy Fitzhardinge
2010-05-20 1:00 ` Gerry Reno
2010-05-27 14:08 ` Pasi Kärkkäinen
2010-05-27 17:08 ` Jeremy Fitzhardinge
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=4BF46495.1060208@triad.rr.com \
--to=listmail@triad.rr.com \
--cc=greno@verizon.net \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/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.