From: Nivedita Singhvi <nsnix@comcast.net>
To: m+Ian.Pratt@cl.cam.ac.uk
Cc: xen-devel@lists.sourceforge.net, srparish@us.ibm.com,
ian.pratt@cl.cam.ac.uk, matta@tektonic.net
Subject: RE: [PATCH] warn when iproute2 or bridge-utils aremissing]]
Date: Sat, 26 Feb 2005 18:53:48 -0800 [thread overview]
Message-ID: <4221363C.9080606@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
> How's about someone knocks up a patch to make routing the default (and
> renames the current 'network' script to 'network-bridge'), and updates
> the documentation appropriately?
>
> Ian
Here's a start - altered the default in the default xend config
file and updated tools/README. The network script needs to be
renamed network-bridge (no patch for that ;)).
User manual documentation patches will follow too, in a while,
along with other cleanups in the scripts...
thanks,
Nivedita
---
Nivedita Singhvi
niv@us.ibm.com
nsnix@comcast.net
[-- Attachment #2: xend-config.sxp.patch --]
[-- Type: text/plain, Size: 1191 bytes --]
--- xend-config.sxp 2005-02-25 20:13:02.000000000 -0800
+++ xend-config.sxp.new 2005-02-26 17:47:08.000000000 -0800
@@ -10,17 +10,23 @@
## Use the following if VIF traffic is routed.
# The script used to start/stop networking for xend.
-#(network-script network-route)
+(network-script network-route)
# The default script used to control virtual interfaces.
-#(vif-script vif-route)
+(vif-script vif-route)
+
+## Use the following if VIF traffic is NAT'd.
+# The script used to start/stop networking for xend.
+#(network-script network-nat)
+# The default script used to control virtual interfaces.
+#(vif-script vif-nat)
## Use the following if VIF traffic is bridged.
# The script used to start/stop networking for xend.
-(network-script network)
+#(network-script network)
# The default bridge that virtual interfaces should be connected to.
-(vif-bridge xen-br0)
+#(vif-bridge xen-br0)
# The default script used to control virtual interfaces.
-(vif-script vif-bridge)
+#(vif-script vif-bridge)
# Whether iptables should be set up to prevent IP spoofing for
# virtual interfaces. Specify 'yes' or 'no'.
[-- Attachment #3: tools_examples_README.patch --]
[-- Type: text/plain, Size: 1249 bytes --]
--- README 2005-02-26 17:22:36.000000000 -0800
+++ README.new 2005-02-26 17:33:14.000000000 -0800
@@ -9,8 +9,17 @@
send it (preferably with a little summary to go in this file) to
<xen-devel@lists.sourceforge.net> so we can add it to this directory.
-network - default network setup script called by xend at startup.
-vif-bridge - default virtual network interface setup script.
+Routing is set up as the default mechanism to handle
+traffic between Dom0 and DomN. Edit the configuration
+file that xend reads (default: xend-config.sxp) to
+change this default to bridging or NAT.
+
+network-route - network setup script called by xend when routing.
+vif-route - virtual network interface setup script when routing.
+network-bridge - network setup script called by xend when bridging.
+vif-bridge - virtual network interface setup script when bridging.
+network-nat - network setup script called by xend for nat.
+vif-nat - virtual network interface setup script for nat.
xend-config.sxp - default xend configuration file.
xmexample1 - example configuration script for 'xm create'.
xmexample2 - a more complex configuration script for 'xm create'.
reply other threads:[~2005-02-27 2:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4221363C.9080606@comcast.net \
--to=nsnix@comcast.net \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=matta@tektonic.net \
--cc=srparish@us.ibm.com \
--cc=xen-devel@lists.sourceforge.net \
/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.