cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] rafaelweingartner closed pull request #12: bridge section was missing
Date Wed, 07 Nov 2018 13:02:49 GMT
rafaelweingartner closed pull request #12: bridge section was missing

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/source/quickinstallationguide/qig.rst b/source/quickinstallationguide/qig.rst
index a45962b..2ce77f3 100644
--- a/source/quickinstallationguide/qig.rst
+++ b/source/quickinstallationguide/qig.rst
@@ -104,27 +104,43 @@ Connecting via the console you should login as root. Check the file
 Unfortunately, this configuration will not permit you to connect to the 
 network, and is also unsuitable for our purposes with CloudStack. We want to 
-configure that file so that it specifies the IP address, netmask, etc., as 
-shown in the following example:
+configure that file so that it specifies the IP address, netmask, etc. We will 
+edit the eth0 interface and make it part of bridge named "cloudbr0" as shown in the
+following example:
 .. note:: 
    You should not use the Hardware Address (aka the MAC address) from our 
    example for your configuration. It is network interface specific, so you 
    should keep the address already provided in the HWADDR directive.
+vi /etc/sysconfig/network-scripts/ifcfg-eth0
-   HWADDR=52:54:00:B9:A6:C0
+   HWADDR=00:04:xx:xx:xx:xx
+   TYPE=Ethernet
+   BRIDGE=cloudbr0
+vi /etc/sysconfig/network-scripts/ifcfg-cloudbr0
+   DEVICE=cloudbr0
+   TYPE=Bridge
+   ONBOOT=yes
+   BOOTPROTO=none
+   IPV6INIT=no
+   DELAY=5
+   STP=yes
 .. note:: 
    IP Addressing - Throughout this document we are assuming that you will have 
    a /24 network for your CloudStack implementation. This can be any RFC 1918 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message