diff --git a/Shorewall-docs2/dhcp.xml b/Shorewall-docs2/dhcp.xml
index 00d6c719f..4fe2c96c7 100755
--- a/Shorewall-docs2/dhcp.xml
+++ b/Shorewall-docs2/dhcp.xml
@@ -15,7 +15,7 @@
- 2004-05-24
+ 2005-11-29
2001
@@ -24,6 +24,8 @@
2004
+ 2005
+
Thomas M. Eastep
@@ -105,4 +107,19 @@
+
+
+ If you wish to pass DHCP requests and responses through a
+ bridge
+
+
+
+ Specify the dhcp
option for the bridge interface
+ in the /etc/shorewall/interfaces
+ file. This will generate rules that will allow DHCP to and from
+ your firewall system as well as through the bridge.
+
+
+
\ No newline at end of file
diff --git a/Shorewall-docs2/three-interface.xml b/Shorewall-docs2/three-interface.xml
index 23beb8104..6667863c2 100755
--- a/Shorewall-docs2/three-interface.xml
+++ b/Shorewall-docs2/three-interface.xml
@@ -15,7 +15,7 @@
- 2005-11-22
+ 2005-11-25
2002-2005
@@ -838,7 +838,7 @@ ACCEPT <source zone> <destination zone> <protocol&g
#ACTION SOURCE DEST PROTO DEST PORT(S)
DNS/ACCEPT net $FW
- Not using defined actions:
+ Not using defined macros:
#ACTION SOURCE DEST PROTO DEST PORT(S)
ACCEPT net $FW tcp 53
@@ -942,15 +942,12 @@ ACCEPT net $FW tcp 80 /etc/shorewall/startup_disabled.
+ firewall, you can enable Shorewall startup by editing
+ /etc/shorewall/shorewall.conf and setting
+ STARTUP_ENABLED=Yes.
Users of the .deb package must edit
/etc/default/shorewall and set
startup=1.
-
- You should edit
- /etc/shorewall/shorewall.conf and set
- STARTUP_ENABLED=Yes.
The firewall is started using the shorewall
start command and stopped using shorewall
stop. When the firewall is stopped, routing is enabled on those