Prompted by a question on the internet, the following diff removes the useless virtual ethernet interface from "Option 4 - VMs as real hosts on the same network" where guests are bridged directly into the host network.
vether(4) serves no purpose in this setup, the egress interface can/will be used to communicate with guests. As florian@ noted, this is probably a copy/pasta left-over from "Option 3". Feedback? Objections? OK? Index: faq16.html =================================================================== RCS file: /cvs/www/faq/faq16.html,v retrieving revision 1.6 diff -u -p -r1.6 faq16.html --- faq16.html 30 Oct 2018 12:10:34 -0000 1.6 +++ faq16.html 30 Oct 2018 19:31:01 -0000 @@ -282,25 +282,13 @@ This option only works for Ethernet-base prevents wireless interfaces from participating in network bridges. <p> -Create the <code>vether0</code> interface: - -<pre class="cmdbox"> -# <b>echo 'up' > /etc/hostname.vether0</b> -# <b>sh /etc/netstart vether0</b> -</pre> - -The <code>vether0</code> interface will be used as the local interface for the -host that is managed via DHCP on the host network. - -<p> Create the <code>bridge0</code> interface with the host network interface as a -bridge port, along with the newly created <code>vether0</code> interface. +bridge port. In this example, the host network interface is <code>em0</code> - you should substitute the interface name that you wish to connect the VM to: <pre class="cmdbox"> # <b>echo 'add em0' > /etc/hostname.bridge0</b> -# <b>echo 'add vether0' >> /etc/hostname.bridge0</b> # <b>sh /etc/netstart bridge0</b> </pre>
