From: Ewan Mellor <ewan@xensource.com>
To: Li Ge <lge@us.ibm.com>
Cc: Xen Developers <xen-devel@lists.xensource.com>
Subject: Re: Network script handling changes
Date: Wed, 2 Nov 2005 17:19:48 +0000 [thread overview]
Message-ID: <20051102171948.GD408@leeni.uk.xensource.com> (raw)
In-Reply-To: <OFA71132F0.5E29A08C-ON872570AD.0059CFF7-062570AD.005B8F26@us.ibm.com>
On Wed, Nov 02, 2005 at 10:50:44AM -0600, Li Ge wrote:
> Ewan,
> I tried the two bridges topology you described below by following the
> exact steps you suggested, but I could not get it work.
>
> [Snip]
>
> Anything that I could have missed in the settings?
No, the settings look right. Of course, I presume that you have noticed that
my wrapper script is not quite right -- it does not pass the "start" command
through to network-bridge.
Even when you run network-bridge manually, it still hasn't worked though. Do
you get any error messages in /var/log/debug, /var/log/syslog, etc? One
obvious problem is that you have no vif0.1 interface, which is the one that
connects from your new eth1 to xenbr1. I presume that the script is bailing
out early for some reason -- it would be good if you could figure out where it
stops, and why.
Could you open a bug, and attach the output of
brctl show
ifconfig
route
iptables -L
before and after running
/etc/xen/scripts/network-bridge vifnum=0 start
/etc/xen/scripts/network-bridge vifnum=1 start
This should give us good clues to help with the debugging.
Thanks a lot,
Ewan.
next prev parent reply other threads:[~2005-11-02 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 16:52 Network script handling changes Ewan Mellor
2005-10-31 17:05 ` Ewan Mellor
2005-11-02 2:53 ` Greg Brackley
2005-11-03 4:39 ` Greg Brackley
2005-11-02 16:50 ` Li Ge
2005-11-02 17:19 ` Ewan Mellor [this message]
2005-11-02 17:33 ` Nivedita Singhvi
2005-11-02 19:28 ` Li Ge
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=20051102171948.GD408@leeni.uk.xensource.com \
--to=ewan@xensource.com \
--cc=lge@us.ibm.com \
--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.