forked from extern/shorewall_code
Modify 'ping6' advice
This commit is contained in:
parent
53ab9427fc
commit
8932106394
@ -429,14 +429,15 @@ iface sit1 inet6 v4tunnel
|
||||
instructions above, you should have a completely functional IPv6
|
||||
network. Try:</para>
|
||||
|
||||
<programlisting><emphasis role="bold">ping6 2001:19f0:feee::dead:beef:cafe</emphasis>
|
||||
<programlisting><emphasis role="bold">ping6 www.kame.net
|
||||
ping6 ipv6.chat.eu.freenode.net</emphasis>
|
||||
</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 'With Shorewall6 cleared, can you ping6
|
||||
2001:19f0:feee::dead:beef:cafe?'.</para>
|
||||
<para>If neither of those work from your firewall and from any local
|
||||
IPv6 systems that you have behind your firewall, do not go any further
|
||||
until one of them does work. If you ask for help from the Shorewall
|
||||
team, the first question we will ask is 'With Shorewall6 cleared, can
|
||||
you ping6 kame or freenode?'.</para>
|
||||
|
||||
<para>The Shorewall6 configuration on my firewall is a very basic
|
||||
three-interface one.</para>
|
||||
|
Loading…
Reference in New Issue
Block a user