All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Michal Suchanek <hramrach@centrum.cz>
Cc: xen-devel@lists.xensource.com
Subject: Re: UDP checksums broken in Dom0 -> DomU vif transfer
Date: Mon, 19 Dec 2011 10:29:43 -0400	[thread overview]
Message-ID: <20111219142943.GD27772@andromeda.dapyr.net> (raw)
In-Reply-To: <CAOMqctShNFqe47w1orEPMCqvDORy5yxh=Gy33e02fyQYrz4nkw@mail.gmail.com>

On Mon, Dec 19, 2011 at 10:27:36AM +0100, Michal Suchanek wrote:
> Hello,
> 
> when I boot DomU which uses DHCP to configure IPv4 address it does

You didn't say what version of DomU you are running? Is it 3.1?
> never get a lease.
> 
> The packets travel to Dom0 where the dhcp server receives them, sends
> a reply, that travels to DomU where dhclient receives it, says the
> checksum is invalid, and discards it.
> 
> The problem is documented here:
> 
> http://old-list-archives.xen.org/archives/html/xen-users/2006-02/msg00152.html
> http://old-list-archives.xen.org/archives/html/xen-devel/2011-04/msg01235.html
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1655
> 
> The fix is to turn off UDP checksum offloading on the vif interface in
> Dom0 as documented in the above mail:
> 
> I edited /etc/xen/scripts/network-bridge,
> adding this command to the end of the op_start() function:
> 
>         add_to_bridge2 ${bridge} ${pdev}
>         do_ifup ${netdev}
> +       # disable ip checksum offloading for veth device
> +       ethtool -K ${netdev} tx off
>     else
>         # old style without ${vdev}
> 
> Note: I am not sure which path is taken through the script, I set the
> parameter manually with ethtool before I found this patch.
> 
> It some solutions suggest to turn off UDP checksum offloading in the
> DomU as well but it does not seem to be necessary since the packets
> would travel to the dhcp server and it would reply to them.
> 
> Some people say this is working for them.
> 
> I suspect this is because some Linux distributions already carry this patch.
> 
> Any reason why this can't be fixed in Xen upstream?

It should be fixed in the kernel and I think it is fixed. Did you have
this problem with a 3.1 or 3.0 kernel?
> 
> This issue is years old and has been discovered, solved, re-discovered
> and re-solved numerous times already.
> 
> Thanks
> 
> Michal
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-12-19 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19  9:27 UDP checksums broken in Dom0 -> DomU vif transfer Michal Suchanek
2011-12-19 14:29 ` Konrad Rzeszutek Wilk [this message]
2011-12-19 15:20   ` Michal Suchanek
2011-12-19 19:43     ` Konrad Rzeszutek Wilk
2011-12-20  9:37       ` Ian Campbell
2011-12-20  9:43         ` Jean Guyader
2011-12-20  9:55           ` Ian Campbell
2011-12-20 11:57             ` Michal Suchanek
2011-12-20 15:35               ` Konrad Rzeszutek Wilk
2011-12-20 16:19                 ` Ian Campbell
2011-12-20 20:03                   ` Konrad Rzeszutek Wilk
2011-12-21 10:22                     ` Ian Campbell
2012-01-02  9:14                 ` Stefan Bader

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=20111219142943.GD27772@andromeda.dapyr.net \
    --to=konrad@darnok.org \
    --cc=hramrach@centrum.cz \
    --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.