All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <nsnix@comcast.net>
To: xen-devel@lists.sourceforge.net
Subject: [Patch Trivial] Getting natpicky..
Date: Sun, 27 Feb 2005 09:47:23 -0800	[thread overview]
Message-ID: <422207AB.1070403@comcast.net> (raw)

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

Trivial nits in the network-nat script..


signed-off by Nivedita Singhvi (niv@us.ibm.com)

thanks,
Nivedita

---
Nivedita Singhvi
niv@us.ibm.com
nsnix@comcast.net


[-- Attachment #2: network-nat.patch --]
[-- Type: text/plain, Size: 1066 bytes --]

--- network-nat	2005-02-25 20:13:00.000000000 -0800
+++ network-nat.new	2005-02-26 21:05:23.000000000 -0800
@@ -1,18 +1,18 @@
 #!/bin/sh
 #============================================================================
-# Default Xen network start/stop script.
+# Default Xen network start/stop script when using NAT.
 # Xend calls a network script when it starts.
 # The script name to use is defined in /etc/xen/xend-config.sxp
 # in the network-script field.
 #
 # Usage:
 #
-# network-route (start|stop|status) {VAR=VAL}*
+# network-nat (start|stop|status) {VAR=VAL}*
 #
 # Vars:
 #
 # netdev     The gateway interface (default eth0).
-# antispoof  Whether to use iptables to prevent spoofing (default yes).
+# antispoof  Whether to use iptables to prevent spoofing (default no).
 #
 #============================================================================
 
@@ -30,7 +30,7 @@
 
 netdev=${netdev:-eth0}
 # antispoofing not yet implemented
-antispoof=${antispoof:-yes}
+antispoof=${antispoof:-no}
 
 echo "network-nat $OP netdev=$netdev antispoof=$antispoof"
 

                 reply	other threads:[~2005-02-27 17:47 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=422207AB.1070403@comcast.net \
    --to=nsnix@comcast.net \
    --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.