mirror of https://github.com/tLDP/LDP
pbldp
parent
4ae9a2e7bb
commit
aa6395485a
|
|
@ -41,8 +41,8 @@ Peter
|
|||
Bieringer
|
||||
\layout SGML
|
||||
|
||||
<affiliation><address> <email>pb (at) bieringer.de</email> </address> </affiliati
|
||||
on>
|
||||
<affiliation><address> <email>pb at bieringer.de</email> </address> </affiliation
|
||||
>
|
||||
\layout SGML
|
||||
|
||||
</author>
|
||||
|
|
@ -51,6 +51,15 @@ on>
|
|||
<revhistory>
|
||||
\layout SGML
|
||||
|
||||
<revision> <revnumber>Release 0.34.1</revnumber> <date>2002-11-25</date> <authorin
|
||||
itials>PB</authorinitials> <revremark>See
|
||||
\begin_inset LatexCommand \ref[revision history]{revision-history}
|
||||
|
||||
\end_inset
|
||||
|
||||
for more</revremark></revision>
|
||||
\layout SGML
|
||||
|
||||
<revision> <revnumber>Release 0.34</revnumber> <date>2002-11-19</date> <authorini
|
||||
tials>PB</authorinitials> <revremark>See
|
||||
\begin_inset LatexCommand \ref[revision history]{revision-history}
|
||||
|
|
@ -69,15 +78,6 @@ tials>PB</authorinitials> <revremark>See
|
|||
for more</revremark></revision>
|
||||
\layout SGML
|
||||
|
||||
<revision> <revnumber>Release 0.32</revnumber> <date>2002-11-03</date> <authorini
|
||||
tials>PB</authorinitials> <revremark>See
|
||||
\begin_inset LatexCommand \ref[revision history]{revision-history}
|
||||
|
||||
\end_inset
|
||||
|
||||
for more</revremark></revision>
|
||||
\layout SGML
|
||||
|
||||
</revhistory>
|
||||
\layout Abstract
|
||||
|
||||
|
|
@ -326,8 +326,8 @@ Translations always have to contain the URL, version number and copyright
|
|||
of the original document (but yours, too).
|
||||
Pls.
|
||||
don't translate the original changelog, this is not very useful.
|
||||
Looks like the the document's change frequency is mostly less than once
|
||||
per month.
|
||||
Looks like the document's change frequency is mostly less than once per
|
||||
month.
|
||||
Since version 0.27 it looks like that most of the content contributed by
|
||||
me has been written.
|
||||
\layout Subsection
|
||||
|
|
@ -565,8 +565,8 @@ It was born
|
|||
\series bold
|
||||
maintain
|
||||
\series default
|
||||
it, but it will slowly fade in favour of the Linux IPv6 HOWTO you are currently
|
||||
reading.
|
||||
it, but it will slowly fade (but not full) in favour of the Linux IPv6 HOWTO
|
||||
you are currently reading.
|
||||
\layout Subsubsection
|
||||
|
||||
Linux IPv6 HOWTO (this document)
|
||||
|
|
@ -600,8 +600,9 @@ Peter Bieringer
|
|||
|
||||
), and as IPv6 is becoming more and more standard, I decided to write a
|
||||
new document covering basic and advanced issues which will remain important
|
||||
over the next few years.
|
||||
Dynamic content will be still found further on in the second HOWTO (
|
||||
over the next few years.
|
||||
More dynamic and some advanced content will be still found further on in
|
||||
the second HOWTO (
|
||||
\begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/}
|
||||
|
||||
\end_inset
|
||||
|
|
@ -645,10 +646,6 @@ host A dual homed host is a node with two network (physical or
|
|||
between the interfaces.
|
||||
\layout Description
|
||||
|
||||
Link A link is a layer 2 network packet transport medium, examples are Ethernet,
|
||||
Token Ring, PPP, SLIP, ATM, ISDN, Frame Relay,...
|
||||
\layout Description
|
||||
|
||||
Host Generally a single homed host on a link.
|
||||
Normally it has only one active network interface, e.g.
|
||||
Ethernet or (not and) PPP.
|
||||
|
|
@ -670,6 +667,10 @@ Header Header of an IP packet (each network packet has a header, kind
|
|||
of is depending on network layer)
|
||||
\layout Description
|
||||
|
||||
Link A link is a layer 2 network packet transport medium, examples are Ethernet,
|
||||
Token Ring, PPP, SLIP, ATM, ISDN, Frame Relay,...
|
||||
\layout Description
|
||||
|
||||
Node A node is a host or a router.
|
||||
\layout Description
|
||||
|
||||
|
|
@ -724,10 +725,10 @@ Shortcuts
|
|||
API Application Programming Interface
|
||||
\layout Description
|
||||
|
||||
BSD Berkeley Software Distribution
|
||||
ASIC Application Specified Integrated Circuit
|
||||
\layout Description
|
||||
|
||||
ASIC Application Specified Integrated Circuit
|
||||
BSD Berkeley Software Distribution
|
||||
\layout Description
|
||||
|
||||
CAN-Bus Controller Area Network Bus (physical bus system)
|
||||
|
|
@ -2413,7 +2414,7 @@ You can download the tar-ball and recompile it:
|
|||
and mirror (missing)
|
||||
\layout Itemize
|
||||
|
||||
You've able to look for a proper RPM package at
|
||||
You're able to look for a proper RPM package at
|
||||
\begin_inset LatexCommand \url[RPMfind/iproute]{http://rpmfind.net/linux/rpm2html/search.php?query=iproute}
|
||||
|
||||
\end_inset
|
||||
|
|
@ -2574,8 +2575,8 @@ iputils
|
|||
.
|
||||
It's a program similar to IPv4 traceroute.
|
||||
But unlike modern IPv4 versions, the IPv6 one still doesn't understand
|
||||
to traceroute using ICMP echo-request packets (which is more accepted by
|
||||
firewalls around than UDP packets to high ports).
|
||||
to traceroute using ICMPv6 echo-request packets (which is more accepted
|
||||
by firewalls around than UDP packets to high ports).
|
||||
Below you will see an example:
|
||||
\layout Code
|
||||
|
||||
|
|
@ -2836,7 +2837,7 @@ Because of security updates in the last years every Domain Name System (DNS)
|
|||
IPv6 address-type AAAA (the newer one named A6 isn't still common at the
|
||||
moment because only supported using BIND9 and newer and also the non-existent
|
||||
support of root domain IP6.ARPA).
|
||||
A simple whether the used system can resolve IPv6 addresses is
|
||||
A simple test whether the used system can resolve IPv6 addresses is
|
||||
\layout Code
|
||||
|
||||
# host -t AAAA www.join.uni-muenster.de
|
||||
|
|
@ -3117,7 +3118,7 @@ root
|
|||
Therefore normal users get such error message.
|
||||
\layout Standard
|
||||
|
||||
Solution: If it's really needed that all users should be able to use this
|
||||
Solution: If it's really needed that all users should be able to use these
|
||||
utilities, you can add the
|
||||
\begin_inset Quotes sld
|
||||
\end_inset
|
||||
|
|
@ -3150,7 +3151,7 @@ wheel
|
|||
\begin_inset Quotes srd
|
||||
\end_inset
|
||||
|
||||
, add this power users to this group and remove the execution bit for other
|
||||
, add these power users to this group and remove the execution bit for other
|
||||
users using
|
||||
\begin_inset Quotes sld
|
||||
\end_inset
|
||||
|
|
@ -3209,7 +3210,7 @@ Virtually bounded interfaces always need special support
|
|||
IPv6-in-IPv4 tunnel interfaces
|
||||
\layout Standard
|
||||
|
||||
This interfaces are normally named
|
||||
These interfaces are normally named
|
||||
\series bold
|
||||
sit
|
||||
\emph on
|
||||
|
|
@ -3905,12 +3906,7 @@ Neighbor discovery was the IPv6 successor for the ARP (Address Resolution
|
|||
Protocol) in IPv4.
|
||||
You can retrieve information about the current neighbors, in addition you
|
||||
can set and delete entries.
|
||||
\layout Standard
|
||||
|
||||
Neighbor detection
|
||||
\layout Standard
|
||||
|
||||
The kernel keeps tracking of successful neighbor detection (like ARP in
|
||||
The kernel keeps tracking of successful neighbor detection (like ARP in
|
||||
IPv4).
|
||||
You can dig into the learnt table using
|
||||
\begin_inset Quotes sld
|
||||
|
|
@ -4203,8 +4199,7 @@ The downstream (6bone -> your 6to4 enabled node) is not really fix and can
|
|||
There exist two possibilities:
|
||||
\layout Itemize
|
||||
|
||||
Foreign host uses uses 6to4 and sends packet direct back to your node (see
|
||||
below)
|
||||
Foreign host uses 6to4 and sends packet direct back to your node (see below)
|
||||
\layout Itemize
|
||||
|
||||
Foreign host sends packets back to the world-wide IPv6 network and depending
|
||||
|
|
@ -4301,7 +4296,7 @@ Add point-to-point tunnels
|
|||
Using "ip"
|
||||
\layout Standard
|
||||
\align left
|
||||
Common method at the moment for a small amount of tunnels
|
||||
Common method at the moment for a small amount of tunnels.
|
||||
\layout Standard
|
||||
|
||||
Usage for creating a tunnel device (but it's not up afterward, also a TTL
|
||||
|
|
@ -4543,7 +4538,7 @@ Usage (generic example for three tunnels):
|
|||
Using "route"
|
||||
\layout Standard
|
||||
|
||||
This is like removing normal IPv6 routes
|
||||
This is like removing normal IPv6 routes.
|
||||
\layout Standard
|
||||
\align left
|
||||
Usage (generic example for three tunnels):
|
||||
|
|
@ -11167,6 +11162,9 @@ Versions x.y.z are work-in-progress and only published as LyX file on CVS.
|
|||
Releases 0.x
|
||||
\layout Description
|
||||
|
||||
0.34.1 2002-11-25/PB: Some fixes
|
||||
\layout Description
|
||||
|
||||
0.34 2002-11-19/PB: Add information about German translation (work in progress),
|
||||
some fixes, create a small shortcut explanation list, extend
|
||||
\begin_inset Quotes sld
|
||||
|
|
|
|||
Loading…
Reference in New Issue