mirror of https://github.com/tLDP/LDP
pbldp
parent
7a6db5704b
commit
c61d9764c9
|
|
@ -20,9 +20,9 @@
|
|||
<affiliation><address> <email>pb (at) bieringer.de</email> </address> </affiliation>
|
||||
</author>
|
||||
<revhistory>
|
||||
<revision> <revnumber>Release 0.19</revnumber> <date>2002-01-25</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
|
||||
<revision> <revnumber>Release 0.18</revnumber> <date>2002-01-22</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
|
||||
<revision> <revnumber>Release 0.17</revnumber> <date>2002-01-19</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
|
||||
<revision> <revnumber>Release 0.16</revnumber> <date>2002-01-19</date> <authorinitials>PB</authorinitials> <revremark>See <link linkend="revision-history">revision history</link> for more</revremark></revision>
|
||||
</revhistory>
|
||||
<abstract>
|
||||
<para>
|
||||
|
|
@ -35,8 +35,8 @@
|
|||
General
|
||||
</title>
|
||||
<comment>
|
||||
“<” must be encoded using “&lt;” because of SGML export, otherwise this will be recognized as SGML tag, which isn't really one...
|
||||
CVS-ID: $Id: Linux+IPv6-HOWTO.lyx,v 1.4 2002/01/22 07:59:48 pbldp Exp $
|
||||
"<" must be encoded using "&lt;" because of SGML export, otherwise this will be recognized as SGML tag, which isn't really one...
|
||||
CVS-ID: $Id: Linux+IPv6-HOWTO.lyx,v 1.8 2002/01/25 21:17:12 pbldp Exp $
|
||||
</comment>
|
||||
<sect1 id="general-copright">
|
||||
<title>
|
||||
|
|
@ -90,7 +90,7 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
1993: I got in contact with the Internet using console based e-mail and news client (e.g. look for “e91abier” on <ulink url="http://groups.google.com/">groups.google.com</ulink>, that's me).
|
||||
1993: I got in contact with the Internet using console based e-mail and news client (e.g. look for "e91abier" on <ulink url="http://groups.google.com/">groups.google.com</ulink>, that's me).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
|
|
@ -128,7 +128,7 @@
|
|||
Category
|
||||
</title>
|
||||
<para>
|
||||
This HOWTO should be listed in category “<emphasis>Networking</emphasis>/<emphasis>Protocols</emphasis>”.
|
||||
This HOWTO should be listed in category "<emphasis>Networking</emphasis>/<emphasis>Protocols</emphasis>".
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
|
|
@ -216,19 +216,19 @@
|
|||
<title>
|
||||
Technical
|
||||
</title>
|
||||
<sect2>
|
||||
<sect2 id="general-original-source">
|
||||
<title>
|
||||
Original source of this HOWTO
|
||||
</title>
|
||||
<para>
|
||||
This HOWTO is written with LyX version 1.1.6fix1 on a Red Hat Linux 7.2 system with template SGML (DocBook book).
|
||||
This HOWTO is written with LyX version 1.1.6fix1 on a Red Hat Linux 7.2 system with template SGML (DocBook book). It's available on <ulink url="http://cvsview.linuxdoc.org/index.cgi/users/Peter-Bieringer/?cvsroot=Linuxdoc">LDP-CVS / users / Peter-Bieringer</ulink> for contribution.
|
||||
</para>
|
||||
<sect3>
|
||||
<title>
|
||||
Code line wrapping
|
||||
</title>
|
||||
<para>
|
||||
Code line wrapping is done using selfmade utility “lyxcodelinewrapper.pl”, you can get it from CVS for your own usage: <ulink url="http://cvsview.linuxdoc.org/index.cgi/users/Peter-Bieringer/?cvsroot=Linuxdoc">LDP-CVS / users / Peter-Bieringer</ulink>
|
||||
Code line wrapping is done using selfmade utility "lyxcodelinewrapper.pl", you can get it from CVS for your own usage: <ulink url="http://cvsview.linuxdoc.org/index.cgi/users/Peter-Bieringer/?cvsroot=Linuxdoc">LDP-CVS / users / Peter-Bieringer</ulink>
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3>
|
||||
|
|
@ -238,6 +238,21 @@
|
|||
<para>
|
||||
SGML is generated using export function in LyX.
|
||||
</para>
|
||||
<para>
|
||||
Also some fixes are have to be made to create proper SGML code (see also here for the Perl programs <ulink url="http://cvsview.linuxdoc.org/index.cgi/users/Peter-Bieringer/?cvsroot=Linuxdoc">LDP-CVS / users / Peter-Bieringer</ulink>):
|
||||
</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Export of LyX table does not create proper "colspan" tags - tool for fixing: "sgmllyxtabletagfix.pl"
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
LyX sometimes uses special left/right entinities for qoutes instead the normal one, which will still exist in generated HTML. Some browers don't parse this very well (known: Opera 6 TP 2 or Konqueror) - tool for fixing: "sgmllyxquotefix.pl"
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
<sect2>
|
||||
|
|
@ -287,7 +302,7 @@
|
|||
The first IPv6 related document was written by <emphasis>Eric Osborne</emphasis> and called <ulink url="http://www.linuxhq.com/IPv6/">Linux IPv6 FAQ/HOWTO</ulink> (please use it only for historical issues). Latest version was 3.2.1 released 14. Juli 1997.
|
||||
</para>
|
||||
<para>
|
||||
Please help: if someone knows the date of birth of this HOWTO, please send me an e-mail (information will be needed in “history”).
|
||||
Please help: if someone knows the date of birth of this HOWTO, please send me an e-mail (information will be needed in "history").
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3>
|
||||
|
|
@ -295,7 +310,7 @@
|
|||
IPv6 & Linux - HowTo (maintained)
|
||||
</title>
|
||||
<comment>
|
||||
This HOWTO is really named “HowTo”
|
||||
This HOWTO is really named "HowTo"
|
||||
</comment>
|
||||
<para>
|
||||
There exists a second one called <ulink url="http://www.bieringer.de/linux/IPv6/">IPv6 & Linux - HowTo</ulink> written by me (<emphasis>Peter Bieringer</emphasis>) in pure HTML. It was born April 1997 and the first English version was published in June 1997. I will continue to maintain it, but it will slowly fade in favor of the Linux IPv6 HOWTO you are reading right this second.
|
||||
|
|
@ -380,7 +395,7 @@
|
|||
Long code line wrapping signal char
|
||||
</title>
|
||||
<para>
|
||||
The special char “¬” is used for signalling that this code line is wrapped for better viewing in PDF and PS files.
|
||||
The special char "¬" is used for signalling that this code line is wrapped for better viewing in PDF and PS files.
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3>
|
||||
|
|
@ -563,7 +578,7 @@ diff -u --recursive --new-file v2.1.7/linux/include/linux/in6.h
|
|||
2^{128}-1: 340282366920938463463374607431768211455
|
||||
</programlisting>
|
||||
<para>
|
||||
"Such numbers are not really addresses that can be memorized. Also the IPv6 address schema is bitwise orientated (just like IPv4, but that's not often recognized). Therefore a better notation of such big numbers is hexadecimal. In hexadecimal, 4 bits (also known as “nibble”) are represented by a digit or char from 0-9 and a-f (10-15) and reduces the length to 32 chars.
|
||||
"Such numbers are not really addresses that can be memorized. Also the IPv6 address schema is bitwise orientated (just like IPv4, but that's not often recognized). Therefore a better notation of such big numbers is hexadecimal. In hexadecimal, 4 bits (also known as "nibble") are represented by a digit or char from 0-9 and a-f (10-15) and reduces the length to 32 chars.
|
||||
</para>
|
||||
<programlisting>
|
||||
2^{128}-1: 0xffffffffffffffffffffffffffffffff
|
||||
|
|
@ -588,7 +603,7 @@ diff -u --recursive --new-file v2.1.7/linux/include/linux/in6.h
|
|||
¬ 3ffe:ffff:100:f101:210:a4ff:fee3:9566
|
||||
</programlisting>
|
||||
<para>
|
||||
One sequence of 16 bit blocks containing only zeroes can be replaced with “::“. But not more than one time, because otherwise its no longer a unique representation.
|
||||
One sequence of 16 bit blocks containing only zeroes can be replaced with "::". But not more than one time, because otherwise its no longer a unique representation.
|
||||
</para>
|
||||
<programlisting>
|
||||
3ffe:ffff:100:f101:0:0:0:1 -> 3ffe:ffff:100:f101::1
|
||||
|
|
@ -650,7 +665,7 @@ Itu&-ZQ82s>J%s99FJXT
|
|||
So designers have chosen 128 bit, 4 times more in length and 2^96 in size than in IPv4 today.
|
||||
</para>
|
||||
<para>
|
||||
But the usable size is smaller than it may appear, because in the currently defined address schema, 64 bits are user for interface identifiers. The other 64 bits are used for routing. Assuming the current strict levels of aggregation (/48, /35, ...), it's still possible to “run out” of space, but surely not in the near future.
|
||||
But the usable size is smaller than it may appear, because in the currently defined address schema, 64 bits are user for interface identifiers. The other 64 bits are used for routing. Assuming the current strict levels of aggregation (/48, /35, ...), it's still possible to "run out" of space, but surely not in the near future.
|
||||
</para>
|
||||
</sect2>
|
||||
<sect2>
|
||||
|
|
@ -694,7 +709,7 @@ Itu&-ZQ82s>J%s99FJXT
|
|||
Localhost address
|
||||
</title>
|
||||
<para>
|
||||
This is a special address for the loopback interface, like IPv4 with its “127.0.0.1”. With IPv6, the localhost address is:
|
||||
This is a special address for the loopback interface, like IPv4 with its "127.0.0.1". With IPv6, the localhost address is:
|
||||
</para>
|
||||
<programlisting>
|
||||
0000:0000:0000:0000:0000:0000:0000:0001
|
||||
|
|
@ -714,7 +729,7 @@ Itu&-ZQ82s>J%s99FJXT
|
|||
Unspecified address
|
||||
</title>
|
||||
<para>
|
||||
This is a special address like “any” or “0.0.0.0” in IPv4 . For IPv6 it's:
|
||||
This is a special address like "any" or "0.0.0.0" in IPv4 . For IPv6 it's:
|
||||
</para>
|
||||
<programlisting>
|
||||
0000:0000:0000:0000:0000:0000:0000:0000
|
||||
|
|
@ -817,7 +832,7 @@ Itu&-ZQ82s>J%s99FJXT
|
|||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>
|
||||
They're starting with (<emphasis>“x”</emphasis> is any hex char, normally <emphasis>“0</emphasis>”)
|
||||
They're starting with (<emphasis>"x"</emphasis> is any hex char, normally <emphasis>"0</emphasis>")
|
||||
</para>
|
||||
<programlisting>
|
||||
fe8<emphasis>x: <- currently the only used one</emphasis>
|
||||
|
|
@ -843,7 +858,7 @@ feb<emphasis>x:</emphasis>
|
|||
Another advantage: because it's possible to assign more than one address to an interface with IPv6, you can also assign such a site local address in addition to a global one.
|
||||
</para>
|
||||
<para>
|
||||
It's starting with (<emphasis>“x”</emphasis> is any hex char, normally <emphasis>“0</emphasis>”)
|
||||
It's starting with (<emphasis>"x"</emphasis> is any hex char, normally <emphasis>"0</emphasis>")
|
||||
</para>
|
||||
<programlisting>
|
||||
fec<emphasis>x: <- common used one</emphasis>
|
||||
|
|
@ -1028,7 +1043,7 @@ ff<emphasis>x</emphasis>y:
|
|||
ff02::1:ff00:1234
|
||||
</programlisting>
|
||||
<para>
|
||||
Used prefix shows that this is a link-local multicast address. The suffix is generated from the destination address. In this example, a packet should be sent to address “fe80::1234”, but the network stack don't know the current layer 2 MAC address. It replaces the upper 104 bits with “ff02:0:0:0:0:1:ff00::/104” and let the least 24 bits exist. Such address is now used on-link to find the corresponding node which has to send a reply containing its layer 2 MAC address also.
|
||||
Used prefix shows that this is a link-local multicast address. The suffix is generated from the destination address. In this example, a packet should be sent to address "fe80::1234", but the network stack don't know the current layer 2 MAC address. It replaces the upper 104 bits with "ff02:0:0:0:0:1:ff00::/104" and let the least 24 bits exist. Such address is now used on-link to find the corresponding node which has to send a reply containing its layer 2 MAC address also.
|
||||
</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
|
@ -1122,7 +1137,7 @@ ff02::1:ff00:1234
|
|||
3ffe:ffff:100:f101::1
|
||||
</programlisting>
|
||||
<para>
|
||||
For manual suffixes like “::1” shown in the above example it's required that the 6th most significant bit is set to 0 (the universal/local bit of the automatically generated identifier). Also some other (otherwise unchosen) bit combinations are reserved for anycast addresses, too.
|
||||
For manual suffixes like "::1" shown in the above example it's required that the 6th most significant bit is set to 0 (the universal/local bit of the automatically generated identifier). Also some other (otherwise unchosen) bit combinations are reserved for anycast addresses, too.
|
||||
</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
|
@ -1339,7 +1354,7 @@ alias net-pf-10 off # disable automatically load of IPv6 module on demand
|
|||
</para>
|
||||
<sect3>
|
||||
<title>
|
||||
Currently known never “IPv6 capable links”
|
||||
Currently known never "IPv6 capable links"
|
||||
</title>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -1361,7 +1376,7 @@ alias net-pf-10 off # disable automatically load of IPv6 module on demand
|
|||
</sect3>
|
||||
<sect3>
|
||||
<title>
|
||||
Currently known “not supported IPv6 capable links”
|
||||
Currently known "not supported IPv6 capable links"
|
||||
</title>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
@ -1440,7 +1455,7 @@ alias net-pf-10 off # disable automatically load of IPv6 module on demand
|
|||
<para>
|
||||
After you've prepared your system for IPv6, you sure want to use IPv6 now for network communications. First you should learn to look with a sniffer program for IPv6 packets. This is very recommended because in debug/troubleshooting issues this can help you very fast.
|
||||
</para>
|
||||
<sect2>
|
||||
<sect2 id="program-ping6">
|
||||
<title>
|
||||
IPv6 ping
|
||||
</title>
|
||||
|
|
@ -1585,17 +1600,17 @@ Resume: pmtu 1280
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
“-s 512”: increase the snap length during capturing of a packet to 512 bytes
|
||||
"-s 512": increase the snap length during capturing of a packet to 512 bytes
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
“-vv”: really verbose output
|
||||
"-vv": really verbose output
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
“-n”: don't resolve addresses to names, useful if reverse DNS resolving isn't working proper
|
||||
"-n": don't resolve addresses to names, useful if reverse DNS resolving isn't working proper
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -1694,7 +1709,7 @@ Content-Type: text/html; charset=ISO-8859-1
|
|||
Connection closed by foreign host.
|
||||
</programlisting>
|
||||
<para>
|
||||
If the telnet client don't understand the IPv6 address and says something like “cannot resolve hostname”, then it's not IPv6-enabled.
|
||||
If the telnet client don't understand the IPv6 address and says something like "cannot resolve hostname", then it's not IPv6-enabled.
|
||||
</para>
|
||||
</sect2>
|
||||
<sect2>
|
||||
|
|
@ -1726,7 +1741,7 @@ user@::1's password: ******
|
|||
[user@ipv6host user]$
|
||||
</programlisting>
|
||||
<para>
|
||||
If your ssh client don't understand the option “-6” then it's not IPv6-enabled, like most ssh version 1 packages.
|
||||
If your ssh client don't understand the option "-6" then it's not IPv6-enabled, like most ssh version 1 packages.
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3>
|
||||
|
|
@ -1784,6 +1799,44 @@ user@::1's password: ******
|
|||
In this part of this HOWTO, more client specific issues are mentioned. Therefore hints for IPv6-ready servers like sshd, httpd, telnetd, etc. are shown below in <link linkend="chapter-hints-daemons">Hints for IPv6-enabled daemons</link>.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>
|
||||
FAQ (IPv6-ready system check)
|
||||
</title>
|
||||
<sect2>
|
||||
<title>
|
||||
Using tools
|
||||
</title>
|
||||
<sect3>
|
||||
<title>
|
||||
Q: Cannot ping6 to link-local addresses
|
||||
</title>
|
||||
<para>
|
||||
Error message: "<emphasis>connect: Invalid argument</emphasis>"
|
||||
</para>
|
||||
<para>
|
||||
Kernel doesn't know, which physical or virtual link you want to use to send such ICMPv6 packets. Therefore it displays this error message.
|
||||
</para>
|
||||
<para>
|
||||
Solution: Specify interface like: "ping6 -I eth0 fe80::2e0:18ff:fe90:9205", see also <link linkend="program-ping6">program ping6 usage</link>.
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3>
|
||||
<title>
|
||||
Q: Cannot ping6 or traceroute6 as normal user
|
||||
</title>
|
||||
<para>
|
||||
Error message: "<emphasis>icmp socket: Operation not permitted</emphasis>"
|
||||
</para>
|
||||
<para>
|
||||
This utilities create special ICMPv6 packets and send them out. This is done by using raw sockets in the kernel. But raw sockets can only be used by the "root" user. Therefore normal users get such error message.
|
||||
</para>
|
||||
<para>
|
||||
Solution: If it's really needed that all users should be able to use this utilites, you can add the "suid" bit using "chmod u+s /path/to/program", see also <link linkend="program-ping6">program ping6 usage</link>. If not all users should be able to, you can change the group of the program to e.g. "wheel", add this power users to this group and remove the execution bit for other users using "chmod o-rwx /path/to/program". Or configure "sudo" for fullfilling your security policy.
|
||||
</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
<chapter id="chapter-configuration-interface">
|
||||
<title>
|
||||
|
|
@ -1871,7 +1924,7 @@ user@::1's password: ******
|
|||
Ether-tap device
|
||||
</title>
|
||||
<para>
|
||||
Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module “ethertap” has to be loaded before.
|
||||
Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module "ethertap" has to be loaded before.
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3>
|
||||
|
|
@ -2280,7 +2333,7 @@ ff00::/8 :: UA 256 0 0 eth0<emphasis> </emphasis><- Interface rou
|
|||
# /sbin/ip -6 route add 2000::/3 dev eth0 metric 1
|
||||
</programlisting>
|
||||
<para>
|
||||
Metric “1” is used here to be compatible with the metric used by route, because the default metric on using “ip” is “1024”.
|
||||
Metric "1" is used here to be compatible with the metric used by route, because the default metric on using "ip" is "1024".
|
||||
</para>
|
||||
</sect2>
|
||||
<sect2>
|
||||
|
|
@ -2419,7 +2472,7 @@ ff00::/8 :: UA 256 0 0 eth0<emphasis> </emphasis><- Interface rou
|
|||
Where FP is the known prefix for global addresses, TLA is the top level aggregator. V4ADDR is the node's global unique IPv4 address (in hexadecimal notation). SLA is the subnet identifier (65536 local subnets possible).
|
||||
</para>
|
||||
<para>
|
||||
Such prefix is generated and normally using SLA “0000” and suffix “::1” assigned to the 6to4 tunnel interface.
|
||||
Such prefix is generated and normally using SLA "0000" and suffix "::1" assigned to the 6to4 tunnel interface.
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3>
|
||||
|
|
@ -2427,7 +2480,7 @@ ff00::/8 :: UA 256 0 0 eth0<emphasis> </emphasis><- Interface rou
|
|||
Upstream tunneling
|
||||
</title>
|
||||
<para>
|
||||
The node has to know to which foreign tunnel endpoint its in IPv4 packed IPv6 packets should be send to. In “early” days of 6to4 tunneling, dedicated upstream accepting routers were defined. See <ulink url="http://www.kfu.com/~nsayer/6to4/">NSayer's 6to4 information</ulink> for a list of routers.
|
||||
The node has to know to which foreign tunnel endpoint its in IPv4 packed IPv6 packets should be send to. In "early" days of 6to4 tunneling, dedicated upstream accepting routers were defined. See <ulink url="http://www.kfu.com/~nsayer/6to4/">NSayer's 6to4 information</ulink> for a list of routers.
|
||||
</para>
|
||||
<para>
|
||||
Nowadays, 6to4 upstream routers can be found auto-magically using the anycast address 192.88.99.1. In the background routing protocols handle this, see <ulink url="http://www.faqs.org/rfcs/rfc3068.html">RFC 3068 / An Anycast Prefix for 6to4 Relay Routers</ulink> for details.
|
||||
|
|
@ -2713,7 +2766,7 @@ ff00::/8 :: UA 256 0 0 sit0
|
|||
2002:0102:0304::
|
||||
</programlisting>
|
||||
<para>
|
||||
Local 6to4 gateways should always assigned the manual suffix “::1”, therefore your local 6to4 address will be
|
||||
Local 6to4 gateways should always assigned the manual suffix "::1", therefore your local 6to4 address will be
|
||||
</para>
|
||||
<programlisting>
|
||||
2002:0102:0304::1
|
||||
|
|
@ -2755,7 +2808,7 @@ ff00::/8 :: UA 256 0 0 sit0
|
|||
</sect3>
|
||||
<sect3>
|
||||
<title>
|
||||
Using "ifconfig" and "route" and generic tunnel device “sit0” (deprecated)
|
||||
Using "ifconfig" and "route" and generic tunnel device "sit0" (deprecated)
|
||||
</title>
|
||||
<para>
|
||||
This is now deprecated because using the generic tunnel device sit0 doesn't let specify filtering per device.
|
||||
|
|
@ -2809,7 +2862,7 @@ ff00::/8 :: UA 256 0 0 sit0
|
|||
</sect3>
|
||||
<sect3>
|
||||
<title>
|
||||
Using “ifconfig” and “route” and generic tunnel device “sit0” (deprecated)
|
||||
Using "ifconfig" and "route" and generic tunnel device "sit0" (deprecated)
|
||||
</title>
|
||||
<para>
|
||||
Remove (default) route through the 6to4 tunnel interface
|
||||
|
|
@ -2894,10 +2947,10 @@ ff00::/8 :: UA 256 0 0 sit0
|
|||
</title>
|
||||
<sect2>
|
||||
<title>
|
||||
Using “netstat” for server socket binding check
|
||||
Using "netstat" for server socket binding check
|
||||
</title>
|
||||
<para>
|
||||
It's always interesting which server sockets are currently active on a node. Using “netstat” is a short way to get such information:
|
||||
It's always interesting which server sockets are currently active on a node. Using "netstat" is a short way to get such information:
|
||||
</para>
|
||||
<para>
|
||||
Used options: -nlptu
|
||||
|
|
@ -3004,7 +3057,7 @@ udp 0 0 :::53 :::*
|
|||
¬ 0:12:34:12:34:50) (len 88, hlim 255)
|
||||
</programlisting>
|
||||
<para>
|
||||
Router with link-local address “fe80::212:34ff:fe12:3450” send an advertisement to the all-node-on-link multicast address “ff02::1” containing two prefixes “2002:0102:0304:1::/64” (lifetime 30 s) and “3ffe:ffff:0:1::/64” (lifetime 2592000 s) including its own layer 2 MAC address “0:12:34:12:34:50”
|
||||
Router with link-local address "fe80::212:34ff:fe12:3450" send an advertisement to the all-node-on-link multicast address "ff02::1" containing two prefixes "2002:0102:0304:1::/64" (lifetime 30 s) and "3ffe:ffff:0:1::/64" (lifetime 2592000 s) including its own layer 2 MAC address "0:12:34:12:34:50"
|
||||
</para>
|
||||
</sect3>
|
||||
<sect3>
|
||||
|
|
@ -3016,7 +3069,7 @@ udp 0 0 :::53 :::*
|
|||
¬ (src lladdr: 0:12:34:12:34:56) (len 16, hlim 255)
|
||||
</programlisting>
|
||||
<para>
|
||||
Node with link-local address “fe80::212:34ff:fe12:3456” and layer 2 MAC address “0:12:34:12:34:56” is looking for a router on-link, therefore sending this solicitation to the all-router-on-link multicast address “ff02::2”.
|
||||
Node with link-local address "fe80::212:34ff:fe12:3456" and layer 2 MAC address "0:12:34:12:34:56" is looking for a router on-link, therefore sending this solicitation to the all-router-on-link multicast address "ff02::2".
|
||||
</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
|
@ -3029,12 +3082,12 @@ udp 0 0 :::53 :::*
|
|||
Neighbor discovery solicitation for duplicate address detection
|
||||
</title>
|
||||
<para>
|
||||
Following packets are sent by a node with layer 2 MAC address “0:12:34:12:34:56” during autoconfiguration to check whether a potential address is already used by another node on the link sending this to the solicited-node link-local multicast address
|
||||
Following packets are sent by a node with layer 2 MAC address "0:12:34:12:34:56" during autoconfiguration to check whether a potential address is already used by another node on the link sending this to the solicited-node link-local multicast address
|
||||
</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Node wants to configure its link-local address “fe80::212:34ff:fe12:3456”, checks for duplicate now
|
||||
Node wants to configure its link-local address "fe80::212:34ff:fe12:3456", checks for duplicate now
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -3045,7 +3098,7 @@ udp 0 0 :::53 :::*
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Node wants to configure its global address “2002:0102:0304:1:212:34ff:fe12:3456” (after receiving advertisement shown above), checks for duplicate now
|
||||
Node wants to configure its global address "2002:0102:0304:1:212:34ff:fe12:3456" (after receiving advertisement shown above), checks for duplicate now
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -3057,7 +3110,7 @@ udp 0 0 :::53 :::*
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Node wants to configure its global address “3ffe:ffff:0:1:212:34ff:fe12:3456” (after receiving advertisement shown above), checks for duplicate now
|
||||
Node wants to configure its global address "3ffe:ffff:0:1:212:34ff:fe12:3456" (after receiving advertisement shown above), checks for duplicate now
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -3074,7 +3127,7 @@ udp 0 0 :::53 :::*
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Note wants to send packages to “3ffe:ffff:0:1::10” but has no layer 2 MAC address to send packet, so send solicitation now
|
||||
Note wants to send packages to "3ffe:ffff:0:1::10" but has no layer 2 MAC address to send packet, so send solicitation now
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -3086,7 +3139,7 @@ udp 0 0 :::53 :::*
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Node looks for “fe80::10” now
|
||||
Node looks for "fe80::10" now
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
@ -3107,7 +3160,7 @@ udp 0 0 :::53 :::*
|
|||
</para>
|
||||
<sect1>
|
||||
<title>
|
||||
Red Hat Linux and “clones”
|
||||
Red Hat Linux and "clones"
|
||||
</title>
|
||||
<para>
|
||||
Since starting writing the <ulink url="http://www.bieringer.de/linux/IPv6/">IPv6 & Linux - HowTo</ulink> it was my intention to enable a persistent IPv6 configuration which catch most of the wished cases like host-only, router-only, dual-homed-host, router with second stub network, normal tunnels, 6to4 tunnels, and so on. Nowadays there exists a set of configuration and script files which do the job very well (never heard about real problems, but I don't know how many use the set. Because this configuration and scrips files are extended from time to time, they got their own HOWTO page: <ulink url="http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/scripts/current/">IPv6-HOWTO/scripts/current</ulink>. Because I began my IPv6 experience using a Red Hat Linux 5.0 clone, my IPv6 development systems are mostly Red Hat Linux based now, it's kind a logic that the scripts are developed for this kind of distribution (so called <emphasis>historic issue</emphasis>). Also it was very easy to extend some configuration files, create new ones and create some simple hook for calling IPv6 setup during IPv4 setup.
|
||||
|
|
@ -3116,7 +3169,7 @@ udp 0 0 :::53 :::*
|
|||
Fortunately, in Red Hat Linux since 7.1 a snapshot of my IPv6 scripts is included, this was and is still further on assisted by Pekka Savola.
|
||||
</para>
|
||||
<para>
|
||||
Mandrake since version 8.0 also includes an IPv6-enabled initscript package, but a minor bug still prevents usage (“ifconfig” misses “inet6” before “add”).
|
||||
Mandrake since version 8.0 also includes an IPv6-enabled initscript package, but a minor bug still prevents usage ("ifconfig" misses "inet6" before "add").
|
||||
</para>
|
||||
<sect2>
|
||||
<title>
|
||||
|
|
@ -3920,7 +3973,7 @@ Chain intOUT (1 references)
|
|||
Quality of Service (QoS)
|
||||
</title>
|
||||
<para>
|
||||
IPv6 supports QoS with use of Flow Labels and Traffic Classes. This can be controlled using “tc” (contained in package “iproute”).
|
||||
IPv6 supports QoS with use of Flow Labels and Traffic Classes. This can be controlled using "tc" (contained in package "iproute").
|
||||
</para>
|
||||
<para>
|
||||
more to be filled...
|
||||
|
|
@ -4370,7 +4423,7 @@ interface eth0 {
|
|||
Debugging
|
||||
</title>
|
||||
<para>
|
||||
A program called “radvdump” can help you looking into sent or received advertisements. Simple to use:
|
||||
A program called "radvdump" can help you looking into sent or received advertisements. Simple to use:
|
||||
</para>
|
||||
<programlisting>
|
||||
# radvdump
|
||||
|
|
@ -4579,9 +4632,44 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
<title>
|
||||
Paper printed books
|
||||
</title>
|
||||
<para>
|
||||
See following URL for more: <ulink url="http://www.switch.ch/lan/ipv6/references.html">SWITCH IPv6 Pilot / References</ulink>
|
||||
</para>
|
||||
<sect2>
|
||||
<title>
|
||||
German language
|
||||
</title>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Technik der IP-Netze (TCP/IP incl. IPv6) <ulink url="http://www.amazon.de/exec/obidos/ASIN/3446215018/">bei Amazon.de</ulink>
|
||||
Anatol Badach, Erwin Hoffmann
|
||||
Carl Hanser Verlag München, Wien, 2001 ISBN: 3-446-21501-8
|
||||
Kap. 6: Protokoll IPv6 S.205-242
|
||||
Kap. 7: Plug&Play-Unterstützung bei IPv6 S.243-276
|
||||
Kap. 8: Migration zum IPv6-Einsatz S.277-294
|
||||
Kap. 9.3.4: RIP für das Protokoll IPv6 (RIPng) S.349-351
|
||||
Kap. 9.4.6: OSPF für IPv6 S.384-385
|
||||
Kommentar: tw. nicht ganz up-to-date bzw. nicht ganz fehlerfreie Abbildungen
|
||||
<ulink url="http://www.fehcom.de/tipn/tipn.html">Homepage des Buches und Tabelle mit Fixes</ulink>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Internet-Sicherheit (Browser, Firewalls und Verschlüsselung) <ulink url="http://www.amazon.de/exec/obidos/ASIN/3446217258/">bei Amazon.de</ulink>
|
||||
Kai Fuhrberg
|
||||
2. akt. Auflage 2000 Carl Hanser Verlag München, Wien, ISBN: 3-446-21333-3
|
||||
Kap.2.3.1.4. IPv6 S.18-22
|
||||
Kurz angerissen werden: RFC1825 - Security Association Konzept RFC1826 - IP authentication Header RFC1827 - IP Encapsulation Security Payload
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
<sect2>
|
||||
<title>
|
||||
Others
|
||||
</title>
|
||||
<para>
|
||||
See following URL for more: <ulink url="http://www.switch.ch/lan/ipv6/references.html">SWITCH IPv6 Pilot / References</ulink>
|
||||
</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
<sect1 id="information-onlineinformation">
|
||||
<title>
|
||||
|
|
@ -4800,7 +4888,7 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<ulink url="http://tipster6.ik.bme.hu/tipster6_en.html">TIPSTER6 project</ulink> - Hungary, “Testing Experimental IPv6 Technology and Services in Hungary”
|
||||
<ulink url="http://tipster6.ik.bme.hu/tipster6_en.html">TIPSTER6 project</ulink> - Hungary, "Testing Experimental IPv6 Technology and Services in Hungary"
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
|
|
@ -4889,18 +4977,20 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
<para>
|
||||
More to be filled later...suggestions are welcome!
|
||||
</para>
|
||||
<informaltable><tgroup cols="5" colsep="1" rowsep="1">
|
||||
<informaltable><tgroup cols="6" colsep="1" rowsep="1">
|
||||
<colspec colname="col0" align="center">
|
||||
<colspec colname="col1" align="center">
|
||||
<colspec colname="col2" align="center">
|
||||
<colspec colname="col3" align="center">
|
||||
<colspec colname="col4" align="center">
|
||||
<colspec colname="col5" align="center">
|
||||
<tbody>
|
||||
<row>
|
||||
<entry align="center" valign="top">Request e-mail address
|
||||
</entry><entry align="center" valign="top">What to subscribe
|
||||
</entry><entry align="center" valign="top">Maillist e-mail address
|
||||
</entry><entry align="center" valign="top">Language
|
||||
</entry><entry align="center" valign="top">Focus
|
||||
</entry><entry align="center" valign="top">Access through WWW
|
||||
</entry></row>
|
||||
<row>
|
||||
|
|
@ -4908,6 +4998,7 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
</entry><entry align="center" valign="top">netdev
|
||||
</entry><entry align="center" valign="top">netdev (at) oss.sgi.com
|
||||
</entry><entry align="center" valign="top">English
|
||||
</entry><entry align="center" valign="top">Linux kernel networking including IPv6
|
||||
</entry><entry align="center" valign="top"><ulink url="http://oss.sgi.com/projects/netdev/archive/">Archive</ulink>
|
||||
</entry></row>
|
||||
<row>
|
||||
|
|
@ -4915,6 +5006,7 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
</entry><entry align="center" valign="top">ipv6
|
||||
</entry><entry align="center" valign="top">ipv6 (at) uni-muenster.de
|
||||
</entry><entry align="center" valign="top">German/English
|
||||
</entry><entry align="center" valign="top">IPv6/6bone in Germany
|
||||
</entry><entry align="center" valign="top"><ulink url="http://www.join.uni-muenster.de/JOIN/ipv6/texte-englisch/mailingliste.html">Info</ulink>, <ulink url="http://www.join.uni-muenster.de/local/majordomo/ipv6/">Archive</ulink>
|
||||
</entry></row>
|
||||
<row>
|
||||
|
|
@ -4922,6 +5014,7 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
</entry><entry align="center" valign="top">6bone
|
||||
</entry><entry align="center" valign="top">6bone (at) isi.edu
|
||||
</entry><entry align="center" valign="top">English
|
||||
</entry><entry align="center" valign="top">6bone
|
||||
</entry><entry align="center" valign="top"><ulink url="http://www.6bone.net/6bone_email.html">Info</ulink>, <ulink url="http://ryouko.dgim.crc.ca/ipv6/">Threaded archive</ulink>, <ulink url="http://www.wcug.wwu.edu/lists/6bone/">Mirror of archive</ulink>
|
||||
</entry></row>
|
||||
<row>
|
||||
|
|
@ -4929,6 +5022,7 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
</entry><entry align="center" valign="top">ipng
|
||||
</entry><entry align="center" valign="top">ipng (at) sunroof.eng.sun.com
|
||||
</entry><entry align="center" valign="top">English
|
||||
</entry><entry align="center" valign="top">IPv6 discussions
|
||||
</entry><entry align="center" valign="top"><ulink url="http://playground.sun.com/pub/ipng/html/instructions.html">Info</ulink>, <ulink url="ftp://playground.sun.com/pub/ipng/mail-archive/">Archive</ulink>, <ulink url="http://www.wcug.wwu.edu/lists/ipng/">Mirror of archive</ulink>
|
||||
</entry></row>
|
||||
<row>
|
||||
|
|
@ -4936,13 +5030,23 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
</entry><entry align="center" valign="top">users
|
||||
</entry><entry align="center" valign="top">users (at) ipv6.org
|
||||
</entry><entry align="center" valign="top">English
|
||||
</entry><entry align="center" valign="top">IPv6 users
|
||||
</entry><entry align="center" valign="top"><ulink url="http://www.ipv6.org/mailing-lists.html">Info</ulink>
|
||||
</entry></row>
|
||||
<row>
|
||||
<entry align="center" valign="top">usagi-users-ctl (at) linux-ipv6.org
|
||||
</entry><entry align="center" valign="top">
|
||||
</entry><entry align="center" valign="top">usagi-users (at) linux-ipv6.org
|
||||
</entry><entry align="center" valign="top">English
|
||||
</entry><entry align="center" valign="top">Linux IPv6 users using USAGI extension
|
||||
</entry><entry align="center" valign="top"><ulink url="http://www.linux-ipv6.org/ml/index.html#usagi-users">Info / Search</ulink>, <ulink url="http://www.linux-ipv6.org/ml/usagi-users/">Archive</ulink>
|
||||
</entry></row>
|
||||
<row>
|
||||
<entry align="center" valign="top">majordomo (at) mfa.eti.br
|
||||
</entry><entry align="center" valign="top">ipv6
|
||||
</entry><entry align="center" valign="top">ipv6 (at) mfa.eti.br
|
||||
</entry><entry align="center" valign="top">Portuguese
|
||||
</entry><entry align="center" valign="top">
|
||||
</entry><entry align="center" valign="top"><ulink url="http://www.mfa.eti.br/listas.html">Info</ulink>
|
||||
</entry></row>
|
||||
</tbody>
|
||||
|
|
@ -4955,11 +5059,8 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
</chapter>
|
||||
<chapter>
|
||||
<title>
|
||||
The End / Revision history / Credits
|
||||
Revision history / Credits / The End
|
||||
</title>
|
||||
<para>
|
||||
Thanks for reading. Hope it helps!
|
||||
</para>
|
||||
<sect1 id="revision-history">
|
||||
<title>
|
||||
Revision history
|
||||
|
|
@ -4969,52 +5070,73 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
Releases 0.x
|
||||
</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.19
|
||||
</term><listitem><para>2002-01-25/PB: Add two German books, fix quote entinities in exported SGML code
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.18.2
|
||||
</term><listitem><para>2002-01-23/PB: Add a FAQ on the program chapter
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.18.1
|
||||
</term><listitem><para>2002-01-23/PB: Move "the end" to the end, add USAGI to maillists
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.18
|
||||
</term><listitem><para>2002-01-22/PB: fix bugs in explanation of multicast address types
|
||||
</term><listitem><para>2002-01-22/PB: Fix bugs in explanation of multicast address types
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.17.2
|
||||
</term><listitem><para>2002-01-22/PB: cosmetic fix double existing text in history (at 0.16), move all credits to the end of the document
|
||||
</term><listitem><para>2002-01-22/PB: Cosmetic fix double existing text in history (at 0.16), move all credits to the end of the document
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.17.1
|
||||
</term><listitem><para>2002-01-20/PB: add a reference, fix URL text in online-test-tools
|
||||
</term><listitem><para>2002-01-20/PB: Add a reference, fix URL text in online-test-tools
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.17
|
||||
</term><listitem><para>2002-01-19/PB: add some forgotten information and URLs about global IPv6 addresses
|
||||
</term><listitem><para>2002-01-19/PB: Add some forgotten information and URLs about global IPv6 addresses
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.16
|
||||
</term><listitem><para>2002-01-19/PB: minor fixes, remove “bold” and “emphasize” formats on code lines, fix “too long unwrapped code lines” using selfmade utility, extend list of URLs.
|
||||
</term><listitem><para>2002-01-19/PB: Minor fixes, remove "bold" and "emphasize" formats on code lines, fix "too long unwrapped code lines" using selfmade utility, extend list of URLs.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.15
|
||||
</term><listitem><para>2002-01-15/PB: fix bug in addresstype/anycast, move content related credits to end of document
|
||||
</term><listitem><para>2002-01-15/PB: Fix bug in addresstype/anycast, move content related credits to end of document
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
0.14
|
||||
</term><listitem><para>2002-01-14/PB: Minor review at all, new chapter “debugging”, review “addresses”, spell checking, grammar checking (from beginning to 3.4.1) by Martin Krafft, add tcpdump examples, copy firewalling/netfilter6 from IPv6+Linux-HowTo, minor enhancements
|
||||
</term><listitem><para>2002-01-14/PB: Minor review at all, new chapter "debugging", review "addresses", spell checking, grammar checking (from beginning to 3.4.1) by Martin Krafft, add tcpdump examples, copy firewalling/netfilter6 from IPv6+Linux-HowTo, minor enhancements
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
@ -5057,7 +5179,7 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
The quickest way to be added to this nice list is to send bug fixes, corrections, and/or updates to me ;-).
|
||||
</para>
|
||||
<para>
|
||||
If you want to do a major review, please ask the author for the native LyX file as diffs against SGML don't help too much.
|
||||
If you want to do a major review, you can use the native LyX file (see <link linkend="general-original-source">original source</link>) and send diffs against it, because diffs against SGML don't help too much.
|
||||
</para>
|
||||
<sect2 id="major-credits">
|
||||
<title>
|
||||
|
|
@ -5115,12 +5237,12 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
S .P. Meenakshi <meena at cs dot iitm dot ernet dot in>: For a hint using a “send mail” shell program on tcp_wrapper/hosts.deny
|
||||
S .P. Meenakshi <meena at cs dot iitm dot ernet dot in>: For a hint using a "send mail" shell program on tcp_wrapper/hosts.deny
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Georg Käfer <gkaefer at salzburg dot co dot at>: For detection of no proper PDF creation (fixed now by LDP maintainer Greg Ferguson) and some suggestions
|
||||
Georg Käfer <gkaefer at salzburg dot co dot at>: For detection of no proper PDF creation (fixed now by LDP maintainer Greg Ferguson), input for German books and some other suggestions
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
|
|
@ -5137,6 +5259,17 @@ Jan 2 20:42:19 gate sshd[12345]: Accepted password for user
|
|||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
<sect1>
|
||||
<title>
|
||||
The End
|
||||
</title>
|
||||
<para>
|
||||
Thanks for reading. Hope it helps!
|
||||
</para>
|
||||
<para>
|
||||
If you have any questions, subscribe to proper <link linkend="information-maillists">maillist</link> and describe your problem.
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue