holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

More 6to4 updates

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@9150 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2008-12-20 16:07:08 +00:00
parent 3db58ceaf5
commit 7e56d56b4e
1 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/6to4.xml
View File

@ -260,7 +260,8 @@ ursa:~ #</programlisting>
<section>
<title>Configuring Shorewall</title>
<para>We need to add an entry in /etc/shorewall/tunnels:</para>
<para>We need to add an entry in /etc/shorewall/tunnels and restart
Shorewall:</para>
<programlisting>#TYPE ZONE GATEWAY GATEWAY
# ZONE
@ -282,11 +283,8 @@ ursa:~ #</programlisting>
<para>If that doesn't work from your firewall and from any local IPv6
systems that you have behind your firewall, do not go any further until
it does work. If you ask for help from the Shorewall team, the first
question we will ask is 'Can you ping6 2001:19f0:feee::dead:beef:cafe?'.
If you can't we won't help you. It's not that we don't want to help; it
is just that most Linux users don't have a clue how IPv4 works let alone
IPv6 -- we simply don't have the bandwidth to teach you the basics of
IPv6.</para>
question we will ask is 'With Shorewall6 cleared, can you ping6
2001:19f0:feee::dead:beef:cafe?'.</para>
<para>The Shorewall6 configuration on my firewall is a very basic
three-interface one.</para>
@ -303,7 +301,7 @@ dmz ipv6
<para><filename>/etc/shorewall6/interfaces</filename>:</para>
<programlisting>#ZONE INTERFACE BROADCAST OPTIONS
<programlisting>#ZONE INTERFACE BROADCAST OPTIONS
net sit1 detect tcpflags,forward=1,nosmurfs
loc eth0 detect tcpflags,forward=1
dmz eth2 detect tcpflags,forward=1