extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-06-24 03:31:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

More cleanup of setup guide

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1055 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-01-04 16:15:35 +00:00
parent fd1e648aa8
commit b37e367832
2 changed files with 25 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Shorewall-docs/shorewall_setup_guide.xml
View File

@ -898,11 +898,12 @@ loc eth2 detect</programlisting>
<title>Routing</title> <title>Routing</title>
<para>One of the purposes of subnetting is that it forms the basis for <para>One of the purposes of subnetting is that it forms the basis for
routing. Here&#39;s the routing table on my firewall:</para> routing. Here&#39;s the routing table on my firewall (compressed for
PDF):</para>
<programlisting>[root@gateway root]# netstat -nr <programlisting>[root@gateway root]# netstat -nr
Kernel IP routing table Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface Destination Gateway Genmask Flgs MSS Win irtt Iface
192.168.9.1 0.0.0.0 255.255.255.255 UH 40 0 0 texas 192.168.9.1 0.0.0.0 255.255.255.255 UH 40 0 0 texas
206.124.146.177 0.0.0.0 255.255.255.255 UH 40 0 0 eth1 206.124.146.177 0.0.0.0 255.255.255.255 UH 40 0 0 eth1
206.124.146.180 0.0.0.0 255.255.255.255 UH 40 0 0 eth3 206.124.146.180 0.0.0.0 255.255.255.255 UH 40 0 0 eth3
@ -1002,10 +1003,10 @@ Destination Gateway Genmask Flags MSS Window irtt Iface
<programlisting>[root@gateway root]# <command>ip addr show eth0</command> <programlisting>[root@gateway root]# <command>ip addr show eth0</command>
2: eth0: &#60;BROADCAST,MULTICAST,UP&#62; mtu 1500 qdisc htb qlen 100 2: eth0: &#60;BROADCAST,MULTICAST,UP&#62; mtu 1500 qdisc htb qlen 100
link/ether 02:00:08:e3:fa:55 brd ff:ff:ff:ff:ff:ff link/ether 02:00:08:e3:fa:55 brd ff:ff:ff:ff:ff:ff
inet 206.124.146.176/24 brd 206.124.146.255 scope global eth0 inet 206.124.146.176/24 brd 206.124.146.255 scope global eth0
inet 206.124.146.178/24 brd 206.124.146.255 scope global secondary eth0 inet 206.124.146.178/24 brd 206.124.146.255 scope global secondary eth0
inet 206.124.146.179/24 brd 206.124.146.255 scope global secondary eth0 inet 206.124.146.179/24 brd 206.124.146.255 scope global secondary eth0
[root@gateway root]# [root@gateway root]#
</programlisting> </programlisting>
@ -1188,7 +1189,7 @@ tcpdump: listening on eth2
What if DMZ 1 (192.0.2.67) tries to communicate with 192.0.2.65? The What if DMZ 1 (192.0.2.67) tries to communicate with 192.0.2.65? The
routing table on DMZ 1 will look like this:</para> routing table on DMZ 1 will look like this:</para>
<programlisting>Kernel IP routing table <programlisting format="linespecific">Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface Destination Gateway Genmask Flags MSS Window irtt Iface
192.0.2.64 0.0.0.0 255.255.255.248 U 40 0 0 eth0 192.0.2.64 0.0.0.0 255.255.255.248 U 40 0 0 eth0
0.0.0.0 192.0.2.66 0.0.0.0 UG 40 0 0 eth0</programlisting> 0.0.0.0 192.0.2.66 0.0.0.0 UG 40 0 0 eth0</programlisting>
@ -1836,8 +1837,8 @@ view &#34;internal&#34; {
192.0.2.179/32; 192.0.2.179/32;
192.0.2.180/32; }; 192.0.2.180/32; };
# #
# If this server can&#39;t complete the request, it should use outside # If this server can&#39;t complete the request, it should use
# servers to do so # outside servers to do so
# #
recursion yes; recursion yes;

2
Shorewall-docs/support.xml
View File

@ -15,7 +15,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2003-01-01</pubdate> <pubdate>2004-01-01</pubdate>
<copyright> <copyright>
<year>2001-2004</year> <year>2001-2004</year>