All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Durack <tdurack@gmail.com>
To: xen-users@lists.xensource.com, xen-devel@lists.xensource.com
Subject: Network stalling
Date: Wed, 31 Aug 2005 13:17:02 -0400	[thread overview]
Message-ID: <9e246b4d05083110174e4bc87@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1377 bytes --]

Guess I should add my experiences:

Running unstable (approx. two weeks old now.)

Dom0 vif1.0 -> guest eth0: icmp works, ssh fails, tcp seems to have checksum 
issues. Building gre tunnels over this works around the problem. I thought 
maybe this was device driver related (tg3), so I tried bcm5700 with the same 
result.

Tried a similar setup with a machine with e100 driver. This time I get udp 
checksum errors instead of tcp, so dns fails but ssh works ;-( A gre tunnel 
is my current workaround.

I say checksum issues because ethereal is complaining about transport layer 
checksums when I do a capture to diagnose the problem.

Tried various combinations of disabling tx/rx/sg/to with ethtool in both 
Dom0 and guest, to no avail. Also tried hacking the driver code to 
permanently disable offloads. Tried looking for the difference between 
stable/unstable netfront and netback, but didnt get far.

A bridged setup works, ip address on Dom0 veth0, Dom0 vif0.0 bridged with 
Dom0 vif1.0. Real pain in the neck to firewall though, due to all the 
interfaces. Never managed to get Masquerading to work in this setup, so went 
back to a routed network with gre tunnels...

I can try a more recent unstable if it might help, but I haven't seen any 
evidence of anything having fixed this. Love to have a simple routed setup 
working.

Tim:>

[-- Attachment #1.2: Type: text/html, Size: 1437 bytes --]

[-- Attachment #2: Type: text/plain, Size: 137 bytes --]

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

             reply	other threads:[~2005-08-31 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 17:17 Tim Durack [this message]
2005-08-31 19:31 ` [Xen-users] Network stalling Nivedita Singhvi
2005-08-31 21:16   ` Tim Durack
2005-09-01  1:59   ` Tim Durack

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=9e246b4d05083110174e4bc87@mail.gmail.com \
    --to=tdurack@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.