From: Michael Brade <brade@kde.org>
To: xen-devel@lists.xensource.com
Subject: Re: Patch fixing vlan handling when network-bridge scriptis used
Date: Thu, 19 Aug 2010 17:59:29 +0200 [thread overview]
Message-ID: <201008191759.39253.brade@kde.org> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01A925CB@trantor>
[-- Attachment #1.1: Type: Text/Plain, Size: 2198 bytes --]
On Thursday 19 August 2010 06:20:47 James Harper wrote:
> > Miroslav Rezanina writes ("[Xen-devel] Patch fixing vlan handling when
> >
> > network-bridge script is used"):
> > > We had problem using tagged vlans inside domU. Testing shows that
> > > this is caused by changing network interfaces in network-bridge
> > > script. Following patch should allow to use vlans in guest.
> >
> > Thanks for reporting this.
> >
> > This is just another way in which the network-bridge approach, of
> > trying to transfer all the details from one interface to another,
> > won't work well.
> >
> > I think you would be much better served if you just used your
> > operating system's features (/etc/network/interfaces on Debian) to set
> > up the bridge and call it xenbr0, and disabled network-bridge
> > entirely.
> >
> > Rather than apply your patch, I would prefer to change network-bridge
> > so that it explicitly fails when vlans are detected and tells you to
> > do it the other way.
> >
> > Anyone else have an opinion /
>
> I always set up networking in /etc/network/interfaces. I think that xend
> doing it for you is nice but it breaks so easily that I wonder if it's
> worth it at all. IMO, the default should be that xend doesn't touch the
> bridge at all, but leave the option to do so in the config but commented
> out.
>
> Of course, you don't hear from the people that are all using it with no
> problem at all...
Well, I did have a few problems with the network-script, too, and then decided
to drop it and do it all in network/interfaces. I didn't report it because the
main problem for me was initialization order and there is nothing that I found
that could be done to fix that script - when xend starts it's already too late.
But I had to add the "ethtool -K $vif tx off" to vif-bridge to fix the checksums
error. Maybe this could be added by default with a check for ethtool?
cheers,
--
Michael Brade; KDE Developer
|-mail: echo brade !#|tr -d "c oh"|s\e\d 's/e/\@/2;s/$/.org/;s/bra/k/2'
°--web: http://www.behindkde.org/people/michaelb/
KDE 4: Beyond Your Expectations
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-08-19 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <232221223.568081282131308987.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-18 11:43 ` Patch fixing vlan handling when network-bridge script is used Miroslav Rezanina
2010-08-18 16:02 ` Ian Jackson
2010-08-19 4:20 ` Patch fixing vlan handling when network-bridge scriptis used James Harper
2010-08-19 13:25 ` Ian Jackson
2010-08-19 15:59 ` Michael Brade [this message]
2010-08-19 17:59 ` Ian Jackson
2010-08-19 18:35 ` Michael Brade
2010-08-19 23:11 ` Jeremy Fitzhardinge
2010-08-20 18:25 ` Michael Brade
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=201008191759.39253.brade@kde.org \
--to=brade@kde.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.