/usr/share/doc/bridge-utils/FIREWALL is in bridge-utils 1.5-15ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | Bridging and firewalling
------------------------
It is possible to use bridging in combination with firewalling. This is
a blatant violation of the OSI model, but it's very useful, so we don't
care.
Assuming you are on a non-stone age kernel (less than 5 years old).
You can use the regular iptables firewalling as if you were doing
routing. So, rules for forwarding are added to the FORWARD chain,
rules for input to the local machine are added to the INPUT chain,
etc. Things will work like you expect them to.
So a rule like
# iptables -A INPUT -i eth0 -j DROP
will drop all traffic coming from 'eth0', even if the interface the packets
are logically from is, say, 'br0'.
Lennert Buytenhek, November 7th 2001
<buytenh@gnu.org>
--------------------------
Bridge+firewalling with 2.2 kernels is also possible, but deprecated. I
would severely recommend against using a 2.2 kernel and ipchains for bridge
firewalling. But if there's really a need, it's still possible. Apply the
extra firewalling patch available from the 'patches' section to your
already-patched-with-the-vanilla-bridge-patch 2.2 kernel, and recompile. Now
if you boot this kernel, the bridging code will check each to-be-forwarded
packet against the ipchains chain which has the same name as the bridge. So..
if a packet on eth0 is to be forwarded to eth1, and those interfaces are
both part of the bridge group br0, the bridging code will check the packet
against the chain called 'br0'. If the chain does not exist, the packet will
be forwarded. So if you want to do firewalling, you'll have to create the
chain yourself. This is important!
|