extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-28 18:43:30 +01:00
Code Issues Packages Projects Releases Wiki Activity

More hacks to make xsltproc work

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@8603 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2008-07-04 15:22:03 +00:00
parent 9a326105aa
commit bc0fb7e178
5 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/blacklisting_support_ru.xml
View File

@ -38,7 +38,7 @@
<orderedlist>
<listitem>
<para>BLACKLISTNEWONLY=No --&nbsp; проверка осуществляется для всех входящих пакетов. Новые записи в чёрном списке позволяют прервать уже существующие соединения.</para>
<para>BLACKLISTNEWONLY=No -- проверка осуществляется для всех входящих пакетов. Новые записи в чёрном списке позволяют прервать уже существующие соединения.</para>
</listitem>
<listitem>

4
docs/dhcp.xml
View File

@ -83,7 +83,7 @@
<para>Specify the <quote>dhcp</quote> option for this interface in the
<ulink
url="manpages/shorewall-interfaces.html"><filename>/etc/shorewall/interfaces</filename></ulink>
file.&nbsp;This will generate rules that will allow DHCP to and from
file. This will generate rules that will allow DHCP to and from
your firewall system.</para>
</listitem>
@ -129,7 +129,7 @@
<para>Specify the <quote>dhcp</quote> option for the bridge interface
in the <ulink
url="manpages/shorewall-interfaces.html"><filename>/etc/shorewall/interfaces</filename></ulink>
file.&nbsp;This will generate rules that will allow DHCP to and from
file. This will generate rules that will allow DHCP to and from
your firewall system as well as through the bridge.</para>
</listitem>
</itemizedlist>

2
docs/kernel.xml
View File

@ -98,7 +98,7 @@
<blockquote>
<programlisting>#
#&nbsp;&nbsp; IP: Netfilter Configuration
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m

2
docs/shorewall_setup_guide.xml
View File

@ -2423,7 +2423,7 @@ foobar.net. 86400 IN A 192.0.2.177
Also, I don't recommend using <quote>shorewall restart</quote>; it is
better to create an <ulink
url="starting_and_stopping_shorewall.htm"><emphasis>an alternate
configuration</emphasis></ulink>&nbsp; and test it using the
configuration</emphasis></ulink> and test it using the
<quote><ulink
url="starting_and_stopping_shorewall.htm"><command>shorewall
try</command></ulink></quote> command.</para>

4
docs/troubleshoot.xml
View File

@ -414,14 +414,14 @@ ACCEPT dmz loc udp 53</programlisting>
<programlisting>#ACTION SOURCE DEST PROTO DEST
# PORT(S)
Ping/ACCEPT <emphasis>&lt;source zone&gt;</emphasis>&nbsp;&nbsp; <emphasis>&lt;destination zone&gt;</emphasis></programlisting>
Ping/ACCEPT <emphasis>&lt;source zone&gt;</emphasis> <emphasis>&lt;destination zone&gt;</emphasis></programlisting>
<para>The ramifications of this can be subtle. For example, if you
have the following in <filename><ulink
url="NAT.htm">/etc/shorewall/nat</ulink></filename>:</para>
<programlisting>#EXTERNAL INTERFACE INTERNAL
10.1.1.2&nbsp;&nbsp;&nbsp; eth0&nbsp;&nbsp;&nbsp; 130.252.100.18</programlisting>
10.1.1.2 eth0 130.252.100.18</programlisting>
<para>and you ping 130.252.100.18, unless you have allowed icmp type 8
between the zone containing the system you are pinging from and the