All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Kirstein <xenlist@custom.ray.net>
To: xen-devel@lists.xensource.com
Cc: Jason <xen@jasonandjessi.com>
Subject: Re: networking checksum errors again
Date: Fri, 31 Mar 2006 07:46:41 +0200	[thread overview]
Message-ID: <20060331074641.E26981@web.ray.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0603302326590.11051@localhost>; from xen@jasonandjessi.com on Thu, Mar 30, 2006 at 11:30:09PM -0600

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

Hallo,

> Regardless of whether or not I use a dom0 kernel or a domU kernel I
> get failed checksum packets whenever I try to route across a virtual
> interface.  I have a pure virtual setup
Ah, I just dived into that recently... Is there a bugzilla id
for that already? I had the same problem as you, Dom0 can't communicate
with DomU due to the checksum errors in a routed setup, everything
works when bridged. But I don't want to bridge :)

> thing on all interfaces, tried changing the code in netback.c to
> force a checksum and have had no luck.   Any else having trouble?
Which netback.c patch did you use? I currently have a working setup
using the "interface.c" patch which removes the NETIF_F_NO_CSUM from
the dev->features in Dom0 (attached). Using this "sum ok" packets go
from Dom0 to DomU (also leaving Dom0 intact), DomU to Dom0 packets
are broken leaving DomU but Dom0 ignores that. Using
ethtool -K eth0 tx off
in DomU I can bring DomU to generate valid sums also, but that's cosmetic
and not needed for a working setup. I'd rather also patch this in the
kernel instead of running ethtool in every DomU but I haven't searched
for that yet. Should be easy, though :)

As far as I understood the discussion, this is not an easy issue and
possibly will be dealt with in in clean way after the 3.0.2 release?
For now I have other problems, the above setup seems to work fine
for me (also for DomU-DomU communication, which of course is routed
over Dom0. Will have to test tunnels/vpn in DomU).

(:ul8er, r@y

[-- Attachment #2: netback-interface.patch --]
[-- Type: text/plain, Size: 656 bytes --]

diff -U 3 -r xen-unstable-orig/linux-2.6-xen-sparse/drivers/xen/netback/interface.c xen-unstable/linux-2.6-xen-sparse/drivers/xen/netback/interface.c
--- xen-unstable-orig/linux-2.6-xen-sparse/drivers/xen/netback/interface.c	2006-03-28 06:11:37.000000000 +0200
+++ xen-unstable/linux-2.6-xen-sparse/drivers/xen/netback/interface.c	2006-03-30 08:17:01.000000000 +0200
@@ -101,7 +101,7 @@
 	dev->get_stats       = netif_be_get_stats;
 	dev->open            = net_open;
 	dev->stop            = net_close;
-	dev->features        = NETIF_F_NO_CSUM;
+	dev->features        = 0; /* replaced NETIF_F_NO_CSUM */
 
 	/* Disable queuing. */
 	dev->tx_queue_len = 0;

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2006-03-31  5:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31  5:30 networking checksum errors again Jason
2006-03-31  5:46 ` Florian Kirstein [this message]
2006-03-31  7:10   ` Jason
     [not found]     ` <20060331083153.F26981@web.ray.net>
2006-03-31 16:21       ` Jason
2006-04-01 21:44         ` Nivedita Singhvi
2006-04-01 23:55           ` Jason

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=20060331074641.E26981@web.ray.net \
    --to=xenlist@custom.ray.net \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen@jasonandjessi.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.