Add bridge/kernel 2.6.20 FAQ

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@6079 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2007-04-23 15:11:05 +00:00
parent fd7301cc6c
commit c51742630c

View File

@ -845,6 +845,26 @@ to debug/develop the newnat interface.</programlisting></para>
url="SimpleBridge.html">Shorewall Simple Bridge url="SimpleBridge.html">Shorewall Simple Bridge
documentation</ulink>.</para> documentation</ulink>.</para>
</section> </section>
<section>
<title>(FAQ 63) I just upgraded my kernel to 2.6.20 and my
bridge/firewall stopped working. What is wrong?</title>
<para><emphasis role="bold">Answer:</emphasis> In kernel 2.6.20, the
Netfilter <firstterm>physdev match</firstterm> feature was changed such
that it is no longer capable of matching the output device of
non-bridged traffic. You will see messages such as the following in your
log:</para>
<programlisting>Apr 20 15:03:50 wookie kernel: [14736.560947] physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for
non-bridged traffic is not supported anymore.</programlisting>
<para>This kernel change, while necessary, means that Shorewall zones
may no longer be defined in terms of bridge ports. See <ulink
url="NewBridge.html">the new bridging documentation</ulink> for
information about configuring a bridge/firewall under kernel 2.6.20 and
later.</para>
</section>
</section> </section>
<section> <section>