cloudstack-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jtomec...@apache.org
Subject [1/2] git commit: refs/heads/4.1 - CLOUDSTACK-1028. Doc. Re-add section Firewall Rules: this section is about ingress rules. Fix intro sentence to agree with new Egress Rules section. Egress traffic is now blocked by default.
Date Fri, 22 Mar 2013 03:50:56 GMT
Updated Branches:
  refs/heads/4.1 886c3a569 -> aa449b70e


CLOUDSTACK-1028.  Doc. Re-add section Firewall Rules: this section is about ingress rules.
Fix intro sentence to agree with new Egress Rules section. Egress traffic is now blocked by
default.


Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo
Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/b1fa2669
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/b1fa2669
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/b1fa2669

Branch: refs/heads/4.1
Commit: b1fa2669ce2ad85281b513e41ddd9e79d218feb6
Parents: 886c3a5
Author: Jessica Tomechak <jessica.tomechak@gmail.com>
Authored: Thu Mar 21 20:43:10 2013 -0700
Committer: Jessica Tomechak <jessica.tomechak@gmail.com>
Committed: Thu Mar 21 20:50:13 2013 -0700

----------------------------------------------------------------------
 docs/en-US/ip-forwarding-firewalling.xml |   11 +++++++----
 1 files changed, 7 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack/blob/b1fa2669/docs/en-US/ip-forwarding-firewalling.xml
----------------------------------------------------------------------
diff --git a/docs/en-US/ip-forwarding-firewalling.xml b/docs/en-US/ip-forwarding-firewalling.xml
index 54e18b7..4705dbd 100644
--- a/docs/en-US/ip-forwarding-firewalling.xml
+++ b/docs/en-US/ip-forwarding-firewalling.xml
@@ -20,13 +20,16 @@
 -->
 <section id="ip-forwarding-firewalling">
   <title>IP Forwarding and Firewalling</title>
-  <para>By default, all incoming traffic to the public IP address is rejected. All
outgoing traffic
-    from the guests is translated via NAT to the public IP address and is allowed.</para>
+  <para>By default, all incoming traffic to the public IP address is rejected.
+    All outgoing traffic from the guests is also blocked by default.</para>
+  <para>To allow outgoing traffic, follow the procedure in <xref linkend="egress-firewall-rule"/>.</para>
   <para>To allow incoming traffic, users may set up firewall rules and/or port forwarding
rules. For
     example, you can use a firewall rule to open a range of ports on the public IP address,
such as
     33 through 44. Then use port forwarding rules to direct traffic from individual ports
within
     that range to specific ports on user VMs. For example, one port forwarding rule could
route
-    incoming traffic on the public IP's port 33 to port 100 on one user VM's private IP.</para>
-   <xi:include href="egress-firewall-rule.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+    incoming traffic on the public IP's port 33 to port 100 on one user VM's private IP.
+    For more information, see <xref linkend="firewall-rules"/> and <xref linkend="port-forwarding"/>.</para>
+  <xi:include href="egress-firewall-rule.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
+  <xi:include href="firewall-rules.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
   <xi:include href="port-forwarding.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/>
 </section>


Mime
View raw message