forked from extern/shorewall_code
Add caution about Bridges and kernel 2.6.20
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@6094 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
3388cc98bd
commit
4eda3e7902
@ -108,6 +108,13 @@
|
|||||||
in (the Extended) Dom0 to isolate the server(s) from the other local
|
in (the Extended) Dom0 to isolate the server(s) from the other local
|
||||||
systems (including Dom0).</para>
|
systems (including Dom0).</para>
|
||||||
|
|
||||||
|
<caution>
|
||||||
|
<para>The Shorewall configuration shown in this article does not work
|
||||||
|
with kernel 2.6.20 and later. For new Xen installations, I strongly
|
||||||
|
recommend against a bridged Xen Domain 0 unless you <ulink
|
||||||
|
url="XenMyWay.html">run Shorewall in a DomU</ulink>.</para>
|
||||||
|
</caution>
|
||||||
|
|
||||||
<caution>
|
<caution>
|
||||||
<para>I find a bridged Xen Domain 0 to be an arcane environment in which
|
<para>I find a bridged Xen Domain 0 to be an arcane environment in which
|
||||||
to try to use Netfilter (and hence Shorewall). As the number of
|
to try to use Netfilter (and hence Shorewall). As the number of
|
||||||
|
Loading…
Reference in New Issue
Block a user