mirror of
https://github.com/libvirt/libvirt.git
synced 2025-02-25 18:55:26 -06:00
network: new network forward mode 'open'
The new forward mode 'open' is just like mode='route', except that no firewall rules are added to assure that any traffic does or doesn't pass. It is assumed that either they aren't necessary, or they will be setup outside the scope of libvirt. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=846810
This commit is contained in:
@@ -260,6 +260,28 @@
|
||||
<span class="since">Since 0.4.2</span>
|
||||
</dd>
|
||||
|
||||
<dt><code>open</code></dt>
|
||||
<dd>
|
||||
As with mode='route', guest network traffic will be
|
||||
forwarded to the physical network via the host's IP
|
||||
routing stack, but there will be no firewall rules added
|
||||
to either enable or prevent any of this traffic. When
|
||||
forward='open' is set, the <code>dev</code> attribute
|
||||
cannot be set (because the forward dev is enforced with
|
||||
firewall rules, and the purpose of forward='open' is to
|
||||
have a forwarding mode where libvirt doesn't add any
|
||||
firewall rules). This mode presumes that the local LAN
|
||||
router has suitable routing table entries to return
|
||||
traffic to this host, and that some other management
|
||||
system has been used to put in place any necessary
|
||||
firewall rules. Although no firewall rules will be added
|
||||
for the network, it is of course still possible to add
|
||||
restrictions for specific guests using
|
||||
<a href="formatnwfilter.html">nwfilter rules</a> on the
|
||||
guests' interfaces.)
|
||||
<span class="since">Since 2.2.0</span>
|
||||
</dd>
|
||||
|
||||
<dt><code>bridge</code></dt>
|
||||
<dd>
|
||||
This network describes either 1) an existing host bridge
|
||||
|
||||
Reference in New Issue
Block a user