From 2da8d97e40f85909c0b2b3aec84c38166eab4e19 Mon Sep 17 00:00:00 2001 From: pbldp <> Date: Tue, 13 Jun 2006 05:56:29 +0000 Subject: [PATCH] No content changes, only load and save with new version of LyX --- .../Peter-Bieringer/Linux+IPv6-HOWTO.de.lyx | 12634 +++++++++------ .../Peter-Bieringer/Linux+IPv6-HOWTO.fr.lyx | 12783 +++++++++------ .../Peter-Bieringer/Linux+IPv6-HOWTO.lyx | 13042 ++++++++++------ 3 files changed, 23471 insertions(+), 14988 deletions(-) diff --git a/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.de.lyx b/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.de.lyx index 4f78f9ae..f4a1012c 100644 --- a/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.de.lyx +++ b/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.de.lyx @@ -1,5 +1,7 @@ -#LyX 1.3 created this file. For more info see http://www.lyx.org/ -\lyxformat 221 +#LyX 1.4.1 created this file. For more info see http://www.lyx.org/ +\lyxformat 245 +\begin_document +\begin_header \textclass docbook-book \begin_preamble @@ -10,388 +12,565 @@ \fontscheme default \graphics default \paperfontsize default -\spacing single -\papersize Default -\paperpackage a4 -\use_geometry 0 -\use_amsmath 0 -\use_natbib 0 -\use_numerical_citations 0 +\spacing single +\papersize default +\use_geometry false +\use_amsmath 1 +\cite_engine basic +\use_bibtopic false \paperorientation portrait \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \defskip medskip \quotes_language swedish -\quotes_times 2 \papercolumns 1 \papersides 1 \paperpagestyle default +\tracking_changes false +\output_changes true +\end_header -\layout Title -\added_space_top vfill \added_space_bottom vfill +\begin_body + +\begin_layout Standard +\begin_inset VSpace vfill +\end_inset + + +\end_layout + +\begin_layout Title Linux IPv6 HOWTO (de) -\layout SGML +\end_layout + +\begin_layout Standard +\begin_inset VSpace vfill +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout FirstName +\end_layout -Peter -\layout Surname +\end_inset + +\end_layout + +\begin_layout Standard +Peter +\end_layout + +\begin_layout Standard Bieringer -\layout SGML +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard
pb at bieringer dot de
 -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard 0.49.de.1 2005-10-03 PB Details siehe \begin_inset LatexCommand \ref[revision history]{revision-history} -\end_inset +\end_inset -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard 0.48.de.1 2005-01-11 PB Details siehe \begin_inset LatexCommand \ref[revision history]{revision-history} -\end_inset +\end_inset -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard 0.47.de.1 2004-08-30 PB Details siehe \begin_inset LatexCommand \ref[revision history]{revision-history} -\end_inset +\end_inset -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard 0.46.de.1 2004-03-16 PB Details siehe \begin_inset LatexCommand \ref[revision history]{revision-history} -\end_inset +\end_inset -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout Abstract +\end_layout +\end_inset + + +\end_layout + +\begin_layout Abstract Das Ziel des Linux IPv6 HOWTO ist die Beantwortung von Basis- und Experten-Frage n zum Thema IPv6 mit Linux-Betriebssystemen. Dieses HOWTO will dem Leser genug Informationen bereitstellen, um IPv6-Anwendun gen auf Linux Computer installieren, konfigurieren und anwenden zu können. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-general} -\end_inset +\end_inset Allgemein -\layout Comment +\end_layout +\begin_layout Standard +\begin_inset Note Comment +status collapsed + +\begin_layout Standard CVS-ID: $Id$ -\layout Standard +\end_layout +\end_inset + + +\end_layout + +\begin_layout Standard Informationen über verfügbare Übersetzungen finden Sie im Abschnitt \begin_inset LatexCommand \ref[Übersetzungen]{general-translations} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-copright} -\end_inset +\end_inset Copyright, Lizenz und anderes -\layout Subsection +\end_layout +\begin_layout Subsection Copyright -\layout Standard +\end_layout +\begin_layout Standard Verfasst von und urheberrechtlich geschützt durch Peter Bieringer © 2001-2004. -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Deutsche Übersetzung: -\layout Standard +\end_layout +\begin_layout Standard Verfasst von und urheberrechtlich geschützt durch Georg Käfer © 2002-2003. -\layout Subsection +\end_layout +\begin_layout Subsection Lizenz -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold Dieses Linux IPv6 HOWTO wird unter der GNU GPL Version 2 herausgegeben: -\series default +\series default -\newline +\newline -\newline +\newline -\newline +\newline -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Dieses Linux IPv6 HOWTO ist ein Handbuch zur Anwendung und Konfiguration von IPv6 auf Linux-Systemen. -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Copyright © 2001-2004 Peter Bieringer -\newline -Deutsche Übersetzung Copyright © 2002-2003 Georg Käfer -\newline +\newline +Deutsche Übersetzung Copyright © 2002-2003 + Georg Käfer +\newline -\layout Standard +\end_layout +\begin_layout Standard Diese Dokumentation ist freie Software; Sie können diese unter den Bedingungen der GNU General Public License, wie von der Free Software Foundation publiziert , entweder unter Version 2 oder optional jede höhere Version redistribuieren und/oder modifizieren. -\layout Standard +\end_layout +\begin_layout Standard Dieses Programm wird in der Hoffnung verteilt, dass es für Sie nutzvoll ist, jedoch OHNE JEDWEDER GEWÄHRLEISTUNG; sogar ohne der implizierten Gewährlei stung der MARKTFÄHIGKEIT oder der FÄHIGKEIT ZU EINEM BESONDEREN ZWECK bzw. VORSATZ. Weitere Details finden Sie in der GNU General Public License. -\layout Standard +\end_layout +\begin_layout Standard Zusammen mit diesem Dokument sollten Sie eine Kopie der GNU General Public License erhalten haben; Wenn dem nicht so ist, können Sie sich an folgende Adresse wenden: Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -\layout Subsection +\end_layout +\begin_layout Subsection Über den Autor -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Internet/IPv6 Background des Autors -\layout Itemize +\end_layout +\begin_layout Itemize 1993: In Kontakt mit dem Internet getreten, kennenlernen von konsolenbasierte E-Mail- und News-Client-Programme (z.B.: suchen Sie nach \begin_inset Quotes sld -\end_inset +\end_inset e91abier \begin_inset Quotes srd -\end_inset +\end_inset auf \begin_inset LatexCommand \url[groups.google.com]{http://groups.google.com/} -\end_inset +\end_inset , das ist der Autor). -\layout Itemize +\end_layout +\begin_layout Itemize 1996: Anfrage zur Gestaltung eines IPv6 Kurses inklusive eines Workshops zum Thema Linux Betriebssystem bekommen. -\layout Itemize +\end_layout +\begin_layout Itemize 1997: Schreiben einer Anleitung, wie man IPv6 auf Linux Systemen installieren, konfigurieren und anwenden kann, genannt \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset (siehe unter \begin_inset LatexCommand \url[IPv6 & Linux - HowTo/History]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-0.html#history} -\end_inset +\end_inset ). -\layout Itemize +\end_layout +\begin_layout Itemize 2001: Begonnen, dieses neue Linux IPv6 HOWTO zu schreiben. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ansprechpartner -\layout Standard +\end_layout +\begin_layout Standard Der Autor kann via E-Mail und auch über seine \begin_inset LatexCommand \url[homepage]{http://www.bieringer.de/pb/} -\end_inset +\end_inset kontaktiert werden. -\layout Standard +\end_layout +\begin_layout Standard Der Autor lebt zurzeit in München (nördlicher Teil von Schwabing) / Bayern / (Süd-)Deutschland / (Mittel-)Europa / Erde (Oberfläche / Festland). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ansprechpartner für Übersetzungen -\layout Standard +\end_layout +\begin_layout Standard Der Autor der deutschsprachigen Version kann via E-Mail unter kontaktiert werden. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-category} -\end_inset +\end_inset Kategorie -\layout Standard +\end_layout +\begin_layout Standard Dieses HOWTO sollte in der Kategorie \begin_inset Quotes sld -\end_inset +\end_inset -\emph on +\emph on Networking -\emph default +\emph default / -\emph on +\emph on Protocols -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset aufgelistet werden. -\layout Section +\end_layout +\begin_layout Section Version, Werdegang und Unerledigtes -\layout Subsection +\end_layout +\begin_layout Subsection Version -\layout Standard +\end_layout +\begin_layout Standard Die aktuelle Versionsnummer finden Sie auf der Titelseite. -\layout Standard +\end_layout +\begin_layout Standard Für andere verfügbare Versionen/Übersetzungen siehe auch \lang english \begin_inset LatexCommand \url[http://www.bieringer.de/linux/IPv6/]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Werdegang -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Eckpunkte -\layout Standard +\end_layout +\begin_layout Standard 2001-11-30: Beginn mit der Neukonzeption dieses HOWTOs. -\layout Standard +\end_layout +\begin_layout Standard 2002-01-02: Viel Inhalt eingearbeitet, erste Version des Kapitels 1 veröffentlic ht (Version 0.10). -\layout Standard +\end_layout +\begin_layout Standard 2002-01-14: Weitere Vervollständigung und Überprüfung des Inhalts, öffentliche Freigabe des kompletten Dokuments (Version 0.14). -\layout Standard +\end_layout +\begin_layout Standard 2002-08-16: Polnische Übersetzung ist in Arbeit. -\layout Standard +\end_layout +\begin_layout Standard 2002-10-31: Chinesische Übersetzung ist verfügbar. -\layout Standard +\end_layout +\begin_layout Standard 2002-11-10: Deutsche Übersetzung ist in Arbeit. -\layout Standard +\end_layout +\begin_layout Standard 2003-02-10: Deutsche Übersetzung ist verfügbar. -\layout Standard +\end_layout +\begin_layout Standard \lang english 2003-04-09: Französische \lang ngerman Übersetzung ist in Arbeit. -\layout Standard +\end_layout +\begin_layout Standard \lang english 2003-05-09: Französische \lang ngerman Übersetzung ist verfügbar. -\layout Standard +\end_layout +\begin_layout Standard \lang english 2003-08-15: Spanische \lang ngerman Übersetzung ist in Arbeit. -\layout Standard +\end_layout +\begin_layout Standard \lang english 2003-10-16: Italienische \lang ngerman Übersetzung ist in Arbeit. -\layout Standard +\end_layout +\begin_layout Standard \lang english 2004-03-12: Italienische \lang ngerman Übersetzung ist verfügbar. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Vollständiger Werdegang -\layout Standard +\end_layout +\begin_layout Standard Am Ende dieses Dokumentes finden Sie die \begin_inset LatexCommand \ref[Historie der Änderungen]{revision-history} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Unerledigtes -\layout Itemize +\end_layout +\begin_layout Itemize Fehlenden Inhalt ergänzen -\layout Itemize +\end_layout +\begin_layout Itemize Grammatik-Überprüfung beenden -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-translations} -\end_inset +\end_inset Übersetzungen -\layout Standard +\end_layout +\begin_layout Standard Übersetzungen müssen den URL, die Versionsnummer und das Copyright des Originald okuments enthalten (aber auch die Daten zu ihrer Übersetzung). Bitte übersetzen Sie nicht das Original-Changelog, das wäre nicht sehr @@ -401,549 +580,646 @@ okuments enthalten (aber auch die Daten zu ihrer Seit Version 0.27 scheint der Hauptteil des vom Autor beigesteuerten Inhaltes geschrieben zu sein. Übersetzungen müssen immer das englische Original als Quelle benutzen. -\layout Subsection +\end_layout +\begin_layout Subsection Diverse Sprachen -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Deutsch -\layout Standard +\end_layout +\begin_layout Standard Mit 2002-11-10 wurde von Georg Käfer die Deutsche Übersetzung begonnen und am 10.02.2003 erstmals publiziert. Grundlage der Übersetzung ist die CVS-Version 1.53 der Lyx-Datei, aus der das Linux IPv6 HOWTO Version 0.39.2 erstellt wurde. -\layout Standard +\end_layout +\begin_layout Standard Mit Sicherheit werden in dieser Übersetzung noch so manche 'Hoppalas' und auch 'grausige' Rechtschreibfehler zu finden sein. Sorry! Ebenfalls fällt es nicht immer leicht, zu entscheiden, ob ein Terminus überhaupt übersetzt werden soll, bzw. ob die Beibehaltung des englischen Originalwortes nicht zielführender wäre... -\layout Standard +\end_layout +\begin_layout Standard -\series bold -\emph on +\series bold +\emph on Neue deutsche Rechtschreibung -\series default -\emph default +\series default +\emph default : es wurde eine konservative Übersetzung angewandt, d.h. nicht alle möglichen Änderungen der Neuen deutschen Rechtschreibung wurden durchgeführt, sondern nur die notwendigen Änderungen. -\layout Standard +\end_layout +\begin_layout Standard Die URL für diese deutsche Übersetzung ist: \begin_inset LatexCommand \url[http://mirrors.deepspace6.net/Linux+IPv6-HOWTO-de/]{http://mirrors.deepspace6.net/Linux+IPv6-HOWTO-de/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Andere Sprachen -\layout Standard +\end_layout +\begin_layout Standard Informationen über Übersetzungen in andere Sprachen finden Sie hier im Originald okument: \begin_inset LatexCommand \url[TLDP / Linux+IPv6-HOWTO / Übersetzungen]{http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/general-translations.html} -\end_inset +\end_inset . -\layout Section +\end_layout +\begin_layout Section Technisches -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{general-original-source} -\end_inset +\end_inset Originalquelle dieses HOWTOs -\layout Standard +\end_layout +\begin_layout Standard Die originale englische Version dieses HOWTOs wurde mit LyX Version 1.20 auf einem Red Hat Linux 7.3 System mit SGML-Template (DocBook book) erstellt. Alle Dateien sind unter \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset verfügbar. -\layout Standard +\end_layout +\begin_layout Standard Auch die deutsche Version wurde mit LyX erstellt und befindet sich ebenfalls im angegebenen CVS-Verzeichnis. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Zeilenumbruch in Code-Beispielen -\layout Standard +\end_layout +\begin_layout Standard Der Zeilenumbruch wird mit Hilfe eines selbst geschriebenen Tools \begin_inset Quotes sld -\end_inset +\end_inset lyxcodelinewrapper.pl \begin_inset Quotes srd -\end_inset +\end_inset erstellt; Sie finden das Skript am CVS unter: \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection SGML Erzeugung -\layout Standard +\end_layout +\begin_layout Standard SGML wird mit Hilfe der Exportfunktion in LyX generiert. -\layout Standard +\end_layout +\begin_layout Standard Um korrekten SGML Code zu erstellen, müssen einige Korrekturen gemacht werden. Die entsprechenden Perl Skripts finden Sie unter \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset : -\layout Itemize +\end_layout +\begin_layout Itemize Der Export von Lyx-Tabellen erstellt keine korrekten \begin_inset Quotes sld -\end_inset +\end_inset colspan \begin_inset Quotes srd -\end_inset +\end_inset Tags. Tool für die Korrektur: \begin_inset Quotes sld -\end_inset +\end_inset sgmllyxtabletagfix.pl \begin_inset Quotes srd -\end_inset +\end_inset (behoben seit LyX Version 1.2.0) -\layout Itemize +\end_layout +\begin_layout Itemize LyX verwendet manchmal , anstelle der normalen, spezielle Links-/Rechts-Formatie rungen für Zitate, die dann auch im generierten HTML Code ausgegeben werden. Einige Browser können das Ergebnis nicht besonders schön darstellen (bekannt sind: Opera TP2 oder Konqueror). Tool für die Korrektur: \begin_inset Quotes sld -\end_inset +\end_inset sgmllyxquotefix.pl \begin_inset Quotes srd -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Online-Verweise auf die HTML Version dieses HOWTOs (Links / Anchors) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Hauptindexseite -\layout Standard +\end_layout +\begin_layout Standard Im Allgemeinen wird ein Verweis auf die Hauptindexseite empfohlen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Seitennamen -\layout Standard +\end_layout +\begin_layout Standard Da die HTML-Seiten aus einer SGML-Datei erstellt werden, werden einige HTML-Date inamen ziemlich zufällig gewählt. Manche Seiten sind jedoch in LyX mit Tags gekennzeichnet, woraus statische Namen resultieren. Diese sollten der besseren Referenz wegen zukünftig nicht geändert werden. -\layout Standard +\end_layout +\begin_layout Standard Bitte lassen Sie es wissen, wenn Sie glauben, dass ein Tag vergessen wurde. -\layout Section +\end_layout +\begin_layout Section Vorwort -\layout Standard +\end_layout +\begin_layout Standard Einiges vorab: -\layout Subsection +\end_layout +\begin_layout Subsection Wie viele IPv6 & Linux bezogene HOWTOs gibt es? -\layout Standard +\end_layout +\begin_layout Standard Inklusive diesem gibt es drei (3) HOWTO-Dokumente. Pardon, wenn das zu viele sind ;-) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Linux Ipv6 FAQ/HOWTO (veraltet) -\layout Standard +\end_layout +\begin_layout Standard Das erste IPv6 bezogene Dokument wurde von -\emph on +\emph on Eric Osborne -\emph default +\emph default geschrieben und heißt \begin_inset LatexCommand \url[Linux IPv6 FAQ/HOWTO]{http://www.linuxhq.com/IPv6/} -\end_inset +\end_inset (bitte benutzen Sie den Text nur im historischen Kontext). -\series bold +\series bold Die neueste Version -\series default +\series default 3.2.1 wurde am 14.Juli -\series bold +\series bold 1997 -\series default +\series default veröffentlicht. -\layout Standard +\end_layout +\begin_layout Standard Bitte um Ihre Mithilfe: Wenn jemand das Erstellungsdatum der Erstversion dieses HOWTOs kennen sollte, senden Sie mir Bitte ein E-Mail (Die Information wird im Abschnitt \begin_inset Quotes sld -\end_inset +\end_inset Werdegang \begin_inset Quotes srd -\end_inset +\end_inset eingearbeitet). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 & Linux - HowTo (gewartet) -\layout Comment +\end_layout +\begin_layout Standard +\begin_inset Note Comment +status collapsed + +\begin_layout Standard Dieses HOWTO ist wirklich \begin_inset Quotes sld -\end_inset +\end_inset HowTo \begin_inset Quotes srd -\end_inset +\end_inset genannt -\layout Standard +\end_layout +\end_inset + + +\end_layout + +\begin_layout Standard Ein zweites Dokument ( \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset ) wurde vom selben Autor (Peter Bieringer) geschrieben und liegt im HTML-Format vor. -\series bold +\series bold Begonnen -\series default +\series default wurde mit dem Schreiben im April -\series bold +\series bold 1997 -\series default +\series default und die erste englische Version wurde im Juni 1997 veröffentlicht. Das Dokument wird -\series bold +\series bold weiterhin -\series default +\series default betreut, es wird aber langsam (jedoch nicht komplett) in das Linux IPv6 HOWTO - das Sie gerade lesen - eingearbeitet. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Linux IPv6 HOWTO (dieses Dokument) -\layout Standard +\end_layout +\begin_layout Standard Da das \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset in HTML geschrieben wurde, war es nicht wirklich mit dem \begin_inset LatexCommand \url[The Linux Documentation Project (TLDP)]{http://www.tldp.org/} -\end_inset +\end_inset kompatibel. Der Autor (Peter Bieringer) bekam Ende Nov. 2001 die Anfrage, das \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset in SGML zu konvertieren. Er entschied sich auf Grund dieser Diskontinuität ( \begin_inset LatexCommand \url[Future of IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-0.html#history} -\end_inset +\end_inset ) und der Tatsache, dass IPv6 mehr und mehr zum Standard wird, zum Schreiben eines neuen Dokuments. Im zweiten HOWTO ( \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset ) wird auch weiterhin dynamischer Inhalt sowie weiterführender Inhalt zu finden sein. -\layout Section +\end_layout +\begin_layout Section Verwendete Begriffe, Glossar und Abkürzungen -\layout Subsection +\end_layout +\begin_layout Subsection Netzwerkbegriffe -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 10 Dezimales Zahlensystem, das die Zahlen 0-9 beinhaltet. -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 16 Generell in Programmiersprachen verwendetes hexedezimales Zahlensystem, das die Zahlen 0-9 und die Buchstaben A-F beinhaltet (Groß/Kleinschreibung möglich). -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 85 85 verschiedene Zahlen/Buchstaben umfasst dieses Zahlensystem und ermöglicht dadurch kürzere Zeichenketten - aber niemals in der Praxis gesehen. -\layout Description +\end_layout +\begin_layout Description Bit Kleinste Speichereinheit mit dem Wert ein/wahr (1) oder aus/falsch (0) -\layout Description +\end_layout +\begin_layout Description Byte Meistens eine Menge von 8 bits (aber kein Muss - siehe ältere Computer Systeme) -\layout Description +\end_layout +\begin_layout Description Device Netzwerkgerät, siehe auch NIC -\layout Description +\end_layout -Dual\SpecialChar ~ -homed\SpecialChar ~ +\begin_layout Description +Dual\InsetSpace ~ +homed\InsetSpace ~ host Ein Dual homed host ist ein Node mit zwei (physischen oder virtuellen) Schnittstellen auf zwei unterschiedlichen Links. Datenpakete können zwischen den zwei Verbindungen nicht weitergeleitet werden. -\layout Description +\end_layout +\begin_layout Description Host Im Regelfall handelt es sich um einen Rechner mit einen Link sowie einer aktiven Netzwerk-Schnittstelle, z.B. Ethernet oder (aber nicht und) PPP. -\layout Description +\end_layout +\begin_layout Description Interface Ident mit \begin_inset Quotes sld -\end_inset +\end_inset device \begin_inset Quotes srd -\end_inset +\end_inset , siehe auch NIC. -\layout Description +\end_layout -IP\SpecialChar ~ +\begin_layout Description +IP\InsetSpace ~ Header Kopf eines IP-Paketes (jedes Netzwerk-Paket hat einen header, die Form des headers ist abhängig von der Netzwerkschicht). -\layout Description +\end_layout +\begin_layout Description Link Ein Link ist eine Schicht 2 Netzwerk-Transportmedium für Pakete; Beispiele sind Ethernet, Token Ring, PPP, SLIP, ATM, ISDN, Frame Relay,... -\layout Description +\end_layout +\begin_layout Description Node Ein Node (=Knoten) ist ein Host oder ein Router. -\layout Description +\end_layout +\begin_layout Description Octet Sammlung von acht (8) realen bits, vergleichbar mit \begin_inset Quotes sld -\end_inset +\end_inset byte \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Description +\end_layout +\begin_layout Description Port Information für den TCP/UDP dispatcher (Schicht 4), mit dessen Hilfe Informationen auf höhere Schichten transportiert werden. -\layout Description +\end_layout +\begin_layout Description Protocol Jede Netzwerkschicht enthält meistens ein Protokoll-Feld damit die Übergabe transportierter Informationen an höhere Netzwerkschichten erleichtert wird. Beispiele hierfür: Schicht 2 (MAC) und 3 (IP). -\layout Description +\end_layout +\begin_layout Description Router Ein Router ist ein Knoten mit zwei (2) oder mehr (physischen oder virtuellen) Schnittstellen, der Datenpakete zwischen den Schnittstellen versenden kann. -\layout Description +\end_layout +\begin_layout Description Socket Ein IP socket wird durch Quell- und Zieladresse, den Ports (und der Verbindung) definiert. -\layout Description +\end_layout +\begin_layout Description Stack Ein Stack setzt sich aus Netzwerkschichten zusammen. -\layout Description +\end_layout +\begin_layout Description Subnetmask IP Netzwerke verwenden Bitmasken um lokale von entfernten Netzwerken zu trennen. -\layout Description +\end_layout +\begin_layout Description Tunnel Ein Tunnel ist typischerweise eine Punkt-zu-Punkt-Verbindung, über die Datenpakete eines anderen Protokolls ausgetauscht werden. Beispiel: IPv6-in-IPv4 Tunnel. -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{Glossar} -\end_inset +\end_inset Abkürzungen -\layout Description +\end_layout +\begin_layout Description ACL Access Control List - Zugriffsliste) -\layout Description +\end_layout +\begin_layout Description API Application Programming Interface - Schnittstellen in Programmen zwischen den Applikationen -\layout Description +\end_layout +\begin_layout Description ASIC Application Specified Integrated Circuit - Applikationsspezifischer integrierter Schaltkreis -\layout Description +\end_layout +\begin_layout Description BSD Berkeley Software Distribution -\layout Description +\end_layout +\begin_layout Description CAN-Bus Controller Area Network Bus (physical bus system) -\layout Description +\end_layout +\begin_layout Description \lang english ISP Internet Service Provider -\layout Description +\end_layout +\begin_layout Description KAME Ein Projekt und gemeinsame Anstrengung von sechs (6) Firmen in Japan mit dem Ziel, einen freien IPv6 und IPsec Stack für BSD Derivate der Öffentlich keit zur Verfügung zu stellen \begin_inset LatexCommand \url[www.kame.net]{http://www.kame.net/} -\end_inset +\end_inset . -\layout Description +\end_layout +\begin_layout Description \lang english LIR Local Internet Registry - Lokale Internet Registratur -\layout Description +\end_layout +\begin_layout Description NIC Network Interface Controller - Netzwerk[schnittstellen]karte, kurz Netzwerkk arte -\layout Description +\end_layout +\begin_layout Description RFC Request For Comments - eine Sammlung von technischen und organisatorischen Dokumenten zum Thema Internet. -\layout Description +\end_layout +\begin_layout Description USAGI UniverSAl playGround for Ipv6 Project - dieses Projekt will für das Linux System einen IPv6 Protokoll stack mit Produktionsqualität ausliefern. -\layout Subsection +\end_layout +\begin_layout Subsection In diesem Dokument verwendete Syntax -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Zeilenumbruchs-Zeichen bei langen Codebeispielen -\layout Standard +\end_layout +\begin_layout Standard Das spezielle Zeichen \begin_inset Quotes sld -\end_inset +\end_inset ¬ \begin_inset Quotes srd -\end_inset +\end_inset zeigt in den Beispielen an, dass die Zeile umgebrochen wurde. Dies wurde für eine korrekte Darstellung des Textes in den PDF- und PS-Versione n benötigt. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Platzhalter -\layout Standard +\end_layout +\begin_layout Standard In allgemeinen Beispielen können Sie öfters lesen: -\layout Code +\end_layout +\begin_layout Code -\layout Standard +\end_layout +\begin_layout Standard In Skripts oder an Ihrer Kommandozeile müssen Sie die < und > weglassen und den Text mit dem entsprechenden Inhalt ersetzen. Das Beispiel hier z.B. könnte sein: -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Shell-Kommandos -\layout Standard +\end_layout +\begin_layout Standard Kommandos, die nicht als Root-Benutzer ausgeführt werden, beginnen mit $, z.B. -\layout Code +\end_layout +\begin_layout Code $ whoami -\layout Standard +\end_layout +\begin_layout Standard Befehle, die mit Root-Rechten ausgeführt werden, beginnen mit #, z.B. -\layout Code +\end_layout +\begin_layout Code # whoami -\layout Section +\end_layout +\begin_layout Section Grundvoraussetzung für die Verwendung dieses HOWTOs -\layout Subsection +\end_layout +\begin_layout Subsection Persönliche Anforderungen -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Erfahrung mit Unix Tools -\layout Standard +\end_layout +\begin_layout Standard Sie sollten mit den gängigsten Unix Tools wie -\emph on +\emph on grep -\emph default +\emph default , -\emph on +\emph on awk -\emph default +\emph default , -\emph on +\emph on find -\emph default +\emph default , etc. und deren Kommandozeilen-Optionen vertraut sein. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Erfahrung mit Netzwerktheorie -\layout Standard +\end_layout +\begin_layout Standard Sie sollten das Schichtmodell und die einzelnen Schichten, Protokolle, Adressart en, Kabelsorten, Stecker etc. kennen. @@ -951,58 +1227,68 @@ en, Kabelsorten, Stecker etc. : \begin_inset LatexCommand \url[linuxports/howto/intro_to_networking]{http://www.linuxports.com/howto/intro_to_networking/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Erfahrung mit der Konfiguration von IPv4 Netzen -\layout Standard +\end_layout +\begin_layout Standard Sie sollten definitiv Erfahrung mit der Konfiguration von IPv4 Netzwerken haben, andernfalls werden Sie dem Text nur schwer folgen können. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Erfahrung mit dem Domain Name System (DNS) -\layout Standard +\end_layout +\begin_layout Standard Sie sollten ebenfalls das Domain Name System (DNS) verstehen und damit umgehen können. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Routine im Umgang mit Strategien zur Netzwerk-Fehlersuche -\layout Standard +\end_layout +\begin_layout Standard Sie sollten zumindest mit tcpdump umgehen und den Output des Programms interpret ieren können. Andernfalls wird die Netzwerk-Fehlersuche für Sie schwierig. -\layout Subsection +\end_layout +\begin_layout Subsection Linux kompatible Hardware -\layout Standard +\end_layout +\begin_layout Standard Sicherlich wollen Sie mit realer Hardware experimentieren und nicht darüber an dieser Stelle lesen und an der einen oder anderen Stelle einschlummern. ;-7) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-basics} -\end_inset +\end_inset Grundlagen -\layout Section +\end_layout +\begin_layout Section Was ist IPv6? -\layout Standard +\end_layout +\begin_layout Standard IPv6 ist ein neues Schicht 3 Transportprotokoll (siehe \color red \begin_inset LatexCommand \url[linuxports/howto/intro_to_networking/ISO - OSI Model]{http://www.linuxports.com/howto/intro_to_networking/c4412.htm#PAGE103HTML} -\end_inset +\end_inset \color default @@ -1010,7 +1296,7 @@ IPv6 ist ein neues Schicht 3 Transportprotokoll (siehe IPv4 wurde vor langer Zeit entworfen ( \begin_inset LatexCommand \url[RFC 760 / Internet Protocol]{http://www.faqs.org/rfcs/rfc760.html} -\end_inset +\end_inset vom Januar 1980). Seitdem wurden viele Adressen vergeben und Erweiterungen angeregt. @@ -1019,7 +1305,7 @@ IPv6 ist ein neues Schicht 3 Transportprotokoll (siehe \begin_inset LatexCommand \url[RFC 2460 / Internet Protocol Version 6 Specification]{http://www.faqs.org/rfcs/rfc2460.html} -\end_inset +\end_inset \lang ngerman @@ -1029,100 +1315,122 @@ IPv6 ist ein neues Schicht 3 Transportprotokoll (siehe Die Schicht 3 ist für den Transport der Pakete von Endpunkt-zu-Endpunkt mittels adressbasierten Paket-Routings zuständig, und wie bei IPv4 müssen bei IPv6 die Adressen (Quell- und Zieladresse) inkludiert sein. -\layout Standard +\end_layout +\begin_layout Standard Für weitere Informationen zur IPv6 Geschichte siehe die älteren RFCs z.B. \begin_inset LatexCommand \url[SWITCH IPv6 Pilot / References]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{basic-history-IPv6-Linux} -\end_inset +\end_inset Geschichte von IPv6 & Linux -\layout Standard +\end_layout +\begin_layout Standard Die Jahre 1992, 1993 und 1994 der allgemeinen IPv6 Geschichte können Sie in folgendem Dokument nachlesen: \begin_inset LatexCommand \url[IPv6 or IPng (IP next generation)]{http://www.laynetworks.com/IPv6.htm#CH3} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Zu erledigen: Bessere Chronologie, mehr Inhalt -\layout Subsection +\end_layout +\begin_layout Subsection Anfang -\layout Standard +\end_layout +\begin_layout Standard Der erste IPv6 Netzwerk Code wurde dem Linux Kernel 2.1.8 im November 1996 durch Pedro Roque hinzugefügt. Er basierte auf dem BSD API: -\layout Code +\end_layout +\begin_layout Code diff -u --recursive --new-file v2.1.7/linux/include/linux/in6.h -\layout Code +\end_layout +\begin_layout Code ¬ linux/include/linux/in6.h -\layout Code +\end_layout +\begin_layout Code --- v2.1.7/linux/include/linux/in6.h Thu Jan 1 02:00:00 1970 -\layout Code +\end_layout +\begin_layout Code +++ linux/include/linux/in6.h Sun Nov 3 11:04:42 1996 -\layout Code +\end_layout +\begin_layout Code @@ -0,0 +1,99 @@ -\layout Code +\end_layout +\begin_layout Code +/* -\layout Code +\end_layout +\begin_layout Code + * Types and definitions for AF_INET6 -\layout Code +\end_layout +\begin_layout Code + * Linux INET6 implementation -\layout Code +\end_layout +\begin_layout Code + * + * Authors: -\layout Code +\end_layout +\begin_layout Code + * Pedro Roque <******> -\layout Code +\end_layout +\begin_layout Code + * -\layout Code +\end_layout +\begin_layout Code + * Source: -\layout Code +\end_layout +\begin_layout Code + * IPv6 Program Interfaces for BSD Systems -\layout Code +\end_layout +\begin_layout Code + * -\layout Standard +\end_layout +\begin_layout Standard Diese Zeilen entstammen dem patch-2.1.8 (die E-Mail-Adresse wurde hier beim Copy & Paste absichtlich gelöscht). -\layout Subsection +\end_layout +\begin_layout Subsection Übergangszeit -\layout Standard +\end_layout +\begin_layout Standard Aufgrund fehlender Arbeitskraft konnte die IPv6-Kernel-Implementierung nicht mit den Drafts oder neu freigegebenen RFCs Schritt halten. Im Oktober 2000 wurde in Japan das \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset Projekt gestartet. Das Ziel war, die fehlende bzw. @@ -1131,21 +1439,23 @@ Aufgrund fehlender Arbeitskraft konnte die IPv6-Kernel-Implementierung nicht IPv6, die durch das \begin_inset LatexCommand \url[KAME project]{http://www.kame.net/} -\end_inset +\end_inset umgesetzt wurde. Von Zeit zu Zeit wurden im Vergleich zu den aktuellen Standard Linux-Kernel-Que llen ein Auszug erstellt. -\layout Subsection +\end_layout +\begin_layout Subsection Heute -\layout Standard +\end_layout +\begin_layout Standard Leider ist der \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset Patch so groß, dass man gegenwärtig nicht in der Lage ist, ihn in den Produktio ns-Kernel zu implementieren. @@ -1154,37 +1464,44 @@ ns-Kernel zu implementieren. oder RFCs erfüllt (siehe: \begin_inset LatexCommand \url[IP Version 6 Working Group (ipv6) Charter]{http://www.ietf.org/html.charters/ipv6-charter.html} -\end_inset +\end_inset ). Dies kann einige Inkompatibilitäts-Probleme zu anderen Betriebssystemen bewirken. -\layout Subsection +\end_layout +\begin_layout Subsection Zukunft -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset benutzt jetzt den neuen Entwicklungs-Kernel der Serie 2.5.x, um alle ihre gegenwärtigen Erweiterungen zu integrieren. Hoffentlich wird die 2.6.x Kernel-Serie eine akkurate und aktuelle IPv6 Implement ierung enthalten. -\layout Section +\end_layout +\begin_layout Section Wie sehen IPv6 Adressen aus? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Wie gesagt, IPv6 Adressen sind 128 bit lang. Diese bit-Anzahl kann sehr hohe dezimale Zahlen mit bis zu 39 Ziffern ergeben: -\layout Code +\end_layout +\begin_layout Code 2^128-1: 340282366920938463463374607431768211455 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Solche Zahlen sind nicht wirklich Adressen, die auswendig gelernt werden können. Die IPv6 Adressdarstellung ist bitweise orientiert (wie bei IPv4, aber @@ -1192,149 +1509,181 @@ Solche Zahlen sind nicht wirklich Adressen, die auswendig gelernt werden Eine bessere Schreibweise ist deshalb die hexadezimale Darstellung. Dabei werden 4 bits (auch ? \begin_inset Quotes srd -\end_inset +\end_inset nubble \begin_inset Quotes srd -\end_inset +\end_inset genannt) durch die Zeichen 0-9 und a-f (10-15) dargestellt, wodurch die Länge auf 32 Zeichen reduziert wird. -\layout Code +\end_layout +\begin_layout Code 2^128-1: 0xffffffffffffffffffffffffffffffff -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Darstellung ist ebenfalls nicht sehr angenehm (mögliche Verwechslung oder Verlust einzelner hexadezimaler Ziffern), so dass die IPv6 Designer das hexadezimales Format mit einem Doppelpunkt als Trennzeichen nach jedem 16 bit Block erweiterten. Ferner wird das führende \begin_inset Quotes srd -\end_inset +\end_inset 0x \begin_inset Quotes srd -\end_inset +\end_inset (ein in Programmiersprachen verwendetes Identifizierungsmerkmal für hexadezimal e Werte) entfernt: -\layout Code +\end_layout +\begin_layout Code 2^128-1: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Eine gültige Adresse (s.u. Adress-Typen) ist z.B.: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Der Vereinfachung halber können führende Nullen jedes 16 bit-Blocks weggelassen werden: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -> -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100:f101:210:a4ff:fee3:9566 -\layout Standard +\end_layout +\begin_layout Standard Eine Sequenz von 16 bit-Blöcken, die nur Nullen enthaltet, kann durch ein \begin_inset Quotes eld -\end_inset +\end_inset -\family typewriter +\family typewriter :: -\family default +\family default \begin_inset Quotes eld -\end_inset +\end_inset ersetzt werden. Diese Komprimierung kann aber nicht öfters als einmal durchgeführt werden -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:0:0:0:1 -> 3ffe:ffff:100:f101::1 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Die höchstmögliche Reduktion sieht man bei der IPv6 Localhost Adresse: -\layout Code +\end_layout +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0001 -> ::1 -\layout Standard +\end_layout +\begin_layout Standard Es gibt auch eine so genannte -\emph on +\emph on kompakte -\emph default +\emph default Darstellung (base 85 codiert) \begin_inset LatexCommand \url[RFC 1924 / A Compact Representation of IPv6 Addresses]{http://www.faqs.org/rfcs/rfc1924.html} -\end_inset +\end_inset (publiziert am 1. April 1996). Diese Notation wurde allerdings nie in der Praxis gesehen und ist wahrscheinlic h ein Aprilscherz. Ein Beispiel: -\layout Code +\end_layout +\begin_layout Code # ipv6calc --addr_to_base85 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -\layout Code +\end_layout +\begin_layout Code Itu&-ZQ82s>J%s99FJXT -\layout Quotation +\end_layout +\begin_layout Quotation Info: -\emph on +\emph on ipv6calc -\emph default +\emph default ist ein IPv6 Adressen-Format-Umrechner und Konvertierungsprogramm und ist hier zu finden: \begin_inset LatexCommand \url[ipv6calc homepage]{http://www.deepspace6.net/projects/ipv6calc.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/projects/ipv6calc.html} -\end_inset +\end_inset ) -\layout Section +\end_layout +\begin_layout Section FAQ (Grundlagen) -\layout Subsection +\end_layout +\begin_layout Subsection Warum wird der Nachfolger von IPv4 nun IPv6 und nicht IPv5 genannt? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left In jedem IP-Header werden die ersten 4 Bits für die Protokollversion reserviert. So sind theoretisch die Protokollnummern 0 bis 15 möglich: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left 4: Wird schon für IPv4 verwendet -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left 5: Ist für das Stream Protocol (STP, \begin_inset LatexCommand \url[RFC 1819 / Internet Stream Protocol Version 2]{http://www.faqs.org/rfcs/rfc1819.html} -\end_inset +\end_inset ) reserviert (das aber nie den Weg in die Öffentlichkeit fand) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left So war die nächste freie Zahl 6. IPv6 war geboren! -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 Adressen: Warum ist die Anzahl der Bits so groß? -\layout Standard +\end_layout +\begin_layout Standard Bei der Entwicklung von IPv4 dachte man, dass 32 bits für die Welt ausreichend wären. Blickt man zurück, so waren bis heute 32 bits ausreichend. @@ -1343,12 +1692,14 @@ Bei der Entwicklung von IPv4 dachte man, dass 32 bits f mit einer globalen Adresse ausstatten zu können. Denken Sie an Mobiltelefone, Autos (mit elektronischen Geräten an einem CAN Bus), Toaster, Kühlschränken, Lichtschalter usw. -\layout Standard +\end_layout +\begin_layout Standard Die IPv6 Designer haben 128 bit gewählt, 4-mal längere und 2^96 größere Adressen als im heutigen IPv4. -\layout Standard +\end_layout +\begin_layout Standard Aber die benutzbare Größe ist kleiner als es erscheinen mag, da in dem gegenwärt ig definierten Adress-Schema 64 bits für die Schnittstellen-Identifizierung verwendet werden. @@ -1358,24 +1709,28 @@ ig definierten Adress-Schema 64 bits f denkbar. Aber mit Sicherheit nicht in naher Zukunft. -\layout Standard +\end_layout +\begin_layout Standard Weitere Informationen finden Sie unter \begin_inset LatexCommand \url[RFC 1715 / The H Ratio for Address Assignment Efficiency]{http://www.faqs.org/rfcs/rfc1715.html} -\end_inset +\end_inset und \begin_inset LatexCommand \url[RFC 3194 / The Host-Density Ratio for Address Assignment Efficiency]{http://www.faqs.org/rfcs/rfc3194.html} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 Adressen: Warum ist die Bit-Anzahl bei einem neuen Design so klein? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Es gibt (wahrscheinlich) eine Gruppe (bekannt ist nur Jim Fleming...) von Personen am Internet, die über IPv8 und IPv16 nachdenken. Für diese Designs gibt es aber keine hohe Akzeptanz und auch keine Kernel-Imple @@ -1387,8 +1742,9 @@ mentierungen. 48 octets (fixer Wert). Dies ist 3.4% der MTU in IPv4 und 3.8% der MTU in IPv6. Dies -\layout Standard +\end_layout +\begin_layout Standard bedeutet, dass der Overhead beim Header fast ident ist. Mehr bits für die Adressierung würden größere Header und deshalb mehr Overhead erfordern. @@ -1398,27 +1754,29 @@ bedeutet, dass der Overhead beim Header fast ident ist. Letztlich wäre es kein korrektes Design, wenn 10% oder 20% der transportierten Daten in einem Schicht 3-Paket für Adressen und nicht für die \begin_inset Quotes srd -\end_inset +\end_inset Nutzlast \begin_inset Quotes srd -\end_inset +\end_inset benötigt würden. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-addresstypes} -\end_inset +\end_inset Adress-Typen -\layout Standard +\end_layout +\begin_layout Standard Wie bei IPv4 können IPv6-Adressen mittels Subnetzmasken (subnet masks) in einen Netz- und einen Host-Teil unterteilt werden. -\layout Standard +\end_layout +\begin_layout Standard Bei IPv4 hat sich gezeigt, dass es manchmal von Nutzen wäre, einem Interface mehr als eine IP-Adresse zuweisen zu können, je nach Bedarf und Zweck (aliases, multicast etc.). @@ -1426,331 +1784,393 @@ Bei IPv4 hat sich gezeigt, dass es manchmal von Nutzen w erlaubt pro Interface mehr als eine zugewiesene IP-Adresse. Derzeit sind durch die RFCs kein Limit gesetzt, wohl aber in der Implementierun g des IPv6 Stacks (um DoS Attacken vorzubeugen). -\layout Standard +\end_layout +\begin_layout Standard Neben der großen bit-Anzahl für Adressen definiert IPv6 basierend auf einigen vorangestellten bits verschiedene Adress-Typen. Diese werden hoffentlich in der Zukunft niemals aufgehoben (zum Unterschied zu IPv4 heute und die Entwicklung der class A, B und C Netze). -\layout Standard +\end_layout +\begin_layout Standard Zur Unterstützung einer automatischen Konfiguration wird die Bitanzahl in einen Netzwerk-Teil (hinteren 64 bits) und einen Hostteil (vorderen 64 bits). -\layout Section +\end_layout +\begin_layout Section Adressen ohne speziellen Präfix -\layout Subsection +\end_layout +\begin_layout Subsection Localhost Adresse -\layout Standard +\end_layout +\begin_layout Standard Dies ist eine spezielle Adresse für das Loopback Interface, vergleichbar zur \begin_inset Quotes sld -\end_inset +\end_inset 127.0.0.1 \begin_inset Quotes srd -\end_inset +\end_inset bei IPv4. Bei IPv6 lautet die localhost Adresse: -\layout Code +\end_layout +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0001 -\layout Standard +\end_layout +\begin_layout Standard bzw. komprimiert: -\layout Code +\end_layout +\begin_layout Code ::1 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Pakete mit dieser Quell- bzw. Ziel-Adresse sollten niemals den sendenden Host verlassen. -\layout Subsection +\end_layout +\begin_layout Subsection Unspezifische Adresse -\layout Standard +\end_layout +\begin_layout Standard Dies ist eine spezielle Adresse vergleichbar mit \begin_inset Quotes sld -\end_inset +\end_inset any \begin_inset Quotes srd -\end_inset +\end_inset oder \begin_inset Quotes sld -\end_inset +\end_inset 0.0.0.0 \begin_inset Quotes srd -\end_inset +\end_inset bei IPv4. In IPv6 lautet sie: -\layout Code +\end_layout +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0000 -\layout Standard +\end_layout +\begin_layout Standard oder: -\layout Code +\end_layout +\begin_layout Code :: -\layout Standard +\end_layout +\begin_layout Standard Diese Adresse wird meistens in Routing-Tabellen und beim \begin_inset Quotes sld -\end_inset +\end_inset socket binding \begin_inset Quotes srd -\end_inset +\end_inset (zu jeder IPv6 Adresse) angewendet bzw. gesehen. -\layout Standard +\end_layout +\begin_layout Standard Beachten: Die Unspezifizierte Adresse kann nicht als Ziel-Adresse verwendet werden. -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 Adressen mit eingebetteter IPv4 Adresse -\layout Standard +\end_layout +\begin_layout Standard Es gibt zwei Adressen-Typen, die IPv4 Adressen enthalten können. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv4 Adressen in IPv6 Format -\layout Standard +\end_layout +\begin_layout Standard IPv4-only IPv6-kompatible Adressen kommen manchmal bei IPv6 kompatiblen Daemon zur Anwendung, die allerdings ausschließlich an IPv4 Adressen gebunden sind. -\layout Standard +\end_layout +\begin_layout Standard Diese Adressen sind mit einer speziellen Präfixlänge von 96 definiert (a.b.c.d. ist die IPv4 Adresse): -\layout Code +\end_layout +\begin_layout Code 0:0:0:0:0:ffff:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard oder in komprimiertem Format: -\layout Code +\end_layout +\begin_layout Code ::ffff:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard Die IPv4 Adresse 1.2.3.4. z.B. sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code ::ffff:1.2.3.4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv4 kompatible IPv6 Adressen -\layout Standard +\end_layout +\begin_layout Standard Dieser Adress-Typ wurde für das automatische Tunneln ( \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset ) verwendet, welches aber durch das \begin_inset LatexCommand \ref[6to4 tunneling]{tunneling-6to4} -\end_inset +\end_inset ersetzt wurde. -\layout Code +\end_layout +\begin_layout Code 0:0:0:0:0:0:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard oder in komprimierter Form: -\layout Code +\end_layout +\begin_layout Code ::a.b.c.d/96 -\layout Section +\end_layout +\begin_layout Section Netzteil der Adresse (Präfix) -\layout Standard +\end_layout +\begin_layout Standard Es wurden einige Adress-Typen definiert und zugleich blieb für zukünftige Anforderungen ausreichend Raum für weitere Definitionen. Im \begin_inset LatexCommand \url[RFC 2373 [July 1998] / IP Version 6 Addressing Architecture]{http://www.faqs.org/rfcs/rfc2373.html} -\end_inset +\end_inset wird das aktuelle Adress-Schema definiert. Ein neues Draft gibt es unter: \begin_inset LatexCommand \url[draft-ietf-ipngwg-addr-arch-*.txt]{ftp://ftp.ietf.org/internet-drafts/} -\end_inset +\end_inset . -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Lassen Sie uns nun einen Blick auf die verschiedenen Präfixe (und somit auf die Adress-Arten) werfen:: -\layout Subsection +\end_layout +\begin_layout Subsection Link-lokaler Adress-Typ -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Es handelt sich um spezielle Adressen, die ausschließlich auf einem Link eines Interfaces gültig sind. Wird diese Adresse als Zieladresse verwendet, so kann das Paket niemals einen Router passieren. Die Adresse wird bei der Link-Kommunikation eingesetzt, z.B.: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Ist noch jemand anderer auf diesem Link? -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Ist jemand mit einer speziellen Adresse hier (z.B. Suche nach einem Router)? -\layout Standard +\end_layout +\begin_layout Standard Die Adresse beginnt mit (wobei -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset x \begin_inset Quotes srd -\end_inset +\end_inset -\emph default +\emph default für ein hexadezimales Zeichen steht, im Normalfall -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset 0 -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Code +\end_layout +\begin_layout Code fe8 -\shape italic -\emph on +\shape italic +\emph on x: <- zurzeit als einziger in Benutzung -\layout Code +\end_layout +\begin_layout Code fe9 -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fea -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code feb -\shape italic -\emph on +\shape italic +\emph on x: -\layout Standard +\end_layout +\begin_layout Standard Eine Adresse mit diesem Präfix gibt es an jedem IPv6 fähigen Interface nach einer stateless automatischen Konfiguration (dies ist der Regelfall). -\layout Subsection +\end_layout +\begin_layout Subsection Site-lokaler Adress-Typ -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Adressen sind vergleichbar zu den \begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://www.faqs.org/rfcs/rfc1918.html} -\end_inset +\end_inset im heutigen IPv4. Eine Neuerung und Vorteil hierbei ist, vergleichbar zum 10.0.0.0/8 im IPv4, die Nutzbarkeit von 16 bits bzw. ein Maximum von 65536 Subnetzen. -\layout Standard +\end_layout +\begin_layout Standard Ein weiterer Vorteil: Da man bei IPv6 mehr als eine Adresse an ein Interface binden kann, ist auch die Zuweisung einer site-local Adresse zusätzlich zu einer globalen Adresse möglich. -\layout Standard +\end_layout +\begin_layout Standard Die Adresse beginnt mit: -\layout Code +\end_layout +\begin_layout Code fec -\shape italic -\emph on +\shape italic +\emph on x: <- meistens genutzt. -\layout Code +\end_layout +\begin_layout Code fed -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fee -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fef -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout -\layout Standard +\begin_layout Code +\end_layout + +\begin_layout Standard ( -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset x \begin_inset Quotes srd -\end_inset +\end_inset -\emph default +\emph default ist ein hexadezimales Zeichen, normalerweise -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset 0 -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Standard +\end_layout +\begin_layout Standard \lang english Zu bemerken ist, dass seit einiger Zeit diskutiert, wird, diesen Adresstyp @@ -1758,90 +2178,106 @@ Zu bemerken ist, dass seit einiger Zeit diskutiert, wird, diesen Adresstyp Im aktuellen Draft ist mehr dazu zu lesen: \begin_inset LatexCommand \url[draft-ietf-ipv6-deprecate-site-local-XY.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard \lang english Für Tests im Labor sind solche Adressen meineserachtens aber immer noch eine gute Wahl. -\layout Subsection +\end_layout +\begin_layout Subsection Globaler Adress-Typ ("Aggregatable global unicast") -\layout Standard +\end_layout +\begin_layout Standard Heute gibt es ist per Definition eine globale Adress-Art (Das erste Design, ''Provider based'' genannt, wurde bereits vor einigen Jahren wieder aufgegeben \begin_inset LatexCommand \url[RFC 1884 / IP Version 6 Addressing Architecture [obsolete]]{http://www.faqs.org/rfcs/rfc1884.html} -\end_inset +\end_inset . Einige Überbleibsel hiervon sind in älteren Linux Kernelquellen noch zu finden. -\layout Standard +\end_layout +\begin_layout Standard Die Adresse beginnt mit (x sind hexadezimale Zeichen) -\layout Code +\end_layout +\begin_layout Code 2 -\shape italic -\emph on +\shape italic +\emph on xxx -\shape default -\emph default +\shape default +\emph default : -\layout Code +\end_layout +\begin_layout Code 3 -\shape italic -\emph on +\shape italic +\emph on xxx -\shape default -\emph default +\shape default +\emph default : -\layout Standard +\end_layout +\begin_layout Standard Hinweis: Der Zusatz \begin_inset Quotes sld -\end_inset +\end_inset aggregatable \begin_inset Quotes srd -\end_inset +\end_inset im Namen wird in aktuellen Drafts abgelegt. -\newline +\newline Es sind weitere Subarten definiert: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection 6bone Test-Adressen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese globalen Adressen waren die Ersten definierten und auch benutzen Adressen. Sie alle beginnen mit: -\layout Code +\end_layout +\begin_layout Code 3ffe: -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f102::1 -\layout Standard +\end_layout +\begin_layout Standard Eine spezielle 6bone Test-Adresse, die niemals weltweit einmalig ist, beginnt mit -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff: -\layout Standard +\end_layout +\begin_layout Standard und wird zumeist in alten Beispielen benutzt, um zu vermeiden, dass Anwender diese mit Copy & Paste in Ihre Konfigurationen übernehmen können. Auf diese Weise können Duplikate weltweit einmaliger Adressen aus Versehen @@ -1852,241 +2288,287 @@ und wird zumeist in alten Beispielen benutzt, um zu vermeiden, dass Anwender \lang english -\newline +\newline Aufgrund dessen, daß IPv6 nun produktiv ist, wird dieser Präfix nicht länger delegiert und wahrscheinlich nach dem 6.6.2006 vom Routing ausgenommen (mehr unter \begin_inset LatexCommand \url[RFC 3701 / 6bone Phaseout]{http://www.faqs.org/rfcs/rfc3701.html} -\end_inset +\end_inset ). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection 6to4 Adressen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Adressen werden für einen speziellen Tunnelmechanismus verwendet [ \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset und \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset ]. Sie kodieren eine gegebene IPv4 Adresse, ein eventuelles Subnetz und beginnen mit -\layout Code +\end_layout +\begin_layout Code 2002: -\layout Standard +\end_layout +\begin_layout Standard z.B. wird 192.168.1.1/5 repräsentiert durch: -\layout Code +\end_layout +\begin_layout Code 2002:c0a8:0101:5::1 -\layout Standard +\end_layout +\begin_layout Standard Ein kleines Shell-Kommando kann aus einer IPv4 eine 6to4 Adresse erstellen: -\layout Code +\end_layout +\begin_layout Code ipv4="1.2.3.4"; sla="5"; printf "2002:%02x%02x:%02x%02x:%04x::1" `echo $ipv4 -\layout Code +\end_layout +\begin_layout Code ¬ | tr "." " "` $sla -\layout Standard +\end_layout +\begin_layout Standard Siehe auch \begin_inset LatexCommand \ref[tunneling using 6to4]{tunneling-6to4} -\end_inset +\end_inset und \begin_inset LatexCommand \ref[information about 6to4 relay routers]{information-joinipv6-6to4-tunneling} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Durch einen Provider zugewiesene Adressen für ein hierarchisches Routing -\layout Standard +\end_layout +\begin_layout Standard Diese Adressen werden an Internet Service Provider (ISP) delegiert und beginnen mit: -\layout Code +\end_layout +\begin_layout Code 2001: -\layout Standard +\end_layout +\begin_layout Standard Präfixe für große ISPs (mit eigenem Backbone) werden durch \begin_inset LatexCommand \ref[local registries]{information-majorregionregistries} -\end_inset +\end_inset vergeben. Zurzeit wird ein Präfix mit der Länge 32 zugeteilt. -\layout Standard +\end_layout +\begin_layout Standard Grosse ISPs delegieren ihrerseits an kleinere ISPs ein Präfix mit der Länge 48. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Für Beispiele und Dokumentationen reservierte Adressen -\layout Standard +\end_layout +\begin_layout Standard \lang english Momentan sind zwei Adressbereiche für Beispiele und Dokumentationen reserviert: -\layout Code +\end_layout +\begin_layout Code \lang english 3ffe:ffff::/32 -\layout Code +\end_layout +\begin_layout Code \lang english 2001:0DB8::/32 EXAMPLENET-WF -\layout Standard +\end_layout +\begin_layout Standard \lang english Diese Adressbereiche sollten nicht geroutet werden und am Übergangsrouter zum Internet (basierend auf Absendeadressen) gefiltert werden. -\layout Subsection +\end_layout +\begin_layout Subsection Multicast-Addressen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Multicast-Adressen werden für entsprechende Dienste verwendet. -\layout Standard +\end_layout +\begin_layout Standard Sie beginnen immer mit (xx ist hierbei der Wert der Reichweite) -\layout Code +\end_layout +\begin_layout Code ff -\shape italic -\emph on +\shape italic +\emph on x -\shape default -\emph default +\shape default +\emph default y: -\layout Standard +\end_layout +\begin_layout Standard Die Adressen werden in Reichweiten und Typen unterteilt: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Multicast-Bereiche -\layout Standard +\end_layout +\begin_layout Standard Die Multicast Reichweite ist ein Parameter, mit dem die maximale Distanz angegeben werden kann, die ein Multicast Paket sich von der versendenden Einheit entfernen kann. -\layout Standard +\end_layout +\begin_layout Standard Zurzeit sind folgende Regionen (reichweiten) definiert: -\layout Itemize +\end_layout +\begin_layout Itemize ffx1: Node-lokal, Pakete verlassen niemals den Knoten -\layout Itemize +\end_layout +\begin_layout Itemize ffx2: Link-lokal, Pakete werden niemals von Routers weitergeleitet, der angegebene Link wird nie verlassen. -\layout Itemize +\end_layout +\begin_layout Itemize ffx5: Site-lokal, Pakete verlassen niemals den Standort (Site) -\layout Itemize +\end_layout +\begin_layout Itemize ffx8: organisationsweit, Pakete verlassen niemals eine Organisation (nicht einfach zu implementieren, dies muss durch das Routing Protokoll abgedeckt werden) -\layout Itemize +\end_layout +\begin_layout Itemize ffxe: Globale Reichweite -\layout Itemize +\end_layout +\begin_layout Itemize Sonstige sind reserviert -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Multicast-Typen -\layout Standard +\end_layout +\begin_layout Standard Es sind bereits viele Typen definiert bzw. reserviert (siehe \begin_inset LatexCommand \url[RFC 2373 / IP Version 6 Addressing Architecture]{http://www.faqs.org/rfcs/rfc2373.html} -\end_inset +\end_inset für weitere Details) Einige Beispiele: -\layout Itemize +\end_layout +\begin_layout Itemize All Nodes Adresse: ID = 1h, alle Hosts am lokalen Node (ff01:0:0:0:0:0:0:1) oder am angeschlossenen Link (ff02:0:0:0:0:0:0:1) werden adressiert. -\layout Itemize +\end_layout +\begin_layout Itemize All Routers Adresse: ID = 2h, alle Router am lokalen Node (ff01:0:0:0:0:0:0:2), am angeschlossenen Link (ff02:0:0:0:0:0:0:2) oder am lokalen Standort werden adressiert. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Erforderliche node link-local Multicast Adresse -\layout Standard +\end_layout +\begin_layout Standard Diese spezielle Multicast Adresse wird als Zieladresse bei der Erkundung des Nahbereichs verwendet, da es ARP bei IPv6 im Gegensatz zu IPv4 nicht mehr gibt. -\layout Standard +\end_layout +\begin_layout Standard Ein Beispiel für diese Adresse könnte sein: -\layout Code +\end_layout +\begin_layout Code ff02::1:ff00:1234 -\layout Standard +\end_layout +\begin_layout Standard Das benutzte Präfix zeigt, dass es sich um eine link-lokale Multicast Adresse handelt. Dass Suffix wird aus der Zieladresse erstellt. In diesem Beispiel soll ein Paket zur Adresse \begin_inset Quotes eld -\end_inset +\end_inset fe80::1234 \begin_inset Quotes erd -\end_inset +\end_inset gesendet werden, aber die Netzwerk-Schicht hat keine Kenntnis der aktuellen Schicht 2 MAC Adresse. Die oberen 104 bits werde mit \begin_inset Quotes eld -\end_inset +\end_inset ff02:0:0:0:01:ff00::/104 \begin_inset Quotes erd -\end_inset +\end_inset ersetzt und die unteres 24 bits bleiben unverändert. Diese Adresse wird nun \begin_inset Quotes srd -\end_inset +\end_inset am Link \begin_inset Quotes srd -\end_inset +\end_inset verwendet, um den entsprechenden Node zu finden, der wiederum seine Schicht 2 MAC Adresse als Antwort zurücksendet. -\layout Subsection +\end_layout +\begin_layout Subsection Anycast-Adressen -\layout Standard +\end_layout +\begin_layout Standard Anycast Adressen sind spezielle Adressen und werden verwendet, um besondere Bereiche wie den nächstgelegenen DNS-Server, den nächstliegenden DHCP Server und vergleichbare dynamische Gruppen abzudecken. @@ -2094,44 +2576,56 @@ Anycast Adressen sind spezielle Adressen und werden verwendet, um besondere oder Site-lokal zurzeit) entnommen. Der Anycast-Mechanismus (client view) wird von dynamischen Routing-Protokollen gehandhabt. -\layout Standard +\end_layout +\begin_layout Standard Hinweis: Anycast Adressen können nicht als Quelladresse verwendet werden, sondern ausschließlich als Zieladressen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Subnet-Router Anycast-Adresse -\layout Standard +\end_layout +\begin_layout Standard Die Subnet-Router Anycast Adresse ist ein einfaches Beispiel für eine Anycast Adresse. Angenommen, der Knoten hat folgende global zugewiesene IPv6 Adresse: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:210:a4ff:fee3:9566/64 <- Node's address -\layout Standard +\end_layout +\begin_layout Standard Die Subnet-Router Anycast Adresse wird durch komplette Streichung des Suffixes (die letzten gültigen 64 bits) erstellt: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::/64 <- subnet-router anycast address -\layout Section +\end_layout +\begin_layout Section Adress-Typen (Host-Teil) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left In Hinblick auf Auto-Konfigurations- und Mobilitätsfragen wurde entschieden, die niedrigeren 64 bits als Host-Bestandteil zu nutzen. Jedes einzelne Subnetz kann deshalb eine große Anzahl an Adressen enthalten. -\layout Standard +\end_layout +\begin_layout Standard Der Host-Teil kann aus unterschiedlichen Blickwinkeln betrachtet werden: -\layout Subsection +\end_layout +\begin_layout Subsection Automatisch erstellte Adressen (auch unter dem Namen stateless bekannt) -\layout Standard +\end_layout +\begin_layout Standard Bei der Auto-Konfiguration wird der Hostteil der Adresse durch die Konvertierung der MAC-Adresse eines Interfaces (falls vorhanden) zu einer einmaligen IPv6 Adresse (mittels EUI-64 Methode) generiert. @@ -2139,92 +2633,111 @@ Bei der Auto-Konfiguration wird der Hostteil der Adresse durch die Konvertierung bei virtuellen Interfaces), wird anstelle dessen etwas anderes herangezogen (wie z.B. die IPv4 Adresse oder die MAC-Adresse eines physikalischen Interfaces). -\layout Standard +\end_layout +\begin_layout Standard Betrachten Sie noch einmal das erste Beispiel: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:210:a4ff:fee3:9566 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Hier ist -\layout Code +\end_layout +\begin_layout Code 210:a4ff:fee3:9566 -\layout Standard -\align left -der Hostteil und wurde aus der MAC-Adresse des NIC's erstellt, -\layout Code +\end_layout +\begin_layout Standard +\align left +der Hostteil und wurde aus der MAC-Adresse des NIC's erstellt, +\end_layout + +\begin_layout Code 00:10:A4:E3:95:66 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left wobei hier das \begin_inset LatexCommand \url[IEEE-Tutorial EUI-64]{http://standards.ieee.org/regauth/oui/tutorials/EUI64.html} -\end_inset +\end_inset Design für EUI-48 Identifiers verwendet wird. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Datenschutzproblem mit automatisch erstellten Adressen sowie eine Lösung -\layout Standard +\end_layout +\begin_layout Standard Der "automatisch generierte" Hostteil ist weltweit einmalig (mit Ausnahme, wenn der Hersteller einer NIC die gleiche MAC-Adresse bei mehr als einer NIC einsetzt). Die Client-Verfolgung am Host wird dadurch möglich, solange kein Proxy verwendet wird. -\layout Standard +\end_layout +\begin_layout Standard Dies ist ein bekanntes Problem und eine Lösung wurde dafür definiert: Datenschut z-Erweiterung, definiert in \begin_inset LatexCommand \url[RFC 3041 / Privacy Extensions for Stateless Address Autoconfiguration in IPv6]{http://www.faqs.org/rfcs/rfc3041.html} -\end_inset +\end_inset (es gibt bereits ein neueres Draft: \begin_inset LatexCommand \url[draft-ietf-ipngwg-temp-addresses-*.txt]{ftp://ftp.ietf.org/internet-drafts/} -\end_inset +\end_inset ). Es wird von Zeit zu Zeit mittels eines statischen und eines Zufallswertes ein neues Suffix erstellt. Hinweis: Dies ist nur für ausgehende Client-Verbindungen sinnvoll und bei bekannten Servern nicht wirklich sinnvoll. -\layout Subsection +\end_layout +\begin_layout Subsection Manuell festgelegte Adressen -\layout Standard +\end_layout +\begin_layout Standard Bei Servern ist es wahrscheinlich leichter, sich einfachere Adressen zu merken. Dies kann z.B. mit der Zuweisung einer zusätzlichen IPv6 Adresse an ein Interface geschehen. -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::1 -\layout Standard +\end_layout +\begin_layout Standard Für das manuelle Suffix, wie \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset im obigen Beispiel, muss das siebte höchstwertige Bit auf 0 gesetzt sein (das universale/local Bit des automatisch generierten Identifiers). Es sind auch noch andere (ansonsten nichtausgewählte) Bit-Kombinationen für Anycast-Adressen reserviert. -\layout Section +\end_layout +\begin_layout Section Präfixlängen für das Routing -\layout Standard +\end_layout +\begin_layout Standard Um eine maximale Reduktion an Routing-Tabellen zu erzielen, war in der frühen Design-Phase noch ein vollkommen hierarchischer Routing-Ansatz vorgesehen. Die Überlegungen hinter diesem Ansatz waren die gegenwärtigen IPv4 Routing-Eint @@ -2232,16 +2745,17 @@ r die Reduktion des Speicherbedarfs für die Routing-Tabellen bei Hardware-Routern (ASIC \begin_inset Quotes sld -\end_inset +\end_inset Application Specified Integrated Circuit \begin_inset Quotes srd -\end_inset +\end_inset , speziell konstuierter Chip) sowie ein daraus resultierender Geschwindigkeitszu wachs (weniger Einträge ergeben hoffentlich schnellere Abfragen). -\layout Standard +\end_layout +\begin_layout Standard Heutiger Standpunkt ist, dass das Routing für Netzwerke mit nur einem Service Provider hauptsächlich mit einem hierarchischen Design realisiert wird. Eine solche Vorgehensweise ist nicht möglich, wenn mehr als eine ISP-Verbindung @@ -2252,21 +2766,23 @@ Heutiger Standpunkt ist, dass das Routing f \begin_inset LatexCommand \url[drafts*multi6*]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset \lang ngerman , \begin_inset LatexCommand \url[IPv6 Multihoming Solutions]{http://arneill-py.sacramento.ca.us/ipv6mh/} -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection Präfixlängen ("netmasks" genannt) -\layout Standard +\end_layout +\begin_layout Standard Vergleichbar zu IPv4, handelt es sich hierbei um den routbaren Netzwerkpfad für das stattfindende Routing. Da die Standard-Notierung der Netzmaske von 128 bit nicht sehr fein aussieht, @@ -2274,279 +2790,346 @@ Vergleichbar zu IPv4, handelt es sich hierbei um den routbaren Netzwerkpfad Schema (CIDR, \begin_inset LatexCommand \url[RFC 1519 / Classless Inter-Domain Routing]{http://www.faqs.org/rfcs/rfc1519.html} -\end_inset +\end_inset ). Mit Hilfe des CIDR wird die Bitanzahl der IP Adresse festgelegt, welche für das Routing verwendet werden. Diese Methode wird auch als "Slash"-Notation genannt. -\layout Standard +\end_layout +\begin_layout Standard Ein Beispiel: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:1:2:3:4:5/48 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Notation wird erweitert zu: -\layout Itemize +\end_layout +\begin_layout Itemize Netzwerk: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0100:0000:0000:0000:0000:0000 -\layout Itemize +\end_layout +\begin_layout Itemize Netzmaske: -\layout Code +\end_layout +\begin_layout Code ffff:ffff:ffff:0000:0000:0000:0000:0000 -\layout Subsection +\end_layout +\begin_layout Subsection Zutreffende Routen -\layout Standard +\end_layout +\begin_layout Standard Im Normalfall (ohne QoS) ergibt eine Suche in der Routing-Tabelle eine Route mit der signifikantesten Adress-Bit-Anzahl, d.h. jene Route mit der größten Präfix-Länge wird zuerst herangezogen. -\layout Standard +\end_layout +\begin_layout Standard Wenn z.B. eine Routing-Tabelle folgende Einträge zeigt (Liste ist nicht komplett): -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::/48 :: U 1 0 0 sit1 -\layout Code +\end_layout +\begin_layout Code 2000::/3 ::192.88.99.1 UG 1 0 0 tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Die gezeigten Zieladressen der IPv6 Pakete werden über die entsprechenden Geräte geroutet -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:1:2:3:4:5/48 -> routed through device sit1 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:200:1:2:3:4:5/48 -> routed through device tun6to4 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-systemcheck} -\end_inset +\end_inset IPv6 System-Check -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Bevor Sie IPv6 auf einem Linux Host einsetzen können, müssen sie überprüfen, ob das System IPv6 fähig ist. Eventuell haben Sie Änderungen vorzunehmen, um IPv6 zu ermöglichen. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{systemcheck-kernel} -\end_inset +\end_inset IPv6 kompatibler Kernel -\layout Standard +\end_layout +\begin_layout Standard Neuere Linux Distributionen beinhalten bereits eine IPv6 fähigen Kernel. Die IPv6-funktionalität wird im Allgemeinen als Modul kompiliert. Es ist aber durchaus möglich, dass das Modul nicht automatisch beim Start des Betriebssystems geladen wird. -\layout Standard +\end_layout +\begin_layout Standard Für aktuelle Informationen siehe die Seite \begin_inset LatexCommand \url[IPv6+Linux-Status-Distribution]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold Hinweis: Sie sollten die Kernel Serie 2.2.x nicht mehr verwenden, da die IPv6 Implementierung nicht mehr aktuell ist. -\layout Subsection +\end_layout +\begin_layout Subsection Überprüfung der IPv6 Unterstützung im aktuellen Kernel -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Um zu überprüfen, ob ihr aktueller Kernel IPv6 unterstützt, sollten sie einen Blick in ihr /proc-Dateisystem werfen. Folgende Einträge müssen existieren: -\layout Code +\end_layout +\begin_layout Code /proc/net/if_inet6 -\layout Standard -\align left -Einen kleinen automatischen Test können Sie wie folgt durchführen: -\layout Code +\end_layout +\begin_layout Standard +\align left +Einen kleinen automatischen Test können Sie wie folgt durchführen: +\end_layout + +\begin_layout Code # test -f /proc/net/if_inet6 && echo "Running kernel is IPv6 ready" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Wenn dieser Test negativ verläuft, ist das IPv6 Modul aller Wahrscheinlichkeit noch nicht geladen. -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 Module laden -\layout Standard -\align left -Mit folgenden Befehl können Sie versuchen, das Modul zu laden: -\layout Code +\end_layout +\begin_layout Standard +\align left +Mit folgenden Befehl können Sie versuchen, das Modul zu laden: +\end_layout + +\begin_layout Code # modprobe ipv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Wenn dieser Befehl positiv verläuft, dann sollten Sie das Modul mit folgendem Befehl auflisten können: -\layout Code +\end_layout +\begin_layout Code # lsmod |grep -w 'ipv6' && echo "IPv6 module successfully loaded" -\layout Standard -\align left -Der obige Test sollte nun erfolgreich verlaufen. -\layout Standard +\end_layout +\begin_layout Standard +\align left +Der obige Test sollte nun erfolgreich verlaufen. +\end_layout + +\begin_layout Standard Hinweis: Ein Entfernen des Moduls im laufenden System wird derzeit nicht unterstützt und kann unter gewissen Bedingungen zu einem Absturz des Kernels führen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Automatisches Laden des Moduls -\layout Standard +\end_layout +\begin_layout Standard Es ist möglich das IPv6 Modul bei Bedarf automatisch zu laden. Sie müssen nur folgende Zeile in die Konfigurationsdatei des kernel modul loaders eintragen (normalerweise: /etc/modules.conf oder /etc/conf.modules): -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 ipv6 # automatically load IPv6 module on demand -\layout Standard +\end_layout +\begin_layout Standard Mit der folgenden Zeile ist es auch möglich, das automatische Laden des IPv6 Moduls auszuschalten. -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 off # disable automatically load of IPv6 module on demand -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: In Kernel Series 2.6.x wurde der Modul-Lade-Mechanismus geändert. Die neue Konfigurationsdatei wird anstelle /etc/modules.conf nun /etc/modprobe.co nf genannt. -\layout Subsection +\end_layout +\begin_layout Subsection Kernel-Kompilierung mit IPv6 Funktionalität -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Wenn beide oben gezeigten Methoden ohne Erfolg blieben und ihr Kernel somit keine IPv6 Unterstützung bietet, dann haben Sie folgende Optionen: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Aktualisieren Sie Ihre Distribution mit einer Version, die von Haus aus IPv6 unterstützt (empfohlen für Anfänger), siehe \begin_inset LatexCommand \url[IPv6+Linux-Status-Distribution]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Sie können einen Standard-Kernel kompilieren (einfach, wenn Sie die benötigten Optionen kennen) -\layout Itemize +\end_layout +\begin_layout Itemize Kompilieren Sie die Kernel-Quellen ihrer Distribution (manchmal nicht ganz so einfach) -\layout Itemize -\align left -Kompilieren Sie einen Kernel mit den USAGI-Erweiterungen -\layout Standard +\end_layout +\begin_layout Itemize +\align left +Kompilieren Sie einen Kernel mit den USAGI-Erweiterungen +\end_layout + +\begin_layout Standard Falls Sie sich dazu entscheiden, einen neuen IPv6 kompatiblen Kernel zu kompilieren, sollten Sie auf jeden Fall bereits Erfahrung mit der Kernel-Kompil ierung haben sowie das \begin_inset LatexCommand \url[Linux Kernel HOWTO]{http://www.tldp.org/HOWTO/Kernel-HOWTO.html} -\end_inset +\end_inset lesen. -\layout Standard +\end_layout +\begin_layout Standard Ein großteils aktueller Vergleich zwischen dem Standard-Kernel und dem Kernel mit USAGI-Erweiterungen ist verfügbar unter \begin_inset LatexCommand \url[IPv6+Linux-Status-Kernel]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Kompilieren eines Standard-Kernels -\layout Standard +\end_layout +\begin_layout Standard Detailliertere Ausführungen zur Kompilierung eines IPv6 fähigen Kernels finden Sie unter \begin_inset LatexCommand \url[IPv6-HOWTO-2#kernel]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-2.html#kernel} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Hinweis: Sie sollten wann immer möglich die Kernel Serie 2.6.x oder höher einsetzen, da die IPv6 Unterstützung der Serie 2.4.x nur einige Backports erhält und die IPv6-Unterstützung von Serie 2.2.x hoffnungslos veraltet ist und nicht mehr weiterentwickelt wird. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Kompilieren eines Kernels mit USAGI-Erweiterungen -\layout Standard +\end_layout +\begin_layout Standard Wie für den Standard-Kernel gilt auch hier, dass das Kompilieren des Kernels nur fortgeschrittenen Benutzern empfohlen wird, die mit IPv6 und dem Kompiliere n des Kernels bereits vertraut sind. -\layout Standard +\end_layout +\begin_layout Standard Siehe auch \begin_inset LatexCommand \url[USAGI project / FAQ]{http://www.linux-ipv6.org/faq.html} -\end_inset +\end_inset und \begin_inset LatexCommand \url[Obtaining the best IPv6 support with Linux (Article)]{http://www.deepspace6.net/docs/best_ipv6_support.html} -\end_inset +\end_inset \lang english ( \begin_inset LatexCommand \url[Spiegel]{http://mirrors.bieringer.de/www.deepspace6.net/docs/best_ipv6_support.html} -\end_inset +\end_inset ) \lang ngerman . -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 kompatible Netzwerkgeräte -\layout Standard +\end_layout +\begin_layout Standard Nicht alle Netzwerkgeräte sind bereits (bzw. überhaupt) dazu in der Lage, IPv6 Pakete übertragen zu können. Den aktuellen Status können Sie unter \begin_inset LatexCommand \url[IPv6+Linux-status-kernel.html#transport]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html#transport} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Ein entscheidender Punkt ist die Tatsache, dass ein IPv6 Paket wegen der Struktur der Netzwerkschicht in der Kernel-Implementierung nicht wirklich aufgrund der IP-Header-Nummer (6 anstelle 4) wiedererkannt wird. @@ -2558,139 +3141,168 @@ Ein entscheidender Punkt ist die Tatsache, dass ein IPv6 Paket wegen der auf der Empfänger-Seite kann das Paket nicht verarbeitet werden (Sie können dies z.B. mit tcpdump sehen). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Gegenwärtig bekannte Verbindungsarten, die niemals IPv6 fähig sein werden -\layout Itemize +\end_layout +\begin_layout Itemize Serial Line IP ( \begin_inset LatexCommand \url[RFC 1055 / SLIP]{http://www.faqs.org/rfcs/rfc1055.html} -\end_inset +\end_inset ), auch SLIPv4 genannt; das Gerät heißt: s1X -\layout Itemize +\end_layout +\begin_layout Itemize Parallel Line IP (PLIP), gleich dem SLIP, Gerätename: plipX -\layout Itemize +\end_layout +\begin_layout Itemize ISDN mit -\emph on +\emph on rawip -\emph default +\emph default Encapsulation; Gerätename: isdnX -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Bekannte Verbindungsarten, die gegenwärtig IPv6 nicht unterstützen -\layout Itemize +\end_layout +\begin_layout Itemize ISDN mit -\emph on +\emph on syncppp -\emph default +\emph default Encapsulation; Gerätename: ipppX (Designfrage des ipppd; in der Kernel Serie 2.5.x wird ipppX in einer allgemeinen PPP Schicht inkludiert) -\layout Section +\end_layout +\begin_layout Section IPv6 kompatible Tools zur Netzwerkkonfiguration -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Ohne entsprechende Tools zur Konfiguration von IPv6 würden Sie mit einem IPv6 fähigen Kernel nicht weit kommen. Es gibt verschiedene Pakete womit IPv6 konfiguriert werden kann. -\layout Subsection +\end_layout +\begin_layout Subsection net-tools Paket -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Das Paket net-tool beinhaltet einige Tools wie -\family typewriter +\family typewriter ifconfig -\family default +\family default und -\family typewriter +\family typewriter route -\family default +\family default . Mit den Tools kann IPv6 auf einem Interface konfiguriert werden. Sehen Sie sich die Ausgabe des Befehls -\family typewriter -\emph on +\family typewriter +\emph on ifconfig -? -\family default -\emph default +\family default +\emph default Bzw. -\family typewriter -\emph on +\family typewriter +\emph on route -? -\family default -\emph default +\family default +\emph default an. Finden Sie in der Ausgabe die Worte IPv6, inet6 oder Ähnliches, dann ist das Tool IPv6-kompatibel. -\layout Standard +\end_layout +\begin_layout Standard Automatische Überprüfung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig -? 2>& 1|grep -qw 'inet6' && echo "utility 'ifconfig' is -\layout Code +\end_layout +\begin_layout Code ¬ IPv6-ready" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Folgenden Check gibt es für -\family typewriter +\family typewriter route -\family default +\family default : -\layout Code +\end_layout +\begin_layout Code # /sbin/route -? 2>& 1|grep -qw 'inet6' && echo "utility 'route' is IPv6-ready" -\layout Subsection +\end_layout +\begin_layout Subsection iproute Paket -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Alexey N.Kuznetsov (gegenwärtig ein Betreuer des Linux Network Codes) erstellte eine Tool-Sammlung, womit das Netzwerk mittels dem netlink Device konfiguriert wird. Diese Tool-Sammlung stellt mehr Funktionalität als das net-tools Paket zur Verfügung, ist aber nicht sehr umfangreich dokumentiert und nichts für schwache Nerven. -\layout Code +\end_layout +\begin_layout Code # /sbin/ip 2>&1 |grep -qw 'inet6' && echo "utility 'ip' is IPv6-ready" -\layout Standard +\end_layout +\begin_layout Standard Wird das Programm /sbin/ip nicht gefunden, dann wird die Installation des iproute Paketes empfohlen. -\layout Itemize +\end_layout +\begin_layout Itemize Sie können dies (falls beinhaltet) von der benutzten Linux-Distribution installieren -\layout Itemize +\end_layout +\begin_layout Itemize Sie können die tar-Version downladen und neu kompilieren: \begin_inset LatexCommand \url[Original FTP source]{ftp://ftp.inr.ac.ru/ip-routing/} -\end_inset +\end_inset sowie FTP-Spiegel (Info fehlt) -\layout Itemize +\end_layout +\begin_layout Itemize Sie können nach einem passenden RPM Paket unter \begin_inset LatexCommand \url[RPMfind/iproute]{http://rpmfind.net/linux/rpm2html/search.php?query=iproute} -\end_inset +\end_inset suchen (manchmal ist auch das kompilieren eines SRPMS Paketes zu empfohlen) -\layout Section +\end_layout +\begin_layout Section IPv6 Test/Debug-Programme -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Nachdem Sie ihr System auf IPv6 vorbereitet haben, wollen Sie nun IPv6 für die Netzwerkkommunikation einsetzen. Zuerst sollten Sie lernen, IPv6 Pakete mit einem Sniffer Programm zu untersuche @@ -2698,423 +3310,515 @@ n. Dies ist zu empfehlen, denn in Hinblick auf Fehlersuche und Troubleshooting kann das Durchführen einer schnellen Diagnose von Nutzen sein. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-ping6} -\end_inset +\end_inset IPv6 ping -\layout Standard +\end_layout +\begin_layout Standard Das Programm ist normalerweise im Paket -\emph on +\emph on iputils -\emph default +\emph default beinhaltet. Durch senden von ICMPv6 echo-request Paketen und warten auf ICMPv6 echo-reply Paketen können einfache Transport-Tests durchgeführt werden. -\layout Standard +\end_layout +\begin_layout Standard Anwendung -\layout Code +\end_layout +\begin_layout Code # ping6 -\layout Code +\end_layout +\begin_layout Code # ping6 -\layout Code +\end_layout +\begin_layout Code # ping6 [-I ] -\layout Standard +\end_layout +\begin_layout Standard Beispiel -\layout Code +\end_layout +\begin_layout Code # ping6 -c 1 ::1 -\layout Code +\end_layout +\begin_layout Code PING ::1(::1) from ::1 : 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from ::1: icmp_seq=0 hops=64 time=292 usec -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code --- ::1 ping statistics --- -\layout Code +\end_layout +\begin_layout Code 1 packets transmitted, 1 packets received, 0% packet loss -\layout Code +\end_layout +\begin_layout Code round-trip min/avg/max/mdev = 0.292/0.292/0.292/0.000 ms -\layout Standard +\end_layout +\begin_layout Standard Hinweis: ping6 benötigt direkten Zugriff auf den Socket und hierfür Root-Rechte. Wenn Nicht-Root-Benutzer ping6 nicht benutzen können, kann dies zwei Ursachen haben: -\layout Enumerate +\end_layout +\begin_layout Enumerate ping6 ist nicht im Pfad des Benutzers eingetragen; ping6 ist allgemein in /usr/sbin zu finden -> Lösung: Den Pfad ergänzen (nicht empfohlen) -\layout Enumerate +\end_layout +\begin_layout Enumerate ping6 lässt sich im Allgemeines wegen fehlender Root-Rechte nicht korrekt ausführen -> Lösung: chmod u+s /usr/sbin/ping6 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Das Interface für einen IPv6 ping bestimmen -\layout Standard +\end_layout +\begin_layout Standard Wenn link-lokale Adressen für ein IPv6 ping verwendet werden, dann hat der Kernel keine Kenntnis darüber, durch welches (physikalische oder virtuelle) Gerät das Paket gesendet werden muss - jedes Gerät hat eine link-lokale Adresse. Ein Versuch resultiert in folgender Fehlermeldung: -\layout Code +\end_layout +\begin_layout Code # ping6 fe80::212:34ff:fe12:3456 -\layout Code +\end_layout +\begin_layout Code connect: Invalid argument -\layout Standard +\end_layout +\begin_layout Standard In diesem Fall müssen Sie das Interface zusätzlich spezifizieren: -\layout Code +\end_layout +\begin_layout Code # ping6 -I eth0 -c 1 fe80::2e0:18ff:fe90:9205 -\layout Code +\end_layout +\begin_layout Code PING fe80::212:23ff:fe12:3456(fe80::212:23ff:fe12:3456) from -\layout Code +\end_layout +\begin_layout Code ¬ fe80::212:34ff:fe12:3478 eth0: 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from fe80::212:23ff:fe12:3456: icmp_seq=0 hops=64 time=445 usec -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code --- fe80::2e0:18ff:fe90:9205 ping statistics --- -\layout Code +\end_layout +\begin_layout Code 1 packets transmitted, 1 packets received, 0% packet loss round-trip -\layout Code +\end_layout +\begin_layout Code ¬ min/avg/max/mdev = 0.445/0.445/0.445/0.000 ms -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ping6 zu Multicast-Adressen -\layout Standard +\end_layout +\begin_layout Standard Ein interessanter Mechanismus zum Aufspüren eines IPv6 aktiven Hosts am Link ist mit ping6 an eine link-lokale all-node Multicast Adresse zu pingen. -\layout Code +\end_layout +\begin_layout Code # ping6 -I eth0 ff02::1 -\layout Code +\end_layout +\begin_layout Code PING ff02::1(ff02::1) from fe80:::2ab:cdff:feef:0123 eth0: 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.104 ms -\layout Code +\end_layout +\begin_layout Code 64 bytes from fe80::212:34ff:fe12:3450: icmp_seq=1 ttl=64 time=0.549 ms (DUP!) -\layout Standard +\end_layout +\begin_layout Standard Bei IPv6 kann dieses Verhalten zurzeit, im Gegensatz zu IPv4, wo Antworten auf ein Ping auf die Broadcast Adresse unterdrückt werden können, nicht unterbunden werden. Ausnahme hierbei ist der Einsatz der lokalen IPv6 Firewall-Funktionalität. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-traceroute6} -\end_inset +\end_inset IPv6 traceroute6 -\layout Standard +\end_layout +\begin_layout Standard Dieses Programm ist normal im Paket iputils enthalten. Es ist ein Programm vergleichbar dem IPv4 traceroute. Unten sehen Sie ein Beispiel: -\layout Code +\end_layout +\begin_layout Code # traceroute6 www.6bone.net -\layout Code +\end_layout +\begin_layout Code traceroute to 6bone.net (3ffe:b00:c18:1::10) from 3ffe:ffff:0000:f101::2, 30 -\layout Code +\end_layout +\begin_layout Code ¬ hops max, 16 byte packets -\layout Code +\end_layout +\begin_layout Code 1 localipv6gateway (3ffe:ffff:0000:f101::1) 1.354 ms 1.566 ms 0.407 ms -\layout Code +\end_layout +\begin_layout Code 2 swi6T1-T0.ipv6.switch.ch (3ffe:2000:0:400::1) 90.431 ms 91.956 ms 92.377 ms -\layout Code +\end_layout +\begin_layout Code 3 3ffe:2000:0:1::132 (3ffe:2000:0:1::132) 118.945 ms 107.982 ms 114.557 ms -\layout Code +\end_layout +\begin_layout Code 4 3ffe:c00:8023:2b::2 (3ffe:c00:8023:2b::2) 968.468 ms 993.392 ms 973.441 ms -\layout Code +\end_layout +\begin_layout Code 5 3ffe:2e00:e:c::3 (3ffe:2e00:e:c::3) 507.784 ms 505.549 ms 508.928 ms -\layout Code +\end_layout +\begin_layout Code 6 www.6bone.net (3ffe:b00:c18:1::10) 1265.85 ms * 1304.74 ms -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Im Unterschied zu modernen IPv4 traceroute Versionen, welche den Einsatz von ICMPv4-echo-request Paketen wie auch UDP Paketen (default) ermöglichen, können mit IPv6-traceroute nur UDP Pakete versendet werden. Wie Sie vielleicht bereits wissen, werden von Firewalls bzw. von ACLs auf Routern ICMP echo-request Pakete mehr akzeptiert als UDP Pakete. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-tracepath6} -\end_inset +\end_inset IPv6 tracepath6 -\layout Standard +\end_layout +\begin_layout Standard Dieses Programm ist normalerweise im Paket -\emph on +\emph on iputils -\emph default +\emph default enthalten. Das Programm ist dem traceroute6 ähnlich, es gibt den Weg zu einem angegebenen Ziel wieder und misst hierbei den MTU-Wert. Unten sehen Sie ein Beispiel: -\layout Code +\end_layout +\begin_layout Code # tracepath6 www.6bone.net -\layout Code +\end_layout +\begin_layout Code 1?: [LOCALHOST] pmtu 1480 -\layout Code +\end_layout +\begin_layout Code 1: 3ffe:401::2c0:33ff:fe02:14 150.705ms -\layout Code +\end_layout +\begin_layout Code 2: 3ffe:b00:c18::5 267.864ms -\layout Code +\end_layout +\begin_layout Code 3: 3ffe:b00:c18::5 asymm 2 266.145ms pmtu 1280 -\layout Code +\end_layout +\begin_layout Code 3: 3ffe:3900:5::2 asymm 4 346.632ms -\layout Code +\end_layout +\begin_layout Code 4: 3ffe:28ff:ffff:4::3 asymm 5 365.965ms -\layout Code +\end_layout +\begin_layout Code 5: 3ffe:1cff:0:ee::2 asymm 4 534.704ms -\layout Code +\end_layout +\begin_layout Code 6: 3ffe:3800::1:1 asymm 4 578.126ms !N -\layout Code +\end_layout +\begin_layout Code Resume: pmtu 1280 -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-tcpdump} -\end_inset +\end_inset IPv6 tcpdump -\layout Standard +\end_layout +\begin_layout Standard In Linux ist tcpdump ein Haupttool zum aufzeichnen von Paketen. Weiter unten sehen Sie einige Beispiele. Normalerweise ist die Ipv6-Unterstützung in der aktuellen Version 3.6 gegeben. -\layout Standard +\end_layout +\begin_layout Standard Bei tcpdump werden zur Geräuschminimierung bei der Paket-Filterung Ausdrücke eingesetzt: -\layout Itemize +\end_layout +\begin_layout Itemize icmp6: ICMPv6 Datenverkehr wird gefiltert -\layout Itemize +\end_layout +\begin_layout Itemize ip6: IPv6 Datenverkehr (inkl.ICMPv6) wird gefiltert -\layout Itemize +\end_layout +\begin_layout Itemize proto ipv6: getunnelter IPv6-in-IPv4 Datenverkehr wird gefiltert -\layout Itemize +\end_layout +\begin_layout Itemize not port ssh: zum unterdrücken der Anzeige von SSH Paketen während der Ausführun g von tcpdump bei einer remote SSH-Sitzung -\layout Standard +\end_layout +\begin_layout Standard Ebenfalls sind einige Kommandozeilen-Optionen sehr hilfreich, um detailliertere Informationen über die Pakete erlangen und protokollieren zu können. Für ICMPv6 Pakete sind hauptsächlich interessant: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -s 512 \begin_inset Quotes erd -\end_inset +\end_inset : Bei der Aufzeichnung der Pakete wird die zu Aufzeichnungslänge auf 512 bytes vergrößert -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -vv \begin_inset Quotes erd -\end_inset +\end_inset : wirklich sehr ausführliche Ausgabe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -n \begin_inset Quotes erd -\end_inset +\end_inset : Adressen werden nicht in Namen aufgelöst. Dies ist hilfreich, wenn die Reverse-DNS-Auflösung nicht sauber arbeiten sollte -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 ping zur Adresse -\size footnotesize +\size footnotesize 3ffe:ffff:100:f101::1 -\size default +\size default über einen lokalen Link -\layout Code +\end_layout +\begin_layout Code # tcpdump -t -n -i eth0 -s 512 -vv ip6 or proto ipv6 -\layout Code +\end_layout +\begin_layout Code tcpdump: listening on eth0 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:2e0:18ff:fe90:9205 > 3ffe:ffff:100:f101::1: icmp6: echo -\layout Code +\end_layout +\begin_layout Code ¬ request (len 64, hlim 64) -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::1 > 3ffe:ffff:100:f101:2e0:18ff:fe90:9205: icmp6: echo -\layout Code +\end_layout +\begin_layout Code ¬ reply (len 64, hlim 64) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 ping zur Adresse -\size footnotesize +\size footnotesize 3ffe:ffff:100::1 -\size default +\size default über einen IPv6-in-IPv4 Tunnel geroutet -\layout Standard +\end_layout +\begin_layout Standard 1.2.3.4. und 5.6.7.8. sind Tunnel-Endpunkte (alle Adressen sind Beispiele) -\layout Code +\end_layout +\begin_layout Code # tcpdump -t -n -i ppp0 -s 512 -vv ip6 or proto ipv6 -\layout Code +\end_layout +\begin_layout Code tcpdump: listening on ppp0 -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 > 5.6.7.8: 2002:ffff:f5f8::1 > 3ffe:ffff:100::1: icmp6: echo request -\layout Code +\end_layout +\begin_layout Code ¬ (len 64, hlim 64) (DF) (ttl 64, id 0, len 124) -\layout Code +\end_layout +\begin_layout Code 5.6.7.8 > 1.2.3.4: 3ffe:ffff:100::1 > 2002:ffff:f5f8::1: icmp6: echo reply (len -\layout Code +\end_layout +\begin_layout Code ¬ 64, hlim 61) (ttl 23, id 29887, len 124) -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 > 5.6.7.8: 2002:ffff:f5f8::1 > 3ffe:ffff:100::1: icmp6: echo request -\layout Code +\end_layout +\begin_layout Code ¬ (len 64, hlim 64) (DF) (ttl 64, id 0, len 124) -\layout Code +\end_layout +\begin_layout Code 5.6.7.8 > 1.2.3.4: 3ffe:ffff:100::1 > 2002:ffff:f5f8::1: icmp6: echo reply (len -\layout Code +\end_layout +\begin_layout Code ¬ 64, hlim 61) (ttl 23, id 29919, len 124) -\layout Section +\end_layout +\begin_layout Section IPv6 kompatible Programme -\layout Standard +\end_layout +\begin_layout Standard Aktuelle Distributionen beinhalten bereits die gängigsten IPv6 kompatiblen Client- und Server-Programme. Weitere Infos gibt es unter \begin_inset LatexCommand \url[IPv6+Linux-Status-Distribution]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset . Falls ein Programm hier noch nicht gelistet sein sollte, können Sie unter \begin_inset LatexCommand \url[IPv6 & Linux - Current Status - Applications]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html} -\end_inset +\end_inset nachlesen, ob das Programm bereits auf IPv6 portiert wurde und unter Linux bereits läuft. Für verbreitete Programme gibt es einige Hinweise unter \begin_inset LatexCommand \url[IPv6 & Linux - HowTo - Part 3]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-3.html} -\end_inset +\end_inset und \begin_inset LatexCommand \url[IPv6 & Linux - HowTo - Part 4]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-4.html} -\end_inset +\end_inset . -\layout Section +\end_layout +\begin_layout Section IPv6 kompatible Client-Programme (Auswahl) -\layout Standard +\end_layout +\begin_layout Standard Um die folgend abgebildeten Tests durchzuführen, benötigen Sie ein funktionieren des IPv6 System. Bei einigen Beispielen werden Adressen angezeigt, die nur bei einer verfügbaren 6bone Verbindung erreichbar sind. -\layout Subsection +\end_layout +\begin_layout Subsection DNS-Überprüfung der IPv6 Adress-Auflösung -\layout Standard +\end_layout +\begin_layout Standard Jeder DNS-Server (Domain Name System) sollte aufgrund der Sicherheitsupdates der letzten Jahre bereits mit neuerer Software bestückt sein, die den Übergangs -IPv6-Adress-Standardtyp AAAA unterstützt (der neueste Standardtyp - A6 @@ -3122,1295 +3826,1605 @@ Jeder DNS-Server (Domain Name System) sollte aufgrund der Sicherheitsupdates daher noch nicht allzu verbreitet. Ebenfalls nicht unterstützt wird die root Domain IP6.ARPA). Ein einfacher Test zum überprüfen der IPv6 Adress-Auflösung ist: -\layout Code +\end_layout +\begin_layout Code # host -t AAAA www.join.uni-muenster.de -\layout Standard +\end_layout +\begin_layout Standard Die Ausgabe des Tests sollte etwa wie folgt sein: -\layout Code +\end_layout +\begin_layout Code www.join.uni-muenster.de. is an alias for tolot.join.uni-muenster.de. -\layout Code +\end_layout +\begin_layout Code tolot.join.uni-muenster.de. has AAAA address 2001:638:500:101:2e0:81ff:fe24:37c6 -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 kompatible Telnet Client-Programme -\layout Standard +\end_layout +\begin_layout Standard IPv6 kompatible Clients sind verfügbar. Ein einfacher Test sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code $ telnet 3ffe:400:100::1 80 -\layout Code +\end_layout +\begin_layout Code Trying 3ffe:400:100::1... -\layout Code +\end_layout +\begin_layout Code Connected to 3ffe:400:100::1. -\layout Code +\end_layout +\begin_layout Code Escape character is '^]'. -\layout Code +\end_layout +\begin_layout Code HEAD / HTTP/1.0 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code HTTP/1.1 200 OK -\layout Code +\end_layout +\begin_layout Code Date: Sun, 16 Dec 2001 16:07:21 -\layout Code +\end_layout +\begin_layout Code GMT Server: Apache/2.0.28 (Unix) -\layout Code +\end_layout +\begin_layout Code Last-Modified: Wed, 01 Aug 2001 21:34:42 GMT -\layout Code +\end_layout +\begin_layout Code ETag: "3f02-a4d-b1b3e080" -\layout Code +\end_layout +\begin_layout Code Accept-Ranges: bytes -\layout Code +\end_layout +\begin_layout Code Content-Length: 2637 -\layout Code +\end_layout +\begin_layout Code Connection: close -\layout Code +\end_layout +\begin_layout Code Content-Type: text/html; charset=ISO-8859-1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code Connection closed by foreign host. -\layout Standard +\end_layout +\begin_layout Standard Wird ein Text wie \begin_inset Quotes sld -\end_inset +\end_inset cannot resolve hostname \begin_inset Quotes srd -\end_inset +\end_inset ausgegeben, dann unterstützt der Telnet Client keine IPv6 Adressen. -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 kompatible ssh Client-Programme -\layout Subsubsection +\end_layout +\begin_layout Subsubsection openssh -\layout Standard +\end_layout +\begin_layout Standard Aktuelle openssh-Versionen sind IPv6 kompatibel. Abhängig von der Konfiguration vor der Kompilierung gibt es zwei unterschiedlic he Verhaltensweisen: -\layout Itemize +\end_layout +\begin_layout Itemize --without-ipv4-default: Der Client versucht zuerst eine IPv6-Verbindung. Misslingt dies, wird eine IPv4-Verbindung aufgebaut -\layout Itemize +\end_layout +\begin_layout Itemize --with-ipv4-default: standardmäßig wird eine IPv4-Verbindung aufgebaut. Eine IPv6-Verbindung muss, wie unten im Beispiel zu sehen ist, erzwungen werden: -\layout Code +\end_layout +\begin_layout Code $ ssh -\series bold +\series bold -6 -\series default +\series default ::1 -\layout Code +\end_layout +\begin_layout Code user@::1's password: ****** -\layout Code +\end_layout +\begin_layout Code [user@ipv6host user]$ -\layout Standard +\end_layout +\begin_layout Standard Falls ihr ssh Client-Programm die Option \begin_inset Quotes sld -\end_inset +\end_inset -6 \begin_inset Quotes srd -\end_inset +\end_inset nicht kennt, dann ist das Programm nicht IPv6 fähig. Dies ist bei den meisten ssh Paketen der Version 1 der Fall. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ssh.com -\layout Standard +\end_layout +\begin_layout Standard SSH.com's SSH Client und Server sind ebenfalls IPv6 kompatibel und darüber hinaus handelt es sich um freie Programme für die Linux- und FreeBSD-Plattform, unabhängig davon, ob sie zu kommerziellem oder zu persönlichen Zweck verwendet werden. -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 kompatible Web-Browser -\layout Standard +\end_layout +\begin_layout Standard Einen aktuellen Statusüberblick zum Thema IPv6 kompatible Web-Browser ist unter \begin_inset LatexCommand \url[IPv6+Linux-status-apps.html#HTTP]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#HTTP} -\end_inset +\end_inset verfügbar. -\layout Standard +\end_layout +\begin_layout Standard Die meisten Browser haben zurzeit noch ungelöste Probleme -\layout Enumerate +\end_layout +\begin_layout Enumerate Ist ein IPv4 Proxy in den Einstellungen eingetragen, dann werden IPv6 Anfragen zum Proxy gesendet. Der Proxy kann keine IPv6 Anfragen verstehen und somit scheitert die Anfrage. Lösung: Proxy Software aktualisieren (siehe weiter unten). -\layout Enumerate +\end_layout +\begin_layout Enumerate Automatik-Einstellungen des Proxy (*.pac) können aufgrund ihrer Beschaffenheit nicht derart erweitert werden, dass sie IPv6 Anfragen anders handhaben (z.B. kein Proxy verwenden) können (Sie sind in Javaskript geschrieben und ziemlich hard coded in den Quellen verankert; z.B. Maxilla Quellcode). -\layout Standard +\end_layout +\begin_layout Standard Ältere Browser-Versionen verstehen ebenfalls keine URL mit IPv6 Adressen wie z.B. \begin_inset LatexCommand \url[http://[3ffe:400:100::1]/]{http://[3ffe:400:100::1]/} -\end_inset +\end_inset (die angegebene URL funktioniert nur mit einem IPv6 kompatiblen Browser!). -\layout Standard +\end_layout +\begin_layout Standard Ein kleiner Test ist diese URL mit einem gegebenen Browser und ohne Proxy zu verwenden. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection URLs zum testen -\layout Standard +\end_layout +\begin_layout Standard Ein guter Ausgangspunkt zum Betrachten von Webseiten mit IPv6 ist \begin_inset LatexCommand \url[http://www.kame.net/]{http://www.kame.net/} -\end_inset +\end_inset . Ist die Schildkröte animiert, dann ist Verbindung mittels IPv6 Verbindung zustande gekommen, andererseits bleibt die Schildkröte statisch. -\layout Section +\end_layout +\begin_layout Section IPv6 kompatible Server -\layout Standard +\end_layout +\begin_layout Standard In diesem Teil des HOWTOs wird stärker auf Client-spezifische Belange eingegange n. Folglich sei zu IPv6 kompatiblen Servern wie sshd, httpd, telnetd usw. auf diese Stelle verwiesen: \begin_inset LatexCommand \ref[Hints for IPv6-enabled daemons]{chapter-hints-daemons} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{faq-ipv6-ready-system-check} -\end_inset +\end_inset FAQ (IPv6 Systemcheck) -\layout Subsection +\end_layout +\begin_layout Subsection Anwendung diverser Tools -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Q: ping6 zu einer link-lokalen Adresse funktioniert nicht -\layout Standard +\end_layout +\begin_layout Standard Fehlermeldung: " -\emph on +\emph on connect: Invalid argument -\emph default +\emph default " -\layout Standard +\end_layout +\begin_layout Standard Der Kernel hat keine Kenntnis darüber, welchen physikalischen oder virtuellen Link Sie zum versenden von ICMPv6 Paketen verwenden möchten. Aus diesem Grund wird die Fehlermeldung ausgegeben. -\layout Standard +\end_layout +\begin_layout Standard Lösung: Spezifizieren Sie den Link, z.B.: \begin_inset Quotes sld -\end_inset +\end_inset ping6 -\series bold +\series bold -I eth0 -\series default +\series default fe80::2e0:18ff:fe90:9205 \begin_inset Quotes srd -\end_inset +\end_inset . Siehe auch \begin_inset LatexCommand \ref[program ping6 usage]{program-ping6} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Q: ping6 oder traceroute6 funktioniert nicht als normaler Benutzer -\layout Standard +\end_layout +\begin_layout Standard Fehlermeldung: \begin_inset Quotes sld -\end_inset +\end_inset -\emph on +\emph on icmp socket: Operation not permitted -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Diese Tools erzeugen spezielle ICMPv6 Pakete und versenden diese unter Verwendun g von raw sockets im Kernel. Raw sockets können aber nur vom Benutzer \begin_inset Quotes sld -\end_inset +\end_inset root \begin_inset Quotes srd -\end_inset +\end_inset verwendet werden. Normale Benutzer bekommen aus diesem Grund diese Fehlermeldung. -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Lösung: Wenn wirklich alle Benutzer auf diese Tools zugreifen sollen, können Sie dies mit setzen des \begin_inset Quotes sld -\end_inset +\end_inset suid \begin_inset Quotes srd -\end_inset +\end_inset bits mittels \begin_inset Quotes sld -\end_inset +\end_inset chmod u+s / path/to/program \begin_inset Quotes srd -\end_inset +\end_inset erreichen (siehe auch \begin_inset LatexCommand \ref[program ping6 usage]{program-ping6} -\end_inset +\end_inset ). Falls nicht alle Benutzer das Programm benötigen, können Sie die Gruppenzugehör igkeit des Programms ändern, z.B. Gruppe \begin_inset Quotes sld -\end_inset +\end_inset wheel \begin_inset Quotes srd -\end_inset +\end_inset . Fügen Sie alle Benutzer zu dieser Gruppe hinzu und entfernen Sie das execution bit für andere Benutzer mittels \begin_inset Quotes sld -\end_inset +\end_inset chmod o-rwx /path/to/program \begin_inset Quotes srd -\end_inset +\end_inset . Alternativ können Sie auch \begin_inset Quotes sld -\end_inset +\end_inset sudo \begin_inset Quotes srd -\end_inset +\end_inset dazu verwenden, um Ihren Sicherheitsbestimmungen Rechnung zu tragen. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-interface} -\end_inset +\end_inset Interface-Konfiguration -\layout Section +\end_layout +\begin_layout Section Unterschiedliche Netzwerk-Geräte -\layout Standard +\end_layout +\begin_layout Standard Ein Knoten besitzt mehrere Netzwerk-Devices, die in Klassen zusammengefasst werden können: -\layout Itemize +\end_layout +\begin_layout Itemize Physikalische Devices wie eth0, tr0 -\layout Itemize +\end_layout +\begin_layout Itemize Virtuelle Devices wie ppp0, tun0, tap0, sit0, isdn0, ippp0 -\layout Subsection +\end_layout +\begin_layout Subsection Physikalische Devices -\layout Standard +\end_layout +\begin_layout Standard Physikalische Interfaces wie Ethernet oder Token-Ring bedürfen keiner speziellen Handhabung. -\layout Subsection +\end_layout +\begin_layout Subsection Virtuelle Devices -\layout Standard +\end_layout +\begin_layout Standard Virtuelle Interfaces hingegen benötigen immer eine spezielle Konfiguration. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6-in-IPv4 Tunnel Interfaces -\layout Standard +\end_layout +\begin_layout Standard Diese Interfaces werden -\series bold +\series bold sitx -\series default +\series default genannt. Der Name sit ist eine Abkürzung für -\series bold +\series bold S -\series default +\series default imple -\series bold +\series bold I -\series default +\series default nternet -\series bold +\series bold T -\series default +\series default ransition. Das Gerät hat die Fähigkeit IPv6 Pakete in IPv4 Pakete zu verkapseln und diese dann über einen Tunnel zum entfernten Endpunkt zu transportieren. -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold sit0 -\series default +\series default hat eine spezielle Bedeutung: dieses Interface kann nicht für fest zugeordnete Tunnel verwendet werden. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection PPP Interfaces -\layout Standard +\end_layout +\begin_layout Standard PPP Interfaces beziehen ihre IPv6 Funktionalität von einem IPv6 kompatiblen PPP Daemon. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ISDN HDLC Interfaces -\layout Standard +\end_layout +\begin_layout Standard Für HDLC mit -\series bold +\series bold IP -\series default +\series default encapsulation ist die IPv6 Funktionalität bereits im Kernel integriert. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ISDN PPP Interfaces -\layout Standard +\end_layout +\begin_layout Standard ISDN PPP Interfaces (ippp) werden durch den Kernel nicht mit IPv6 Funktionalität unterstützt. Es gibt auch keine Pläne hierfür, da im Kernel 2.5.+ dieser Interface-Typ durch eine allgemeinere ppp Interface Schicht ersetzt werden soll. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection SLIP + PLIP -\layout Standard +\end_layout +\begin_layout Standard Wie bereits erwähnt, unterstützen diese Interfaces keinen IPv6 Transport (senden ist ok, das abfertigen ankommender Pakete funktioniert jedoch nicht). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ether-tap Device -\layout Standard +\end_layout +\begin_layout Standard Ether-tap Devices sind IPv6 kompatibel und als stateless konfiguriert. Für den Gebrauch muss das Modul \begin_inset Quotes sld -\end_inset +\end_inset ethertap \begin_inset Quotes srd -\end_inset +\end_inset geladen werden. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection tun Device -\layout Standard +\end_layout +\begin_layout Standard Nicht von mir getestet... -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ATM -\layout Standard +\end_layout +\begin_layout Standard 01/2002: ATM wird vom Standard-Kernel nicht, jedoch aber durch die USAGI-Erweite rungen unterstützt. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Sonstige -\layout Standard +\end_layout +\begin_layout Standard Wurde ein Interface vergessen...? -\layout Section +\end_layout +\begin_layout Section Interfaces ein/aus-schalten -\layout Standard +\end_layout +\begin_layout Standard Es gibt zwei Methoden, ein Interface ein- oder auszuschalten. -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Gebrauch: -\layout Code +\end_layout +\begin_layout Code # ip link set dev up -\layout Code +\end_layout +\begin_layout Code # ip link set dev down -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # ip link set dev eth0 up -\layout Code +\end_layout +\begin_layout Code # ip link set dev eth0 down -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Gebrauch: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig up -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig down -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 down -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-address} -\end_inset +\end_inset IPv6 Adressen konfigurieren -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Es gibt verschiedene Methoden zum konfigurieren einer IPv6 Adresse eines Interfaces. Sie können "ifconfig" oder "ip" dazu einsetzen. -\layout Section +\end_layout +\begin_layout Section Bestehende IPv6 Adressen anzeigen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Zuerst sollten sie überprüfen, ob und welche IPv6 Adressen bereits konfiguriert sind (etwa durch automatischer stateless Konfiguration). -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show dev -\layout Standard +\end_layout +\begin_layout Standard Beispiel für einen statisch konfigurierten Host: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show dev eth0 -\layout Code +\end_layout +\begin_layout Code 2: eth0: -\layout Standard +\end_layout +\begin_layout Standard Hier sehen Sie verschiedene IP Adressen mit unterschiedlichen Gültigkeitsbereich en (die Ausgabe wurde mit grep gefiltert) -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 |grep "inet6 addr:" -\layout Code +\end_layout +\begin_layout Code inet6 addr: fe80::210:a4ff:fee3:9566/10 Scope:Link -\layout Code +\end_layout +\begin_layout Code inet6 addr: 3ffe:ffff:0:f101::1/64 Scope:Global -\layout Code +\end_layout +\begin_layout Code inet6 addr: fec0:0:0:f101::1/64 Scope:Site -\layout Section +\end_layout +\begin_layout Section Hinzufügen einer IPv6 Adresse -\layout Standard +\end_layout +\begin_layout Standard Die Vorgehensweise beim hinzufügen einer IPv6 Adresse ist vergleichbar mit dem "IP ALIAS"-Mechanismus bei IPv4 adressierten Interfaces. -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add / dev -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add 3ffe:ffff:0:f101::1/64 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig inet6 add / -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 inet6 add 3ffe:ffff:0:f101::1/64 -\layout Section +\end_layout +\begin_layout Section IPv6 Adressen entfernen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Funktion wird selten benötigt. Vorsicht ist beim entfernen nicht existenter IPv6 Adressen geboten, da ältere Kernel dieses Fehlverhalten manchmal mit einem Crash quittieren. -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr del / dev -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr del 3ffe:ffff:0:f101::1/64 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig inet6 del / -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 inet6 del 3ffe:ffff:0:f101::1/64 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-route} -\end_inset +\end_inset Konfiguration normaler IPv6-Routen -\layout Standard +\end_layout +\begin_layout Standard Wenn Sie Ihren lokalen Link verlassen und Pakete in das weltweite IPv6-Internet versenden wollen, dann benötigen Sie Routing. Wenn sich bereits ein IPv6 fähiger Router an Ihrem Link befindet, dann reicht eventuell das Hinzufügen von IPv6 Routen. -\layout Section +\end_layout +\begin_layout Section Bestehende IPv6-Routen anzeigen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Zuerst sollten sie überprüfen, ob und welche IPv6 Adressen bereits konfiguriert sind (etwa durch automatischer Konfiguration). -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route show [dev ] -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route show dev eth0 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0:f101::/64 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code fe80::/10 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code ff00::/8 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code default proto kernel metric 256 mtu 1500 advmss 1440 -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "route" -\layout Standard -\align left -Anwendung: -\layout Code +\end_layout +\begin_layout Standard +\align left +Anwendung: +\end_layout + +\begin_layout Code # /sbin/route -A inet6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Sie sehen hier mehrere IPv6 Routen mit unterschiedlichen Adressen eines einzelnen Interfaces (bei der Ausgabe wurde das Interface eth0 herausgefiltert). -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 |grep -w "eth0" -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0:f101 ::/64 :: UA 256 0 0 eth0 <- Interface route for global -\layout Code +\end_layout +\begin_layout Code ¬ address -\layout Code +\end_layout +\begin_layout Code fe80::/10 :: UA 256 0 0 eth0 <- Interface route for link-local -\layout Code +\end_layout +\begin_layout Code ¬ address -\layout Code +\end_layout +\begin_layout Code ff00::/8 :: UA 256 0 0 eth0 <- Interface route for all multicast -\layout Code +\end_layout +\begin_layout Code ¬ addresses -\layout Code +\end_layout +\begin_layout Code ::/0 :: UDA 256 0 0 eth0 <- Automatic default route -\layout Section +\end_layout +\begin_layout Section Eine IPv6-Route über ein Gateway hinzufügen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Eine Route wird meistens benötigt, um mit IPv6 die Außenwelt über einen IPv6 fähigen Router und über Ihren Link zu erreichen. -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add / via -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 via 3ffe:ffff:0:f101::1 -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add / gw -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Standard +\end_layout +\begin_layout Standard Die optionale Angabe eines Devices wird dann benötigt, wenn die IPv6 Adresse des Gateways eine lokale Link-Adresse ist. -\layout Standard +\end_layout +\begin_layout Standard Im folgenden Beispiel wird eine Route für alle aktuellen globalen Adressen (2000::/3) über das Gateway -\family typewriter +\family typewriter 3ffe:ffff:0:f101::1 -\family default +\family default hinzugefügt. -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 gw 3ffe:ffff:0:f101::1 -\layout Section +\end_layout +\begin_layout Section Eine IPv6-Route über ein Gateway entfernen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Das manuelle entfernen einer Route wird nicht oft benötigt, meistens wird dies automatisch durch Netzwerk-Konfigurationsscripts beim herunterfahren (des Betriebssystems oder eines Interfaces) bewirkt. -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del / via -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del 2000::/3 via 3ffe:ffff:0:f101::1 -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del / [dev ] -\layout Standard +\end_layout +\begin_layout Standard Beispiel zum entfernen der im obigen Beispiel hinzugefügten Route: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 gw 3ffe:ffff:0:f101::1 -\layout Section +\end_layout +\begin_layout Section Eine IPv6-Route über ein Interface hinzufügen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Funktion wird manchmal im Fall dedizierter Punkt-zu-Punkt Verbindungen verwendet, in der Regel aber eher selten benötigt. -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add / dev -\layout Code +\end_layout +\begin_layout Code ¬ metric 1 -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 dev eth0 metric 1 -\layout Standard +\end_layout +\begin_layout Standard Der Metrik-Wert \begin_inset Quotes sld -\end_inset +\end_inset 1 \begin_inset Quotes srd -\end_inset +\end_inset wird verwendet, um mit dem Metrik Wert von route kompatibel zu sein; der Standard-Metrik-Wert von \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset ist \begin_inset Quotes sld -\end_inset +\end_inset 1024 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add / dev -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 dev eth0 -\layout Section +\end_layout +\begin_layout Section Eine IPv6-Route über ein Interface entfernen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Dies wird manuell nicht so oft benötigt, jedoch aber beim herunterfahren von Konfigurationsscripts benutzt. -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del / dev -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del 2000::/3 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del / dev -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 dev eth0 -\layout Section +\end_layout +\begin_layout Section FAQ für IPv6-Routen -\layout Subsection +\end_layout +\begin_layout Subsection Unterstützung einer IPv6 Default-Route -\layout Standard +\end_layout +\begin_layout Standard Ein Schwerpunkt bei IPv6 ist das hierarchische Routing. Aus diesem Grund werden in Routern nur wenige Routing-Einträge benötigt. -\layout Standard +\end_layout +\begin_layout Standard Einige Punkte sind im aktuellen Kernel zu beachten: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Clients (kein Routing eines Paketes!) -\layout Standard +\end_layout +\begin_layout Standard Ein client kann eine Default Route (z.B. \begin_inset Quotes sld -\end_inset +\end_inset ::/0 \begin_inset Quotes srd -\end_inset +\end_inset ) einrichten, diese aber auch durch automatische Konfiguration, z.B. mit radvd, erlernen: -\layout Code +\end_layout +\begin_layout Code # ip -6 route show | grep ^default -\layout Code +\end_layout +\begin_layout Code default via fe80::212:34ff:fe12:3450 dev eth0 proto kernel metric 1024 expires -\layout Code +\end_layout +\begin_layout Code ¬ 29sec mtu 1500 advmss 1440 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Router & Paketweiterleitung -\layout Standard +\end_layout +\begin_layout Standard Aktuelle Mainstream Linux Kernel ( zumindest <= 2.4.17) unterstützen keine Default Routen. Man kann dies einrichten, aber die Abfrage dieser Route misslingt im Fall, dass ein Paket weitergeleitet werden soll ( normaler Zwecke eines Routers). -\layout Standard +\end_layout +\begin_layout Standard Zurzeit kann aus diesem Grund ein \begin_inset Quotes sld -\end_inset +\end_inset default routing \begin_inset Quotes srd -\end_inset +\end_inset nur eingerichtet werden, wenn hierbei das einzig globale Adress-Präfix \begin_inset Quotes sld -\end_inset +\end_inset 2000::/3 \begin_inset Quotes srd -\end_inset +\end_inset verwendet wird. -\layout Standard +\end_layout +\begin_layout Standard Das USAGI Projekt unterstützt das default routing in ihren Erweiterungen mit einem Hack. -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Walten Sie mit Vorsicht bei der Anwendung von default routing auf exponierten Routern, wenn keine Adressfilterung eingesetzt wird. Andernfalls kann Multicast- oder lokaler Site-Datenverkehr den Router ungewollt verlassen. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-Neighbor-Discovery} -\end_inset +\end_inset Neighbor Discovery -\layout Standard +\end_layout +\begin_layout Standard Die Neighbor Discovery (Ermittlung der Netzwerkumgebung) ist der IPv6 Nachfolger für das ARP (Address Resolution Protocol) bei IPv4. Sie können Informationen über die aktuelle Netzwerkumgebung gewinnen, Einträge erstellen und entfernen. -\layout Standard +\end_layout +\begin_layout Standard Der Kernel merkt sich erfolgreich gelernte \begin_inset Quotes sld -\end_inset +\end_inset Nachbarn \begin_inset Quotes srd -\end_inset +\end_inset (wie ARP in IPv4). Sie können die gelernten Einträge mit \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset einsehen. -\layout Section +\end_layout +\begin_layout Section Netzwerkumgebung mit \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset anzeigen -\layout Standard +\end_layout +\begin_layout Standard Mit dem folgenden Befehl können Sie die gelernten oder konfigurierten IPv6 Nachbarn anzeigen: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh show [dev ] -\layout Standard +\end_layout +\begin_layout Standard Das folgende Beispiel zeigt einen Nachbar, einen erreichbaren Router: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh show -\layout Code +\end_layout +\begin_layout Code fe80::201:23ff:fe45:6789 dev eth0 lladdr 00:01:23:45:67:89 router nud reachable -\layout Section +\end_layout +\begin_layout Section Tabell der Netzwerkumgebung mit \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset editieren -\layout Subsection +\end_layout +\begin_layout Subsection Eintrag manuell hinzufügen -\layout Standard +\end_layout +\begin_layout Standard Mit folgendem Befehl können Sie einen Eintrag manuell hinzufügen: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh add lladdr dev -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh add fec0::1 lladdr 02:01:02:03:04:05 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Eintrag manuell entfernen -\layout Standard +\end_layout +\begin_layout Standard Sie können einen Eintrag auch löschen: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh del lladdr dev -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh del fec0::1 lladdr 02:01:02:03:04:05 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Erweiterte Einstellungen -\layout Standard +\end_layout +\begin_layout Standard Das Tool \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset ist weniger ausführlich dokumentiert, dennoch ist es sehr mächtig. Sehen Sie online mit \begin_inset Quotes sld -\end_inset +\end_inset help \begin_inset Quotes srd -\end_inset +\end_inset für weitere Details: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh help -\layout Code +\end_layout +\begin_layout Code Usage: ip neigh { add | del | change | replace } { ADDR [ lladdr LLADDR ] -\layout Code +\end_layout +\begin_layout Code [ nud { permanent | noarp | stale | reachable } ] -\layout Code +\end_layout +\begin_layout Code | proxy ADDR } [ dev DEV ] -\layout Code +\end_layout +\begin_layout Code ip neigh {show|flush} [ to PREFIX ] [ dev DEV ] [ nud STATE ] -\layout Standard +\end_layout +\begin_layout Standard Es sieht aus, als seien manche Optionen ausschließlich für IPv4 gedacht... Es wird um Ihre Mithilfe gebeten, wenn Sie Informationen zu Optionen und der erweiterten Anwendung beisteuern können. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuring-ipv6-in-ipv4-tunnels} -\end_inset +\end_inset Konfiguration eines IPv6-in-IPv4 Tunnels -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Beim verlassen Ihres Links steht Ihnen kein IPv6 fähiges Netzwerk zur Verfügung. Aus diesem Grund benötigen Sie zum erreichen des weltweiten IPv6 Internet einen IPv6-in-IPv4 Tunnel. -\layout Standard +\end_layout +\begin_layout Standard Es gibt unterschiedliche Tunnel-Mechanismen sowie einige Möglichkeiten zum Einrichten eines Tunnels. -\layout Section +\end_layout +\begin_layout Section Tunnelarten -\layout Standard +\end_layout +\begin_layout Standard Es steht Ihnen mehr als eine Möglichkeit zur Verfügung, IPv6 Pakete über ausschließliche IPv4 Links zu tunneln. -\layout Subsection +\end_layout +\begin_layout Subsection Statische Punkt-zu-Punkt Tunnel: 6bone -\layout Standard +\end_layout +\begin_layout Standard Ein Punkt-zu-Punkt Tunnel ist ein dedizierter Tunnel zu einem Endpunkt, der Kenntnis über das lokale IPv6 Netzwerk (für das Routing zurück...) und die IPv4 Adresse des Tunnel-Endpunktes verfügt. Definition des Punkt-zu-Punkt Tunnels siehe: \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset . Anforderungen: -\layout Itemize +\end_layout +\begin_layout Itemize Die IPv4 Adresse des lokalen Tunnel-Endpunktes muss statisch sein, global eindeutig und vom entfernten Tunnel-Endpunkt aus erreichbar sein. -\layout Itemize +\end_layout +\begin_layout Itemize Sie müssen ein globales IPv6 Präfix zugewiesen bekommen haben (siehe 6bone registry) -\layout Itemize +\end_layout +\begin_layout Itemize Ein entfernter Tunnel-Endpunkt muss dazu in der Lage sein, ihr IPv6 Präfix bis zu Ihrem lokalen Tunnel-Endpunkt zu routen (wobei meistens manuelle Konfiguration notwendig wird). -\layout Subsection +\end_layout +\begin_layout Subsection Automatische Tunnel -\layout Standard +\end_layout +\begin_layout Standard Automatisches Tunneln tritt dann ein, wenn ein Knoten direkt einen anderen Knoten (dessen IPv4-Adresse er zuerst kennen lernen muss) über die IPv4-mapped IPv6-Adresse anspricht. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{tunneling-6to4} -\end_inset +\end_inset 6to4 Tunnel -\layout Standard +\end_layout +\begin_layout Standard 6to4 Tunnel ( \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset ) verwenden einen einfachen Mechanismus zum erstellen eines automatischen Tunnels. @@ -4422,519 +5436,670 @@ Automatisches Tunneln tritt dann ein, wenn ein Knoten direkt einen anderen nnel unterteilt. Ferner zeigt eine spezielle IPv6 Adresse an, dass der Knoten einen 6to4 Tunnel für die Verbindung zum weltweiten IPv6 Netzwerk verwendet. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Erstellen eines 6to4 Präfixes -\layout Standard +\end_layout +\begin_layout Standard Die 6to4 Adresse wird wie folgt definiert (Schema ist dem \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset entnommen): -\layout Code +\end_layout +\begin_layout Code | 3+13 | 32 | 16 | 64 bits | -\layout Code +\end_layout +\begin_layout Code +---+------+-----------+--------+--------------------------------+ -\layout Code +\end_layout +\begin_layout Code | FP+TLA | V4ADDR | SLA ID | Interface ID | -\layout Code +\end_layout +\begin_layout Code | 0x2002 | | | | -\layout Code +\end_layout +\begin_layout Code +---+------+-----------+--------+--------------------------------+ -\layout Standard +\end_layout +\begin_layout Standard FP und TLA zusammen haben den Wert 0x2002. V4ADDR ist die weltweit einmalige IPv4 Adresse des Knoten (in hexadezimaler Notation). Mit dem SLA wird das Subnetz identifiziert (65536 lokale Subnetze sind möglich) und benutzbar, um die lokale Netzwerstruktur abzubilden. -\layout Standard +\end_layout +\begin_layout Standard Für Gateways wird dieser Präfix normalerweise mit dem SLA \begin_inset Quotes sld -\end_inset +\end_inset 0000 \begin_inset Quotes srd -\end_inset +\end_inset definiert und dem 6to4 Tunnel-Interface das Suffix \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset (kann aber auch ein beliebiger mit local-scope sein) zugewiesen. Zu bemerken ist, dass Microsoft Windows als Suffix auch immer die V4ADDR einsetzt. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection 6to4 Tunnel zum Upstream -\layout Standard +\end_layout +\begin_layout Standard Der Knoten muss die Kenntnis darüber haben, an welchen entfernten Tunnel-Endpunk t die in IPv4 Paketen eingeschlossenen IPv6 Pakete gesendet werden sollen. In den \begin_inset Quotes sld -\end_inset +\end_inset Anfängen \begin_inset Quotes srd -\end_inset +\end_inset der 6to4 Tunnel-Anwendung wurden dedizierte Upstream akzeptierende Router definiert. Liste der Router siehe: \begin_inset LatexCommand \url[NSayer's 6to4 information]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Heute können Upstream Router automatisch mittels der anycast Adresse 192.88.99.1 gefunden werden. Routing Protokolle sind für die Verarbeitung im Hintergrund zuständig, siehe \begin_inset LatexCommand \url[RFC 3068 / An Anycast Prefix for 6to4 Relay Routers]{http://www.faqs.org/rfcs/rfc3068.html} -\end_inset +\end_inset für weitere Details. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection 6to4 Tunnel zum Downstream -\layout Standard +\end_layout +\begin_layout Standard Der Downstream (6bone -> Ihr 6to4 fähiger Node) ist nicht wirklich fix, er kann von jenem Host variieren, an dem ursprünglich die Pakete gesendet wurden. Es gibt zwei Möglichkeiten: -\layout Itemize +\end_layout +\begin_layout Itemize Der entfernte Host benutzt 6to4 und sendet die Pakete direkt an den lokalen Knoten zurück (siehe unten). -\layout Itemize +\end_layout +\begin_layout Itemize Der entfernte Host sendet die Pakete zurück an das weltweite IPv6 Netzwerk, und abhängig vom dynamischen Routing, erstellt dann ein Relay-Router automatisc h zum lokalen Knoten einen Tunnel. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Möglicher 6to4 Verkehr -\layout Itemize +\end_layout +\begin_layout Itemize Vom 6to4 zum 6to4: der Tunnel entsteht normalerweise direkt zwischen den beiden 6to4 fähigen Hosts. -\layout Itemize +\end_layout +\begin_layout Itemize Vom 6to4 zum non-6to4: Der Datenstrom wird mittels Upstream-Tunnel versendet. -\layout Itemize +\end_layout +\begin_layout Itemize Vom non-6to4 zum 6to4: Der Datenstrom wird mittels Downstream-Tunnel versendet. -\layout Section +\end_layout +\begin_layout Section Bestehende Tunnel anzeigen -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 tunnel show [] -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 tunnel show -\layout Code +\end_layout +\begin_layout Code sit0: ipv6/ip remote any local any ttl 64 nopmtudisc -\layout Code +\end_layout +\begin_layout Code sit1: ipv6/ip remote 195.226.187.50 local any ttl 64 -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "route" -\layout Standard +\end_layout +\begin_layout Standard Anwendung: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 -\layout Standard +\end_layout +\begin_layout Standard Beispiel (Ausgabe wurde derart gefiltert, dass nur Tunnels über das virtuelle Interface sit0 angezeigt werden): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 | grep " -\backslash +\backslash Wsit0 -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code ::/96 :: U 256 2 0 sit0 -\layout Code +\end_layout +\begin_layout Code 2002::/16 :: UA 256 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code 2000::/3 ::193.113.58.75 UG 1 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code fe80::/10 :: UA 256 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code ff00::/8 :: UA 256 0 0 sit0 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{conf-ipv6-in-ipv4-point-to-point-tunnels} -\end_inset +\end_inset Einrichtung eines Punkt-zu-Punkt Tunnels -\layout Standard +\end_layout +\begin_layout Standard Es gibt drei Methoden ein Punkt-zu-Punkt Tunnel hinzuzufügen bzw. zu entfernen. -\layout Standard +\end_layout +\begin_layout Standard Eine gute Informationsquelle zum Thema Tunnel-Einrichtung mit \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset ist folgender Artikel: \begin_inset LatexCommand \url[Configuring tunnels with iproute2 (article)]{http://www.deepspace6.net/docs/iproute2tunnel-en.html} -\end_inset +\end_inset \lang english ( \begin_inset LatexCommand \url[Spiegel]{http://mirrors.bieringer.de/www.deepspace6.net/docs/iproute2tunnel-en.html} -\end_inset +\end_inset ) \lang ngerman . -\layout Subsection +\end_layout +\begin_layout Subsection Einen Punkt-zu-Punkt Tunnel hinzufügen -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Bei einer kleinen Anzahl von Tunnels ist die Verwendung von \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset zurzeit die Standardmethode. -\layout Standard +\end_layout +\begin_layout Standard Beispiel für das Erstellen eines Tunnel-Devices (das Device wird aber hiermit nicht aktiviert; ebenso muss ein TTL Wert spezifiziert werden, da der Standardw ert 0 ist): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add mode sit ttl remote -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Standard +\end_layout +\begin_layout Standard Anwendung (drei allgemeine Beispiele): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add sit1 mode sit ttl remote -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit1 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit1 metric 1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip tunnel add sit2 mode sit ttl -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit2 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit2 metric 1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip tunnel add sit3 mode sit ttl -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit3 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit3 metric 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung von "ifconfig" und "route" (nicht empfehlenswert) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Methode zum Hinzufügen eines Tunnels wird nicht empfohlen, da Ungereimthei ten auftreten. Es gibt keine Probleme, wenn nur ein Tunnel hinzugefügt wird. Werden hingegen mehrere Tunnel hinzugefügt, dann kann der erste Tunnel nicht einfach deaktiviert werden, wenn die restlichen Tunnel aktiviert bleiben sollen. -\layout Standard +\end_layout +\begin_layout Standard Anwendung (drei allgemeine Beispiele): -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit1 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit2 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit2 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit3 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit3 -\layout Standard +\end_layout +\begin_layout Standard WICHTIG: NICHT VERWENDEN! Mit diesem Setup wird von überall aus dem Internet das "automatische Tunneln" vorbehaltlos aktiviert. Das ist ein unnötiges Risiko. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung allein von "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Sie können einen Tunnel auch im NBMA-Stil (Non Broadcast Multiple Access) einrichten. Bei dieser Vorgehensweise können Sie sehr einfach mehrere Tunnels zugleich einrichten, aber kein Tunnel kann nummeriert werden (und das ist ein kein benötigtes Feature). -\layout Standard +\end_layout +\begin_layout Standard Anwendung (drei allgemeine Beispiele): -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Standard +\end_layout +\begin_layout Standard WICHTIG: NICHT VERWENDEN! Mit diesem Setup wird von überall aus dem Internet das "automatische Tunneln" vorbehaltlos aktiviert. Das ist ein unnötiges Risiko. -\layout Subsection +\end_layout +\begin_layout Subsection Punkt-zu-Punkt Tunnel entfernen -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Funktion wird selten manuell durchgeführt. Skripte verwenden diese Funktion zum sauberen deaktivieren bzw. beim Neustart einer IPv6 Konfiguration. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung von "ip" -\layout Standard +\end_layout +\begin_layout Standard Entfernen eines Tunnel-Devices: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del -\layout Standard +\end_layout +\begin_layout Standard Anwendung (drei allgemeine Beispiele): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del dev sit1 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit1 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip -6 route del dev sit2 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit2 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit2 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip -6 route del dev sit3 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit3 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit3 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung von "ifconfig" und "route" (nicht empfehlenswert, da unbequem) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Nicht nur bei der Erstellung eines Tunnels kommt es zu Ungereimtheiten, sondern auch bei dessen Entfernung. Die Tunnel müssen in umgekehrter Reihenfolge wieder entfernt werden, d.h. der zuletzt erstellte Tunnel muss als Erster entfernt werden... -\layout Standard +\end_layout +\begin_layout Standard Anwendung (drei allgemeine Beispiele): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del dev sit3 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit3 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 del dev sit2 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit2 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 add dev sit1 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit1 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Code +\end_layout -\layout Subsubsection +\begin_layout Code +\end_layout + +\begin_layout Subsubsection Verwendung von "route" -\layout Standard +\end_layout +\begin_layout Standard Die Vorgehensweise ist vergleichbar mit dem löschen einer normalen IPv6 Route. -\layout Standard +\end_layout +\begin_layout Standard Anwendung (drei allgemeine Beispiele): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Subsection +\end_layout +\begin_layout Subsection Nummerierte Punkt-zu-Punkt Tunnel -\layout Standard +\end_layout +\begin_layout Standard Manchmal ist es notwendig, einen Punkt-zu-Punkt Tunnel mit IPv6 Adresse genauso einzurichten, wie heute bei IPv4. Dies ist nur mit der ersten (ifconfig+route - nicht empfehlenswert) sowie @@ -4942,2003 +6107,2454 @@ Manchmal ist es notwendig, einen Punkt-zu-Punkt Tunnel mit IPv6 Adresse Tunnels möglich. Bei diesen Fällen können Sie den Tunnel-Interfaces die IPv6 Adressen, wie im Abschnitt zur Interface-Konfiguration beschrieben, hinzufügen. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{configuring-ipv6to4-tunnels} -\end_inset +\end_inset Einrichtung von 6to4 Tunnel -\layout Standard +\end_layout +\begin_layout Standard Beachten sie Bitte, dass 6to4 Tunnel im Standard-Kernel der Serie 2.2.x (siehe \begin_inset LatexCommand \ref[systemcheck/kernel]{systemcheck-kernel} -\end_inset +\end_inset ) nicht unterstützt werden. Weiter ist zu beachten, dass die Präfix-Länge für 6to4 Adressen 16 ist, da sich aus Perspektive des Netzwerks betrachtet, alle anderen 6to4 Hosts sich in der gleichen Schicht 2 befinden. -\layout Subsection +\end_layout +\begin_layout Subsection 6to4 Tunnel hinzufügen -\layout Standard +\end_layout +\begin_layout Standard Zu Anfang müssen Sie Ihre 6to4 Präfix-Länge mittels der lokal zugewiesenen global routbaren IPv4 Adresse berechnen (sollte ihr Host keine global routebare IPv4 Adresse haben, dann ist unter speziellen Bedingungen NAT auf dem Border Gateway möglich): -\layout Standard +\end_layout +\begin_layout Standard Angenommen, Ihre IPv4 Adresse ist: -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 -\layout Standard +\end_layout +\begin_layout Standard Dann ist das daraus resultierende 6to4 Präfix: -\layout Code +\end_layout +\begin_layout Code 2002:0102:0304:: -\layout Standard +\end_layout +\begin_layout Standard Lokalen 6to4 Gateways sollte immer (ist aber kein Muss, ein beliebiger local-sco pe Suffix kann benutzt werden) das Suffix \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset zugewiesen werden. Daraus resultierend ergibt sich Ihre lokale 6to4 Adresse: -\layout Code +\end_layout +\begin_layout Code 2002:0102:0304::1 -\layout Standard +\end_layout +\begin_layout Standard Zum automatischen Erstellen der Adresse können Sie folgenden Befehl nutzen: -\layout Code +\end_layout +\begin_layout Code ipv4="1.2.3.4"; printf "2002:%02x%02x:%02x%02x::1" `echo $ipv4 | tr "." " "` -\layout Standard +\end_layout +\begin_layout Standard Es gibt nun zwei Möglichkeiten einen 6to4 Tunnel einzurichten. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung von "ip" und einem dedizierten Tunnel-Device -\layout Standard +\end_layout +\begin_layout Standard Die empfohlene Vorgehensweise (der Wert TTL muss angegeben werden, da der Standardwert 0 ist): -\layout Standard +\end_layout +\begin_layout Standard Erstellen eines neues Tunnel-Device: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add tun6to4 mode sit ttl remote any local -\layout Standard +\end_layout +\begin_layout Standard Interface aktivieren: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev tun6to4 up -\layout Standard +\end_layout +\begin_layout Standard Eine lokale 6to4 Adresse am Interface hinzufügen (Hinweis: Präfix-Länge 16 ist wichtig!) -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add /16 dev tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Hinzufügen der (Standard-) Route zum globalen IPv6 Netz unter Verwendung der all-6to4-routers IPv4 anycast Adresse: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 via ::192.88.99.1 dev tun6to4 metric 1 -\layout Standard +\end_layout +\begin_layout Standard \lang english Manche Versionen von \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset (z.B. SuSE Linux 9.0) unterstützen keine IPv4-kompatiblen IPv6-Adressen für Gateways, in diesem Fall muss die entsprechende IPv6-Adresse benutzt werden: -\layout Code +\end_layout +\begin_layout Code \lang english # /sbin/ip -6 route add 2000::/3 via -\series bold +\series bold 2002:c058:6301::1 -\series default +\series default dev tun6to4 metric 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung von "ifconfig" und "route" sowie einem generischen Tunnel-Device "sit0" (nicht empfehlenswert) -\layout Standard +\end_layout +\begin_layout Standard Diese Vorgehensweise wird nicht empfohlen, da bei Verwendung des allgemeinen Tunnel Device sit0 keine Filter-Spezifizierung pro Device ermöglicht wird. -\layout Standard +\end_layout +\begin_layout Standard Das allgemeine Tunnel Interface sit0 aktivieren: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Standard +\end_layout +\begin_layout Standard Dem Interface eine lokale 6to4 Adresse hinzufügen: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 add /16 -\layout Standard +\end_layout +\begin_layout Standard Hinzufügen der (Standard-) Route zum globalen IPv6 Netz unter Verwendung der all-6to4-routers IPv4 anycast Adresse: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 gw ::192.88.99.1 dev sit0 -\layout Subsection +\end_layout +\begin_layout Subsection 6to4 Tunnel entfernen -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung von "ip" und einem dedizierten Tunnel-Device -\layout Standard +\end_layout +\begin_layout Standard Entfernen aller Routen über dieses bestimmten Tunnel Devices: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route flush dev tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Interface deaktivieren: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev tun6to4 down -\layout Standard +\end_layout +\begin_layout Standard Ein erstelltes Tunnel Device entfernen: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del tun6to4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwendung von "ifconfig" und "route" sowie einem generischen Tunnel-Device "sit0" (nicht empfehlenswert) -\layout Standard +\end_layout +\begin_layout Standard Entfernen der (Standard-) Route über ein 6to4 Tunnel Device: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 gw ::192.88.99.1 dev sit0 -\layout Standard +\end_layout +\begin_layout Standard Eine 6to4 Adresse des Interfaces entfernen: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 del /16 -\layout Standard +\end_layout +\begin_layout Standard Ein allgemeines Tunnel Device deaktivieren (aber Achtung, eventuell ist das Interface noch in Verwendung...) -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuring-ipv4-in-ipv6-tunnels} -\end_inset +\end_inset IPv4-in-IPv6 Tunnel konfigurieren -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Diese Tunnel-Art wird derzeit vorwiegend in Test-Umgebungen verwendet. Das Kapitel ist aus diesem Grund noch leer. \lang english Allerdings scheint die Unterstützung for Linux momentan noch zu fehlen (03/2004). -\layout Standard +\end_layout +\begin_layout Standard In der Zwischenzeit finden Sie hier mehr Informationen: \begin_inset LatexCommand \url[RFC 2473 / Generic Packet Tunneling in IPv6 Specification]{http://www.faqs.org/rfcs/rfc2473.html} -\end_inset +\end_inset -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-kernel-settings} -\end_inset +\end_inset Kernel-Einstellungen im /proc-Dateisystem -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \label{proc-filesystem} -\end_inset +\end_inset Anmerkung: Dieses Kapitel basiert großteils auf der Datei \begin_inset Quotes sld -\end_inset +\end_inset ip-sysctl.txt \begin_inset Quotes srd -\end_inset +\end_inset , welche in den aktuellen Kernel-Quellen im Verzeichnis \begin_inset Quotes sld -\end_inset +\end_inset Documentation/networking \begin_inset Quotes srd -\end_inset +\end_inset zu finden ist. Danke an dieser Stelle an Pekka Savola, der den IPv6 relevanten Inhalt dieser Datei wartet und betreut. Ebenso sei erwähnt, dass einige Textstellen hieraus mehr oder weniger mit Copy & Paste in dieses Dokument übernommen wurden. -\layout Section +\end_layout +\begin_layout Section Zugriff auf das /proc-Dateisystem -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "cat" und "echo" -\layout Standard +\end_layout +\begin_layout Standard Mit \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset und \begin_inset Quotes sld -\end_inset +\end_inset echo \begin_inset Quotes srd -\end_inset +\end_inset können Sie am einfachsten das /proc Dateisystem einsehen. Hierfür gibt es aber einige Voraussetzungen, die erfüllt sein müssen: -\layout Itemize +\end_layout +\begin_layout Itemize Das /proc-Dateisystem muss im Kernel aktiviert sein. Hierfür muss die folgende Einstellung beim kompilieren des Kernels vorgenommen werden: -\layout Code +\end_layout +\begin_layout Code CONFIG_PROC_FS=y -\layout Itemize +\end_layout +\begin_layout Itemize Das /proc-Dateisystem muss zuerst gemountet sein. Dies kann wie folgt getestet werden: -\layout Code +\end_layout +\begin_layout Code # mount | grep "type proc" -\layout Code +\end_layout +\begin_layout Code none on /proc type proc (rw) -\layout Itemize +\end_layout +\begin_layout Itemize Sie benötigen Lese- und manchmal auch Schreib-Zugriff (normalerweise nur als Root-Benutzer) auf das /proc-Dateisystem. -\layout Standard +\end_layout +\begin_layout Standard Normalerweise sind, mit Ausnahme in /proc/sys/*, alle Einträge ausschließlich mit Leserechten ausgestattet. Die Einträge werden zum Zweck der Informationsgewinnung verwendet. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Wert anzeigen -\layout Standard +\end_layout +\begin_layout Standard Den Inhalt eines Eintrags können sie mit \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset anzeigen: -\layout Code +\end_layout +\begin_layout Code # cat /proc/sys/net/ipv6/conf/all/forwarding -\layout Code +\end_layout +\begin_layout Code 0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Wert einstellen -\layout Standard +\end_layout +\begin_layout Standard Mit \begin_inset Quotes sld -\end_inset +\end_inset echo \begin_inset Quotes srd -\end_inset +\end_inset können sie einen neuen Wert zuweisen (nur wenn der Eintrag beschreibbar ist): -\layout Code +\end_layout +\begin_layout Code # echo "1" >/proc/sys/net/ipv6/conf/all/forwarding -\layout Subsection +\end_layout +\begin_layout Subsection Verwendung von "sysctl" -\layout Standard +\end_layout +\begin_layout Standard Die Verwendung des Programms \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset ist eine zeitgemäße Methode zum Anzeigen der Kernel-Switches. Es funktioniert auch dann, wenn das /proc-Dateisystem nicht gemountet ist, wobei aber nur ein Zugriff auf /proc/sys/* möglich ist! -\layout Standard +\end_layout +\begin_layout Standard Das Programm \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset ist (auf Red Hat Linux Systemen) im Paket \begin_inset Quotes sld -\end_inset +\end_inset procps \begin_inset Quotes srd -\end_inset +\end_inset enthalten. -\layout Itemize +\end_layout +\begin_layout Itemize Das sysctl-Interface muss im Kernel aktiviert sein. Hierfür muss die folgende Einstellung beim kompilieren des Kernels vorgenommen werden: -\layout Code +\end_layout +\begin_layout Code CONFIG_SYSCTL=y -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Wert anzeigen -\layout Standard +\end_layout +\begin_layout Standard Der Wert eines Eintrags kann nun angezeigt werden: -\layout Code +\end_layout +\begin_layout Code # sysctl net.ipv6.conf.all.forwarding -\layout Code +\end_layout +\begin_layout Code net.ipv6.conf.all.forwarding = 0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Wert einstellen -\layout Standard +\end_layout +\begin_layout Standard Ein neuer Wert kann wie folgt zugewiesen werden (wenn der Eintrag beschreibbar ist): -\layout Code +\end_layout +\begin_layout Code # sysctl -w net.ipv6.conf.all.forwarding=1 -\layout Code +\end_layout +\begin_layout Code net.ipv6.conf.all.forwarding = 1 -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Verwenden Sie beim setzen eines Wertes keine Leerzeichen vor oder nach dem \begin_inset Quotes sld -\end_inset +\end_inset = \begin_inset Quotes srd -\end_inset +\end_inset . Sollten Sie mehrere Werte in einer Zeile angeben, müssen sie diese mit Anführungszeichen umgeben: -\layout Code +\end_layout +\begin_layout Code # sysctl -w net.ipv4.ip_local_port_range= -\series bold +\series bold " -\series default +\series default 32768 61000 -\series bold +\series bold " -\layout Code +\end_layout +\begin_layout Code net.ipv4.ip_local_port_range = 32768 61000 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Sonstiges -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Es gibt sysctl-Versionen im Umlauf, die anstelle des Punktes \begin_inset Quotes sld -\end_inset +\end_inset . \begin_inset Quotes srd -\end_inset +\end_inset einen slash \begin_inset Quotes sld -\end_inset +\end_inset / \begin_inset Quotes srd -\end_inset +\end_inset ausgeben. -\layout Standard +\end_layout +\begin_layout Standard Für weitere Details siehe die manpage von sysctl. -\layout Standard +\end_layout +\begin_layout Standard Hinweise: Um schnell einen Überblick über die Einstellungen zu bekommen, verwenden Sie einfach die Option \begin_inset Quotes sld -\end_inset +\end_inset -a \begin_inset Quotes srd -\end_inset +\end_inset (anzeigen aller Einträge) sowie das Tool \begin_inset Quotes sld -\end_inset +\end_inset grep \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Werte im /proc-Dateisystem -\layout Standard +\end_layout +\begin_layout Standard Es gibt im /proc-Dateisystem unterschiedliche Formate: -\layout Itemize +\end_layout +\begin_layout Itemize BOOLEAN: einfach eine \begin_inset Quotes sld -\end_inset +\end_inset 0 \begin_inset Quotes srd -\end_inset +\end_inset (falsch) oder eine \begin_inset Quotes sld -\end_inset +\end_inset 1 \begin_inset Quotes srd -\end_inset +\end_inset (wahr) -\layout Itemize +\end_layout +\begin_layout Itemize INTEGER: Wert ist eine Ganzzahl (kann auch eine unsigned int sein) -\layout Itemize +\end_layout +\begin_layout Itemize Kompliziertere Zeilen mit verschiedenen Werten: manchmal wir eine Header-Zeile mit angezeigt... Sie können aber auch weitere Informationen zu den Werten und deren Bedeutung direkt in den Kernel Quellen beziehen. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-sys-net-ipv6} -\end_inset +\end_inset Einträge in /proc/sys/net/ipv6/ -\layout Subsection +\end_layout +\begin_layout Subsection conf/default/* -\layout Standard +\end_layout +\begin_layout Standard Ändern der Interface-spezifischen Einstellungen. -\layout Subsection +\end_layout +\begin_layout Subsection conf/all/* -\layout Standard +\end_layout +\begin_layout Standard Ändern aller Interface-spezifischen Einstellungen. -\layout Standard +\end_layout +\begin_layout Standard Ausnahme: \begin_inset Quotes sld -\end_inset +\end_inset conf/all/forwarding \begin_inset Quotes srd -\end_inset +\end_inset hat hier eine andere Bedeutung: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection conf/all/forwarding -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Standard +\end_layout +\begin_layout Standard Hiermit wird die globale IPv6 Weiterleitung zwischen allen Interfaces aktiviert. -\layout Standard +\end_layout +\begin_layout Standard In IPv6 ist kein forwarding per Device möglich. Die Steuerung der Weiterleitung muss mittels IPv6-netfilter Regel-Sets (mit dem Programm ip6tables) und der Bestimmung der Ein- und Ausgabe-Devices (siehe \begin_inset LatexCommand \ref[Firewalling/Netfilter6]{firewalling-netfilter6} -\end_inset +\end_inset für Details) vollzogen werden. In IPv4 ist das anders, forwarding per device ist hier möglich (hier wird am Interface, wo das Paket einlangt, die entsprechende Entscheidung getroffen). -\layout Standard +\end_layout +\begin_layout Standard Hiermit werden die Host/Router Einstellungen 'forwarding' aller Interfaces eingestellt (auch globales Forwarding genannt). Für weitere Details Siehe unten. -\layout Standard +\end_layout +\begin_layout Standard Ist der Wert gleich 0, dann ist IPv6 forwarding deaktiviert. Pakete verlassen in diesem Fall niemals ein anderes Interface (weder physikalis che noch logische wie z.B. Tunnel). -\layout Subsection +\end_layout +\begin_layout Subsection conf/interface/* -\layout Standard +\end_layout +\begin_layout Standard Spezielle Einstellungen per Interface ändern. -\layout Standard +\end_layout +\begin_layout Standard Das funktionale Verhalten einzelner Einstellungen ist davon abhängig, ob lokales forwarding aktiviert ist oder nicht. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection accept_ra -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Itemize +\end_layout +\begin_layout Itemize Standardeinstellung: aktiviert, wenn lokales forwarding deaktiviert ist. Deaktiviert, wenn lokales forwarding aktiviert ist. -\layout Standard +\end_layout +\begin_layout Standard Router Advertisements werden akzeptiert; das Interface wird mit Status 'received data' automatisch konfiguriert. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection accept_redirects -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Itemize +\end_layout +\begin_layout Itemize · Standardeinstellung: aktiviert, wenn lokales forwarding deaktiviert ist. Deaktiviert, wenn lokales forwarding aktiviert ist. -\layout Standard +\end_layout +\begin_layout Standard Akzeptiert von IPv6 Router gesendete Redirects. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection autoconf -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: WAHR -\layout Standard +\end_layout +\begin_layout Standard Link-lokale Adressen (s.a. \begin_inset LatexCommand \ref[Address-Typen]{chapter-addresstypes} -\end_inset +\end_inset ) mit L2 Hardware-Adressen konfigurieren. Es wird z.B. am Interface eine Adresse wie \begin_inset Quotes sld -\end_inset +\end_inset fe80::210:23ff:fe45:6789 \begin_inset Quotes srd -\end_inset +\end_inset mit einer L2-MAC-Adresse automatisch erstellt. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dad_transmits -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 1 -\layout Standard +\end_layout +\begin_layout Standard Die Anzahl der gesendeten Proben zum entdecken von Adress-Duplikaten. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection forwarding -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: FALSCH, wenn globale forwarding deaktiviert ist (Standard), ansonst WAHR -\layout Standard +\end_layout +\begin_layout Standard Konfigurieren von Interface-spezifischem Host/Router-Verhalten. -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Es wird die gleiche Konfiguration für alle Interfaces empfohlen; Gemischte Host/Router-Szenarios sind eher unüblich. -\layout Itemize +\end_layout +\begin_layout Itemize Wert FALSCH: Per Standard wird von einem Host-Verhalten ausgegangen. Das bedeutet: -\layout Enumerate +\end_layout +\begin_layout Enumerate Der Schalter IsRouter ist bei Router Advertisements nicht aktiviert. -\layout Enumerate +\end_layout +\begin_layout Enumerate Router-Anfragen werden bei Bedarf gesendet. -\layout Enumerate +\end_layout +\begin_layout Enumerate Wenn accept_ra WAHR ist (Standard), dann werden Router Advertisements akzeptiert (und starte die automatische Konfiguration). -\layout Enumerate +\end_layout +\begin_layout Enumerate Wenn accept_redirects WAHR ist (Standard), dann akzeptiere Redirects. -\layout Itemize +\end_layout +\begin_layout Itemize Wert WAHR: Ist lokales forwarding eingeschaltet, dann wird von einem Router-Verh alten ausgegangen. Das bedeutet genau das Gegenteil zu oben: -\layout Enumerate +\end_layout +\begin_layout Enumerate Der Schalter IsRouter ist bei Router Advertisements aktiviert. -\layout Enumerate +\end_layout +\begin_layout Enumerate Router-Anfragen werden nicht gesendet. -\layout Enumerate +\end_layout +\begin_layout Enumerate Router Advertisements werden ignoriert. -\layout Enumerate +\end_layout +\begin_layout Enumerate Redirects werden ignoriert. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection hop_limit -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 64 -\layout Standard +\end_layout +\begin_layout Standard Der Standardwert für das Hop-Limit wird hiermit eingestellt. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mtu -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 1280 (Minimumwert in IPv6) -\layout Standard +\end_layout +\begin_layout Standard Der Standardwert für die Maximum Transfer Unit wird hiermit eingestellt. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitation_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 1 -\layout Standard +\end_layout +\begin_layout Standard Die Anzahl der nach der Aktivierung eines Interfaces zu wartenden Sekunden bevor Router-Anfragen gesendet werden. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitation_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 4 -\layout Standard +\end_layout +\begin_layout Standard Die Anzahl der Sekunden zwischen Router-Anfragen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitations -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 3 -\layout Standard +\end_layout +\begin_layout Standard Die Anzahl der Router-Anfragen, bevor angenommen wird, dass keine Router verfügbar sind. -\layout Subsection +\end_layout +\begin_layout Subsection neigh/default/* -\layout Standard +\end_layout +\begin_layout Standard Standardeinstellungen der Neighbor-Erkennung und einige spezielle globale Intervall- sowie Threshold-Werte ändern: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh1 -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 128 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh2 -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 512 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh3 -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 1024 -\layout Standard +\end_layout +\begin_layout Standard Parameter zum Einstellen der Größe der Neighbour-Tabelle. -\layout Standard +\end_layout +\begin_layout Standard Wenn Sie viele Interfaces und Probleme mit inkorrekt oder nicht funktionierenden Routen haben, dann sollten Sie diesen Wert erhöhen. Ebenfalls erhöhen sollten Sie den Wert, wenn von einem aktiven \begin_inset LatexCommand \url[Zebra (routing daemon)]{http://www.zebra.org/} -\end_inset +\end_inset Folgendes angezeigt wird: -\layout Code +\end_layout +\begin_layout Code ZEBRA: netlink-listen error: No buffer space available, type=RTM_NEWROUTE(24), seq=426, pid=0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 30 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsection +\end_layout +\begin_layout Subsection neigh/interface/* -\layout Standard +\end_layout +\begin_layout Standard Per Interface ändern spezieller Einstellungen zur Neighbor-Erkennung. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection anycast_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 100 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_stale_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 60 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection proxy_qlen -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 64 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection unres_qlen -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 3 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection app_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 0 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection locktime -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 0 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection retrans_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 100 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection base_reachable_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 30 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mcast_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 3 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ucast_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 3 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection delay_first_probe_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 5 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection proxy_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 80 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsection +\end_layout +\begin_layout Subsection route/* -\layout Standard +\end_layout +\begin_layout Standard Globale Routing-Einstellungen ändern. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection flush -\layout Standard +\end_layout +\begin_layout Standard In neueren Kernel-Versionen wurde diese Option entfernt - mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 30 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 1024 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mtu_expires -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 600 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_elasticity -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 0 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_min_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 5 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_timeout -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 60 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection min_adv_mss -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 12 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection max_size -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Standardwert: 4096 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-sys-net-ipv4} -\end_inset +\end_inset IPv6 relevante Einträge in /proc/sys/net/ipv4/ -\layout Standard +\end_layout +\begin_layout Standard Zurzeit werden einige Schalter auch bei IPv6 eingesetzt (Dies bleibt so, bis IPv4 zur Gänze in ein unabhängiges Kernel-Modul umgewandelt wurde). -\layout Subsection +\end_layout +\begin_layout Subsection ip_* -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ip_local_port_range -\layout Standard +\end_layout +\begin_layout Standard Diese Kontrolleinstellung wird ebenfalls bei IPv6 verwendet. -\layout Subsection +\end_layout +\begin_layout Subsection tcp_* -\layout Standard +\end_layout +\begin_layout Standard Diese Kontrolleinstellungen werden ebenfalls bei IPv6 verwendet. -\layout Subsection +\end_layout +\begin_layout Subsection icmp_* -\layout Standard +\end_layout +\begin_layout Standard Diese Kontrolleinstellungen werden bei IPv6 nicht verwendet. Zum aktivieren der ICMPv6 Quoten-Limitierung (auf Grund der ICMPv6 storms Auswirkungen sehr empfohlen) müssen netfilter-v6-Regeln eingesetzt werden. -\layout Subsection +\end_layout +\begin_layout Subsection Sonstige Einträge -\layout Standard +\end_layout +\begin_layout Standard Keine bekannt, bzw. von IPv6 vermutlich ungenutzt. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-net} -\end_inset +\end_inset IPv6 relevante Einträge in /proc/net/ -\layout Standard +\end_layout +\begin_layout Standard In /proc/net gibt es einige Einträge die ausschließlich Lese-Rechte besitzen. Mit \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset können Sie hier keine Informationen bekommen, verwenden Sie anstelle dessen z.B. \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection if_inet6 -\layout Itemize +\end_layout +\begin_layout Itemize Typ: Eine Zeile pro Adresse mit jeweils mehreren Werten -\layout Standard +\end_layout +\begin_layout Standard Alle konfigurierten IPv6 Adressen werden hier in einem speziellen Format angezeigt. Im Beispiel wird ein Loopback-Interface angezeigt. Die Werte werden unten erklärt (siehe \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/addrconf.c \begin_inset Quotes srd -\end_inset +\end_inset für Details). -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/if_inet6 -\layout Code +\end_layout +\begin_layout Code 00000000000000000000000000000001 01 80 10 80 lo -\layout Code +\end_layout +\begin_layout Code +------------------------------+ ++ ++ ++ ++ ++ -\layout Code +\end_layout +\begin_layout Code | | | | | | -\layout Code +\end_layout +\begin_layout Code 1 2 3 4 5 6 -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 Adresse mit 32 hexadezimalen Zeichen ohne Doppelpunkte als Trennzeichen -\layout Enumerate +\end_layout +\begin_layout Enumerate Netlink Device Nummer (Interface Index) im hexadezimalen Format (siehe auch \begin_inset Quotes sld -\end_inset +\end_inset ip addr \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Enumerate +\end_layout +\begin_layout Enumerate Präfix-Länge in hexadezimaler Notation -\layout Enumerate +\end_layout +\begin_layout Enumerate Wert des Gültigkeitsbereichs (s.a. Kernel Quellen \begin_inset Quotes sld -\end_inset +\end_inset include/net/ipv6.h \begin_inset Quotes srd -\end_inset +\end_inset und \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/addrconf.c \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Enumerate +\end_layout +\begin_layout Enumerate Interface flags (s.a. \begin_inset Quotes sld -\end_inset +\end_inset include/linux/rtnetlink.h \begin_inset Quotes srd -\end_inset +\end_inset und \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/addrconf.c \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Enumerate +\end_layout +\begin_layout Enumerate Devicename -\layout Subsection +\end_layout +\begin_layout Subsection ipv6_route -\layout Itemize +\end_layout +\begin_layout Itemize Typ: Eine Zeile pro Route mit jeweils mehreren Werten -\layout Standard +\end_layout +\begin_layout Standard Alle konfigurierten IPv6 Routen werden hier in einem speziellen Format angezeigt. Im Beispiel wird ein Loopback-Interface angezeigt. Die Werte werden unten erklärt (siehe \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/route.c \begin_inset Quotes srd -\end_inset +\end_inset für Details). -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/ipv6_route -\layout Code +\end_layout +\begin_layout Code 00000000000000000000000000000000 00 00000000000000000000000000000000 00 -\layout Code +\end_layout +\begin_layout Code +------------------------------+ ++ +------------------------------+ ++ -\layout Code +\end_layout +\begin_layout Code | | | | -\layout Code +\end_layout +\begin_layout Code 1 2 3 4 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code ¬ 00000000000000000000000000000000 ffffffff 00000001 00000001 00200200 lo -\layout Code +\end_layout +\begin_layout Code ¬ +------------------------------+ +------+ +------+ +------+ +------+ ++ -\layout Code +\end_layout +\begin_layout Code ¬ | | | | | | -\layout Code +\end_layout +\begin_layout Code ¬ 5 6 7 8 9 10 -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 Zielnetzwerk mit 32 hexadezimalen Zeichen ohne Doppelpunkte als Trennzeiche n -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 Ziel-Präfix-Länge in hexadezimaler Notation -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 Ursprungsnetzwerk mit 32 hexadezimalen Zeichen ohne Doppelpunkte als Trennzeichen -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 Ursprungs-Präfix-Länge in hexadezimaler Notation -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 next Hop mit 32 hexadezimalen Zeichen ohne Doppelpunkte als Trennzeichen -\layout Enumerate +\end_layout +\begin_layout Enumerate Metrik in hexadezimaler Schreibweise -\layout Enumerate +\end_layout +\begin_layout Enumerate Reference Counter -\layout Enumerate +\end_layout +\begin_layout Enumerate Use Counter -\layout Enumerate +\end_layout +\begin_layout Enumerate Flags -\layout Enumerate +\end_layout +\begin_layout Enumerate Devicename -\layout Subsection +\end_layout +\begin_layout Subsection sockstat6 -\layout Itemize +\end_layout +\begin_layout Itemize Typ: Eine Zeile pro Protokoll mit Beschreibung und Wert -\layout Standard +\end_layout +\begin_layout Standard Statistiken über verwendete IPv6 Sockets. Beispiel: -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/sockstat6 -\layout Code +\end_layout +\begin_layout Code TCP6: inuse 7 -\layout Code +\end_layout +\begin_layout Code UDP6: inuse 2 -\layout Code +\end_layout +\begin_layout Code RAW6: inuse 1 -\layout Code +\end_layout +\begin_layout Code FRAG6: inuse 0 memory 0 -\layout Subsection +\end_layout +\begin_layout Subsection tcp6 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsection +\end_layout +\begin_layout Subsection udp6 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsection +\end_layout +\begin_layout Subsection igmp6 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsection +\end_layout +\begin_layout Subsection raw6 -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsection +\end_layout +\begin_layout Subsection ip6_flowlabel -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsection +\end_layout +\begin_layout Subsection rt6_stats -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Subsection +\end_layout +\begin_layout Subsection snmp6 -\layout Itemize +\end_layout +\begin_layout Itemize Typ: Eine Zeile pro SNMP Beschreibung und Wert -\layout Standard +\end_layout +\begin_layout Standard SNMP Statistiken; diese können mittels snmp server und entsprechender MIB Tabelle mit einer Network Management Software gewonnen werden. -\layout Subsection +\end_layout +\begin_layout Subsection ip6_tables_names -\layout Standard +\end_layout +\begin_layout Standard Verfügbare netfilter6 Tabellen -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{netlink} -\end_inset +\end_inset Netlink-Interface zum Kernel -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen... der Autor hat hiermit keine Erfahrung... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{network-debugging} -\end_inset +\end_inset Netzwerk-Fehlersuche -\layout Section +\end_layout +\begin_layout Section Server Socket-Anbindung -\layout Subsection +\end_layout +\begin_layout Subsection Überprüfung der Server Socket-Anbindung mit \begin_inset Quotes sld -\end_inset +\end_inset netstat \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Es ist immer von Interesse welche Sockets eines Knotens gerade aktiv sind. Mit \begin_inset Quotes sld -\end_inset +\end_inset netstat \begin_inset Quotes srd -\end_inset +\end_inset können Sie die betreffenden Informationen abfragen: -\layout Standard +\end_layout +\begin_layout Standard Verwendete Optionen: -nlptu -\layout Standard +\end_layout +\begin_layout Standard Beispiel: -\layout Code +\end_layout +\begin_layout Code # netstat -nlptu -\layout Code +\end_layout +\begin_layout Code Active Internet connections (only servers) -\layout Code +\end_layout +\begin_layout Code Proto Recv-Q Send-Q Local Address Foreign Address State -\layout Code +\end_layout +\begin_layout Code ¬ PID/Program name -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:32768 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1258/rpc.statd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1502/rpc.mountd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:515 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 22433/lpd Waiting -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:139 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1746/smbd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1230/portmap -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 3551/X -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:8081 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 18735/junkbuster -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:3128 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:1.2.3.1:993 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::13 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:1.2.3.1:143 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::53 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::22 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1410/sshd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::6010 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 13237/sshd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32768 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1258/rpc.statd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:2049 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ - -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32770 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1502/rpc.mountd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32771 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ - -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:137 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:137 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:138 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:138 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:33044 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:53 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 127.0.0.1:53 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:67 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1530/dhcpd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:67 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1530/dhcpd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32858 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:4827 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:111 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1230/portmap -\layout Code +\end_layout +\begin_layout Code udp 0 0 :::53 :::* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{examples-tcpdump} -\end_inset +\end_inset tcpdump-Beispiele -\layout Standard +\end_layout +\begin_layout Standard Hier folgen einige Beispiele von (mit tcpdump) aufgezeichneten Paketen, die hoffentlich bei Ihrer Fehlersuche nützlich sein können. -\layout Standard +\end_layout +\begin_layout Standard ... mehr Beispiele in den nächsten Versionen... -\layout Subsection +\end_layout +\begin_layout Subsection Router-Erkennung -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Router Advertisement -\layout Code +\end_layout +\begin_layout Code 15:43:49.484751 fe80::212:34ff:fe12:3450 > ff02::1: icmp6: router -\layout Code +\end_layout +\begin_layout Code ¬ advertisement(chlim=64, router_ltime=30, reachable_time=0, -\layout Code +\end_layout +\begin_layout Code ¬ retrans_time=0)(prefix info: AR valid_ltime=30, preffered_ltime=20, -\layout Code +\end_layout +\begin_layout Code ¬ prefix=2002:0102:0304:1::/64)(prefix info: LAR valid_ltime=2592000, -\layout Code +\end_layout +\begin_layout Code ¬ preffered_ltime=604800, prefix=3ffe:ffff:0:1::/64)(src lladdr: -\layout Code +\end_layout +\begin_layout Code ¬ 0:12:34:12:34:50) (len 88, hlim 255) -\layout Standard +\end_layout +\begin_layout Standard Der Router mit der link-lokalen Adresse \begin_inset Quotes sld -\end_inset +\end_inset fe80::212:34ff:fe12:3450 \begin_inset Quotes srd -\end_inset +\end_inset sendet eine Ankündigung mit zwei Präfixes \begin_inset Quotes sld -\end_inset +\end_inset 2002:0102:0304:1::/64 \begin_inset Quotes srd -\end_inset +\end_inset (Lebensdauer 30s) und \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1::/64 \begin_inset Quotes srd -\end_inset +\end_inset (Lebensdauer 2592000s) sowie der eigenen Schicht 2 MAC Adresse \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:50 \begin_inset Quotes srd -\end_inset +\end_inset an die all-node-on-link Multicast Adresse \begin_inset Quotes sld -\end_inset +\end_inset ff02::1 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Router Anfrage -\layout Code +\end_layout +\begin_layout Code 15:44:21.152646 fe80::212:34ff:fe12:3456 > ff02::2: icmp6: router solicitation -\layout Code +\end_layout +\begin_layout Code ¬ (src lladdr: 0:12:34:12:34:56) (len 16, hlim 255) -\layout Standard +\end_layout +\begin_layout Standard Der Knoten mit der link-lokalen Adresse \begin_inset Quotes sld -\end_inset +\end_inset fe80:212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset und der Schicht 2 MAC Adresse \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:56 \begin_inset Quotes srd -\end_inset +\end_inset sucht nach einem Router und sendet hierfür diese Anfrage an die all-router-on-l ink Multicast Adresse \begin_inset Quotes sld -\end_inset +\end_inset ff02::2 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Neighbor-Erkennung -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Neighbor discovery solicitation zur Entdeckung doppelter Adressen -\layout Standard +\end_layout +\begin_layout Standard Folgende Pakete werden vom Knoten mit der Schicht 2 MAC Adresse \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:56 \begin_inset Quotes srd -\end_inset +\end_inset während der automatischen Konfiguration an die solicited-node link-lokale Multicast Adresse gesendet. Es wird überprüft, ob eine potentielle Adresse bereits von einem anderen Knoten am Link verwendet wird. -\layout Itemize +\end_layout +\begin_layout Itemize Der Knoten will seine link-lokale Adresse \begin_inset Quotes sld -\end_inset +\end_inset fe80:212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset konfigurieren und überprüft auf Duplikate -\layout Code +\end_layout +\begin_layout Code 15:44:17.712338 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ fe80::212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Der Knoten will seine globale Adresse \begin_inset Quotes sld -\end_inset +\end_inset 2002:0102:0304:1:212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset konfigurieren (nach Empfang eines Advertisements wie weiter oben abgebildet) und überprüft auf Duplikate -\layout Code +\end_layout +\begin_layout Code 15:44:21.905596 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ 2002:0102:0304:1:212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, -\layout Code +\end_layout +\begin_layout Code ¬ hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Der Knoten will seine globale Adresse \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1:212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset konfigurieren (nach Empfang eines Advertisements wie weiter oben abgebildet) und überprüft auf Duplikate -\layout Code +\end_layout +\begin_layout Code 15:44:22.304028 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:0:1:212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, hlim -\layout Code +\end_layout +\begin_layout Code ¬ 255) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Neighbor discovery solicitation zur Host oder Gateway-Suche -\layout Itemize +\end_layout +\begin_layout Itemize Der Knoten möchte Pakete an die Adresse \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1::10 \begin_inset Quotes srd -\end_inset +\end_inset senden, hat hierfür aber keine Schicht 2 MAC Adresse und sendet aus diesem Grund zuerst eine Anfrage -\layout Code +\end_layout +\begin_layout Code 13:07:47.664538 2002:0102:0304:1:2e0:18ff:fe90:9205 > ff02::1:ff00:10: icmp6: -\layout Code +\end_layout +\begin_layout Code ¬ neighbor sol: who has 3ffe:ffff:0:1::10(src lladdr: 0:e0:18:90:92:5) (len 32, -\layout Code +\end_layout +\begin_layout Code ¬ hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Der Knoten sucht nun nach der Adresse \begin_inset Quotes sld -\end_inset +\end_inset fe80::10 \begin_inset Quotes srd -\end_inset +\end_inset -\layout Code +\end_layout +\begin_layout Code 13:11:20.870070 fe80::2e0:18ff:fe90:9205 > ff02::1:ff00:10: icmp6: neighbor -\layout Code +\end_layout +\begin_layout Code ¬ sol: who has fe80::10(src lladdr: 0:e0:18:90:92:5) (len 32, hlim 255) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-support-persistent-configuration} -\end_inset +\end_inset Unterstützung einer ständigen IPv6-Konfiguration in Linux Distributionen -\layout Standard +\end_layout +\begin_layout Standard Einige Linux-Distributionen unterstützen bereits eine permanente IPv6 Konfigurat ion. Hierbei werden sowohl bestehende oder als auch neue Konfiguration- und Skriptdateien verwendet sowie tlw. IPv4 Skripte abgeändert. -\layout Section +\end_layout +\begin_layout Section Red Hat Linux und \begin_inset Quotes sld -\end_inset +\end_inset Klone \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Seitdem der Autor begann das \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset zu schreiben, war es seine Absicht eine permanente IPv6 Konfiguration zu ermöglichen, wobei die gebräuchlichsten Anwendungsszenarien wie Host-only, @@ -6954,12 +8570,12 @@ Seitdem der Autor begann das \begin_inset LatexCommand \url[initscripts-ipv6 homepage]{http://www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Spiegel]{http://mirrors.bieringer.de/www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ) \lang ngerman @@ -6970,82 +8586,95 @@ Seitdem der Autor begann das Distributionen gedacht. Es war ebenfalls sehr einfach bestehende Konfigurationsdateien zu erweitern, neue zu erstellen und den Start des IPv6 Setup in das IPv4 Setup einzubetten. -\layout Standard +\end_layout +\begin_layout Standard Erfreulicherweise beinhaltet Red Hat Linux seit der Version 7.1 die IPv6-Skripts des Autors. Unterstützt wurde dies und wird auch weiterhin von Pekka Savola. -\layout Standard +\end_layout +\begin_layout Standard Bei Mandrake ist ab Version 8.0 ebenfalls ein IPv6-fähiges initscript Paket beinhaltet, ein kleiner Fehler verhindert aber nach wie vor die Anwendung ( \begin_inset Quotes sld -\end_inset +\end_inset ifconfig \begin_inset Quotes srd -\end_inset +\end_inset vermisst \begin_inset Quotes sld -\end_inset +\end_inset inet6 \begin_inset Quotes srd -\end_inset +\end_inset vor \begin_inset Quotes sld -\end_inset +\end_inset add \begin_inset Quotes srd -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection Test der IPv6-Unterstützung bei Netzwerk-Konfigurations-Scripts -\layout Standard +\end_layout +\begin_layout Standard Sie können überprüfen, ob Ihre Distribution eine permanente IPv6 Konfiguration unter Verwendung der Skript-Sammlung des Autors unterstützt. Folgende script library sollte existieren: -\layout Code +\end_layout +\begin_layout Code /etc/sysconfig/network-scripts/network-functions-ipv6 -\layout Standard +\end_layout +\begin_layout Standard Automatischer Test: -\layout Code +\end_layout +\begin_layout Code # test -f /etc/sysconfig/network-scripts/network-functions-ipv6 && echo "Main -\layout Code +\end_layout +\begin_layout Code ¬ IPv6 script library exists" -\layout Standard +\end_layout +\begin_layout Standard Die Versionsnummer der Library ist von Interesse, wenn Sie Features vermissen sollten. Die Versionsnummer können Sie anzeigen, indem Sie folgenden Befehl ausführen (einfacher ist es sicherlich, wenn Sie im Header der Datei nachlesen): -\layout Code +\end_layout +\begin_layout Code # source /etc/sysconfig/network-scripts/network-functions-ipv6 && -\layout Code +\end_layout +\begin_layout Code ¬ getversion_ipv6_functions -\layout Code +\end_layout +\begin_layout Code 20011124 -\layout Standard +\end_layout +\begin_layout Standard Im obigen Beispiel ist die Versionsnummer -\series bold +\series bold 20011124 -\series default +\series default . Um zu sehen, was sich inzwischen geändert hat, können Sie hier die neuesten Informationen nachlesen: @@ -7053,177 +8682,208 @@ Im obigen Beispiel ist die Versionsnummer \begin_inset LatexCommand \url[initscripts-ipv6 homepage]{http://www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Spiegel]{http://mirrors.bieringer.de/www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ) \lang ngerman . Sie finden hier auch ein Change-Log. -\layout Subsection +\end_layout +\begin_layout Subsection Kurze Anleitung zum aktivieren von IPv6 bei RHL 7.1, 7.2, 7.3, ... -\layout Itemize +\end_layout +\begin_layout Itemize Überprüfen Sie, ob das IPv6 Modul auf Ihrem System bereits geladen ist: -\layout Code +\end_layout +\begin_layout Code # modprobe -c | grep net-pf-10 -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 off -\layout Itemize +\end_layout +\begin_layout Itemize Ist das Ergebnis \begin_inset Quotes sld -\end_inset +\end_inset off \begin_inset Quotes srd -\end_inset +\end_inset , dann aktivieren Sie IPv6 durch hinzufügen folgender Zeile in /etc/sysconfig/ne twork -\layout Code +\end_layout +\begin_layout Code NETWORKING_IPV6=yes -\layout Itemize +\end_layout +\begin_layout Itemize Rebooten bzw. starten Sie das Netzwerk neu mit dem Befehl -\layout Code +\end_layout +\begin_layout Code # service network restart -\layout Itemize +\end_layout +\begin_layout Itemize Nun sollte das IPv6 Modul geladen sein -\layout Code +\end_layout +\begin_layout Code # modprobe -c | grep ipv6 -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 ipv6 -\layout Standard +\end_layout +\begin_layout Standard Ist ihr System an einem Link, der Router Advertisements liefert, dann wird die automatische Konfiguration automatisch durchgeführt. Zusätzlich Informationen darüber, welche Einstellungen unterstützt werden finden Sie in der Datei /usr/share/doc/initscripts-$version/sysconfig.txt. -\layout Section +\end_layout +\begin_layout Section SuSE Linux -\layout Standard +\end_layout +\begin_layout Standard Seit neueren 7.x Versionen gibt es eine wirklich rudimentäre Unterstützung für IPv6, siehe /etc/rc.config für Details. -\layout Standard +\end_layout +\begin_layout Standard Aufgrund der komplett unterschiedlichen Struktur der Konfigurations- und Scriptdateien ist es sehr schwer (oder unmöglich) das Set für Red Hat Linux und seine Klone mit dieser Distribution zu verwenden. -\newline -In Version 8.x wurde das Konfigurations-Setup bei SuSE komplett abgeändert. -\layout Subsection +\newline +In Version 8.x wurde + das Konfigurations-Setup bei SuSE komplett abgeändert. +\end_layout +\begin_layout Subsection \lang english SuSE Linux 7.3 -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[How to setup 6to4 IPv6 with SuSE 7.3]{http://www.feyrer.de/IPv6/SuSE73-IPv6+6to4-setup.html} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection \lang english SuSE Linux 8.0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english IPv6-Adress-Konfiguration -\layout Standard +\end_layout +\begin_layout Standard \lang english Editiere Datei /etc/sysconfig/network/ifcfg- und setze folgende Variable entsprechend -\layout Code +\end_layout +\begin_layout Code \lang english IP6ADDR="/" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Zusätzliche information -\layout Standard +\end_layout +\begin_layout Standard \lang english Siehe Datei /usr/share/doc/packages/sysconfig/README -\layout Subsection +\end_layout +\begin_layout Subsection \lang english SuSE Linux 8.1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english IPv6-Adress-Konfiguration -\layout Standard +\end_layout +\begin_layout Standard \lang english Editiere Datei /etc/sysconfig/network/ifcfg- und setze folgende Variable entsprechend -\layout Code +\end_layout +\begin_layout Code \lang english IPADDR="/" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Zusätzliche information -\layout Standard +\end_layout +\begin_layout Standard \lang english Siehe Datei /usr/share/doc/packages/sysconfig/Network -\layout Section +\end_layout +\begin_layout Section \lang english - \begin_inset LatexCommand \label{Configuration-Debian-Linux} -\end_inset +\end_inset \lang ngerman Debian Linux -\layout Standard +\end_layout +\begin_layout Standard \lang english Folgende Information wurde von Stephane Bortzmeyer beigesteuert. -\layout Enumerate +\end_layout +\begin_layout Enumerate \lang english Überprüfe, ob IPv6 aktiv ist, entweder weil es in den Kernel hineinkompilier @@ -7231,940 +8891,1084 @@ Folgende Information wurde von Stephane Bortzmeyer /proc/sys/net/ipv6/conf/all/autoconf -\layout Code +\end_layout +\begin_layout Code \lang english netmask 64 -\layout Code +\end_layout +\begin_layout Code \lang english # The router is autoconfigured and has no fixed address. -\layout Code +\end_layout +\begin_layout Code \lang english # It is magically -\layout Code +\end_layout +\begin_layout Code \lang english # found. (/proc/sys/net/ipv6/conf/all/accept_ra). Otherwise: -\layout Code +\end_layout +\begin_layout Code \lang english #gateway 3ffe:ffff:1234:5::1 -\layout Standard +\end_layout +\begin_layout Standard \lang english Danach rebooten oder folgendes Kommando ausführen -\layout Code +\end_layout +\begin_layout Code \lang english # ifup --force eth0 -\layout Standard +\end_layout +\begin_layout Standard \lang english Danach sollte die statische IPv6-Adresse konfiguriert sein. -\layout Subsection +\end_layout +\begin_layout Subsection Weiterführende Informationen -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 on Debian Linux]{http://people.debian.org/~csmall/ipv6/} -\end_inset +\end_inset von Craig Small -\layout Itemize +\end_layout +\begin_layout Itemize Jean-Marc V. Liotier's \lang english \begin_inset LatexCommand \url[HOWTO for Freenet6 & Debian Users]{http://www.ruwenzori.net/ipv6/Jims_LAN_IPv6_global_connectivity_howto.html} -\end_inset +\end_inset \lang ngerman (am 24.12.2002 in der \begin_inset LatexCommand \ref[mailinglist]{information-maillists} -\end_inset +\end_inset users@ipv6.org angekündigt) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-autoconfiguration} -\end_inset +\end_inset Automatische Konfiguration und Mobilität -\layout Section +\end_layout +\begin_layout Section Stateless Auto-Konfiguration -\layout Standard +\end_layout +\begin_layout Standard Wird unterstützt und kann bei der zugewiesenen link-lokalen Adressen beobachtet werden, sobald ein IPv6 fähiges Interface aktiv ist. -\layout Standard +\end_layout +\begin_layout Standard \lang english Beispiel: -\layout Code +\end_layout +\begin_layout Code \lang english # ip -6 addr show dev eth0 scope link -\layout Code +\end_layout +\begin_layout Code \lang english 2: eth0: mtu 1500 qlen1000 -\layout Code +\end_layout +\begin_layout Code \lang english inet6 fe80::211:d8ff:fe6b:f0f5/64 scope link -\layout Code +\end_layout +\begin_layout Code \lang english valid_lft forever preferred_lft forever -\layout Section +\end_layout +\begin_layout Section Stateful Auto-Konfiguration unter Verwendung des Router Advertisement Daemon (radvd) -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. Siehe unten im Abschnitt \begin_inset LatexCommand \ref[radvd daemon autoconfiguration]{hints-daemons-radvd} -\end_inset +\end_inset . -\layout Section +\end_layout +\begin_layout Section Dynamic Host Configuration Protocol v6 (DHCPv6) -\layout Standard +\end_layout +\begin_layout Standard \lang english Nach einer langen Zeit der Diskussion wurde \begin_inset LatexCommand \url[RFC 3315 / Dynamic Host Configuration Protocol for IPv6 (DHCPv6)]{http://www.faqs.org/rfcs/rfc3315.html} -\end_inset +\end_inset verabschiedet. Momentan (10/2005) existieren 2 Implementierungen: -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Dibbler]{http://klub.com.pl/dhcpv6/} -\end_inset +\end_inset von Tomasz Mrugalski -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[DHCPv6 on Sourceforge]{http://dhcpv6.sourceforge.net/} -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section Mobilität -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Standard +\end_layout +\begin_layout Standard Für weiterführende Details siehe \begin_inset LatexCommand \url[Mobile IPv6 for Linux(MIPL) homepage]{http://www.mipl.mediapoli.com/} -\end_inset +\end_inset . Weitere Details sind unter folgenden Links zu finden: -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-oneill-mipv6-cao-??.txt / MIPv6 Care of Address Option]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-mccann-mobileip-80211fh-??.txt / Mobile IPv6 Fast Handovers for 802.11 Networks]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-haberman-ipv6-anycast-rr-??.txt / IPv6 Anycast Binding using Return Routability]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-mun-aaa-localkm-mobileipv6-??.txt / Localized Key Management for AAA in MobileIPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-thubert-nemo-ro-taxonomy-??.txt / Taxonomy of Route Optimization Models in the NEMO Context]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-le-aaa-diameter-mobileipv6-??.txt / Diameter Mobile IPv6 Application]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-wakikawa-manet-globalv6-??.txt / Global Connectivity for IPv6 Mobile Ad Hoc Networks]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ietf-mobileip-fast-mipv6-??.txt / Fast Handovers for Mobile IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ietf-mobileip-ipv6-??.txt / Mobility Support in IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ohnishi-mobileip-v6vpngateway-??.txt / Mobile IPv6 VPN using Gateway Home Agent]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ietf-mobileip-hmipv6-??.txt / Hierarchical MIPv6 mobility management (HMIPv6)]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-mkhalil-ipv6-fastra-??.txt / IPv6 Fast Router Advertisement]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-okazaki-mobileip-abk-??.txt / Securing MIPv6 Binding Updates Using Address Based Keys (ABKs)]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-vriz-mobileip-hbhlmap-??.txt / Hop-by-Hop Local Mobility Agents Probing for Mobile IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-thubert-nemo-reverse-routing-header-??.txt / IPv6 Reverse Routing Header and its application to Mobile Networks]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ietf-mobileip-mipv6-ha-ipsec-??.txt / Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-suh-rmm-??.txt / Regional Mobile IPv6 mobility management]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-mccann-mobileip-ipv6mipv4-??.txt / IPv6 over Mobile IPv4]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-kempf-mobileip-fmipv6-sem-??.txt / Improving the Architectural Alignment for FMIPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-le-aaa-mipv6-requirements-??.txt / Mobile IPv6 Authentication, Authorization, and Accounting Requirements]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-hwang-rohc-mipv6-??.txt / RObust Header Compression (ROHC): A Compression Profile for Mobile IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[LANCASTER MOBILE IPv6 PACKAGE]{http://www.cs-ipv6.lancs.ac.uk/ipv6/MobileIP/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Testbed for MIND project on IPv6]{http://gsyc.escet.urjc.es/Mobiquo/Mind/documentacion/MontajeMaquetaIPv6_en/MontajeMaquetaIPv6_en.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[HS247/Mobile IP Web Links]{http://hs247.com/modules.php?name=Web_Links&l_op=viewlink&cid=16} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Mobile IPv6 Issue List]{http://www.piuha.net/~jarkko/publications/mipv6/MIPv6-Issues.html} -\end_inset +\end_inset -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-firewalling-security} -\end_inset +\end_inset Firewall-Funktionalität -\layout Standard +\end_layout +\begin_layout Standard Die IPv6 Firewall-Funktionalität ist wichtig; vor allem dann, wenn Sie auf Ihren internen Netzen IPv6 mit globalen IPv6 Adressen einsetzen. In IPv6 werden - im Unterschied zu IPv4, wo interne Hosts automatisch durch private IPv6 Adressen geschützt werden ( \begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://www.faqs.org/rfcs/rfc1918.html} -\end_inset +\end_inset bzw. \begin_inset LatexCommand \url[Google search for Microsoft + APIPA]{http://www.google.com/search?q=apipa+microsoft} -\end_inset +\end_inset ) - globale Adressen verwendet und jeder mit IPv6-Anbindung kann alle internen Knoten, bei denen IPv6 aktiv ist, erreichen. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{firewalling-netfilter6} -\end_inset +\end_inset Firewall-Funktionalität mit netfilter6 -\layout Standard +\end_layout +\begin_layout Standard Von Haus aus unterstützt wird die IPv6-Firewall-Funktionalität im Kernel erst ab Version 2.4+. In älteren 2.2+ Versionen können sie nur mit Protocol 41 IPv6-in-IPv4-Daten filtern. -\layout Standard +\end_layout +\begin_layout Standard Achtung: Es gibt keine Garantie, dass die beschriebenen Regeln und Beispiele ihr System auch wirklich schützen können! -\layout Standard +\end_layout +\begin_layout Standard Beobachten Sie nach der Installation ihr Regelset, siehe Abschnitt \begin_inset LatexCommand \ref{IPv6-security-auditing} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard \lang english Zudem arbeitet das USAGI-Projekt momentan daran, Connection-Tracking für IPv6 fertigzustellen. Dies wird den Regelsatz in Zukunft einfacher und sicherer machen! -\layout Subsection +\end_layout +\begin_layout Subsection Weitere Informationen -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Netfilter project]{http://www.netfilter.org/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[maillist archive of netfilter users]{https://lists.netfilter.org/mailman/listinfo/netfilter} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[maillist archive of netfilter developers]{https://lists.netfilter.org/mailman/listinfo/netfilter-devel} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Unofficial status informations]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html#netfilter6 } -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section Vorbereitung -\layout Subsection +\end_layout +\begin_layout Subsection Quellen besorgen -\layout Standard +\end_layout +\begin_layout Standard Besorgen Sie sich den aktuellsten Kernel: \begin_inset LatexCommand \url[http://www.kernel.org/]{http://www.kernel.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Besorgen Sie sich das aktuellste iptables Paket: -\layout Itemize +\end_layout +\begin_layout Itemize Source tarball (für Kernel Patches): \begin_inset LatexCommand \url[http://www.netfilter.org/]{http://www.netfilter.org/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Source RPM für die Neukompilierung des Programms (für Red Hat Systeme): \begin_inset LatexCommand \url[ftp://ftp.redhat.com/redhat/linux/rawhide/SRPMS/SRPMS/]{ftp://ftp.redhat.com/redhat/linux/rawhide/SRPMS/SRPMS/} -\end_inset +\end_inset oder ev. unter \begin_inset LatexCommand \url[http://www.netcore.fi/pekkas/linux/ipv6/]{http://www.netcore.fi/pekkas/linux/ipv6/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Quellen entpacken -\layout Standard +\end_layout +\begin_layout Standard Wechseln Sie in das Source-Verzeichnis: -\layout Code +\end_layout +\begin_layout Code # cd /path/to/src -\layout Standard +\end_layout +\begin_layout Standard Entpacken sie die Kernel-Quellen und vergeben diesen einen neuen Namen -\layout Code +\end_layout +\begin_layout Code # tar z|jxf kernel-version.tar.gz|bz2 -\layout Code +\end_layout +\begin_layout Code # mv linux linux-version-iptables-version+IPv6 -\layout Standard +\end_layout +\begin_layout Standard Entpacken Sie die iptables Quellen -\layout Code +\end_layout +\begin_layout Code # tar z|jxf iptables-version.tar.gz|bz2 -\layout Subsection +\end_layout +\begin_layout Subsection Neueste iptables/IPv6-relevante Patches den Kernel-Quellen hinzufügen -\layout Standard +\end_layout +\begin_layout Standard Wechseln Sie in das iptables Verzeichnis -\layout Code +\end_layout +\begin_layout Code # cd iptables-version -\layout Standard +\end_layout +\begin_layout Standard Fügen Sie relevante Patches hinzu -\layout Code +\end_layout +\begin_layout Code # make pending-patches KERNEL_DIR=/path/to/src/linux-version-iptables-version/ -\layout Standard +\end_layout +\begin_layout Standard Fügen Sie zusätzliche IPv6 relevante IPv6 Patches hinzu (die nach wie vor nicht im Standard-Kernel enthalten sind) -\layout Code +\end_layout +\begin_layout Code # make patch-o-matic KERNEL_DIR=/path/to/src/linux-version-iptables-version/ -\layout Standard +\end_layout +\begin_layout Standard Sagen Sie zu folgenden Optionen (iptables-1.2.2) Ja: -\layout Itemize +\end_layout +\begin_layout Itemize ah-esp.patch -\layout Itemize +\end_layout +\begin_layout Itemize masq-dynaddr.patch (nur benötigt bei Systemen mit dynamischer IP-Zuweisung am WAN mittels PPP oder PPPoE) -\layout Itemize +\end_layout +\begin_layout Itemize ipv6-agr.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize ipv6-ports.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize LOG.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize REJECT.patch.ipv6 -\layout Standard +\end_layout +\begin_layout Standard Überprüfen Sie die Erweiterungen -\layout Code +\end_layout +\begin_layout Code # make print-extensions -\layout Code +\end_layout +\begin_layout Code Extensions found: IPv6:owner IPv6:limit IPv6:mac IPv6:multiport -\layout Subsection +\end_layout +\begin_layout Subsection Konfiguration, kompilieren und Installation eines neues Kernels -\layout Standard +\end_layout +\begin_layout Standard Wechseln Sie zu den Kernel-Quellen -\layout Code +\end_layout +\begin_layout Code # cd /path/to/src/linux-version-iptables-version/ -\layout Standard +\end_layout +\begin_layout Standard Editieren Sie das Makefile -\layout Code +\end_layout +\begin_layout Code - EXTRAVERSION = -\layout Code +\end_layout +\begin_layout Code + EXTRAVERSION = -iptables-version+IPv6-try -\layout Standard +\end_layout +\begin_layout Standard Starten Sie configure und aktivieren Sie IPv6 relevante Optionen -\layout Code +\end_layout +\begin_layout Code Code maturity level options -\layout Code +\end_layout +\begin_layout Code Prompt for development and/or incomplete code/drivers : yes -\layout Code +\end_layout +\begin_layout Code Networking options -\layout Code +\end_layout +\begin_layout Code Network packet filtering: yes -\layout Code +\end_layout +\begin_layout Code The IPv6 protocol: module -\layout Code +\end_layout +\begin_layout Code IPv6: Netfilter Configuration -\layout Code +\end_layout +\begin_layout Code IP6 tables support: module -\layout Code +\end_layout +\begin_layout Code All new options like following: -\layout Code +\end_layout +\begin_layout Code limit match support: module -\layout Code +\end_layout +\begin_layout Code MAC address match support: module -\layout Code +\end_layout +\begin_layout Code Multiple port match support: module -\layout Code +\end_layout +\begin_layout Code Owner match support: module -\layout Code +\end_layout +\begin_layout Code netfilter MARK match support: module -\layout Code +\end_layout +\begin_layout Code Aggregated address check: module -\layout Code +\end_layout +\begin_layout Code Packet filtering: module -\layout Code +\end_layout +\begin_layout Code REJECT target support: module -\layout Code +\end_layout +\begin_layout Code LOG target support: module -\layout Code +\end_layout +\begin_layout Code Packet mangling: module -\layout Code +\end_layout +\begin_layout Code MARK target support: module -\layout Standard +\end_layout +\begin_layout Standard Konfigurieren Sie bei Bedarf Sonstiges abseits von IPv6. -\layout Standard +\end_layout +\begin_layout Standard Kompilieren und Installation: siehe Kapitel Kernel sowie andere HOWTOs. -\layout Subsection +\end_layout +\begin_layout Subsection iptables neu kompilieren und installieren -\layout Standard +\end_layout +\begin_layout Standard Stellen Sie sicher, dass obige Kernel-Sourceverzeichnisstruktur unter /usr/src/l inux liegt -\layout Standard +\end_layout +\begin_layout Standard Benennen sie das ältere Verzeichnis um -\layout Code +\end_layout +\begin_layout Code # mv /usr/src/linux /usr/src/linux.old -\layout Standard +\end_layout +\begin_layout Standard Erstellen Sie einen neuen symbolischen Link -\layout Code +\end_layout +\begin_layout Code # ln -s /path/to/src/linux-version-iptables-version /usr/src/linux -\layout Standard +\end_layout +\begin_layout Standard Erstellen Sie ein neues SRPMS -\layout Code +\end_layout +\begin_layout Code # rpm --rebuild /path/to/SRPMS/iptables-version-release.src.rpm -\layout Standard +\end_layout +\begin_layout Standard Installieren Sie das neue iptables Paket (iptables + iptables-ipv6) -\layout Itemize +\end_layout +\begin_layout Itemize Bei RH 7.1 Systemen ist normalerweise eine ältere Version hiervon bereits installiert, verwenden Sie daher die Option \begin_inset Quotes sld -\end_inset +\end_inset Freshen \begin_inset Quotes srd -\end_inset +\end_inset : -\layout Code +\end_layout +\begin_layout Code # rpm -Fhv /path/to/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Itemize +\end_layout +\begin_layout Itemize Ist keine ältere Version installiert, benutzen Sie die Option \begin_inset Quotes sld -\end_inset +\end_inset install \begin_inset Quotes srd -\end_inset +\end_inset : -\layout Code +\end_layout +\begin_layout Code # rpm -ihv /path/to/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Itemize +\end_layout +\begin_layout Itemize Bei RH 6.2 Systemen ist normalerweise kein Kernel Version 2.4.x installiert und die Anforderungen sind demnach nicht gegeben. Benutzen Sie in diesem Fall \begin_inset Quotes sld -\end_inset +\end_inset nodeps \begin_inset Quotes srd -\end_inset +\end_inset : -\layout Code +\end_layout +\begin_layout Code # rpm -ihv --nodeps /path/to/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Standard +\end_layout +\begin_layout Standard Damit iptables die Libraries finden kann, ist es eventuell notwendig, einen symbolischen Link für die iptables Libraries zu erstellen: -\layout Code +\end_layout +\begin_layout Code # ln -s /lib/iptables/ /usr/lib/iptables -\layout Section +\end_layout +\begin_layout Section Verwendung -\layout Subsection +\end_layout +\begin_layout Subsection Unterstützung im Kernel -\layout Standard +\end_layout +\begin_layout Standard Laden Sie das Modul (falls dies im Kernel so kompiliert wurde): -\layout Code +\end_layout +\begin_layout Code # modprobe ip6_tables -\layout Standard +\end_layout +\begin_layout Standard Überprüfen der IPv6-Unterstützung: -\layout Code +\end_layout +\begin_layout Code # [ ! -f /proc/net/ip6_tables_names ] && echo "Current kernel doesn't support -\layout Code +\end_layout +\begin_layout Code ¬ 'ip6tables' firewalling (IPv6)!" -\layout Subsection +\end_layout +\begin_layout Subsection Die Benützung von iptables lernen -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Auflistung aller netfilter Einträge -\layout Itemize +\end_layout +\begin_layout Itemize Kurze Auflistung: -\layout Code +\end_layout +\begin_layout Code # ip6tables -L -\layout Itemize +\end_layout +\begin_layout Itemize Erweiterte Auflistung: -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v --line-numbers -L -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Auflistung angegebener Filter -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v --line-numbers -L INPUT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Hinzufügen einer Log-Regel zum Input-Filter mit Optionen -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --append INPUT -j LOG --log-prefix "INPUT:" -\layout Code +\end_layout +\begin_layout Code ¬ --log-level 7 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Hinzufügen einer Drop-Regel zum Input-Filter -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --append INPUT -j DROP -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Löschen einer Regel mit Hilfe der Regelnummer -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --delete INPUT 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ICMPv6 erlauben -\layout Standard +\end_layout +\begin_layout Standard Bei älteren Kernelversionen (unpatched kernel 2.4.5 und iptables-1.2.2) kann keine nähere Spezifizierung des ICMPv6-Typs vorgenommen werden: -\layout Itemize +\end_layout +\begin_layout Itemize Eingehender ICMPv6 Verkehr durch Tunnel erlauben -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -i sit+ -p icmpv6 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Ausgehenden ICMPv6 Verkehr durch Tunnel erlauben -\layout Code +\end_layout +\begin_layout Code # ip6tables -A OUTPUT -o sit+ -p icmpv6 -j ACCEPT -\layout Standard +\end_layout +\begin_layout Standard Neuere Kernel erlauben das Spezifizieren des ICMPv6-Typs: -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -p icmpv6 --icmpv6-type echo-request -j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Rate-limiting -\layout Standard +\end_layout +\begin_layout Standard Da es zu einem ICMPv6 Storm kommen kann (der Autor hat dies bereits mehrfach beobachtet), sollten sie das rate limiting zumindest für das ICMP Regelset einsetzen. @@ -8172,764 +9976,944 @@ Da es zu einem ICMPv6 Storm kommen kann (der Autor hat dies bereits mehrfach werden, um DoS Attacken gegen das syslog sowie gegen die Logdateien enthaltende n Patitionen entgegenzuwirken. Ein Beispiel für ein rate limited ICMPv6 sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT --protocol icmpv6 --icmpv6-type echo-request -\layout Code +\end_layout +\begin_layout Code ¬ -j ACCEPT --match limit --limit 30/minute -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Eingehende SSH-Verbindung erlauben -\layout Standard +\end_layout +\begin_layout Standard Im folgenden Beispiel werden eingehende SSH-Verbindungen von einer speziellen IPv6 Adresse zugelassen: -\layout Itemize +\end_layout +\begin_layout Itemize Eingehende SSH Verbindungen werden von der Adresse 3ffe:ffff:100::1/128 erlaubt -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -i sit+ -p tcp -s 3ffe:ffff:100::1/128 --sport 512:65535 -\layout Code +\end_layout +\begin_layout Code ¬ --dport 22 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Erlaube Antwortpakete (IPv6 Verbindungs-Tracking ist im Mainstream netfilter6 zurzeit nicht implementiert) -\layout Code +\end_layout +\begin_layout Code # ip6tables -A OUTPUT -o sit+ -p tcp -d 3ffe:ffff:100::1/128 --dport 512:65535 -\layout Code +\end_layout +\begin_layout Code ¬ --sport 22 ! --syn j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Getunnelten IPv6-in-IPv4 Datenverkehr erlauben -\layout Standard +\end_layout +\begin_layout Standard Um getunnelte IPv6-in-IPv4 Pakete zu akzeptieren, müssen Sie in Ihrem IPv4 Firewall-Setup entsprechende Regeln einzufügen, z.B. -\layout Itemize +\end_layout +\begin_layout Itemize Akzeptiere eingehende IPv6-in-IPv4 Daten am interface ppp0 -\layout Code +\end_layout +\begin_layout Code # iptables -A INPUT -i ppp0 -p ipv6 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Akzeptiere ausgehende IPv6-in-IPv4 Daten am interface ppp0 -\layout Code +\end_layout +\begin_layout Code # iptables -A OUTPUT -o ppp0 -p ipv6 -j ACCEPT -\layout Standard +\end_layout +\begin_layout Standard Haben Sie nur einen statischen Tunnel, dann können sie die IPv4 Adresse auch dediziert angeben: -\layout Itemize +\end_layout +\begin_layout Itemize Akzeptiere eingehende IPv6-in-IPv4 Daten vom Tunnel-Endpunkt 1.2.3.4 am interface ppp0 -\layout Code +\end_layout +\begin_layout Code # iptables -A INPUT -i ppp0 -p ipv6 -s 1.2.3.4 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Akzeptiere ausgehende IPv6-in-IPv4 Daten vom Tunnel-Endpunkt 1.2.3.4 am interface ppp0 -\layout Code +\end_layout +\begin_layout Code # iptables -A OUTPUT -o ppp0 -p ipv6 -d 1.2.3.4 -j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Schutz gegen eingehende TCP-Verbindungs-Anfragen -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold SEHR EMPFOHLEN! -\series default +\series default Aus Sicherheitsgründen sollten Sie auf jeden Fall eine Regel inkludieren, wodurch eingehende TCP-Verbindungs-Anfragen geblockt werden. Wenn Sie andere Interfacenamen verwenden, müssen Sie die Option "-i" entspreche nd anpassen! -\layout Itemize +\end_layout +\begin_layout Itemize Blockiere eingehende TCP-Verbindungs-Anfragen zu diesem Host -\layout Code +\end_layout +\begin_layout Code # ip6tables -I INPUT -i sit+ -p tcp --syn -j DROP -\layout Itemize +\end_layout +\begin_layout Itemize Blockiere eingehende TCP-Verbindungs-Anfragen zu Hosts hinter diesem Router -\layout Code +\end_layout +\begin_layout Code # ip6tables -I FORWARD -i sit+ -p tcp --syn -j DROP -\layout Standard +\end_layout +\begin_layout Standard Eventuell müssen diese Regeln unterhalb anderer Regeln platziert werden. Nehmen Sie sich für die Reihenfolge der Regeln etwas Zeit. Sinnvoll wird es auch sein, ein Script mit den Regeln zu erstellen, damit die Regeln in der gewünschten Reihenfolge angewendet werden. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Schutz gegen eingehende UDP-Verbindungs-Anfragen -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold EBENFALLS SEHR EMPHOLEN! -\series default +\series default Wie bereits im Kapitel Firewall erwähnt, ist es möglich die Ports bei ausgehend en UDP/TCP-Verbindungen zu kontrollieren. Im Falle, dass all Ihre IPv6 Systeme lokale Ports verwenden, z.B. von 32768 bis 60999, dann können sie ebenfalls UDP Verbindungen filtern (bis das Verbindungs-Tracking funktioniert): -\layout Itemize +\end_layout +\begin_layout Itemize Blockiere eingehende UDP-Pakete, die nicht Antworten ausgehender Anfragen dieses Host sein können -\layout Code +\end_layout +\begin_layout Code # ip6tables -I INPUT -i sit+ -p udp ! --dport 32768:60999 -j DROP -\layout Itemize +\end_layout +\begin_layout Itemize Blockiere eingehende UDP-Pakete, die nicht Antworten auf Anfragen von hinter diesem Router gelegenen Hosts sein können -\layout Code +\end_layout +\begin_layout Code # ip6tables -I FORWARD -i sit+ -p udp ! --dport 32768:60999 -j DROP -\layout Subsection +\end_layout +\begin_layout Subsection Anwendungsbeispiel -\layout Standard +\end_layout +\begin_layout Standard Folgende Zeilen zeigen ein umfangreicheres Setup. Happy netfilter6 Regelset erstellen... -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v -L -\layout Code +\end_layout +\begin_layout Code Chain INPUT (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code 0 0 extIN all sit+ * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 4 384 intIN all eth0 * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::1/128 ::1/128 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all lo * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `INPUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain FORWARD (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 int2ext all eth0 sit+ ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ext2int all sit+ eth0 ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `FORWARD-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain OUTPUT (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 extOUT all * sit+ ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 4 384 intOUT all * eth0 ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::1/128 ::1/128 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * lo ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `OUTPUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain ext2int (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1:65535 dpts:1024:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `ext2int-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain extIN (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * 3ffe:400:100::1/128 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:512:65535 dpt:22 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * 3ffe:400:100::2/128 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:512:65535 dpt:22 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1:65535 dpts:1024:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ udp spts:1:65535 dpts:1024:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ limit: avg 5/min burst 5 LOG flags 0 level 7 prefix `extIN-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain extOUT (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100::1/128tcp spt:22 dpts:512:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100::2/128tcp spt:22 dpts:512:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ udp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `extOUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain int2ext (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `int2ext:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `int2ext-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain intIN (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ fe80::/ffc0:: -\layout Code +\end_layout +\begin_layout Code 4 384 ACCEPT all * * ::/0 ff02::/16 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain intOUT (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ fe80::/ffc0:: -\layout Code +\end_layout +\begin_layout Code 4 384 ACCEPT all * * ::/0 ff02::/16 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `intOUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-security} -\end_inset +\end_inset Sicherheit -\layout Section +\end_layout +\begin_layout Section Sicherheit des Knoten -\layout Standard +\end_layout +\begin_layout Standard Es wird sehr empfohlen alle verfügbaren Patches einzuspielen sowie alle nicht benötigten Dienste zu deaktivieren. Ebenfalls sollten Sie lokales firewalling aktivieren und binden Sie die Dienste ausschließlich an benötigte IPv4/IPv6 Adressen. -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Section +\end_layout +\begin_layout Section Zugangsbeschränkungen -\layout Standard +\end_layout +\begin_layout Standard Viele Dienste setzen die tcp_wrapper Bibliothek für die Zugangskontrolle ein. Eine Beschreibung finden Sie unter \begin_inset LatexCommand \ref[use of tcp_wrapper]{hints-daemons-tcpwrapper} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{IPv6-security-auditing} -\end_inset +\end_inset IPv6 Sicherheitsüberwachung -\layout Standard +\end_layout +\begin_layout Standard Aktuell gibt es keine komfortablen Sicherheitstools mit denen man ein System über ein Netzwerk nach IPv6 relevanten Sicherheitslücken hin überprüfen kann. Weder \begin_inset LatexCommand \url[Nessus]{http://www.nessus.org/} -\end_inset +\end_inset noch irgendein kommerzieller Security Scanner ist zur Zeit dazu in der Lage, IPv6-Adressen scannen zu können. -\layout Subsection +\end_layout +\begin_layout Subsection Rechtsfragen -\layout Standard +\end_layout +\begin_layout Standard ACHTUNG: Bitte stellen Sie immer sicher, dass Sie ausschließlich ihr eigenes Netzwerk scannen oder einen Scan nur nach Erhalt einer schriftlichen Erlaubnis durchführen. Andernfalls haben sie mit rechtlichen Konsequenzen zu rechnen! -\newline -ÜBERPRÜFEN Sie die Ziel-IPv6-Adresse ZWEIMAL, bevor Sie einen Scan starten. -\layout Subsection +\newline +ÜBERPRÜFEN + Sie die Ziel-IPv6-Adresse ZWEIMAL, bevor Sie einen Scan starten. +\end_layout +\begin_layout Subsection Sicherheitsüberwachung mit IPv6 fähigen netcat -\layout Standard +\end_layout +\begin_layout Standard Mit dem IPv6 fähigen netcat (siehe \begin_inset LatexCommand \url[IPv6+Linux-status-apps/security-auditing]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#security-auditing} -\end_inset +\end_inset für Details) können Sie einen Portscan durchführen. Es wird ein Script abgearbeitet, wobei u.a. ein Port-Bereich überprüft und Banners mitprotokolliert werden. Anwendungsbeispiel: -\layout Code +\end_layout +\begin_layout Code # nc6 ::1 daytime -\layout Code +\end_layout +\begin_layout Code 13 JUL 2002 11:22:22 CEST -\layout Subsection +\end_layout +\begin_layout Subsection Sicherheitsüberwachung mit IPv6 fähigen NMap -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[NMap]{http://www.insecure.org/nmap/} -\end_inset +\end_inset , einer der weltweit besten Portscanner, unterstützt IPv6 seit der Version 3.10ALPHA1. Anwendungsbeispiel: -\layout Code +\end_layout +\begin_layout Code # nmap -6 -sT ::1 -\layout Code +\end_layout +\begin_layout Code Starting nmap V. 3.10ALPHA3 ( www.insecure.org/nmap/ ) -\layout Code +\end_layout +\begin_layout Code Interesting ports on localhost6 (::1): -\layout Code +\end_layout +\begin_layout Code (The 1600 ports scanned but not shown below are in state: closed) -\layout Code +\end_layout +\begin_layout Code Port State Service -\layout Code +\end_layout +\begin_layout Code 22/tcp open ssh -\layout Code +\end_layout +\begin_layout Code 53/tcp open domain -\layout Code +\end_layout +\begin_layout Code 515/tcp open printer -\layout Code +\end_layout +\begin_layout Code 2401/tcp open cvspserver -\layout Code +\end_layout +\begin_layout Code Nmap run completed -- 1 IP address (1 host up) scanned in 0.525 seconds -\layout Subsection +\end_layout +\begin_layout Subsection Sicherheitsüberwachung mit IPv6 fähigen strobe -\layout Standard +\end_layout +\begin_layout Standard Strobe ist (im Vergleich zu NMap) ein low budget Portscanner. Allerdings gibt es für Strobe einen IPv6 Patch (siehe \begin_inset LatexCommand \url[IPv6+Linux-status-apps/security-auditing]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#security-auditing} -\end_inset +\end_inset für Details). Anwendungsbeispiel: -\layout Code +\end_layout +\begin_layout Code # ./strobe ::1 strobe 1.05 (c) 1995-1999 Julian Assange . -\layout Code +\end_layout +\begin_layout Code ::1 2401 unassigned unknown -\layout Code +\end_layout +\begin_layout Code ::1 22 ssh Secure Shell - RSA encrypted rsh -\layout Code +\end_layout +\begin_layout Code ::1 515 printer spooler (lpd) -\layout Code +\end_layout +\begin_layout Code ::1 6010 unassigned unknown -\layout Code +\end_layout +\begin_layout Code ::1 53 domain Domain Name Server -\layout Standard +\end_layout +\begin_layout Standard Hinweis: strobe wird nicht wirklich weiterentwickelt, die abgebildete Versionsnu mmer ist zudem falsch. -\layout Subsection +\end_layout +\begin_layout Subsection Überwachungsergebnisse -\layout Standard +\end_layout +\begin_layout Standard Falls das Ergebnis einer Überwachung nicht Ihren IPv6 Sicherheitsrichtlinien entspricht, schließen Sie die Lücken mit Hilfe der IPv6-Firewall-Funktionalität , z.B. mit netfilter6 (siehe \begin_inset LatexCommand \ref[Firewalling/Netfilter6]{firewalling-netfilter6} -\end_inset +\end_inset für Details). -\layout Standard +\end_layout +\begin_layout Standard Hinweis: Detailliertere Informationen zum Thema IPv6 Sicherheit finden Sie unter folgenden Links: -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Firewalling Considerations for IPv6 / draft-savola-v6ops-firewalling-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[IPv6 Neighbour Discovery trust models and threats / draft-ietf-send-psreq-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Security Considerations for 6to4 / draft-savola-v6ops-6to4-security-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Access Control Prefix Router Advertisement Option for IPv6 / draft-bellovin-ipv6-accessprefix-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Requirements for Plug and Play IPsec for IPv6 applications /draft-kobayakawa-ipsec-ipv6-pnpipsec-reqts-??.txt ]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Security of IPv6 Routing Header and Home Address Options / draft-savola-ipv6-rh-ha-security-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Chapter +\end_layout +\begin_layout Chapter \lang english - \begin_inset LatexCommand \label{chapter-encryption-authentication} -\end_inset +\end_inset Verschlüsselung und Authentifizierung -\layout Standard +\end_layout +\begin_layout Standard \lang english Zum Unterschied zu IPv4 ist die Verschlüsselung und die Authentifizierung @@ -8937,67 +10921,78 @@ Zum Unterschied zu IPv4 ist die Verschl Diese Features werden normalerweise mit IPsec implementiert (das auch von IPv4 verwendet wird). -\layout Section +\end_layout +\begin_layout Section \lang english Nutzungsarten von Verschlüsselung und Authentifizierung -\layout Standard +\end_layout +\begin_layout Standard \lang english Zwei Arten von Verschlüsselung und Authentifzierung einer Verbindung sind möglich: -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Transport-Modus -\layout Standard +\end_layout +\begin_layout Standard \lang english Der Transport-Modus ist ein Modus nur für Ende-zu-Ende-Verbindungen. Hier wird nur die Nutzlast (üblicherweise ICMP, TCP oder UDP) mit deren entsprechenden Headern verschlüsselt, wogegen der IP-Header nicht verschlüsselt wird (aber üblicherweise in die Authentifizierung eingebunden wird). -\layout Standard +\end_layout +\begin_layout Standard \lang english Bei Nutzung von AES-128 für Verschlüsselung und SHA1 für Authentifizierung reduziert dieser Modus die MTU um 42 Oktetts. -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Tunnel-Modus -\layout Standard +\end_layout +\begin_layout Standard \lang english Der Tunnel-Modus kann einerseits für eine Ende-zu-Ende wie auch für eine Gatewas-zu-Gateway-Verbindung genutzt werden. Hier wird das komplette IP-Paket verschlüsselt und ein neuer IP-Header vorangestellt . -\layout Standard +\end_layout +\begin_layout Standard \lang english Dieser Modus reduziert die MTU um weitere 40 Oktetts (bei IPv6), ausgehend von der MTU des Transport-Modus. -\layout Section +\end_layout +\begin_layout Section \lang english Unterstützung im Kernel (ESP und AH) -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Unterstützung im vanilla Linux Kernel 2.4.x -\layout Standard +\end_layout +\begin_layout Standard \lang english Fehlt in vanilla 2.4. @@ -9007,42 +11002,47 @@ Fehlt in vanilla 2.4. Dies ist auch ein Grund, wieso \begin_inset LatexCommand \url[FreeS/WAN project]{http://www.freeswan.org/} -\end_inset +\end_inset nicht in die vanilla Quellen miteingebunden wurde. -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Unterstützung im vanilla Linux kernel 2.6.x -\layout Standard +\end_layout +\begin_layout Standard \lang english Aktuelle Versionen (zum Zeitpunkt des Schreibens 2.6.9 und neuer) unterstützt IPsec für IPv4 und IPv6. -\layout Standard +\end_layout +\begin_layout Standard \lang english Die Implementierung wurde u.a. vom USAGI project unterstützt. -\layout Section +\end_layout +\begin_layout Section \lang english Automatischer Schlüssel-Austausch (IKE) -\layout Standard +\end_layout +\begin_layout Standard \lang english IPsec benötigt einen Schlüsselaustausch mit einem \begin_inset Quotes sld -\end_inset +\end_inset Geheimnis \begin_inset Quotes srd -\end_inset +\end_inset . Dieser Vorgang wird meistens automatisch durch sogenannte IKE-Daemons durchgefü @@ -9050,758 +11050,884 @@ hrt. Diese führen ebenso die Authentifizierung der Partner durch, entweder durch ein gemeinsam bekanntes Geheimnis (auch \begin_inset Quotes sld -\end_inset +\end_inset pre-shared secret \begin_inset Quotes srd -\end_inset +\end_inset genannt) oder bei RSA-Schlüssel (z.B. aus X.509 Zertifikaten). -\layout Standard +\end_layout +\begin_layout Standard \lang english Momentan stehen (für Linux) zwei verschiedene IKE-Daemons zur Verfügung, die aber sich ziemlich in Konfiguration und Benutzung unterscheiden. -\layout Standard +\end_layout +\begin_layout Standard \lang english Ich präferiere \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset von der *S/WAN Implementierung, wei dieser eine überschaubare (und nur eine) Konfiguration. -\layout Subsection +\end_layout +\begin_layout Subsection \lang english IKE-Daemon \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard \lang english Der IKE-Daemon \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset ist vom KAME-Project und auf Linux portiert worden. Aktuelle Linux-Distributionen beinhalten diesen Daemon im Paket \begin_inset Quotes sld -\end_inset +\end_inset ipsec-tools \begin_inset Quotes srd -\end_inset +\end_inset . Zwei Programme sind für ein funktionierendes IPsec-Setup notwendig. Siehe dazu auch das \begin_inset LatexCommand \url[Linux Advanced Routing & Traffic Control HOWTO / IPSEC]{http://lartc.org/howto/lartc.ipsec.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Manipulation der IPsec SA/SP Datenbank mit dem Werkzeug \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard \lang english - \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset ist für die Definition der Security Policy (SP) im Kernel wichtig. -\layout Standard +\end_layout +\begin_layout Standard \lang english Datei: /etc/racoon/setkey.sh -\layout Itemize +\end_layout +\begin_layout Itemize \lang english Beispiel für eine Ende-zu-Ende verschlüsselte Verbindung im Transport-Modus -\layout Code +\end_layout +\begin_layout Code \lang english #!/sbin/setkey -f -\layout Code +\end_layout +\begin_layout Code \lang english flush; -\layout Code +\end_layout +\begin_layout Code \lang english spdflush; -\layout Code +\end_layout +\begin_layout Code \lang english spdadd 2001:db8:1:1::1 2001:db8:2:2::2 any -P out ipsec esp/transport//require; -\layout Code +\end_layout +\begin_layout Code \lang english spdadd 2001:db8:2:2::2 2001:db8:1:1::1 any -P in ipsec esp/transport//require; -\layout Code +\end_layout -\layout Itemize +\begin_layout Code +\end_layout + +\begin_layout Itemize \lang english Beispiel für eine Ende-zu-Ende verschlüsselte Verbindung im Tunnel-Modus -\layout Code +\end_layout +\begin_layout Code \lang english #!/sbin/setkey -f -\layout Code +\end_layout +\begin_layout Code \lang english flush; -\layout Code +\end_layout +\begin_layout Code \lang english spdflush; -\layout Code +\end_layout +\begin_layout Code \lang english spdadd 2001:db8:1:1::1 2001:db8:2:2::2 any -P out ipsec -\layout Code +\end_layout +\begin_layout Code \lang english ¬ esp/tunnel/2001:db8:1:1::1-2001:db8:2:2::2/require; -\layout Code +\end_layout +\begin_layout Code \lang english spdadd 2001:db8:2:2::2 2001:db8:1:1::1 any -P in ipsec -\layout Code +\end_layout +\begin_layout Code \lang english ¬ esp/tunnel/2001:db8:2:2::2-2001:db8:1:1::1/require; -\layout Standard +\end_layout +\begin_layout Standard \lang english Beim anderen Partner ist \begin_inset Quotes sld -\end_inset +\end_inset in \begin_inset Quotes srd -\end_inset +\end_inset mit \begin_inset Quotes sld -\end_inset +\end_inset out \begin_inset Quotes srd -\end_inset +\end_inset zu vertauschen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Konfiguration des IKE-Daemon \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard \lang english - \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset benötigt eine Konfigurationsdatei zur Ausführung. Es beinhaltet zu der Security Policy entprechenden Einstellungen, welche vorher mit \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset definiert wurde. -\layout Standard +\end_layout +\begin_layout Standard \lang english Datei: /etc/racoon/racoon.conf -\layout Code +\end_layout +\begin_layout Code \lang english # Racoon IKE daemon configuration file. -\layout Code +\end_layout +\begin_layout Code \lang english # See 'man racoon.conf' for a description of the format and entries. -\layout Code +\end_layout +\begin_layout Code \lang english path include "/etc/racoon"; -\layout Code +\end_layout +\begin_layout Code \lang english path pre_shared_key "/etc/racoon/psk.txt"; -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english listen -\layout Code +\end_layout +\begin_layout Code \lang english { -\layout Code +\end_layout +\begin_layout Code \lang english isakmp 2001:db8:1:1::1; -\layout Code +\end_layout +\begin_layout Code \lang english } -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english remote 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code \lang english { -\layout Code +\end_layout +\begin_layout Code \lang english exchange_mode main; -\layout Code +\end_layout +\begin_layout Code \lang english lifetime time 24 hour; -\layout Code +\end_layout +\begin_layout Code \lang english proposal -\layout Code +\end_layout +\begin_layout Code \lang english { -\layout Code +\end_layout +\begin_layout Code \lang english encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code \lang english hash_algorithm md5; -\layout Code +\end_layout +\begin_layout Code \lang english authentication_method pre_shared_key; -\layout Code +\end_layout +\begin_layout Code \lang english dh_group 2; -\layout Code +\end_layout +\begin_layout Code \lang english } -\layout Code +\end_layout +\begin_layout Code \lang english } -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english # gateway-to-gateway -\layout Code +\end_layout +\begin_layout Code \lang english sainfo address 2001:db8:1:1::1 any address 2001:db8:2:2::2 any -\layout Code +\end_layout +\begin_layout Code \lang english { -\layout Code +\end_layout +\begin_layout Code \lang english lifetime time 1 hour; -\layout Code +\end_layout +\begin_layout Code \lang english encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code \lang english authentication_algorithm hmac_md5; -\layout Code +\end_layout +\begin_layout Code \lang english compression_algorithm deflate; -\layout Code +\end_layout +\begin_layout Code \lang english } -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english sainfo address 2001:db8:2:2::2 any address 2001:db8:1:1::1 any -\layout Code +\end_layout +\begin_layout Code \lang english { -\layout Code +\end_layout +\begin_layout Code \lang english lifetime time 1 hour; -\layout Code +\end_layout +\begin_layout Code \lang english encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code \lang english authentication_algorithm hmac_md5; -\layout Code +\end_layout +\begin_layout Code \lang english compression_algorithm deflate; -\layout Code +\end_layout +\begin_layout Code \lang english } -\layout Standard +\end_layout +\begin_layout Standard \lang english Zudem muss das gemeinsame Geheimnis definiert werden: -\layout Standard +\end_layout +\begin_layout Standard \lang english Datei: /etc/racoon/psk.txt -\layout Code +\end_layout +\begin_layout Code \lang english # file for pre-shared keys used for IKE authentication -\layout Code +\end_layout +\begin_layout Code \lang english # format is: 'identifier' 'key' -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english 2001:db8:2:2::2 verysecret -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english IPsec mit IKE-Daemon \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset starten -\layout Standard +\end_layout +\begin_layout Standard \lang english Zum Schluss muss der Daemon gestartet werden. Beim ersten Mal sollte Debug- & Vordergrund-Modus aktiviert werden. Das folgende Beispiel zeigt eine erfolgreiche Aushandlung von IKE-Phase 1 (ISAKMP-SA) und 2 (IPsec-SA): -\layout Code +\end_layout +\begin_layout Code \lang english # racoon -F -v -f /etc/racoon/racoon.conf -\layout Code +\end_layout +\begin_layout Code \lang english Foreground mode. -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:30:15: INFO: @(#)ipsec-tools 0.3.3 (http://ipsec-tools.sourceforge.net ) -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:30:15: INFO: @(#)This product linked -\layout Code +\end_layout +\begin_layout Code \lang english ¬ OpenSSL 0.9.7a Feb 19 2003 (http://www.openssl.org/) -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:30:15: INFO: 2001:db8:1:1::1[500] used as isakmp port (fd=7) -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:31:06: INFO: IPsec-SA request for 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code \lang english ¬ queued due to no phase1 found. -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:31:06: INFO: initiate new phase 1 negotiation: -\layout Code +\end_layout +\begin_layout Code \lang english ¬ 2001:db8:1:1::1[500]<=>2001:db8:2:2::2[500] -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:31:06: INFO: begin Identity Protection mode. -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:31:09: INFO: ISAKMP-SA established -\layout Code +\end_layout +\begin_layout Code \lang english ¬ 2001:db8:1:1::1[500]-2001:db8:2:2::2[500] spi:da3d3693289c9698:ac039a402b2db40 1 -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:31:09: INFO: initiate new phase 2 negotiation: -\layout Code +\end_layout +\begin_layout Code \lang english ¬ 2001:6f8:900:94::2[0]<=>2001:db8:2:2::2[0] -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:31:10: INFO: IPsec-SA established: -\layout Code +\end_layout +\begin_layout Code \lang english ¬ ESP/Tunnel 2001:db8:2:2::2->2001:db8:1:1::1 spi=253935531(0xf22bfab) -\layout Code +\end_layout +\begin_layout Code \lang english 2005-01-01 20:31:10: INFO: IPsec-SA established: -\layout Code +\end_layout +\begin_layout Code \lang english ¬ ESP/Tunnel 2001:db8:1:1::1->2001:db8:2:2::2 spi=175002564(0xa6e53c4) -\layout Standard +\end_layout +\begin_layout Standard \lang english Jede Richtung bekommt einen eigenen SPI (wie im IPsec-Standard definiert). Mit \begin_inset Quotes sld -\end_inset +\end_inset tcpdump \begin_inset Quotes srd -\end_inset +\end_inset kann an der entprechenden Schnittstelle dann das Ergebnis eines IPv6-pings gesehen werden: -\layout Code +\end_layout +\begin_layout Code \lang english 20:35:55.305707 2001:db8:1:1::1 > 2001:db8:2:2::2: ESP(spi=0x0a6e53c4,seq=0x3) -\layout Code +\end_layout +\begin_layout Code \lang english 20:35:55.537522 2001:db8:2:2::2 > 2001:db8:1:1::1: ESP(spi=0x0f22bfab,seq=0x3) -\layout Standard +\end_layout +\begin_layout Standard \lang english Wie erwartet, werden die ausgehandelten SPIs angezeigt. -\layout Standard +\end_layout +\begin_layout Standard \lang english Mit \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset werden die aktiven Parameter angezeigt: -\layout Code +\end_layout +\begin_layout Code \lang english # setkey -D -\layout Code +\end_layout +\begin_layout Code \lang english 2001:db8:1:1::1 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code \lang english esp mode=tunnel spi=175002564(0x0a6e53c4) reqid=0(0x00000000) -\layout Code +\end_layout +\begin_layout Code \lang english E: 3des-cbc bd26bc45 aea0d249 ef9c6b89 7056080f 5d9fa49c 924e2edd -\layout Code +\end_layout +\begin_layout Code \lang english A: hmac-md5 60c2c505 517dd8b7 c9609128 a5efc2db -\layout Code +\end_layout +\begin_layout Code \lang english seq=0x00000000 replay=4 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code \lang english created: Jan 1 20:31:10 2005 current: Jan 1 20:40:47 2005 -\layout Code +\end_layout +\begin_layout Code \lang english diff: 577(s) hard: 3600(s) soft: 2880(s) -\layout Code +\end_layout +\begin_layout Code \lang english last: Jan 1 20:35:05 2005 hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code \lang english current: 540(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code \lang english allocated: 3 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code \lang english sadb_seq=1 pid=22358 refcnt=0 -\layout Code +\end_layout +\begin_layout Code \lang english 2001:db8:2:2::2 2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code \lang english esp mode=tunnel spi=253935531(0x0f22bfab) reqid=0(0x00000000) -\layout Code +\end_layout +\begin_layout Code \lang english E: 3des-cbc c1ddba65 83debd62 3f6683c1 20e747ac 933d203f 4777a7ce -\layout Code +\end_layout +\begin_layout Code \lang english A: hmac-md5 3f957db9 9adddc8c 44e5739d 3f53ca0e -\layout Code +\end_layout +\begin_layout Code \lang english seq=0x00000000 replay=4 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code \lang english created: Jan 1 20:31:10 2005 current: Jan 1 20:40:47 2005 -\layout Code +\end_layout +\begin_layout Code \lang english diff: 577(s) hard: 3600(s) soft: 2880(s) -\layout Code +\end_layout +\begin_layout Code \lang english last: Jan 1 20:35:05 2005 hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code \lang english current: 312(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code \lang english allocated: 3 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code \lang english sadb_seq=0 pid=22358 refcnt=0 -\layout Subsection +\end_layout +\begin_layout Subsection \lang english IKE-Daemon \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard \lang english Der IKE-Daemon \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset ist in den Paketen der *S/WAN-Projekte beinhaltet. Das *S/WAN-Projekt startete zu Anfags als \begin_inset LatexCommand \url[FreeS/WAN]{http://www.freeswan.org/} -\end_inset +\end_inset . Leider wurde die Weiterentwicklung von FreeS/WAN in 2004 eingestellt. @@ -9809,1010 +11935,1228 @@ pluto entstanden zwei Spin-Offs: \begin_inset LatexCommand \url[strongSwan]{http://www.strongswan.org/} -\end_inset +\end_inset und \begin_inset LatexCommand \url[Openswan]{http://www.openswan.org/} -\end_inset +\end_inset . Heutzutage stehen installationsfertige Pakete bereit, u.a. von Openswan (in Fedora Core 3 beinhaltet). -\layout Standard +\end_layout +\begin_layout Standard \lang english Ein großer Unterschied zu \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset ist, dass nur eine Konfigurationsdatei notwendig ist. Zudem steht ein initscript für automatisches Starten beim Booten zur Verfügung. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Konfiguration des IKE-Daemon \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard \lang english Die Konfiguration ist der zu IPv4 sehr ähnlich, nur eine wichtige Option ist notwendig. -\layout Standard +\end_layout +\begin_layout Standard \lang english Datei: /etc/ipsec.conf -\layout Code +\end_layout +\begin_layout Code \lang english # /etc/ipsec.conf - Openswan IPsec configuration file -\layout Code +\end_layout +\begin_layout Code \lang english # -\layout Code +\end_layout +\begin_layout Code \lang english # Manual: ipsec.conf.5 -\layout Code +\end_layout +\begin_layout Code \lang english version 2.0 # conforms to second version of ipsec.conf specification -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english # basic configuration -\layout Code +\end_layout +\begin_layout Code \lang english config setup -\layout Code +\end_layout +\begin_layout Code \lang english # Debug-logging controls: "none" for (almost) none, "all" for lots. -\layout Code +\end_layout +\begin_layout Code \lang english # klipsdebug=none -\layout Code +\end_layout +\begin_layout Code \lang english # plutodebug="control parsing" -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english #Disable Opportunistic Encryption -\layout Code +\end_layout +\begin_layout Code \lang english include /etc/ipsec.d/examples/no_oe.conf -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english conn ipv6-p1-p2 -\layout Code +\end_layout +\begin_layout Code \lang english connaddrfamily=ipv6 # Important for IPv6! -\layout Code +\end_layout +\begin_layout Code \lang english left=2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code \lang english right=2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code \lang english authby=secret -\layout Code +\end_layout +\begin_layout Code \lang english esp=aes128-sha1 -\layout Code +\end_layout +\begin_layout Code \lang english ike=aes128-sha-modp1024 -\layout Code +\end_layout +\begin_layout Code \lang english type=transport -\layout Code +\end_layout +\begin_layout Code \lang english #type=tunnel -\layout Code +\end_layout +\begin_layout Code \lang english compress=no -\layout Code +\end_layout +\begin_layout Code \lang english #compress=yes -\layout Code +\end_layout +\begin_layout Code \lang english auto=add -\layout Code +\end_layout +\begin_layout Code \lang english #auto=start -\layout Code +\end_layout -\layout Standard +\begin_layout Code +\end_layout + +\begin_layout Standard \lang english Zudem muss das gemeinsame Geheimnis definiert werden: -\layout Standard +\end_layout +\begin_layout Standard \lang english Datei: /etc/ipsec.secrets -\layout Code +\end_layout +\begin_layout Code \lang english 2001:db8:1:1::1 2001:db8:2:2::2 : PSK "verysecret" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english IPsec mit IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset starten -\layout Standard +\end_layout +\begin_layout Standard \lang english Wenn die Installation von Openswan erfolgreich war, sollte ein initscript zum Starten von IPsec zur Verfügung stehen. Dann einfach auf jedem Partner folgendes ausführen: -\layout Code +\end_layout +\begin_layout Code \lang english # /etc/rc.d/init.d/ipsec start -\layout Standard +\end_layout +\begin_layout Standard \lang english Danach kann die Verbindung auf einem Partner gestartet werden. Wenn im folgenden die Zeile \begin_inset Quotes sld -\end_inset +\end_inset IPsec SA established \begin_inset Quotes srd -\end_inset +\end_inset erscheint, hat die Aushandlung funktioniert. -\layout Code +\end_layout +\begin_layout Code \lang english # ipsec auto --up ipv6-peer1-peer2 -\layout Code +\end_layout +\begin_layout Code \lang english 104 "ipv6-p1-p2" #1: STATE_MAIN_I1: initiate -\layout Code +\end_layout +\begin_layout Code \lang english 106 "ipv6-p1-p2" #1: STATE_MAIN_I2: sent MI2, expecting MR2 -\layout Code +\end_layout +\begin_layout Code \lang english 108 "ipv6-p1-p2" #1: STATE_MAIN_I3: sent MI3, expecting MR3 -\layout Code +\end_layout +\begin_layout Code \lang english 004 "ipv6-p1-p2" #1: STATE_MAIN_I4: ISAKMP SA established -\layout Code +\end_layout +\begin_layout Code \lang english 112 "ipv6-p1-p2" #2: STATE_QUICK_I1: initiate -\layout Code +\end_layout +\begin_layout Code \lang english 004 "ipv6-p1-p2" #2: STATE_QUICK_I2: sent QI2, -\layout Code +\end_layout +\begin_layout Code \lang english ¬ IPsec SA established {ESP=>0xa98b7710 <0xa51e1f22} -\layout Standard +\end_layout +\begin_layout Standard \lang english Weil *S/WAN und setkey/racoon die gleiche IPsec-Implementation im Linux kernel 2.6.x benutzen, zeigt \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset auch hier die aktiven Parameter: -\layout Code +\end_layout +\begin_layout Code \lang english # setkey -D -\layout Code +\end_layout +\begin_layout Code \lang english 2001:db8:1:1::1 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code \lang english esp mode=transport spi=2844489488(0xa98b7710) reqid=16385(0x00004001) -\layout Code +\end_layout +\begin_layout Code \lang english E: aes-cbc 082ee274 2744bae5 7451da37 1162b483 -\layout Code +\end_layout +\begin_layout Code \lang english A: hmac-sha1 b7803753 757417da 477b1c1a 64070455 ab79082c -\layout Code +\end_layout +\begin_layout Code \lang english seq=0x00000000 replay=64 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code \lang english created: Jan 1 21:16:32 2005 current: Jan 1 21:22:20 2005 -\layout Code +\end_layout +\begin_layout Code \lang english diff: 348(s) hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code \lang english last: hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code \lang english current: 0(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code \lang english allocated: 0 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code \lang english sadb_seq=1 pid=23825 refcnt=0 -\layout Code +\end_layout +\begin_layout Code \lang english 2001:db8:2:2::2 2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code \lang english esp mode=transport spi=2770214690(0xa51e1f22) reqid=16385(0x00004001) -\layout Code +\end_layout +\begin_layout Code \lang english E: aes-cbc 6f59cc30 8d856056 65e07b76 552cac18 -\layout Code +\end_layout +\begin_layout Code \lang english A: hmac-sha1 c7c7d82b abfca8b1 5440021f e0c3b335 975b508b -\layout Code +\end_layout +\begin_layout Code \lang english seq=0x00000000 replay=64 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code \lang english created: Jan 1 21:16:31 2005 current: Jan 1 21:22:20 2005 -\layout Code +\end_layout +\begin_layout Code \lang english diff: 349(s) hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code \lang english last: hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code \lang english current: 0(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code \lang english allocated: 0 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code \lang english sadb_seq=0 pid=23825 refcnt=0 -\layout Section +\end_layout +\begin_layout Section \lang english Anmerkungen: -\layout Standard +\end_layout +\begin_layout Standard \lang english Bei Linux Kernel 2.6.x kann der IPsec-Status und die Policy auch mit \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset angezeigt werden: -\layout Code +\end_layout +\begin_layout Code \lang english # ip xfrm policy -\layout Code +\end_layout +\begin_layout Code \lang english ... -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code \lang english # ip xfrm state -\layout Code +\end_layout +\begin_layout Code \lang english ... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-qos} -\end_inset +\end_inset Quality of Service (QoS) -\layout Standard +\end_layout +\begin_layout Standard IPv6 unterstützt QoS durch die Anwendung von Flow Labels und Traffic Classes. QoS kann mittels \begin_inset Quotes sld -\end_inset +\end_inset tc \begin_inset Quotes srd -\end_inset +\end_inset (im Paket \begin_inset Quotes sld -\end_inset +\end_inset iproute \begin_inset Quotes srd -\end_inset +\end_inset enthalten) kontrolliert werden. -\layout Standard +\end_layout +\begin_layout Standard Zusätzliche Infos: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[RFC 3697 / IPv6 Flow Label Specification]{http://www.faqs.org/rfcs/rfc3697.html} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos hierzu in späteren Versionen. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-hints-daemons} -\end_inset +\end_inset Hinweise zu IPv6 kompatiblen Daemons -\layout Standard +\end_layout +\begin_layout Standard Im folgenden Kapitel werden einige Hinweise zu IPv6 kompatiblen Daemons gegeben. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-bind} -\end_inset +\end_inset Berkeley Internet Name Daemon BIND (named) -\layout Standard +\end_layout +\begin_layout Standard Seit der Version 9 wird IPv6 unterstützt. Setzen Sie immer die neuest verfügbare Version ein. Zumindest muss Version 9.1.3 eingesetzt werden, da ältere Versionen Sicherheitslö cher beinhalten können, die von Remote entsprechend ausgenutzt werden können. -\layout Subsection +\end_layout +\begin_layout Subsection Auf IPv6 Adressen hören -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Im Gegensatz zu IPv4 können bei aktuellen Versionen Server Sockets nicht an dedizierte IPv6 Adressen gebunden werden, es ist folglich -\emph on +\emph on jede -\emph default +\emph default oder -\emph on +\emph on keine -\emph default +\emph default Adresse gültig. Da dies ein Sicherheitsproblem sein kann, lesen Sie diesbezüglich ebenfalls den Abschnitt Access Control Lists (ACL) weiter unten! -\layout Subsubsection +\end_layout +\begin_layout Subsubsection BIND named konfigurieren, damit er auf IPv6 Adressen antwortet -\layout Standard +\end_layout +\begin_layout Standard Folgende Optionen müssen geändert werden, damit IPv6 aktiviert wird -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # sure other options here, too -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { any; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Nach einem Neustart (des Dienstes) sollte z.B. Folgendes zu sehen sein: -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu |grep "named -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::53 :::* LISTEN 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming TCP requests -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.4:53 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP requests to IPv4 1.2.3.4 -\layout Code +\end_layout +\begin_layout Code udp 0 0 127.0.0.1:53 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP requests to IPv4 localhost -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32868 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # dynamic chosen port for outgoing queries -\layout Code +\end_layout +\begin_layout Code udp 0 0 :::53 :::* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP request to any IPv6 -\layout Standard +\end_layout +\begin_layout Standard Ein kleiner Test sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code # dig localhost @::1 -\layout Standard +\end_layout +\begin_layout Standard und sollte Ihnen ein Ergebnis anzeigen... -\layout Subsubsection +\end_layout +\begin_layout Subsubsection BIND named konfigurieren, damit er auf IPv6 Adressen nicht antwortet -\layout Standard +\end_layout +\begin_layout Standard Folgende Optionen müssen geändert werden, damit IPv6 deaktiviert wird: -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # sure other options here, too -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { none; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Subsection +\end_layout +\begin_layout Subsection Access Control Lists (ACL) mit IPv6 Unterstützung -\layout Standard +\end_layout +\begin_layout Standard ACLs mit IPv6 Adressen sind realisierbar und sollten wann immer möglich eingesetzt werden. Ein Beispiel: -\layout Code +\end_layout +\begin_layout Code acl internal-net { -\layout Code +\end_layout +\begin_layout Code 127.0.0.1; -\layout Code +\end_layout +\begin_layout Code 1.2.3.0/24; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::/56; -\layout Code +\end_layout +\begin_layout Code ::1/128; -\layout Code +\end_layout +\begin_layout Code ::ffff:1.2.3.4/128; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code acl ns-internal-net { -\layout Code +\end_layout +\begin_layout Code 1.2.3.4; -\layout Code +\end_layout +\begin_layout Code 1.2.3.5; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::4/128; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::5/128; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Diese ACLs können für Client-Anfragen und Zonentransfers zu Secondary Nameserver eingesetzt werden. Es kann auch unterbunden werden, dass ihr Caching-Nameserver mittels IPv6 von der Außenwelt verwendet wird. -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # sure other options here, too -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { none; }; -\layout Code +\end_layout +\begin_layout Code allow-query { internal-net; }; -\layout Code +\end_layout +\begin_layout Code allow-transfer { ns-internal-net; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Es ist ebenfalls möglich, dass die Optionen -\emph on +\emph on allow-query -\emph default +\emph default und -\emph on +\emph on allow-transfer -\emph default +\emph default bei den meisten Single-Zonen-Definitionen verwendet werden. -\layout Subsection +\end_layout +\begin_layout Subsection Anfragen mit festen IPv6 Adressen senden -\layout Standard +\end_layout +\begin_layout Standard Diese Option ist nicht verpflichtend, ev. aber benötigt: -\layout Code +\end_layout +\begin_layout Code query-source-v6 address port ; -\layout Subsection +\end_layout +\begin_layout Subsection Pro Zone definierte feste IPv6 Adressen -\layout Standard +\end_layout +\begin_layout Standard Es ist möglich pro Zone mehrere IPv6 Adressen zu definieren. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Transfer source Adresse -\layout Standard +\end_layout +\begin_layout Standard Die Transfer source Adresse wird für ausgehende Zonentransfers verwendet: -\layout Code +\end_layout +\begin_layout Code transfer-source-v6 [port port]; -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Notify source Adresse -\layout Standard +\end_layout +\begin_layout Standard Die Notify source Adresse wird für ausgehende notify Mitteilungen verwendet: -\layout Code +\end_layout +\begin_layout Code notify-source-v6 [port port]; -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 DNS zone files Beispiele -\layout Standard +\end_layout +\begin_layout Standard Einige Informationen finden Sie auch unter \begin_inset LatexCommand \url[IPv6 DNS Setup Information (article)]{http://www.isi.edu/~bmanning/v6DNS.html} -\end_inset +\end_inset . Eventuell ebenfalls hilfreich ist folgendes Tool: \begin_inset LatexCommand \url[IPv6 Reverse DNS zone builder for BIND 8/9 (webtool)]{http://tools.fpsn.net/ipv6-inaddr/} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 bezogene DNS-Daten bereitstellen -\layout Standard +\end_layout +\begin_layout Standard Für IPv6 wurden neue Reverse Lookup Arten und Root Zonen definiert: -\layout Itemize +\end_layout +\begin_layout Itemize AAAA und reverse IP6.INT: beschrieben in \begin_inset LatexCommand \url[RFC 1886 / DNS Extensions to support IP version 6]{http://www.faqs.org/rfcs/rfc1886.html} -\end_inset +\end_inset sowie seit BIND Version 4.9.6 in Verwendung -\layout Itemize +\end_layout +\begin_layout Itemize A6, DNAME (WURDE ABGELEHNT!) und reverse IP6.ARPA: beschrieben in \begin_inset LatexCommand \url[RFC 2874 / DNS Extensions to Support IPv6 Address Aggregation and Renumbering]{http://www.faqs.org/rfcs/rfc2874.html} -\end_inset +\end_inset sowie seit BIND 9 in Verwendung. Informationen zum aktuellen Stand sind unter \begin_inset LatexCommand \url[draft-ietf-dnsext-ipv6-addresses-00.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset zu finden. -\layout Standard +\end_layout +\begin_layout Standard Mehr Inhalt zu diesem Thema wird eventuell in späteren Versionen eingearbeitet, inzwischen können Sie in den RFCs und in folgenden Quellen nachlesen: -\layout Itemize +\end_layout +\begin_layout Itemize AAAA und reverse IP6.INT: \begin_inset LatexCommand \url[IPv6 DNS Setup Information]{http://www.isi.edu/~bmanning/v6DNS.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize A6, DNAME (WURDE ABGELEHNT!) und reverse IP6.ARPA: lesen Sie im Kapitel 4 und 6 des BIND 9 Administrator Reference Manual (ARM) nach, welches mit dem bind-Paket mitgeliefert wird. Sie können es auch hier bekommen: \begin_inset LatexCommand \url[BIND version 9 ARM (PDF)]{http://www.nominum.com/content/documents/bind9arm.pdf} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Da IP6.INT (ebenfalls) ABGELEHNT WURDE, (jedoch nach wie vor in Verwendung ist,) muss ein DNS Server, der IPv6 Informationen anbieten will, beide reverse Zonen bereitstellen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Aktuell beste Praxis -\layout Standard +\end_layout +\begin_layout Standard Da es mit den neuen Formaten noch Probleme gibt, ist die aktuell beste Praxis: -\layout Standard +\end_layout +\begin_layout Standard Vorwärts-Auflösung mit: -\layout Itemize +\end_layout +\begin_layout Itemize AAAA -\layout Standard +\end_layout +\begin_layout Standard Rückwärts-Auflösung mit: -\layout Itemize +\end_layout +\begin_layout Itemize Reverse nibble format für die Zone ip6.int (FÜR RÜCKWÄRTSKOMPATIBILITÄT) -\layout Itemize +\end_layout +\begin_layout Itemize Reverse nibble format für die Zone ip6.arpa (EMPFHOHLEN) -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 Verbindung überprüfen -\layout Standard +\end_layout +\begin_layout Standard Ob BIND auf einen IPv6 socket hört bzw. IPv6 Daten bereitstellt, können Sie anhand folgender Beispiele überprüfen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 Verbindung durch ACL abgelehnt -\layout Standard +\end_layout +\begin_layout Standard Eine IPv6 Verbindung kann durch Angabe eines dedizierten Server, der abgefragt werden soll, erzwungen werden: -\layout Code +\end_layout +\begin_layout Code $ host -t aaaa www.6bone.net 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Using domain server: -\layout Code +\end_layout +\begin_layout Code Name: 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Address: 3ffe:ffff:200:f101::1#53 -\layout Code +\end_layout +\begin_layout Code Aliases: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code Host www.6bone.net. not found: 5(REFUSED) -\layout Standard +\end_layout +\begin_layout Standard Ein entsprechender Log-Eintrag sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code Jan 3 12:43:32 gate named[12347]: client -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:200:f101:212:34ff:fe12:3456#32770: -\layout Code +\end_layout +\begin_layout Code query denied -\layout Standard +\end_layout +\begin_layout Standard Wenn Sie diesen Eintrag in der Logdatei finden, prüfen Sie, ob von diesem Client Anfragen akzeptiert werden sollen und ggf. ändern Sie Ihre ACL Konfiguration. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Erfolgreiche IPv6 Verbindung -\layout Standard +\end_layout +\begin_layout Standard Eine erfolgreiche IPv6 Verbindung sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code $ host -t aaaa www.6bone.net 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Using domain server: -\layout Code +\end_layout +\begin_layout Code Name: 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Address: 3ffe:ffff:200:f101::1#53 -\layout Code +\end_layout +\begin_layout Code Aliases: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code www.6bone.net. is an alias for 6bone.net. -\layout Code +\end_layout +\begin_layout Code 6bone.net. has AAAA address 3ffe:b00:c18:1::10 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-xinetd} -\end_inset +\end_inset Internet super daemon (xinetd) -\layout Standard +\end_layout +\begin_layout Standard IPv6 wird ungefähr seit der \begin_inset LatexCommand \url[xinetd]{http://www.xinetd.org/} -\end_inset +\end_inset Version 1.8.9 unterstützt. Verwenden sie immer die neueste Version, zumindest aber Version 2.3.3, da ältere Versionen Sicherheitslöcher beinhalten können, die von Remote entspreche nd ausgenutzt werden können. -\layout Standard +\end_layout +\begin_layout Standard Einige Linux Distributionen beinhalten ein separates IPv6 kompatibles Paket des xinetd, bei anderen Distributionen wird der IPv6 kompatible xinetd mit folgender Variable zumeist in der Datei /etc/sysconfig/network (bei Red Hat kompatible Distributionen) gestartet: NETWORKING_IPV6="yes". In neuere Versionen unterstützt eine Binärdatei sowohl IPv4 als auch IPv6. -\layout Standard +\end_layout +\begin_layout Standard Wenn Sie nun einen "eingebauten" Service wie z.B. daytime durch folgende Änderung der Konfigurationsdatei /etc/xinetd.d/daytime aktivieren -\layout Code +\end_layout +\begin_layout Code # diff -u /etc/xinetd.d/daytime.orig /etc/xinetd.d/daytime -\layout Code +\end_layout +\begin_layout Code --- /etc/xinetd.d/daytime.orig Sun Dec 16 19:00:14 2001 -\layout Code +\end_layout +\begin_layout Code +++ /etc/xinetd.d/daytime Sun Dec 16 19:00:22 2001 -\layout Code +\end_layout +\begin_layout Code @@ -10,5 +10,5 @@ -\layout Code +\end_layout +\begin_layout Code protocol = tcp -\layout Code +\end_layout +\begin_layout Code user = root -\layout Code +\end_layout +\begin_layout Code wait = no -\layout Code +\end_layout +\begin_layout Code - disable = yes -\layout Code +\end_layout +\begin_layout Code + disable = no -\layout Code +\end_layout +\begin_layout Code } -\layout Standard +\end_layout +\begin_layout Standard dann sollten Sie nach einem Neustart des xinetd-Dienstes z.B. folgendes positive Ergebnis sehen: -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu -A inet6 |grep "xinetd*" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:192.168.1.1:993 :::* LISTEN 12345/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::13 :::* LISTEN 12345/xinetd-ipv6 <- service -\layout Code +\end_layout +\begin_layout Code ¬ daytime/tcp -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:192.168.1.1:143 :::* LISTEN 12345/xinetd-ipv6 -\layout Standard +\end_layout +\begin_layout Standard Das Beispiel zeigt auch die xinetd Dienste IMAP und IMAP-SSL, die nur auf IPv4 Adressen hören. -\layout Standard +\end_layout +\begin_layout Standard \lang english Hinweis: frühere Versionen hatten ein Problem, dass der nur für IPv4 kompilierte xinetd nicht bei einem IPv6-aktivierten Knoten startete, und eine IPv6-aktivier te nicht bei einem Knoten, der nur IPv4 aktiv hatte. Dies sollte aber mindestens seit Version 2.3.11 gefixt sein. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-apache2} -\end_inset +\end_inset Webserver Apache2 (httpd2) -\layout Standard +\end_layout +\begin_layout Standard IPv6 wird beim Apache Webserver durch die Entwickler seit der Version 2.0.14 unterstützt. Verfügbare Patches für die alte 1.3.x Serie sind inzwischen nicht mehr aktuell @@ -10821,94 +13165,117 @@ IPv6 wird beim Apache Webserver durch die Entwickler seit der Version 2.0.14 Verfügbar sind die Patches noch unter \begin_inset LatexCommand \url[KAME / Misc]{ftp://ftp.kame.net/pub/kame/misc/} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Auf IPv6 Adressen hören -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Virtuelle Hosts mit IPv6 Adressen sind bis zur Version 2.0.28 nicht operabel (es gibt für die Version 2.0.28 einen Patch). Testen Sie aber immer zuerst die neueste Version, da ältere Versionen mitunter auch Sicherheitsprobleme mit sich bringen können. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Virtueller Host mit IPv6 Adresse -\layout Code +\end_layout +\begin_layout Code Listen [3ffe:ffff:100::1]:80 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code ServerName ipv6only.yourdomain.yourtopleveldomain -\layout Code +\end_layout +\begin_layout Code # ...sure more config lines -\layout Code +\end_layout +\begin_layout Code -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Virtueller Host mit IPv4 und IPv6 Adresse -\layout Code +\end_layout +\begin_layout Code Listen [3ffe:ffff:100::2]:80 -\layout Code +\end_layout +\begin_layout Code Listen 1.2.3.4:80 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code ServerName ipv6andipv4.yourdomain.yourtopleveldomain -\layout Code +\end_layout +\begin_layout Code # ...sure more config lines -\layout Code +\end_layout +\begin_layout Code -\layout Standard +\end_layout +\begin_layout Standard Das Ergebnis sollten nach einen Neustart des Dienstes etwa Folgendes sein: -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu |grep "httpd2 -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.4:80 0.0.0.0:* LISTEN 12345/httpd2 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 3ffe:ffff:100::1:80 :::* LISTEN 12345/httpd2 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 3ffe:ffff:100::2:80 :::* LISTEN 12345/httpd2 -\layout Standard +\end_layout +\begin_layout Standard Für einfache Tests können Sie auf das bereits gezeigte telnet-Beispiel zurückgre ifen. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Zusätzliche Anmerkungen -\layout Standard +\end_layout +\begin_layout Standard \lang english Apache2 unterstützt eine Methode namens \begin_inset Quotes sld -\end_inset +\end_inset sendfile \begin_inset Quotes srd -\end_inset +\end_inset , um die Auslieferung von Datenn zu beschleunigen. Einige NIC-Treiber unterstützen auch offline das Berechnen der Checksumme. @@ -10916,126 +13283,154 @@ sendfile men führen. In diesen Fällen ist \begin_inset Quotes sld -\end_inset +\end_inset sendfile \begin_inset Quotes srd -\end_inset +\end_inset zu deaktivieren, entweder durch Rekompilieren unter der Benützung der configure -Option \begin_inset Quotes sld -\end_inset +\end_inset --without-sendfile \begin_inset Quotes srd -\end_inset +\end_inset oder durch Benützung der Direktive "EnableSendfile off" in der Konfigurationsda tei. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-radvd} -\end_inset +\end_inset Router Advertisement Daemon (radvd) -\layout Standard +\end_layout +\begin_layout Standard Der Router Advertisement Daemon ist auf einem LAN dann sehr sinnvoll, wenn die Clients automatisch konfiguriert werden sollen. Der Daemon selbst sollte auf einem Linux Gateway Router eingerichtet sein (es hat nicht notwendigerweise das default IPv4 Gateway zu sein, Vorsicht also wer am LAN Router Advertisements versendet). -\layout Standard +\end_layout +\begin_layout Standard Sie können einige Flags und Informationen im Advertisement spezifizieren. Allgemein werden verwendet: -\layout Itemize +\end_layout +\begin_layout Itemize Präfix (notwendige Angabe) -\layout Itemize +\end_layout +\begin_layout Itemize Lebensdauer des Präfix -\layout Itemize +\end_layout +\begin_layout Itemize Intervall der Advertisements (optional) -\layout Standard +\end_layout +\begin_layout Standard Nach der korrekten Konfiguration sendet der Daemon die Advertisements über angegebene Interfaces. Die Clients empfangen die Advertisements und konfigurieren automatisch Ihre Adressen mit dem empfangenen Präfix und der Default-Route. -\layout Subsection +\end_layout +\begin_layout Subsection radvd konfigurieren -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Einfache Konfiguration -\layout Standard +\end_layout +\begin_layout Standard Die Konfigurationsdatei des radvd ist normalerweise die Datei /etc/radvd.conf. Eine einfache Konfiguration sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code AdvSendAdvert on; -\layout Code +\end_layout +\begin_layout Code MinRtrAdvInterval 3; -\layout Code +\end_layout +\begin_layout Code MaxRtrAdvInterval 10; -\layout Code +\end_layout +\begin_layout Code prefix 3ffe:ffff:0100:f101::/64 { -\layout Code +\end_layout +\begin_layout Code AdvOnLink on; -\layout Code +\end_layout +\begin_layout Code AdvAutonomous on; -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr on; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Als Ergebnis auf der Client-Seite ergibt sich hieraus: -\layout Code +\end_layout +\begin_layout Code # ip -6 addr show eth0 -\layout Code +\end_layout +\begin_layout Code 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 -\layout Code +\end_layout +\begin_layout Code inet6 3ffe:ffff:100:f101:2e0:12ff:fe34:1234/64 scope global dynamic -\layout Code +\end_layout +\begin_layout Code valid_lft 2591992sec preferred_lft 604792sec -\layout Code +\end_layout +\begin_layout Code inet6 fe80::2e0:12ff:fe34:1234/10 scope link -\layout Standard +\end_layout +\begin_layout Standard Ein hoher Wert für die Lebensdauer wurde verwendet, da der Wert nicht manuell konfiguriert wurde. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Spezielle 6to4 Konfiguration -\layout Standard +\end_layout +\begin_layout Standard Seit der Version 0.6.2pl3 wird die automatische (Neu)-Erstellung des Präfixes abhängig von der IPv4 Adresse eines angegebenen Interfaces unterstützt. Dies kann dazu eingesetzt werden, die Advertisements dann in einem LAN @@ -11045,734 +13440,894 @@ Seit der Version 0.6.2pl3 wird die automatische (Neu)-Erstellung des Pr Wegen der sicherlich kürzeren Lebensdauer dieser Präfixe (nach jedem dial-up ist ein anderes Präfix gültig), wird der Wert der Lebensdauer auf einen minimalen Wert gesetzt: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code AdvSendAdvert on; -\layout Code +\end_layout +\begin_layout Code MinRtrAdvInterval 3; -\layout Code +\end_layout +\begin_layout Code MaxRtrAdvInterval 10; -\layout Code +\end_layout +\begin_layout Code prefix 0:0:0:f101::/64 { -\layout Code +\end_layout +\begin_layout Code AdvOnLink off; -\layout Code +\end_layout +\begin_layout Code AdvAutonomous on; -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr on; -\layout Code +\end_layout +\begin_layout Code Base6to4Interface ppp0; -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime 20; -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime 30; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Das Ergebnis auf Clientseite ist (unter der Annahme, dass ppp0 die lokale IPv4 Adresse 1.2.3.4 hat): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show eth0 -\layout Code +\end_layout +\begin_layout Code 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 -\layout Code +\end_layout +\begin_layout Code inet6 2002:0102:0304 -\series bold +\series bold : -\series default +\series default f101:2e0:12ff:fe34:1234/64 scope global dynamic -\layout Code +\end_layout +\begin_layout Code valid_lft 22sec preferred_lft 12sec -\layout Code +\end_layout +\begin_layout Code inet6 fe80::2e0:12ff:fe34:1234/10 scope link -\layout Standard +\end_layout +\begin_layout Standard Da eine kurze Lebensdauer definiert wurde, wird das Präfix bald verworfen werden, sollte kein entsprechendes Advertisement empfangen werden. -\layout Standard +\end_layout +\begin_layout Standard \lang english Achtung: wenn keine spezielle 6to4-Unterstützung der initscripts benutzt wird, ist eine spezielle Route am internen Interface des Routers notwendig, sonst gibt es Probleme bei eingehenden Paketen. Für das gezeigte Beispiel lautet diese: -\layout Code +\end_layout +\begin_layout Code \lang english # /sbin/ip -6 route add 2002:0102:0304 -\series bold +\series bold : -\series default +\series default f101::/64 dev eth0 metric 1 -\layout Standard +\end_layout +\begin_layout Standard \lang english Diese Route muß jedesmal, wenn der Prefix wechselt, ersetzt werden. Die ist dann der Fall, wenn das Dial-Up-Interface eine neue IPv4-Adresse bekommen hat. -\layout Subsection +\end_layout +\begin_layout Subsection Fehlersuche -\layout Standard +\end_layout +\begin_layout Standard Mit dem Programm \begin_inset Quotes sld -\end_inset +\end_inset radvdump \begin_inset Quotes srd -\end_inset +\end_inset können Sie gesendete und empfangene Advertisements detailliert betrachten. Die Anwendung ist einfach: -\layout Code +\end_layout +\begin_layout Code # radvdump -\layout Code +\end_layout +\begin_layout Code Router advertisement from fe80::280:c8ff:feb9:cef9 (hoplimit 255) -\layout Code +\end_layout +\begin_layout Code AdvCurHopLimit: 64 -\layout Code +\end_layout +\begin_layout Code AdvManagedFlag: off -\layout Code +\end_layout +\begin_layout Code AdvOtherConfigFlag: off -\layout Code +\end_layout +\begin_layout Code AdvHomeAgentFlag: off -\layout Code +\end_layout +\begin_layout Code AdvReachableTime: 0 -\layout Code +\end_layout +\begin_layout Code AdvRetransTimer: 0 -\layout Code +\end_layout +\begin_layout Code Prefix 2002:0102:0304:f101::/64 -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime: 30 -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime: 20 -\layout Code +\end_layout +\begin_layout Code AdvOnLink: off -\layout Code +\end_layout +\begin_layout Code AdvAutonomous: on -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr: on -\layout Code +\end_layout +\begin_layout Code Prefix 3ffe:ffff:100:f101::/64 -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime: 2592000 -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime: 604800 -\layout Code +\end_layout +\begin_layout Code AdvOnLink: on -\layout Code +\end_layout +\begin_layout Code AdvAutonomous: on -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr: on -\layout Code +\end_layout +\begin_layout Code AdvSourceLLAddress: 00 80 12 34 56 78 -\layout Standard +\end_layout +\begin_layout Standard Im Output wird jedes Advertisement in einem lesbarem Format dargestellt. Zu sehen sollten die von Ihnen eingestellten Werte sein; falls dem nicht so ist, wurde das Advertisement eventuell nicht von Ihrem radvd gesendet... (für die Rückverfolgung des Routers können Sie die LLAddress, die MAC Adresse des Routers, verwenden...) -\layout Section +\end_layout +\begin_layout Section \lang english - \begin_inset LatexCommand \label{hints-daemons-dhcpv6} -\end_inset +\end_inset Dynamic Host Configuration v6 Server (dhcp6s) -\layout Standard +\end_layout +\begin_layout Standard \lang english DHCPv6 kann für stateful Konfiguration benutzt werden. Der Daemon selbst muß nicht unbedingt auf dem Linux-Standard-Router laufen. -\layout Standard +\end_layout +\begin_layout Standard \lang english Man kann hier mehr Informationen als bei radvd spezifizieren. Die meisten sind denen des IPv4 DHCP-Servers ähnlich. -\layout Standard +\end_layout +\begin_layout Standard \lang english Nach einer passenden Konfiguration reagiert der Daemon aur empfangene IPv6-Multi cast-Pakete, die von einem Client an die Adresse ff02::16 gesendet werden. -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Konfiguration des DHCPv6-Servers (dhcp6s) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Einfache Konfiguration -\layout Standard +\end_layout +\begin_layout Standard \lang english Die Konfigurationsdatei des dhcp6s ist normalerweise /etc/dhcp6s.conf. Ein einfaches Beispiel sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code \lang english interface eth0 { -\layout Code +\end_layout +\begin_layout Code \lang english server-preference 255; -\layout Code +\end_layout +\begin_layout Code \lang english renew-time 60; -\layout Code +\end_layout +\begin_layout Code \lang english rebind-time 90; -\layout Code +\end_layout +\begin_layout Code \lang english prefer-life-time 130; -\layout Code +\end_layout +\begin_layout Code \lang english valid-life-time 200; -\layout Code +\end_layout +\begin_layout Code \lang english allow rapid-commit; -\layout Code +\end_layout +\begin_layout Code \lang english option dns_servers 2001:db8:0:f101::1 sub.domain.example; -\layout Code +\end_layout +\begin_layout Code \lang english link AAA { -\layout Code +\end_layout +\begin_layout Code \lang english range 2001:db8:0:f101::1000 to 2001:db8:0:f101::ffff/64; -\layout Code +\end_layout +\begin_layout Code \lang english prefix 2001:db8:0:f101::/64; -\layout Code +\end_layout +\begin_layout Code \lang english }; -\layout Code +\end_layout +\begin_layout Code \lang english }; -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Konfiguration des DHCPv6-Client (dhcp6s) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Einfache Konfiguration -\layout Standard +\end_layout +\begin_layout Standard \lang english Die Konfigurationsdatei von dhcp6c ist normalerweise /etc/dhcp6c.conf. Ein einfaches Beispiel sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code \lang english interface eth0 { -\layout Code +\end_layout +\begin_layout Code \lang english send rapid-commit; -\layout Code +\end_layout +\begin_layout Code \lang english request domain-name-servers; -\layout Code +\end_layout +\begin_layout Code \lang english }; -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Benutzung -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english dhcp6s -\layout Standard +\end_layout +\begin_layout Standard \lang english Starten des Servers, z.B. durch -\layout Code +\end_layout +\begin_layout Code \lang english # service dhcp6s start -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english dhcp6c -\layout Standard +\end_layout +\begin_layout Standard \lang english Starten des Clients im Vordergrund, z.B. durch -\layout Code +\end_layout +\begin_layout Code \lang english # # dhcp6c -f eth0 -\layout Code +\end_layout +\begin_layout Code \lang english ... -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Fehlersuche -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english dhcp6s -\layout Standard +\end_layout +\begin_layout Standard \lang english Der Server hat einen Vordergrund und zwei Debug-Schalter (von denen beide benutzt werden sollten), hier ein Beispiel: -\layout Code +\end_layout +\begin_layout Code \lang english # dhcp6c -d -D -f eth0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english dhcp6c -\layout Standard +\end_layout +\begin_layout Standard \lang english Der Client hat einen Vordergrund und zwei Debug-Schalter, hier ein Beispiel: -\layout Code +\end_layout +\begin_layout Code \lang english # dhcp6c -d -f eth0 -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:16 dhcpv6 doesn't support hardware type 776 -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:16 doesn't support sit0 address family 0 -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:16 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:16 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:17 status code for this address is: success -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:17 status code: success -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:17 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:17 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:17 assigned address 2001:db8:0:f101::1002 prefix len is not in any RAs prefix length using 64 bit instead -\layout Code +\end_layout +\begin_layout Code \lang english Oct/03/2005 17:18:17 renew time 60, rebind time 9 -\layout Standard +\end_layout +\begin_layout Standard \lang english Bemerkung: die netlink-Fehlermeldungen haben keinen Einfluß auf die Funktionalit ät. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-tcpwrapper} -\end_inset +\end_inset tcp_wrapper -\layout Standard +\end_layout +\begin_layout Standard Mit der tcp_wrapper Programmbibliothek können Sie Ihre Dienste gegen Missbrauch schützen. -\layout Subsection +\end_layout +\begin_layout Subsection Filter-Funktionalität -\layout Standard +\end_layout +\begin_layout Standard Sie können tcp_wrapper für folgende Zwecke einsetzen: -\layout Itemize +\end_layout +\begin_layout Itemize Nach Source-Adressen filtern (IPv4 oder IPv6) -\layout Itemize +\end_layout +\begin_layout Itemize Nach Benutzern filtern (benötigt einen aktiven ident Daemon auf der Client-Seite ) -\layout Subsection +\end_layout +\begin_layout Subsection Welches Programm benützt tcp_wrapper -\layout Standard +\end_layout +\begin_layout Standard Folgende Programme sind bekannt: -\layout Itemize +\end_layout +\begin_layout Itemize Jeder Dienst, der durch den xinetd aufgerufen wird (und wenn der xinetd mit der tcp_wrapper Bibliothek kompiliert wurde) -\layout Itemize +\end_layout +\begin_layout Itemize sshd (wenn der mit der tcp_wrapper Bibliothek kompiliert wurde) -\layout Subsection +\end_layout +\begin_layout Subsection Anwendung -\layout Standard +\end_layout +\begin_layout Standard Der tcp_wrapper wird durch zwei Dateien konfiguriert und kontrolliert: /etc/host s.allow sowie /etc/hosts.deny. Weitere Informationen finden Sie mit: -\layout Code +\end_layout +\begin_layout Code $ man hosts.allow -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Beispiel für /etc/hosts.allow -\layout Standard +\end_layout +\begin_layout Standard In dieser Datei wird ein Dienst pro Zeile eingetragen, der positiv gefiltert werden soll (d.h. Verbindungen werden erlaubt). -\layout Code +\end_layout +\begin_layout Code sshd: 1.2.3. [3ffe:ffff:100:200::]/64 -\layout Code +\end_layout +\begin_layout Code daytime-stream: 1.2.3. [3ffe:ffff:100:200::]/64 -\layout Standard +\end_layout +\begin_layout Standard Achtung: es existieren fehlerhafte Implementierungen, welche folgende fehlerhaft e IPv6-Netzwerk-Beschreibung unterstützen: [3ffe:ffff:100:200::/64]. Hoffentlich werden diese Versionen bald gefixt. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Beispiel für /etc/hosts.deny -\layout Standard +\end_layout +\begin_layout Standard In dieser Datei werden alle Einträge negativ gefiltert. Und normalerweise sollen alle Verbindungen unterbunden werden: -\layout Code +\end_layout +\begin_layout Code ALL: ALL -\layout Standard +\end_layout +\begin_layout Standard Sie können bei Bedarf obige Standardzeile auch durch Folgende ersetzen, jedoch wird dadurch bei zu vielen Verbindungen in kurzer Zeitz eine DoS Angriff möglich (Last des Mailers sowie des Spool-Verzeichnisses). Ein logwatch ist somit wahrscheinlich die bessere Lösung. -\layout Code +\end_layout +\begin_layout Code ALL: ALL: spawn (echo "Attempt from %h %a to %d at `date`" -\layout Code +\end_layout +\begin_layout Code | tee -a /var/log/tcp.deny.log | mail root@localhost) -\layout Subsection +\end_layout +\begin_layout Subsection Protokollierung -\layout Standard +\end_layout +\begin_layout Standard Entsprechend der Syslog Daemon Konfiguration in der Datei /etc/syslog.conf protokolliert der tcp_wrapper normalerweise in die Datei /var/log/secure. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Abgelehnte Verbindung -\layout Standard +\end_layout +\begin_layout Standard Das Logging einer abgelehnten IPv4-Verbindung zu einem durch den xinetd überwachten Daytime Dienst sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code Jan 2 20:40:44 gate xinetd-ipv6[12346]: FAIL: daytime-stream libwrap -\layout Code +\end_layout +\begin_layout Code ¬ from=::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:32:06 gate xinetd-ipv6[12346]: FAIL: daytime-stream libwrap -\layout Code +\end_layout +\begin_layout Code from=3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Standard +\end_layout +\begin_layout Standard Das Logging einer abgelehnten IPv4-Verbindung zu einem durch den xinetd überwachten sshd Daemon (auf IPv4 und IPv6 auf Verbindungen wartend) sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code Jan 2 20:24:17 gate sshd[12345]: refused connect from ::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code ¬ (::ffff:1.2.3.4) -\layout Code +\end_layout +\begin_layout Code Jan 2 20:39:33 gate sshd[12345]: refused connect -\layout Code +\end_layout +\begin_layout Code from 3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Code +\end_layout +\begin_layout Code ¬ (3ffe:ffff:100:200::212:34ff:fe12:3456) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Akzeptierte Verbindung -\layout Standard +\end_layout +\begin_layout Standard Das Logging einer akzeptierten IPv4-Verbindung zu einem durch den xinetd überwachten Daytime Dienst sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code Jan 2 20:37:50 gate xinetd-ipv6[12346]: START: daytime-stream pid=0 -\layout Code +\end_layout +\begin_layout Code ¬ from=::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:37:56 gate xinetd-ipv6[12346]: START: daytime-stream pid=0 -\layout Code +\end_layout +\begin_layout Code from=3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Standard +\end_layout +\begin_layout Standard Das Logging einer akzeptierten IPv4-Verbindung zu einem auf zwei Ports hörenden sshd sieht wie folgt aus: -\layout Code +\end_layout +\begin_layout Code Jan 2 20:43:10 gate sshd[21975]: Accepted password for user from ::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code ¬ port 33381 ssh2 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:42:19 gate sshd[12345]: Accepted password for user -\layout Code +\end_layout +\begin_layout Code from 3ffe:ffff:100:200::212:34ff:fe12:3456 port 33380 ssh2 -\layout Section +\end_layout +\begin_layout Section \lang english - \begin_inset LatexCommand \label{hints-daemons-vsftpd} -\end_inset +\end_inset vsftpd -\layout Subsection +\end_layout +\begin_layout Subsection Auf IPv6-Adressen lauschen -\layout Standard +\end_layout +\begin_layout Standard \lang english Editiere die Konfigurationsdatei, üblicherweise /etc/vsftpd/vsftpd.conf, und setze die Option für das \begin_inset Quotes sld -\end_inset +\end_inset listen \begin_inset Quotes srd -\end_inset +\end_inset wie folgt: -\layout Code +\end_layout +\begin_layout Code \lang english listen_ipv6=yes -\layout Standard +\end_layout +\begin_layout Standard \lang english Mehr ist nicht zu tun. -\layout Section +\end_layout +\begin_layout Section \lang english - \begin_inset LatexCommand \label{hints-daemons-proftpd} -\end_inset +\end_inset proftpd -\layout Subsection +\end_layout +\begin_layout Subsection Auf IPv6-Adressen lauschen -\layout Standard +\end_layout +\begin_layout Standard \lang english Editiere die Konfigurationsdatei, üblicherweise /etc/proftpd.conf, allerdings ist hier zu beachten, daß dies in der Konfigurationsart virtueller Host nicht 100% logisch ist -\layout Code +\end_layout +\begin_layout Code \lang english -\layout Code +\end_layout +\begin_layout Code \lang english ... -\layout Code +\end_layout +\begin_layout Code \lang english Bind 2001:0DB8::1 -\layout Code +\end_layout +\begin_layout Code \lang english ... -\layout Code +\end_layout +\begin_layout Code \lang english -\layout Standard +\end_layout +\begin_layout Standard \lang english Mehr ist nicht zu tun. -\layout Section +\end_layout +\begin_layout Section \lang english - \begin_inset LatexCommand \label{hints-daemons-others} -\end_inset +\end_inset Andere Daemons -\layout Standard +\end_layout +\begin_layout Standard \lang english Seit einiger Zeit ist dies meist einfach, suchen Sie einfach nach einer @@ -11782,491 +14337,509 @@ Seit einiger Zeit ist dies meist einfach, suchen Sie einfach nach einer FAQs nach. Es kann allerdings durchaus sein, daß sich der Daemon nur an die IPv6- \begin_inset Quotes sld -\end_inset +\end_inset any \begin_inset Quotes srd -\end_inset +\end_inset -Adresse (::) binden läßt und kein dediziertes Binden an eine spezielle IPv6-Adresse möglich ist (das hängt von der Unterstützung des Programmierers ab). -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-programming-using-API} -\end_inset +\end_inset Programmierung (mit API) -\layout Standard +\end_layout +\begin_layout Standard Ich habe keine Erfahrung in IPv6 Programmierung. Vielleicht findet sich jemand, der dieses Kapitel schreibt, eventuell wird das Kapitel aber auch in ein eigenes HOWTO integriert. -\layout Standard +\end_layout +\begin_layout Standard Zusätzliche Informationen zu diesem Thema: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[RFC 2553 / Basic Socket Interface Extensions for IPv6]{http://www.faqs.org/rfcs/rfc2553.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Draft / Advanced Sockets API for IPv6 / draft-ietf-ipngwg-rfc2292bis-XY.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Porting applications to IPv6 HowTo]{http://jungla.dit.upm.es/~ecastro/IPv6-web/ipv6.html} -\end_inset +\end_inset von Eva M. Castro -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-interoperability} -\end_inset +\end_inset Kompatibilität -\layout Standard +\end_layout +\begin_layout Standard Weltweit gibt es mehrere Projekte deren Ziel es ist, das Zusammenspiel der verschiedenen Betriebssysteme in Hinblick auf IPv6 Funktionalität und Implement ierung zu überprüfen. Folgende Links gibt es: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TAHI Project]{http://www.tahi.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Mehr dazu später... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-information} -\end_inset +\end_inset Weitere Informationen und URLs -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-books} -\end_inset +\end_inset Gedruckte Bücher, Artikel, Onlinerezensionen -\layout Subsection +\end_layout +\begin_layout Subsection Gedruckte Bücher (Englisch) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Cisco -\layout Itemize +\end_layout +\begin_layout Itemize Cisco Self-Study: \begin_inset LatexCommand \url[Implementing IPv6 Networks (IPV6)]{http://www.amazon.com/exec/obidos/tg/detail/-/1587050862/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset , von Regis Desmeules. Cisco Press; ISBN 1587050862; 500 Seiten; 1. Edition (April 11, 2003). -\newline +\newline Anmerkung: Dieser Titel wird am 11. April 2003 publiziert. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Configuring IPv6 with Cisco IOS]{http://www.amazon.com/exec/obidos/tg/detail/-/1928994849/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset , von Sam Brown, Sam Browne, Neal Chen, Robbie Harrell, Edgar, Jr. Parenti (Editor), Eric Knipp (Editor), Paul Fong (Editor) 362 Seiten; Syngress Media Inc; ISBN 1928994849; (July 12, 2002). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Allgemein -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Essentials]{http://www.sunny.ch/publications/f_ipv6.htm} -\end_inset +\end_inset von Silvia Hagen, July 2002, O'Reilly \begin_inset LatexCommand \url[Order Number: 1258]{http://www.oreilly.com/catalog/ipv6ess/} -\end_inset +\end_inset , ISBN 0-5960-0125-8, 352 Seiten. -\newline +\newline \begin_inset LatexCommand \url[ToC, Index, Sample Chapter etc.]{http://www.oreilly.com/catalog/ipv6ess/} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[O'Reilly Pressrelease]{http://press.oreilly.com/ipv6ess.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize IPv6: The New Internet Protocol. Von Christian Huitema; Publiziert von Prentice-Hall; ISBN 0138505055. -\newline +\newline Beschreibung: Dieses Buch, geschrieben von Christian Huitema - einem Mitglied des Internet Architecture Board, bietet eine exzellente Beschreibung von IPv6, die Unterschiede zu IPv4 sowie die 'wies' und 'warums' der IPv6 Entwicklu ng. -\newline +\newline Quelle: \begin_inset LatexCommand \url[http://www.cs.uu.nl/wais/html/na-dir/internet/tcp-ip/resource-list.html]{http://www.cs.uu.nl/wais/html/na-dir/internet/tcp-ip/resource-list.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Networks]{http://www.epinions.com/book_mu-3402412/display_~full_specs} -\end_inset +\end_inset von Niles, Kitty; (ISBN 0070248079); 550 Seiten; Datum der Veröffentlichung: 05/01/1998. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Implementing IPV6. Supporting the Next Generation Internet Protocols]{http://www.amazon.com/exec/obidos/tg/detail/-/0764545892/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset von P. E. Miller, Mark A. Miller; Hrsg.: John Wiley & Sons; ISBN 0764545892; 2. Edition (15.März 2000); 402 Seiten. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Big Book of Ipv6 Addressing Rfcs]{http://www.amazon.com/exec/obidos/tg/detail/-/0126167702/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset von Peter H. Salus (Compiler), Morgan Kaufmann (Hrsg.), April 2000, 450 Seiten ISBN 012616770 2. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Understanding IPV6]{http://www.epinions.com/book_mu-3922588/display_~full_specs} -\end_inset +\end_inset von Davies, Joseph; ISBN 0735612455; Datum der Veröffentlichung: 05/01/2001; 350 Seiten. -\newline +\newline \begin_inset LatexCommand \url[Understanding IPV6]{http://www.microsoft.com/MSPress/books/4883.asp} -\end_inset +\end_inset von Davies, Joseph; ISBN 0735612455; Datum der Veröffentlichung: 13/11/2002; 544 Seiten. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migrating to IPv6 - IPv6 in Practice]{http://www.amazon.com/exec/obidos/tg/detail/-/0471498920/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset . Von Marc Blanchet; John Wiley & Sons (Hrsg.); ISBN 0471498920; 1. Edition (November 2002); 368 Seiten. -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Ipv6 Network Programming]{http://www.amazon.com/exec/obidos/ASIN/1555583180/} -\end_inset +\end_inset von Jun-ichiro Hagino; ISBN 1555583180 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Wireless boosting IPv6]{http://www.nwfusion.com/news/2000/1023ipv6.html} -\end_inset +\end_inset von Carolyn Duffy Marsan, 10/23/2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[O'reilly Network search for keyword IPv6]{http://www.oreillynet.com/search/index.ncsp?sp-q=IPv6} -\end_inset +\end_inset ergibt 29 Treffer (28. Januar 2002). -\layout Subsection +\end_layout +\begin_layout Subsection Gedruckte Bücher (Deutsch) -\layout Itemize +\end_layout +\begin_layout Itemize Technik der IP-Netze (TCP/IP incl. IPv6) \begin_inset LatexCommand \url[bei Amazon.de]{http://www.amazon.de/exec/obidos/ASIN/3446215018/} -\end_inset +\end_inset -\newline +\newline Anatol Badach, Erwin Hoffmann -\newline -Carl Hanser Verlag München, Wien, 2001 ISBN 3-446-21501-8 -\newline +\newline +Carl Hanser Verlag München, Wien, 2001 ISBN + 3-446-21501-8 +\newline Kap. 6: Protokoll IPv6 S.205-242 -\newline +\newline Kap. 7: Plug&Play-Unterstützung bei IPv6 S.243-276 -\newline +\newline Kap. 8: Migration zum IPv6-Einsatz S.277-294 -\newline +\newline Kap. 9.3.4: RIP für das Protokoll IPv6 (RIPng) S.349-351 -\newline +\newline Kap. 9.4.6: OSPF für IPv6 S.384-385 -\newline +\newline Kommentar: tw. nicht ganz up-to-date bzw. nicht ganz fehlerfreie Abbildungen -\newline +\newline \begin_inset LatexCommand \url[Homepage des Buches und Tabelle mit Fixes]{http://www.fehcom.de/tipn/tipn.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Internet-Sicherheit (Browser, Firewalls und Verschlüsselung) \begin_inset LatexCommand \url[bei Amazon.de]{http://www.amazon.de/exec/obidos/ASIN/3446217258/} -\end_inset +\end_inset -\newline +\newline Kai Fuhrberg -\newline +\newline 2. akt. Auflage 2000 Carl Hanser Verlag München, Wien, ISBN 3-446-21333-3 -\newline +\newline Kap.2.3.1.4. IPv6 S.18-22 -\newline -Kurz angerissen werden: RFC1825 - Security Association Konzept RFC1826 - - IP authentication Header RFC1827 - IP Encapsulation Security Payload -\layout Itemize +\newline +Kurz angerissen werden: RFC1825 - Security Association Konzept + RFC1826 - IP authentication Header RFC1827 - IP Encapsulation Security + Payload +\end_layout +\begin_layout Itemize IPv6. Das neue Internet- Protokoll. Technik, Anwendung, Migration \begin_inset LatexCommand \url[bei Amazon]{http://www.amazon.de/exec/obidos/ASIN/389864149X} -\end_inset +\end_inset -\newline +\newline Hans Peter Dittler -\newline +\newline 2. akt. und erweiterte Auflage 2002 dpunkt.verlag, ISBN 3-89864-149-X -\layout Itemize +\end_layout +\begin_layout Itemize Das neue Internetprotokoll IPv6 \begin_inset LatexCommand \url[bei Amazon]{http://www.amazon.de/exec/obidos/ASIN/3446216855} -\end_inset +\end_inset -\newline +\newline Herbert Wiese -\newline +\newline 2002 Carl Hanser Verlag, ISBN 3446216855 -\layout Subsection +\end_layout +\begin_layout Subsection Artikel, eBooks, Online Rezensionen -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Getting Connected with 6to4]{http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html} -\end_inset +\end_inset von Huber Feyrer, 06/01/2001 -\layout Itemize +\end_layout +\begin_layout Itemize Transient Addressing for Related Processes: Improved Firewalling by Using IPv6 and Multiple Addresses per Host; geschrieben von Peter M. Gleiz, Steven M. Bellovin ( \begin_inset LatexCommand \url[PC-PDF-Version]{http://www.securiteinfo.com/ebooks/pdf/tarp.pdf} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[Palm-PDF-Version]{http://www.securiteinfo.com/ebooks/palm/tarp.pdf} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[PDB-Version]{http://www.securiteinfo.com/ebooks/pdb/tarp.pdb} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6, théorie et pratique]{http://www.oreilly.fr/catalogue/ipv6-3ed.html} -\end_inset +\end_inset (französisch) 3e édition, mars 2002, O'Reilly, ISBN 2-84177-139-3 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPSec]{http://www.securiteinfo.com/crypto/IPSec.shtml} -\end_inset +\end_inset (Sprache: französisch) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internetworking IPv6 with Cisco Routers]{http://www.ip6.com/index.html} -\end_inset +\end_inset von Silvano Gai, McGrawHill Italia, 1997. Die 13 Kapitel und der Anhang A-D sind als PDF-Dokument 'downladbar'. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Secure and Dynamic Tunnel Broker]{http://www.vermicelli.pasta.cs.uit.no/ipv6/students/vegars/} -\end_inset +\end_inset von Vegar Skaerven Wang, Master of Engineering Diplomarbeit in Computerwissensc haften, 2.Juni 2000, Fakultät der Wissenschaften, Abteilung Computerwissenschafte n, Universiät Tromso, Norwegen. -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Aufbruch in die neue Welt - IPv6 in IPv4 Netzen]{http://www.old.netobjectdays.org/pdf/99/stja/doering.pdf} -\end_inset +\end_inset \lang ngerman von Dipl.Ing. Ralf Döring, TU Illmenau, 1999 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migration and Co-existence of IPv4 and IPv6 in Residential Networks]{http://www.csc.fi/~psavola/residential.html} -\end_inset +\end_inset von Pekka Savola, CSC/FUNET, 2002 -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-sciencepublication} -\end_inset +\end_inset Wissenschaftliche Publikationen (Kurzbeschreibungen, Bibliographien, Online Quellen) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[GEANT IPv6 Workplan]{http://www.ipv6.ac.uk/gtpv6/workplan.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A simulation study on the performance of Mobile IPv6 in a WLAN-based cellular network]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=1} -\end_inset +\end_inset , von Perez Costa X.; Hartenstein H. -- Computer Networks, September 2002, Vol. 40, Nr. 1, S. 191-204(14) -- Elsevier Science. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Trials on UK Academic Networks: Bermuda Project Aug.2002]{http://www.ipv6.ac.uk/bermuda2/} -\end_inset +\end_inset : Participants - Getting connected - Project deliverables - Network topology - Address assignments - Wireless IPv6 access - IPv6 migration - Project presentations - Internet 2 - Other IPv6 projects - IPv6 fora and standards Bermuda 2... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[http://www.ipv6.ac.uk/]{http://www.ipv6.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A scalable parallel internet router that enables the QoS through merging ATM with IPv6]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=2} -\end_inset +\end_inset . Von Song S. @@ -12274,14 +14847,14 @@ Wissenschaftliche Publikationen (Kurzbeschreibungen, Bibliographien, Online 25, Nr. 7, S. 647-651(5) -- Elsevier Science. -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Linux IPv6: Which One to Deploy?]{http://liinwww.ira.uka.de/mpsbib?query=ti%3D(Linux+IPv6+Which+One+Deploy)} -\end_inset +\end_inset Linux Journal, Vol. 96, p. @@ -12289,15 +14862,15 @@ Wissenschaftliche Publikationen (Kurzbeschreibungen, Bibliographien, Online (siehe auch \begin_inset LatexCommand \url[liinwww.ira.uka.de/ipv6]{http://liinwww.ira.uka.de/mpsbib?query=ipv6&maxnum=200} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[An overview and analysis of mobile Internet protocols in cellular environments]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=3} -\end_inset +\end_inset . Chao H-C. @@ -12306,12 +14879,12 @@ Wissenschaftliche Publikationen (Kurzbeschreibungen, Bibliographien, Online 11, Nr. 5, S. 435-450(16) -- MCB University Press -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 for Future Wireless Networks]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=5} -\end_inset +\end_inset . Toftegaard Nielsen T. @@ -12319,20 +14892,20 @@ Wissenschaftliche Publikationen (Kurzbeschreibungen, Bibliographien, Online 17, Nr. 2/3, S. 237-247(11) -- Kluwer Academic Publishers, Dordrecht, The Netherlands -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 at the University of Southampton]{http://www.ipv6.ecs.soton.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Seamless Support for Mobile Internet Protocol Based Cellular Environments]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=4} -\end_inset +\end_inset . Chao H-C.; Chu Y-M. @@ -12340,23 +14913,23 @@ Wissenschaftliche Publikationen (Kurzbeschreibungen, Bibliographien, Online 8, Nr. 3, S. 133-153(21) -- Kluwer Academic/Plenum Publishers, New York, U.S.A. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: The Solution for Future Universal Networks]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1818, S. 82-??, 2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Modeling and performance analysis for IPv6 traffic with multiple QoS classes]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=8} -\end_inset +\end_inset . Zhang L.; Zheng L. @@ -12364,42 +14937,43 @@ Wissenschaftliche Publikationen (Kurzbeschreibungen, Bibliographien, Online 24, Nr. 15, S. 1626-1636(11) -- Elsevier Science. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Threshold-Based Registration (TBR) in Mobile IPv6]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1818, S. 150-??, 2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Performance Analysis on FreeBSD Workstation Using Simple Applications]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1961, S. 33-??, 2000. -\layout Itemize +\end_layout +\begin_layout Itemize Microsoft Research IPv6 Implementation (MSRIPv6): \begin_inset LatexCommand \url[MSRIPv6 Configuring 6to4 - Connectivity with MSR IPv6 - Our 6Bone Node... ]{http://www.research.microsoft.com/msripv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[New frontiers in cybersegmentation: marketing success in cyberspace depends on IP address]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=9} -\end_inset +\end_inset . Louvieris P.; Driver J. @@ -12408,916 +14982,960 @@ Microsoft Research IPv6 Implementation (MSRIPv6): 4, Nr. 3, S. 169-181(13) -- MCB University Press. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[QoS-Conditionalized Handoff for Mobile IPv6]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3113c/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 2345, S. 721-??, 2002. -\layout Subsection +\end_layout +\begin_layout Subsection Sonstiges -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos gibt es unter: \begin_inset LatexCommand \url[SWITCH IPv6 Pilot / References]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-conferences} -\end_inset +\end_inset Konferenzen und Meetings -\layout Subsection +\end_layout +\begin_layout Subsection 2002 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Renater - Conférence IPv6 2002]{http://www.renater.fr/IPv6-2002/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Deployment Summit at INET 2002]{http://www.ipv6summit.com/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Fehlt etwas? Vorschläge sind Willkommen! -\layout Subsection +\end_layout +\begin_layout Subsection 2003 -\layout Standard +\end_layout +\begin_layout Standard Vorschläge sind Willkommen! -\layout Subsection +\end_layout +\begin_layout Subsection \lang english 2004 -\layout Itemize +\end_layout +\begin_layout Itemize \lang english 1st Global IPv6 Summit in Sao Paul, Brazil -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlineinformation} -\end_inset +\end_inset Online-Informationen -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-joinipv6} -\end_inset +\end_inset Mit dem IPv6 Backbone verbinden -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos in späteren Versionen... Vorschläge sind Willkommen! -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-globalregistries} -\end_inset +\end_inset Globale Registrierungsstellen -\layout Itemize +\end_layout +\begin_layout Itemize IPv6 Test-Backbone: \begin_inset LatexCommand \url[6bone]{http://www.6bone.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[How to join 6bone]{http://www.6bone.net/6bone_hookup.html} -\end_inset +\end_inset , -\newline +\newline \begin_inset LatexCommand \url[Teilnahme am 6bone]{http://www.join.uni-muenster.de/6bone/6bone-teilnahme.html} -\end_inset +\end_inset (deutsche Sprache), -\newline +\newline \begin_inset LatexCommand \url[6bone participation]{http://www.join.uni-muenster.de/6bone/6bone-participation.html} -\end_inset +\end_inset (englische Sprache) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-majorregionregistries} -\end_inset +\end_inset Regionale Haupt-Registrierungsstellen -\layout Itemize +\end_layout +\begin_layout Itemize Amerika: \begin_inset LatexCommand \url[ARIN]{http://www.arin.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[ARIN / registration page]{http://www.arin.net/registration/ipv6/index.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[ARIN / IPv6 guidelines]{http://www.arin.net/registration/ipv6/index.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize EMEA: \begin_inset LatexCommand \url[Ripe NCC]{http://www.ripe.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Ripe NCC / registration page]{http://www.ripe.net/ripencc/mem-services/registration/} -\end_inset +\end_inset , \lang english \begin_inset LatexCommand \url[Ripe NCC / IPv6 registration]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Asien/Pazifik: \begin_inset LatexCommand \url[APNIC]{http://www.apnic.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[APNIC / IPv6 ressource guide]{http://www.apnic.net/services/ipv6_guide.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Latein Amerika und Karikik: \begin_inset LatexCommand \url[LACNIC]{http://lacnic.org/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[IPv6 Registration Services]{http://lacnic.net/en/bt-IPv6.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[IPv6 Allocation Policy]{http://lacnic.net/en/chapter-4-en.pdf} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Afrika: \begin_inset LatexCommand \url[AfriNIC]{http://www.afrinic.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Es existiert auch eine Liste der größten Zuteilungen sortiert nach lokalen Registrierungsstellen: \begin_inset LatexCommand \url[Ripe NCC / IPv6 allocations]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6allocs.html} -\end_inset +\end_inset . -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-joinipv6-tunnelbrokers} -\end_inset +\end_inset Tunnel-Broker -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Eine Tunnel-Broker Liste ist im Abschnitt \begin_inset LatexCommand \ref[Tunnel broker]{information-Tunnelbroker} -\end_inset +\end_inset weiter unten zu finden. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Sourcecode]{http://www.vermicelli.pasta.cs.uit.no/ipv6/students/vegars/TunnelBroker/} -\end_inset +\end_inset der in Vermicellis Magisterarbeit über Tunnelbroker Verwendung findet, University of Tromso. -\layout Itemize +\end_layout +\begin_layout Itemize Former IPng. Tunnelbroker and IPv6 resources, now migrated to the \begin_inset LatexCommand \url[SixXs System]{http://www.sixxs.net/main/} -\end_inset +\end_inset . -\layout Itemize +\end_layout +\begin_layout Itemize Eckes \begin_inset LatexCommand \url[IPv6-with-Linux]{http://sites.inka.de/lina/linux/ipv6.html} -\end_inset +\end_inset Seite. -\layout Itemize +\end_layout +\begin_layout Itemize tunnelc - ein Perl basiertes Tunnel Client Script: -\newline +\newline freshmeat.net: \begin_inset LatexCommand \url[Project details for tunnel client]{http://freshmeat.net/projects/tunnelc} -\end_inset +\end_inset -\newline +\newline SourceForge: \begin_inset LatexCommand \url[Project Info - tunnelc]{http://sourceforge.net/projects/tunnelc} -\end_inset +\end_inset (also \begin_inset LatexCommand \url[here]{http://tunnelc.sourceforge.net/} -\end_inset +\end_inset ) -\layout Itemize +\end_layout +\begin_layout Itemize Linux Advanced Routing & Traffic Control HOWTO, \begin_inset LatexCommand \url[Chapter 6: IPv6 tunneling with Cisco and/or 6bone]{http://howtos.linuxbroker.com/howtoreader.shtml?file=Adv-Routing-HOWTO.html#LARTC.TUNNEL-IPV6.ADDRESSING} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Weitere URLs und Informationen finden Sie unter: \begin_inset LatexCommand \url[ipv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset . -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-joinipv6-6to4-tunneling} -\end_inset +\end_inset 6to4 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NSayer's 6to4 information]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[RFC 3068 / An Anycast Prefix for 6to4 Relay Routers]{http://www.faqs.org/rfcs/rfc3068.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english - \begin_inset LatexCommand \label{information-joinipv6-isatap-tunneling} -\end_inset +\end_inset ISATAP -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[ISATAP (Intra-Site Automatic Tunnel Access Protocol) Information]{http://www.join.uni-muenster.de/Dokumente/Howtos/Howto_ISATAP.php?lang=en} -\end_inset +\end_inset by \begin_inset LatexCommand \url[JOIN]{http://www.join.uni-muenster.de/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Neueste Nachrichten und URLs zu anderen Dokumenten -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos in späteren Versionen... Vorschläge sind Willkommen! -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset , deutsches Forum -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Viele URLs zu anderen Dokumenten]{http://www.estoile.com/links/ipv6} -\end_inset +\end_inset von Anil Edathara -\layout Subsection +\end_layout +\begin_layout Subsection Protokoll-Informationen -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 bezogene Request For Comments (RFCs) -\layout Standard +\end_layout +\begin_layout Standard Das veröffentlichen einer Liste mit IPv6 relevanter RFCs geht über den Rahmen dieses Dokumentes hinaus, unter folgenden Links können Sie jedenfalls diverse Listen finden: -\layout Itemize +\end_layout +\begin_layout Itemize sortierte Liste: \begin_inset LatexCommand \url[IPng Standardization Status]{http://playground.sun.com/pub/ipng/html/specs/standards.html} -\end_inset +\end_inset oder \begin_inset LatexCommand \url[IPng Current Specifications]{http://playground.sun.com/pub/ipng/html/specs/specifications.html} -\end_inset +\end_inset von Robert Hinden -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Related Specifications]{http://www.ipv6.org/specs.html} -\end_inset +\end_inset auf IPv6.org -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Aktuelle Entwürfe diverser Arbeitsgruppen -\layout Standard +\end_layout +\begin_layout Standard Aktuelle (auch) IPv6-bezogene Drafts finden Sie hier: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IP Version 6 (ipv6)]{http://www.ietf.org/ids.by.wg/ipv6.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Next Generation Transition (ngtrans)]{http://www.ietf.org/ids.by.wg/ngtrans.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Dynamic Host Configuration (dhc)]{http://www.ietf.org/ids.by.wg/dhc.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Domain Name System Extension (dnsext)]{http://www.ietf.org/ids.by.wg/dnsext.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Mobile IP (mobileip)]{http://www.ietf.org/ids.by.wg/mobileip.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Get any information about IPv6, from overviews, through RFCs & drafts, to implementations]{http://playground.sun.com/pub/ipng/html/ipng-main.html} -\end_inset +\end_inset (inklusive Verfügbarkeit der Stacks auf verschiedenen Plattformen & Quellcode diverser IPv6 Stacks) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Sonstige -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Network Sorcery / IPv6, Internet Protocol version 6]{http://www.networksorcery.com/enp/protocol/ipv6.htm} -\end_inset +\end_inset , IPv6 Protokoll Header -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SWITCH IPv6 Pilot / References]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset , umfangreiche Liste mit IPv6 Quellen betreut von Simon Leinen -\layout Subsection +\end_layout +\begin_layout Subsection Weitere Informationen -\layout Standard +\end_layout +\begin_layout Standard Mehr Infos in späteren Versionen... Vorschläge sind willkommen! -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[DeepSpace6 / Weitere interessante Links]{http://www.deepspace6.net/sections/links.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Linux Informationen -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / (Not only) Linux IPv6 Portal]{http://www.deepspace6.net/} -\end_inset +\end_inset - Italien \lang english ( \begin_inset LatexCommand \url[Spiegel]{http://mirrors.bieringer.de/www.deepspace6.net/} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-HowTo for Linux by Peter Bieringer]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset - Deutschland, und sein \begin_inset LatexCommand \url[Bieringer / IPv6 - software archive]{ftp://ftp.bieringer.de/pub/linux/IPv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Linux+IPv6 status by Peter Bieringer]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status.html} -\end_inset +\end_inset - Deutschland -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[DeepSpace6 / IPv6 Status Page]{http://www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset - Italien ( \begin_inset LatexCommand \url[Spiegel]{http://mirrors.bieringer.de/www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset ) (ersetzt das oben genannte in Zukunft) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[USAGI project]{http://www.linux-ipv6.org/} -\end_inset +\end_inset - Japan, und deren \begin_inset LatexCommand \url[USAGI project - software archive]{ftp://ftp.linux-ipv6.org/pub/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Linux Optimized Link State Routing Protocol (OLSR) IPv6 HOWTO]{http://www.tldp.org/HOWTO/OLSR-IPv6-HOWTO/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Informationen zu Linux-Distributionen -\layout Description +\end_layout +\begin_layout Description PLD \begin_inset LatexCommand \url[PLD Linux Distribution]{http://www.pld-linux.org/} -\end_inset +\end_inset ( \begin_inset Quotes sld -\end_inset +\end_inset Marktführer \begin_inset Quotes srd -\end_inset +\end_inset bei inkludierten IPv6 fähigen Paketen)) -\layout Description +\end_layout -Red\SpecialChar ~ +\begin_layout Description +Red\InsetSpace ~ Hat \begin_inset LatexCommand \url[Red Hat Linux]{http://www.redhat.com/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[ Pekka Savola's IPv6 packages]{http://www.netcore.fi/pekkas/linux/ipv6/} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description Debian \begin_inset LatexCommand \url[Debian Linux]{http://www.debian.org/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Craig Small's IPv6 information and status]{http://people.debian.org/~csmall/ipv6/} -\end_inset +\end_inset \lang english , \begin_inset LatexCommand \url[Jim's insignificant LAN IPv6 global connectivity HOWTO]{http://www.ruwenzori.net/ipv6/Jims_LAN_IPv6_global_connectivity_howto.html} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description Novell/SuSE \begin_inset LatexCommand \url[Novell/SuSE Linux]{http://www.novell.com/linux/suse/} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description \lang english Mandriva \begin_inset LatexCommand \url[Mandriva]{http://www.mandriva.com} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Weitere Details siehe unter \begin_inset LatexCommand \url[IPv6+Linux Status Distributions]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Allgemeine Informationen -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6.org]{http://www.ipv6.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6bone]{http://www.6bone.net/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UK IPv6 Resource Centre]{http://www.cs-ipv6.lancs.ac.uk/} -\end_inset +\end_inset - Großbritannien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[WIDE project]{http://www.v6.wide.ad.jp/} -\end_inset +\end_inset - Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SWITCH IPv6 Pilot]{http://www.switch.ch/lan/ipv6/} -\end_inset +\end_inset - Schweiz -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Corner of Hubert Feyrer]{http://www.feyrer.de/IPv6/} -\end_inset +\end_inset - Deutschland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Vermicelli Project]{http://www.vermicelli.pasta.cs.uit.no/ipv6/} -\end_inset +\end_inset - Norwegen -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Forum]{http://www.ipv6forum.com/} -\end_inset +\end_inset - ein weltweites Konsortium führender Internet-Hersteller, Forschungs- & Bildungseinrichtungen... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Playground.sun.com / IPv6 Info Page]{http://playground.sun.com/pub/ipng/html/ipng-main.html} -\end_inset +\end_inset - betreut von Robert Hinden, Nokia. Hier gibt es jede Information zum Thema IPv6: Zusammenfassungen, RFCs & Drafts, Implementierungen (Verfügbarkeit der Stacks auf verschiedenen Plattform en & Quellcode diverser IPv6 Stacks). -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6INIT]{http://www.6init.com/} -\end_inset +\end_inset - IPv6 Internet Initiative - ein Fifth Framework Projekt der EU im Rahmen des IST Programmes. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Task Force (European Union)]{http://www.ipv6-taskforce.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Document Project]{http://www.v6.sfc.wide.ad.jp/v6doc/} -\end_inset +\end_inset (japanische Sprache) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6init]{http://www.6init.org/} -\end_inset +\end_inset - IPv6 INternet IniTiative -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IP Next Generation Overview]{http://www.isoc.org/HMP/PAPER/PT1/html/pt1.html.hinden} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: The New Version of the Internet Protocol]{http://www.usenix.org/publications/library/proceedings/ana97/summaries/deering.html} -\end_inset +\end_inset , von Steve Deering. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: The Next Generation Internet Protocol]{http://www.garykessler.net/library/ipv6_exp.html} -\end_inset +\end_inset , von Gary C. Kessler. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: Next Generation Internet Protocol]{http://www.3com.com/nsc/ipv6.html} -\end_inset +\end_inset - 3Com -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Next Generation Internet Initiative]{http://www.ngi.gov/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[The Quality of Service Forum site]{http://www.qosforum.com/tech_resources.htm} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[internet || site]{http://www.internet2.org/} -\end_inset +\end_inset und \begin_inset LatexCommand \url[internet2 Working Group]{http://ipv6.internet2.edu/} -\end_inset +\end_inset - \begin_inset LatexCommand \url[Presentation (HTML + PPT)]{http://ipv6.internet2.edu/presentations/} -\end_inset +\end_inset from IPv6 Workshops: (Stateless Autoconfiguration, IPv6 Addressing, USAGI, Provider Independent IPv6 Addressing and other topics). -\layout Itemize +\end_layout +\begin_layout Itemize NetworkWorldFusion: Search / Doc Finder: \begin_inset LatexCommand \url[searched for IPv6]{http://search.nwfusion.com/query.html?qt=IPv6&qp=&ch=cn&} -\end_inset +\end_inset (102 Dokumente gefunden - 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[The Register]{http://www.theregister.co.uk/} -\end_inset +\end_inset (Suche nach IPv6 ergab 30 Dokumente, 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ZDNet Search for IPv6]{http://zdnet.search.com/search?cat=279&q=IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TechTarget Search for IPv6]{http://whatis.techtarget.com/wsearchResults/1,290214,sid9,00.html?query=IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 & TCP Resources List]{http://www.faqs.org/faqs/internet/tcp-ip/resource-list/index.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Klingon IPv6 tools]{http://ipv6.klingon.nl/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Klingon IPv6 tools (native IPv6 only access)]{http://www.ipv6.klingon.nl/} -\end_inset +\end_inset : IPv6 Firewall Beispiele, Bandbreiten-Tests sowie Portscanner -\layout Standard +\end_layout +\begin_layout Standard Fehlt etwas? Vorschläge sind Willkommen! -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-marketresearch} -\end_inset +\end_inset Marktforschung -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A Tale of Two Wireless Technology Trends: Processor Development Outsourcing and IPv6]{http://www.seminarinformation.com/wconnect/wc.dll?sis~details0~307~TSN} -\end_inset +\end_inset Yankee Group - 4/1/2002 - 12 Seiten - ID: YANL768881 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[The World Atlas of the Internet: Americas]{http://www.marketresearch.com/product/display.asp?SID=88602378-241489274-186851952&ProductID=803907} -\end_inset +\end_inset ; IDATE - 2/1/2002 - 242 Seiten - ID: IDT803907. Folgende Länder werden behandelt: Zentralamerika, Nordamerika,Südamerika; @@ -13325,1652 +15943,1706 @@ Yankee Group - 4/1/2002 - 12 Seiten - ID: YANL768881 the globe. Market assessment and forecasts up to 2006 for 34 countries: market structure: main ISPs and market shares; number of subscribers, of ISPs. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Early Interest Rising for IPv6]{http://www.amazon.com/exec/obidos/tg/detail/-/B000065T8E/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset von IDC (Autor); Listenpreis: $1,500.00; Edition: e-book (Acrobat Reader); Hrsg.: IDC; ISBN B000065T8E; (1. March 2002) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-patents} -\end_inset +\end_inset Patente -\layout Itemize +\end_layout +\begin_layout Itemize Kanadische Patentdatenbank: \begin_inset LatexCommand \url[Home]{http://patents1.ic.gc.ca/intro-e.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Search]{http://patents1.ic.gc.ca/srch_sim-e.html} -\end_inset +\end_inset (Basis Suche, einfach IPv6 im Suchfeld eingeben ;-); 84 Dokumente gefunden, 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Espacenet]{http://www.european-patent-office.org/espacenet/info/index.htm} -\end_inset +\end_inset - Euorpäische Patentinformationen: -\newline +\newline \begin_inset LatexCommand \url[National Offices, Members of Espacenet]{http://www.european-patent-office.org/espacenet/info/access.htm} -\end_inset +\end_inset (IPv6: 84 Dokumente, 22.12.2002) -\layout Itemize +\end_layout +\begin_layout Itemize Delphion Research: \begin_inset LatexCommand \url[Patent Search Page]{http://www.delphion.com/research/} -\end_inset +\end_inset . Basic (kostenlose) Registrierung ist notwendig. Beispiele für die Suche nach IPv6 (vom 21.12.2002): -\newline +\newline \begin_inset LatexCommand \url[Communicating method between IPv4 terminal and IPv6 terminal and IPv4-IPv6 converting apparatus]{http://www.delphion.com/details?pn=US06118784__} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Translator for IP networks, network system using the translator, and IP network coupling method therefor]{http://www.delphion.com/details?pn=US06038233__} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Sortiert nach Ländern -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Europa -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[www.ist-ipv6.org]{http://www.ist-ipv6.org/} -\end_inset +\end_inset : IST IPv6 Cluster, European IPv6 Research and Development Projects -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Euro6IX]{http://www.euro6ix.org/} -\end_inset +\end_inset : European IPv6 Internet Exchanges Backbone -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Australien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Carl's Australian IPv6 Pages]{http://oversteer.bl.echidna.id.au/IPv6/} -\end_inset +\end_inset (alter Inhalt) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Belgien -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Brasilien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[BR6bone]{http://www.6bone.rnp.br/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[IPv6 Summit in Brazil]{http://www.ipv6summit.com.br/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[IPv6 do Brasil]{http://www.ipv6dobrasil.com.br/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection China -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Deutschland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset , IPv6 Forum in Deutschland -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Frankreich -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Renater]{http://www.renater.fr/Projets/IPv6/index.htm} -\end_inset +\end_inset : Renater IPv6 Projekt Seite -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[IPv6 - RSVP - ATM at INRIA]{http://www.inria.fr/recherche/equipes/ipv6.fr.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[NetBSD IPv6 Dokumentation]{http://www.netbsd.org/fr/Documentation/network/ipv6/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Großbritannien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 in the UK]{http://www.ipv6.org.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UK IPv6 Resource Center]{http://www.cs-ipv6.lancs.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[British Telecom IPv6 Home]{http://www.bt.com/ipv6/} -\end_inset +\end_inset : BT's ISP IPv6 Versuch, Englands erster IPv6 Internet Exchange etc. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Indien -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Italien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Project6]{http://project6.ferrara.linux.it/} -\end_inset +\end_inset : IPv6 mit Linux -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Linux IPv6 Users Group JP]{http://www.v6.linux.or.jp/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Yamaha IPv6]{http://www.rtpro.yamaha.co.jp/RT/ipv6/} -\end_inset +\end_inset (sorry, alles in japanischer Sprache ...) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Korea -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ETRI]{http://www.krv6.net/} -\end_inset +\end_inset : Electronics and Telecommunications Research Institut -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Forum Korea]{http://www.ipv6.or.kr/english/index.new.htm} -\end_inset +\end_inset : IPv6 Infrastruktur Projekt in Korea -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Mexiko -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Mexico]{http://www.ipv6.unam.mx/} -\end_inset +\end_inset (spanische & englische Version) - IPv6 Projekt Homepage der National Autonomous University of Mexico (UNAM) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Niederlande -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SURFnet]{http://www.ipv6.surfnet.nl/} -\end_inset +\end_inset : SURFnet IPv6 Backbone -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[STACK]{http://www.stack.nl/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[STACK (IPv6)]{http://www.stack.nl/ipv6/} -\end_inset +\end_inset : Computer-Studendten-Verband der Eindhoven University of Technology, Niederland e. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPng.nl]{http://www.ipng.nl/} -\end_inset +\end_inset : Zusammenarbeit zwischen WiseGuys und Intouch. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Österreich -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6@IKNnet and MIPv6 Research Group]{http://www.ikn.tuwien.ac.at/~ipv6/} -\end_inset +\end_inset : TU Vienna, Austria (IPv6: Projekte, Publikationen, Diplom- / Doktorarbeiten, Konferenzunterlagen etc.) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Portugal -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[FCCN (National Foundation for the Scientific Computation)]{http://www.fccn.pt/projectos/ipv6/index_html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Russland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Forum for Russia]{http://www.ipv6.ru/} -\end_inset +\end_inset : Yaroslavl State University Internet Center -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Schweiz -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SWITCH]{http://www.switch.ch/network/ipv6/references.html} -\end_inset +\end_inset : Das Schweizer Erziehungs- & Wissenschaftsnetzwerk -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Tschechische Republik -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ungarn -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Testing Experimental IPv6 Technology and Services in Hungary]{http://tipster6.ik.bme.hu/tipster6_en.html} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Sortiert nach Betriebssystemen -\layout Subsubsection +\end_layout +\begin_layout Subsubsection *BSD -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[KAME project]{http://www.kame.net/} -\end_inset +\end_inset (*BSD) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NetBSD's IPv6 Networking FAQ]{http://www.netbsd.org/Documentation/network/ipv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[FreeBSD Ports: Ipv6]{http://www.freebsd.org/ports/ipv6.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize BUGAT - BSD Usergroup Austria - \begin_inset LatexCommand \url[www.bugat.at]{http://www.bugat.at/} -\end_inset +\end_inset : \begin_inset LatexCommand \url[FreeBSD IPv6 Tunnel]{http://www.bugat.at/inforum/contentview.php/mini-howto/freebsd-ipv6.ihtml} -\end_inset +\end_inset (deutsche Sprache) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Cisco IOS -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Cisco IOS IPv6 Entry Page]{http://www.cisco.com/warp/public/732/Tech/ipv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 for Cisco IOS Software]{http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/ftipv6c.htm} -\end_inset +\end_inset , Datei 2 von 3: Aug 2002 -- Inhalt: IPv6 for Cisco IOS Software; Configuring Documentation Specifics; Enabling IPv6 Routing and Configuring; IPv6 Addressing ; Enabling IPv6 Processing Globally. -\layout Itemize +\end_layout +\begin_layout Itemize Cisco Internet Networking Handbook, \begin_inset LatexCommand \url[Chapter IPv6]{http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/ipv6.htm} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Compaq -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 at Compaq]{http://www.compaq.com/ipv6/} -\end_inset +\end_inset - Präsentationen, White Papers, Dokumentation... -\layout Subsubsection +\end_layout +\begin_layout Subsubsection HPUX -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[comp.sys.hp.hpux FAQ]{http://www.faqs.org/faqs/hp/hpux-faq/index.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IBM -\layout Itemize +\end_layout +\begin_layout Itemize Now that IBM's announced the availability of z/OS V1.4, \begin_inset LatexCommand \url[what's new in this release?]{http://search390.techtarget.com/ateQuestionNResponse/0,289625,sid10_cid486367_tax292523,00.html} -\end_inset +\end_inset Die Frage wurde am 15. August 2002 'geposted'. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Microsoft -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Microsoft Windows 2000 IPv6]{http://www.microsoft.com/windows2000/technologies/communications/ipv6/default.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[MSRIPv6]{http://www.research.microsoft.com/msripv6} -\end_inset +\end_inset - Microsoft Research Network - IPv6 Homepage -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Getting Started with the Microsoft IPv6 Technology Preview for Windows 2000]{http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internet Connection Firewall Does Not Block Internet Protocol Version 6 Traffic]{http://support.microsoft.com/default.aspx?scid=kb;en-us;306203} -\end_inset +\end_inset (6.11.2001) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internet Protocol Numbers]{http://support.microsoft.com/default.aspx?scid=kb;en-us;289892} -\end_inset +\end_inset (8.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Technology Preview Refresh]{http://support.microsoft.com/default.aspx?scid=kb;en-us;273826} -\end_inset +\end_inset (16.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[HOW TO: Install and Configure IP Version 6 in Windows .NET Enterprise Server]{http://support.microsoft.com/default.aspx?scid=kb;en-us;325449} -\end_inset +\end_inset (26.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Windows .NET Server 6to4 Router Service Quits When You Advertise a 2002 Address on the Public Interface]{http://support.microsoft.com/default.aspx?scid=kb;en-us;329984} -\end_inset +\end_inset (28.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[msdn - Microsoft Windows CE .NET - IPv6 commands]{http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcetcpip/htm/cmconIPv6exe.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[msdn - search for IPv6]{http://search.microsoft.com/default.asp?qu=IPv6&boolean=ALL&nq=NEW&so=RECCNT&p=1&ig=01&i=00&i=01&i=02&i=03&i=04&i=05&i=06&i=07&i=08&i=09&i=10&i=11&i=12&i=13&i=14&i=15&i=16&i=17&i=18&i=19&i=20&i=21&i=22&i=23&i=24&i=25&i=26&i=27&i=28&i=29&i=30&i=31&i=32&i=33&i=34&i=35&i=36&i=37&i=38&i=39&i=40&i=41&siteid=us/dev} -\end_inset +\end_inset (100 Ergebnisse, 22.12.2002) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Solaris -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Sun Microsystems Solaris]{http://www.sun.com/software/solaris/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Solaris 2 Frequently Asked Questions (FAQ) 1.73]{http://www.cs.uu.nl/wais/html/na-dir/Solaris2/FAQ.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Sumitoma -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Sumitomo Electric has implemented IPv6 on Suminet 3700 family routers]{http://playground.sun.com/pub/ipng/html/ipng-implementations.html#Sumitomo} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ZebOS -\layout Itemize +\end_layout +\begin_layout Itemize IpInfusion's \begin_inset LatexCommand \url[ZebOS Server Routing Software]{http://www.ipinfusion.com/products/server/products_server.html} -\end_inset +\end_inset -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-ipv6andsecurity} -\end_inset +\end_inset IPv6 Sicherheit -\layout Itemize +\end_layout +\begin_layout Itemize Internet Security Systems: Security Center, \begin_inset LatexCommand \url[X-Force Database Search]{http://www.iss.net/security_center/search.php?type=3&type=3&pattern=IPv6} -\end_inset +\end_inset (21.12.2002 - 6 Themen bez. IPv6 gefunden) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NIST IPsec Project]{http://csrc.nist.gov/ipsec/} -\end_inset +\end_inset ( National Institute of Standards and Technology, NIST) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Information Security]{http://www.infosecuritymag.com/index.shtml} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NewOrder.box.sk (search for IPv6)]{http://neworder.box.sk/search.php3?srch=IPv6} -\end_inset +\end_inset (Artikel, Exploits, Datei-Datenbank etc.) -\layout Subsection +\end_layout +\begin_layout Subsection Programm-Listen -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[DeepSpace6 / IPv6 Status Page]{http://www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6.org / IPv6 enabled applications]{http://www.ipv6.org/v6-apps.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Freshmeat / IPv6 search]{http://freshmeat.net/search/?q=IPv6} -\end_inset +\end_inset , aktuell (14 Dez. 2002) 62 Projekte -\layout Itemize +\end_layout +\begin_layout Itemize IPv6 Forum: \begin_inset LatexCommand \url[IPv6 Router List]{http://www.ipv6forum.com/navbar/links/v6routerlist.htm} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Analyse-Werkzeuge -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Ethereal]{http://ethereal.planetmirror.com/} -\end_inset +\end_inset - Ethereal is ein kostenloser Netzwerkprotokoll-Analyseprogramm für Unix und Windows -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Radcom RC100-WL]{http://www.ip6.com/us/analyzer.htm} -\end_inset +\end_inset - Download Radcom RC100-WL Protokollanalyseprogramm version 3.20 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 Produkte -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6wind]{http://www.6wind.com/} -\end_inset +\end_inset - Lösungen für IPv4/IPv6 Router, QoS, Multicast, Mobility, Security/VPN/Firewal l. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Fefe's patches for IPv6 with djbdns]{http://www.fefe.de/dns/} -\end_inset +\end_inset - Aug 2002 - Was ist djbdns und warum es IPv6 benötigt? djbdns ist ein vollwertiger DNS Server, welcher \begin_inset Quotes sld -\end_inset +\end_inset outperforms BIND in nearly all respects \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ZebOS Server Routing Suite ]{http://www.ipinfusion.com/products/server/products_server.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SPA Mail Server 2.21 ]{http://download.com.com/3000-2165-10153543.html?tag=lst-0-21} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Inframail (Advantage Server Edition) 6.0 ]{http://download.com.com/3000-2165-8202652.html?tag=lst-0-2} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[HTTrack Website Copier]{http://download.com.com/3000-2377-10149393.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[CommView 5.0]{http://download.com.com/3000-2085-10132748.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Posadis 0.50.6]{http://download.com.com/3000-2104-10149750.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TCP Wrapper (IPv6 aware)]{ftp://ftp.porcupine.org/pub/ipv6/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-snmp} -\end_inset +\end_inset SNMP -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[comp.protocpols.snmp SNMP FAQ Part 1 of 2]{http://www.cs.uu.nl/wais/html/na-dir/snmp-faq/part1.html} -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section IPv6 Infrastruktur -\layout Subsection +\end_layout +\begin_layout Subsection Statistiken -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 routing table history]{http://www.space.net/~gert/RIPE/} -\end_inset +\end_inset erstellt von Gert Döring, \begin_inset LatexCommand \url[Space.Net]{http://www.space.net/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Official 6bone Webserver list Statisic]{http://6bone.informatik.uni-leipzig.de/ipv6/stats/stats.php3} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Allocation Data & Survey Results]{http://www.ripe.net/ripe/meetings/archive/ripe-42/presentations/ripe42-ipv6-survey/sld001.html} -\end_inset +\end_inset , IPv6 WG, Ripe 42, Ripe NCC -\layout Subsection +\end_layout +\begin_layout Subsection Internet Exchanges -\layout Standard +\end_layout +\begin_layout Standard Eine weitere Liste von IPv6 Internet Exchanges gibt es unter: \begin_inset LatexCommand \url[IPv6 Exchanges Web Site]{http://www.v6nap.net/} -\end_inset +\end_inset \lang english or \begin_inset LatexCommand \url[IPv6 status of IXPs in Europe]{http://www.euro-ix.net/isp/choosing/search/matrix.php} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-germany} -\end_inset +\end_inset Deutschland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[INXS]{http://www.inxs.de/} -\end_inset +\end_inset : (Cable & Wireless) München und Hamburg -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-estonia} -\end_inset +\end_inset Estlanda -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TIX]{http://tix.estpak.ee/} -\end_inset +\end_inset (Tallinn Interneti eXchange mit IPv6 Support) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-europe} -\end_inset +\end_inset Europa -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Euro6IX]{http://www.euro6ix.net/} -\end_inset +\end_inset , European IPv6 Internet Exchange Backbone -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-france} -\end_inset +\end_inset Frankreich -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[French National Internet Exchange IPv6]{http://www.fnix6.net/} -\end_inset +\end_inset (seit 1.11.2002 aktiv). -\newline -FNIX6 bietet ISPs im Großraum Paris den Dienst eines kostenlosen und zuverlässli -chen High Speed FastEthernet Internet Exchange. -\layout Subsubsection - +\newline +FNIX6 bietet ISPs im Großraum Paris den Dienst eines + kostenlosen und zuverlässlichen High Speed FastEthernet Internet Exchange. +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-uk} -\end_inset +\end_inset Großbritannien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UK6X]{http://www.uk6x.com/} -\end_inset +\end_inset : London -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XchangePoint]{http://www.xchangepoint.net/} -\end_inset +\end_inset : London -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-japan} -\end_inset +\end_inset Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NSPIXP-6]{http://www.wide.ad.jp/nspixp6/} -\end_inset +\end_inset : IPv6--basierter Internet Exchange in Tokio -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[JPIX]{http://www.jpix.co.jp/} -\end_inset +\end_inset , Tokio -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-korea} -\end_inset +\end_inset Korea -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6NGIX]{http://www.ngix.ne.kr/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-netherlands} -\end_inset +\end_inset Niederlande -\layout Itemize +\end_layout +\begin_layout Itemize -\noun on - +\noun on \begin_inset LatexCommand \url[AMS-IX]{http://www.ams-ix.net/} -\end_inset +\end_inset -\noun default +\noun default : Amsterdam Internet Exchange -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-usa} -\end_inset +\end_inset USA -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6TAP]{http://www.6tap.net} -\end_inset +\end_inset : Chicago. Bietet weltweit Peerings an. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NY6IX]{http://www.ny6ix.net/} -\end_inset +\end_inset : New York City IPv6 basierter Internet Exchange -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[PAIX]{http://www.paix.net/} -\end_inset +\end_inset : Palo Alto -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-Tunnelbroker} -\end_inset +\end_inset Tunnel broker -\layout Standard +\end_layout +\begin_layout Standard \lang english Auch interessant: \begin_inset LatexCommand \url[http://www.deepspace6.net/docs/tunnelbrokers.html]{http://www.deepspace6.net/docs/tunnelbrokers.html} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-belgium} -\end_inset +\end_inset Belgien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Wanadoo]{http://tunnel.be.wanadoo.com/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-canada} -\end_inset +\end_inset Canada -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Freenet6]{http://www.freenet6.net/} -\end_inset +\end_inset - /48 Delegation, Canada -\newline +\newline \begin_inset LatexCommand \url[Getting IPv6 Using Freenet6 on Debian]{http://www.linuxjournal.com/article.php?sid=5963&mode=thread&order=0} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Freenet6 creater]{http://www.viagenie.qc.ca/en/index.shtml} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-china} -\end_inset +\end_inset China -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[CERNET-Nokia]{http://tb.6test.edu.cn/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-germany} -\end_inset +\end_inset Deutschland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6bone Knoten Leipzig]{http://6bone.informatik.uni-leipzig.de/} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Info bez. Hackangriff (2001)]{http://www.mail-archive.com/ipv6@uni-muenster.de/msg00056.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Berkom]{http://fix.ipv6.berkom.de/cgi-bin/tb.pl} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-estonia} -\end_inset +\end_inset Estlanda -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Estpak]{http://tunnelbroker.ipv6.estpak.ee/?tunnel&PHPSESSID=aa2184190cc2cc6d3a6f6ddd01ae3635} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Europa -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XS26 Distributed Tunnel Broker]{http://www.xs26.net/} -\end_inset +\end_inset , USA & Europa -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-uk} -\end_inset +\end_inset Großbritannien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NTT Europe]{http://www.uk.v6.ntt.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[NTT]{http://www.nttv6.net/} -\end_inset +\end_inset , Großbritannien - IPv6 Versuch. IPv4 Tunnel und native IPv6 Standleitungs-Verbindungen. POPs gibt es in: London, Düsseldorf, New Jersey (USA, East Coast) Cupertino (USA, West Coast) Tokio -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[BtexacT IPv6 Tunnel Broker Service]{https://tb.ipv6.btexact.com/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPNG-UK]{http://ipng.org.uk/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-italy} -\end_inset +\end_inset Italien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Centro Studi e Laboratory Telecomunicazioni]{https://carmen.cselt.it/ipv6tb/} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Downloadpage: TunnelBroker Version 2.1.]{http://carmen.cselt.it/cgi-bin/download.pl?pkg=TunnelBroker} -\end_inset +\end_inset ) -\newline +\newline IPv6 Tunnel Broker: \begin_inset LatexCommand \url[Installation instructions]{http://carmen.cselt.it/ipv6/tools/ipv6tb/Installing-ipv6tb.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Comv6]{http://www.comv6.com/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Bersafe]{http://www.bersafe.it} -\end_inset +\end_inset (italienische Sprache) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Telecom Italia LAB]{http://carmen.ipv6.tilab.com/} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Tunnelbroker Software Downloadpage]{http://carmen.ipv6.tilab.com/cgi-bin/download.pl?pkg=TunnelBroker} -\end_inset +\end_inset ) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-japan} -\end_inset +\end_inset Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internet Initiative Japan]{http://www.iij.ad.jp/IPv6/index-e.html} -\end_inset +\end_inset \lang english ( \begin_inset LatexCommand \url[Japanese language]{http://www.iij.ad.jp/IPv6/} -\end_inset +\end_inset ) \lang ngerman - IPv6 native Standleitungs- und IPv6 tunneling Service -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-malaysia} -\end_inset +\end_inset Malaysia -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Manis]{http://tbroker.manis.net.my/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-netherlands} -\end_inset +\end_inset Niederlande -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XS26 - "Access to Six"]{http://www.xs26.net/} -\end_inset +\end_inset - mit POPs in Slovakei, Tschechischen Republik, Niederlanden, Deutschland und Ungarn. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPng Netherland]{http://www.ipng.nl/} -\end_inset +\end_inset - Intouch, SurfNet, AMS-IX, UUNet, Cistron, RIPE NCC und AT&T sind am AMS-IX angeschlossen. Unter bestimmten Voraussetzungen ist es möglich, einen statischen Tunnel zu bekommen. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SURFnet Customers]{http://www.ipv6.surfnet.nl/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-norway} -\end_inset +\end_inset Norwegen -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UNINETT]{http://www.uninett.no/testnett/index.en.html} -\end_inset +\end_inset - Pilot IPv6 Service (für Kunden): tunnelbroker & address allocation -\newline +\newline \begin_inset LatexCommand \url[Uninett-Autoupdate-HOWTO]{http://www.guruz.de/Uninett-Autoupdate-HOWTO} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english - \begin_inset LatexCommand \label{information-tunnelbroker-spain} -\end_inset +\end_inset Spanien -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Consulintel]{http://tb.consulintel.euro6ix.org/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-switzerland} -\end_inset +\end_inset Schweiz -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Tunnelbroker AS8758]{http://tunnelbroker.as8758.net/} -\end_inset +\end_inset , Dolphins Network Systems (seit 20.12.2002 online) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-usa} -\end_inset +\end_inset USA -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ESnet]{http://www.es.net/hypertext/welcome/pr/ipv6.html} -\end_inset +\end_inset , USA - Energy Sciences Network: Tunnel Registry & Address Delegation für direkt angeschlossene ESnet Sites und ESnet Partner. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6REN]{http://www.6ren.net/} -\end_inset +\end_inset , USA - Die 6ren Initiative wird durch das Energy Sciences Network (ESnet) koordiniert, dem 'Network for the Energy Research program' des US Dept. of Energy, angesiedelt am California's Lawrence Berkeley National Laboratory. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XS26 Distributed Tunnel Broker]{http://www.xs26.net/} -\end_inset +\end_inset , USA & Europa -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Hurricane Electric]{http://ipv6tb.he.net/} -\end_inset +\end_inset , US backbone; -\newline +\newline \begin_inset LatexCommand \url[Hurrican Electric Tunnelbroker]{http://tunnelbroker.net/} -\end_inset +\end_inset (also available under \begin_inset LatexCommand \url[http://tunnelbroker.com/]{http://tunnelbroker.com/} -\end_inset +\end_inset ) -\newline +\newline Presseaussendung: \begin_inset LatexCommand \url[Hurricane Electric Upgrades IPv6 Tunnel Broker]{http://www.he.net/releases/release6.html} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Tunnel Broker Endpoint Autoupdate]{http://ipv6.he.net/tunnelbroker-update.php} -\end_inset +\end_inset , Perl Skript -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english - \begin_inset LatexCommand \label{information-tunnelbroker-singapore} -\end_inset +\end_inset Singapore -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[http://tunnel-broker.singnet.com.sg/]{http://tunnel-broker.singnet.com.sg/} -\end_inset +\end_inset , with NAT and IPsec option -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-more} -\end_inset +\end_inset Weitere Tunnel broker... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Public 6to4 relay routers]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset (MS IIE Boycott!) -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-infrastructure-nativeipv6service} -\end_inset +\end_inset Native IPv6 Dienste -\layout Standard +\end_layout +\begin_layout Standard Anmerkung: Die folgenden Dienste sind meist nur mit einer gültigen IPv6 Verbbindung erreichbar! -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english - \begin_inset LatexCommand \label{information-nativeipv6nntp} -\end_inset +\end_inset Net News (NNTP) -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[news.ipv6.scarlet-internet.nl]{nntp://news.ipv6.scarlet-internet.nl/} -\end_inset +\end_inset (erreichbar über alle SixXS POPs) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6gameserver} -\end_inset +\end_inset Spiele Server -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Quake2]{http://www.viagenie.qc.ca/en/ipv6/quake2/ipv6-quake2.shtml} -\end_inset +\end_inset über IPv6 -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6ircserver} -\end_inset +\end_inset IRC Server -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Cyconet]{http://ipv6.cyconet.org/?id=server} -\end_inset +\end_inset (Cyconet IRCnet Servers über IPv6) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Radiosender, Musik-Streams -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Experimental Live IPv6 Stream!]{http://aopteryx.informatik.uni-leipzig.de:8000/live.mp3} -\end_inset +\end_inset , Universität Leipzig, Deutschland -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6webserver} -\end_inset +\end_inset Web Server -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Peter Bieringer's Home of Linux IPv6 HOWTO ]{http://www.ipv6.bieringer.de/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Fehlt etwas? Vorschläge sind Willkommen! -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-maillists} -\end_inset +\end_inset Mailinglisten -\layout Standard +\end_layout +\begin_layout Standard Weitere Listen von Mailinglisten sind verfügbar unter: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / Mailling Lists]{http://www.deepspace6.net/sections/lists.html} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Die größten Mailinglisten sind in folgender Tabelle zusammengefasst: -\layout Standard +\end_layout +\begin_layout Standard . -\layout Standard +\end_layout - -\begin_inset Tabular +\begin_layout Standard +\begin_inset Tabular @@ -14983,1003 +17655,1087 @@ Die gr \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Schwerpunkt -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Request e-mail Adresse -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize subscriben -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize e-mail Adresse der Mailingliste -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Sprache -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Zugang via WWW -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Linux Kernel Networking inkl. IPv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) oss.sgi.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize netdev -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize netdev (at) oss.sgi.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Archive]{http://oss.sgi.com/projects/netdev/archive/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Linux und IPv6 allgemein (1) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) list.f00f.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize linux-ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize linux-ipv6 (at) list.f00f.org (3) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Linux Impl. des IPv6 Protokolls -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Web-based, siehe URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize project6 (at) ferrara.linux.it -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info]{http://project6.ferrara.linux.it/sections/lists.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Subscription]{http://mailman.ferrara.linux.it/listinfo/project6} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Mobile IP(v6) für Linux -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) list.mipl.mediapoli.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize mipl -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize mipl (at) list.mipl.mediapoli.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info]{http://www.mipl.mediapoli.com/mailinglist.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.mipl.mediapoli.com/mail-archive/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Linux IPv6 User & USAGI -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize usagi-users-ctl (at) linux-ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize usagi-users (at) linux-ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info / Search]{http://www.linux-ipv6.org/ml/index.html#usagi-users} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.linux-ipv6.org/ml/usagi-users/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize IPv6 und Debian Linux -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Web-based, siehe URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize debian-ipv6 (at) lists.debian.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info/Subscription/Archive]{http://lists.debian.org/debian-ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize IPv6/6bone in Deutschland -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) atlan.uni-muenster.de -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize ipv6 (at) uni-muenster.de -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Dt./Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info]{http://www.join.uni-muenster.de/JOIN/ipv6/texte-englisch/mailingliste.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.join.uni-muenster.de/local/majordomo/ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize 6bone -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) isi.edu -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize 6bone -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize 6bone (at) isi.edu -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info]{http://www.6bone.net/6bone_email.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://mailman.isi.edu/pipermail/6bone/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize IPv6 Diskussion -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) sunroof.eng.sun.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize ipng -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize ipng (at) sunroof.eng.sun.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info]{http://playground.sun.com/pub/ipng/html/instructions.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{ftp://playground.sun.com/pub/ipng/mail-archive/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Mirror of archive]{http://www.wcug.wwu.edu/lists/ipng/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize IPv6 User allgemein -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize users -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize users (at) ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info]{http://www.ipv6.org/mailing-lists.html} -\end_inset +\end_inset -\size default +\size default \lang english , \begin_inset LatexCommand \url[Archive]{http://news.gmane.org/thread.php?group=gmane.network.ipv6.general} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Bugtracking Internet Programme (2) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize bugtraq-subscribe (at) securityfocus.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize bugtraq (at) securityfocus.com (3) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info]{http://online.securityfocus.com/popups/forums/bugtraq/intro.shtml} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://online.securityfocus.com/archive/1} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize IPv6 im Allgemeinen -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Web-based, siehe URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize ipv6 (at) ipng.nl -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Englisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info/Subscription]{http://mailman.ipng.nl/mailman/listinfo/ipv6/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://mailman.ipng.nl/pipermail/ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize majordomo (at) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize ipv6 (at) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard - -\size scriptsize +\size scriptsize Portugisisch -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - -\size scriptsize +\begin_layout Standard +\size scriptsize \begin_inset LatexCommand \url[Info]{http://www.marcelo.pro.br/mailman/listinfo/ipv6} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard . -\layout Standard +\end_layout +\begin_layout Standard (1) empfohlen bei allgemeinen Linux & IPv6 Fragen -\layout Standard +\end_layout +\begin_layout Standard (2) sehr empfohlen wenn Sie Server-Programme zur Verfügung stellen. -\layout Standard +\end_layout +\begin_layout Standard (3) Mailingliste ist moderiert. -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Fehlt etwas? Vorschläge sind Willkommen! -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Via Web sind auch folgende Mailinglisten & Newsgroups verfügbar: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (France)]{http://www.tile.net/lists/showlists.php?list_id=35905} -\end_inset +\end_inset -\newline +\newline Beschreibung: ipv6 Cette liste existe pour discuter en francais de IP version 6. Elle s'adresse aux personnes desirant demarer des aujourd'hui des tests @@ -15988,164 +18744,164 @@ Beschreibung: ipv6 Cette liste existe pour discuter en francais de IP version Pour de plus amples informations: \begin_inset LatexCommand \url[http://www.urec.fr/IPng]{http://www.urec.fr/IPng} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Tunnelbroker Maillingliste (Germany)]{http://www.ipv6.uni-leipzig.de/~6bone/tb/maillist.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (Hungary)]{http://www.tile.net/lists/showlists.php?list_id=36611} -\end_inset +\end_inset -\newline +\newline Beschreibung: ipv6 Az IPv6 protokoll listaja Konfiguracios es adminisztracios kerdesek az IPv6-al kapcsolatban. \begin_inset LatexCommand \url[(Archivum)]{http://www.ipv6.fsz.bme.hu/mlists/ipv6/ipv6.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[student-ipv6 (India)]{http://groups.yahoo.com/group/student-ipv6} -\end_inset +\end_inset -\newline +\newline Beschreibung: Dies ist eine Newsgruppe für die 'Student Awareness group of IPv6' in Indien -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPV6-CNR@LISTSERV.CNR.IT (Italy)]{http://www.lsoft.com/scripts/wl.exe?SL1=IPV6-CNR&H=LISTSERV.CNR.IT} -\end_inset +\end_inset -\newline +\newline Beschreibung: Gruppo di interesse IPv6 del CNR -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-jp (Japan)]{http://www.tile.net/lists/showlists.php?list_id=14761} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (Japan)]{http://www.tile.net/lists/showlists.php?list_id=37305} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[sun-ipv6-users]{http://groups.yahoo.com/group/sun-ipv6-users} -\end_inset +\end_inset -\newline +\newline Beschreibung: Bitte berichten Sie Probleme/Vorschläge in Bezug auf die IPng Implementation von SUN Microsystems -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-BITS]{http://groups.yahoo.com/group/IPv6-BITS} -\end_inset +\end_inset -\newline +\newline Beschreibung: Diese Liste dient der Koordination des Projekts Vertebrae. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[openbsd-ipv6]{http://www.tile.net/lists/showlists.php?list_id=23220} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6]{http://www.tile.net/lists/showlists.php?list_id=35203} -\end_inset +\end_inset -\newline +\newline Beschreibung: Diese Mailingliste dient der technischen Diskussion der Möglichkei ten von ipv6/ipsec WRT OpenBSD. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[linux-bangalore-ipv6]{http://groups.yahoo.com/group/linux-bangalore-ipv6} -\end_inset +\end_inset -\newline +\newline Beschreibung: Die IPv6 deployment Liste der Bangalore Linux User Group -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[gab]{http://www.tile.net/lists/showlists.php?list_id=32034} -\end_inset +\end_inset -\newline +\newline Beschreibung: Schwerpunkt der diskussion sind die Geographic Addressing Plans für IPv6. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-bsd-user]{http://www.tile.net/lists/showlists.php?list_id=37430} -\end_inset +\end_inset -\newline +\newline Beschreibung: Diese Liste behandelt die INRIA/IMAG IPv6 Implementation. Cette liste de discussion est au sujet de l'implementation INRIA/IMAG IPv6. Elle est bilingue Francais/Anglais. Die Mailingliste ist zweisprachig, Französisch & Englisch. If you wish to contact the implementors, try ipv6-bsd-core@imag.fr Si vous voulez contacter les implementeurs, essayez ipv6-bsd-core@imag.fr -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[gated-ipv6]{http://www.tile.net/lists/showlists.php?list_id=41375} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[packet-switching]{http://groups.yahoo.com/group/packet-switching} -\end_inset +\end_inset -\newline +\newline Beschreibung: Dies Liste behandelt folgende Themen: packet switching theory, technology, implementation and application in any relevant aspect including without limitation LAPB, X.25, SDLC, P802.1d, LLC, IP, IPv6, IPX, DECNET, @@ -16153,523 +18909,595 @@ Beschreibung: Dies Liste behandelt folgende Themen: packet switching theory, like SNMP, e-mail, network transparent window systems, protocol implementation, protocol verification, conformance testing and tools used in maintaining or developing packet switching systems. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[mumbaiinternetgroup]{http://groups.yahoo.com/group/mumbaiinternetgroup} -\end_inset +\end_inset -\newline +\newline Beschreibung: Dieses Forum behandelt Internet-Themen & -Entwicklungen im Asiatisch-Pazifischen Raum. Beinhaltet sind Themen wie IPv4, IPv6, Multilingual DNS, Autonomous System Numbers, Internet Governence ... -\layout Itemize +\end_layout +\begin_layout Itemize de.comm.protocols.tcp-ip -\newline +\newline Beschreibung: Umstellung auf IPv6 -\newline +\newline Quelle: \begin_inset LatexCommand \url[Chartas der Newsgruppen in de.*]{http://www.faqs.org/faqs/de-newsgroups/chartas/index.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Google Group: \begin_inset LatexCommand \url[comp.protocols.tcp-ip]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=comp.protocols.tcp-ip} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Google Group: \begin_inset LatexCommand \url[linux.debian.maint.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=linux.debian.maint.ipv6} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Google Group: \begin_inset LatexCommand \url[microsoft.public.platformsdk.networking.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=microsoft.public.platformsdk.networking.ipv6} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Google Group: \begin_inset LatexCommand \url[fa.openbsd.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=fa.openbsd.ipv6} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlinetesttools} -\end_inset +\end_inset Online-Werkzeuge -\layout Subsection +\end_layout +\begin_layout Subsection Test-Werkzeuge -\layout Itemize +\end_layout +\begin_layout Itemize finger, nslookup, ping, traceroute, whois: \begin_inset LatexCommand \url[UK IPv6 Resource Centre / The test page]{http://www.cs-ipv6.lancs.ac.uk/ipv6/testing/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize ping, traceroute, tracepath, 6bone registry, DNS: \begin_inset LatexCommand \url[JOIN / Testtools]{http://www.join.uni-muenster.de/lab/testtools.html} -\end_inset +\end_inset (nur in deutscher Sprache, sollte aber keine Probleme für nicht Deutsch sprechende Personen sein) -\layout Itemize +\end_layout +\begin_layout Itemize traceroute6, whois: \begin_inset LatexCommand \url[IPng.nl]{http://www.ipng.nl/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english AAAA Lookup Checker \begin_inset LatexCommand \url[http://www.cnri.dit.ie/cgi-bin/check_aaaa.pl]{http://www.cnri.dit.ie/cgi-bin/check_aaaa.pl} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english Verschiedene Werkzeuge: \begin_inset LatexCommand \url[IPv6tools]{http://www.ipv6tools.com/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[IPv6 Adress Analye Werkzeug]{http://doc.tavian.com/ipv6util/index.htm} -\end_inset +\end_inset (ähnlich zur Informations-Option von ipv6calc) -\layout Subsection +\end_layout +\begin_layout Subsection Informationsbeschaffung -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6BONE Registry]{http://www.kessens.com/~david/6bone/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[List of worldwide all IPv6-aggregated IP-Blocks]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6allocs.html} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 Looking Glasses -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Looking Glass at SURRIEL]{http://linux.uninet.edu:81/lg/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DRENv6 Looking Glass]{http://www.v6.dren.net/lg/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection \lang english Hilfsapplikationen -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[IPv6 Prefix Calculator]{http://www.tdoi.org/prefcalc.php} -\end_inset +\end_inset von \begin_inset LatexCommand \url[TDOI]{http://www.tdoi.org/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[DNS record checker]{http://www.maths.tcd.ie/cgi-bin/check_dns.pl} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-trainingsandseminars} -\end_inset +\end_inset Trainings, Seminare -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Training and Workshop]{http://www.aerasec.de/workshops/ipv6.html} -\end_inset +\end_inset , AERAsec, Deutschland (derzeit nur in deutscher Sprache) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migrating to IPv6]{http://www.seminarinformation.com/wconnect/wc.dll?sis~details0~194045} -\end_inset +\end_inset , Learning Tree International -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[CIW Internetworking Professional Training CBT CD]{http://www.e-trainonline.com/html/ciw_internetworking_profession.html#IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Training Pages]{http://www.trainingpages.net/x/category.html?kw=125} -\end_inset +\end_inset , U.K. - Suche nach IPv6 (13 Kurse, 22.12.2002) -\layout Standard +\end_layout +\begin_layout Standard Fehlt etwas? Vorschläge sind Willkommen! -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlinediscovery} -\end_inset +\end_inset 'Die Online Entdekcung' ... -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[IPv6: Addressing The Needs Of the Future]{http://www.amazon.com/exec/obidos/tg/detail/-/B00006334Y/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset [DOWNLOAD: PDF] -\layout Standard +\end_layout +\begin_layout Standard von Yankee Group (Autor) -\layout Standard +\end_layout +\begin_layout Standard Listenpreis: -\series bold +\series bold $595.00 -\layout Standard +\end_layout +\begin_layout Standard Edition: e-book (Acrobat Reader) -\layout Standard +\end_layout +\begin_layout Standard Seiten: -\series bold +\series bold 3 -\series default +\series default (drei) -\layout Standard +\end_layout +\begin_layout Standard Hrsg.: MarketResearch.com; ISBN B00006334Y; (1. November 2001) -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold ;-) -\series default +\series default Die Auflagenhöhe dieses eBooks wäre doch sehr interessant... -\newline +\newline -\layout Chapter +\end_layout +\begin_layout Chapter Versions-Überblick / Danksagung / Zum Schluss -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{revision-history} -\end_inset +\end_inset Versions-Überblick -\layout Standard +\end_layout +\begin_layout Standard Die Versionen x.y. werden im Internet veröffentlicht. -\layout Standard +\end_layout +\begin_layout Standard Die Versionen x.y.z stellen Zwischenschritte dar, die nur als LyX- und SGML-Datei im TLDP-CVS veröffentlicht werden. Dadurch, dass allerdings Deep Space 6 diese SGML-Dateien spiegelt und daraus öffentliche Versionen generiert, sind diese auch dort und auf den Servern, die Deep Space 6 spiegeln, verfügbar. -\layout Subsection +\end_layout +\begin_layout Subsection Ausgabe 0.x -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Englische Sprachversion (Peter Bieringer's Original) -\layout Standard +\end_layout +\begin_layout Standard Die Historie der Änderungen der englischen Sprachversion finden Sie dort: \begin_inset LatexCommand \url[TLDP / Linux+IPv6-HOWTO / Revision History]{http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/revision-history.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Deutsche Sprachversion -\layout Description +\end_layout +\begin_layout Description 0.48.de.1 2005-01-11/PB: Sync mit Original -\layout Description +\end_layout +\begin_layout Description 0.47.de.1 2004-08-30/PB: Sync mit Original -\layout Description +\end_layout +\begin_layout Description 0.46.5.de.1 2004-07-22/PB: Sync mit Original -\layout Description +\end_layout +\begin_layout Description 0.46.4.de.1 2004-07-19/PB: Sync mit Original und kleine Korrekturen der Übersetzung -\layout Description +\end_layout +\begin_layout Description 0.46.2.de.1 2004-05-22/PB: Sync mit Original -\layout Description +\end_layout +\begin_layout Description 0.46.1.de.1 2004-04-18/PB: Sync mit Original -\layout Description +\end_layout +\begin_layout Description 0.46.de.1 2004-04-04/PB: Sync mit Original (Italienische Übersetzung verfügbar, Informationen über DHCPv6, kleinere Updates) -\layout Description +\end_layout +\begin_layout Description 0.45.1.de.1 2004-01-12/PB: Sync mit Original (kleine Erweiterung) -\layout Description +\end_layout +\begin_layout Description 0.45.de.1 2004-01-11/PB: Sync mit Original (kleine Korrekturen, URL-Korrekturen und Erweiterungen) -\layout Description +\end_layout +\begin_layout Description 0.44.2.de.1 2003-10-30/PB: Sync mit Original (kleine Korrektur) -\layout Description +\end_layout +\begin_layout Description 0.44.de.1 2003-08-15/PB: Sync mit Original (URL-Korrekturen, Tipp bei tcp_wrappers und Apache2) -\layout Description +\end_layout +\begin_layout Description 0.43.2.de.2 2003-07-26/PB: Sync mit Original (URL-Korrekturen) -\layout Description +\end_layout +\begin_layout Description 0.43.2.de.1 2003-06-11/PB: Sync mit Original (URL-Korrekturen) -\layout Description +\end_layout +\begin_layout Description 0.43.1.de.2 2003-06-11/PB: Typo gefixt -\layout Description +\end_layout +\begin_layout Description 0.43.1.de.1 2003-06-07/PB: Sync mit Original (Links, IPsec) -\layout Description +\end_layout +\begin_layout Description 0.43.de.1 2003-06-05/PB: Sync mit Original (SuSe-Linux-Tipps) -\layout Description +\end_layout +\begin_layout Description 0.41.4.de.1 2003-05-02/PB: Sync mit Original (URL-Korrekturen) -\layout Description +\end_layout +\begin_layout Description 0.41.3.de.1 2003-04-23/PB: Sync mit Original (URL-Korrektur) -\layout Description +\end_layout +\begin_layout Description 0.41.1.de.1 2003-03-31/PB: Sync mit Original (URL-Korrektur) -\layout Description +\end_layout +\begin_layout Description 0.41.de.1 2003-03-22/PB: Angabe der URL dieser Übersetzung -\layout Description +\end_layout +\begin_layout Description 0.40.2.de.1 2003-02-27/PB: Sync mit Original (URL-Korrektur) -\layout Description +\end_layout +\begin_layout Description 0.40.1.de.1 2003-02-12/PB: Sync mit Original (Debian-Linux-Konfiguration), Ersetzen der Info über verfügbare Übersetzungen durch einen Link zum Original. -\layout Description +\end_layout +\begin_layout Description 0.40.de.1 2003-02-10/PB: Kleine sprachliche Änderungen und paar kleine Verbesserung en. -\layout Description +\end_layout +\begin_layout Description 0.39.2.de.1 2003-02-10/GK: Erste öffentliche Version in deutscher Sprache. Diese Version entspricht inhaltlich der englischen Version 0.39.2. Der Zusatz de.1 bezeichnet die Revision der deutschen Sprachversion. Diese Version wurde unter Mandrake Linux 9.0 mit LyX Version 1.2.1 und der Klasse DocBook book (SGML) erstellt. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{credits} -\end_inset +\end_inset Danksagung -\layout Standard +\end_layout +\begin_layout Standard Dieser feinen Liste hinzugefügt werden können Sie am schnellsten, indem Sie mir Bug fixes, Korrekturen und/oder Updates schicken ;-) -\layout Standard +\end_layout +\begin_layout Standard Wenn Sie eine größere Überarbeitung vornehmen wollen, können Sie dazu die LyX Datei (siehe \begin_inset LatexCommand \ref[original source]{general-original-source} -\end_inset +\end_inset ) verwenden und mir entsprechende diffs dann zusenden, diffs der SGML-Version sind hingegen nicht sehr nützlich. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{major-credits} -\end_inset +\end_inset Primärer Dank... -\layout Itemize +\end_layout +\begin_layout Itemize David Ranch : Er ermutigte mich zum Schreiben dieses HOWTOs, für seine Anmerkungen zu den ersten englischen Versionen, für seine Beiträge zu den IPv6 Test-Ergebnissen auf der IPv6-Homepage des Autors. Ebenfalls für seine größeren Überarbeitungen und Vorschläge. -\layout Itemize +\end_layout +\begin_layout Itemize Pekka Savola : Für größere Überarbeitungen der englischen Version, seinen Input und Vorschläge. -\layout Itemize +\end_layout +\begin_layout Itemize Georg Käfer : Für das Aufspüren eines Fehlers bei der PDF Erstellung (durch LDP Betreuer Greg Ferguson behoben), den Input betreff deutscher Bücher, einer großen URL-Liste, die Überprüfung aller Links und vieler weiterer Vorschläge, Korrekturen und Beiträge. -\layout Subsection +\end_layout +\begin_layout Subsection Sonstiger Dank... -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Verwaltung des Dokuments -\layout Standard +\end_layout +\begin_layout Standard Als Neuling ein LDP HOWTO zu schreiben (in LyX schreiben sowie SGML konformer Export zu DocBook) ist nicht so einfach, wie von so manchem behauptet wird. Es gibt einige sonderbare Fallen... Nichtsdestoweniger Dank an: -\layout Itemize +\end_layout +\begin_layout Itemize Autoren des \begin_inset LatexCommand \url[LDP Author Guide]{http://www.tldp.org/LDP/LDP-Author-Guide/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize B. Guillon: Für sein \begin_inset LatexCommand \url[DocBook with LyX HOWTO]{http://perso.libertysurf.fr/bgu/doc/db4lyx/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{content-related-credits} -\end_inset +\end_inset Inhalt des Dokuments -\layout Standard +\end_layout +\begin_layout Standard Mein Dank für Fixes und Hinweise ist hier aufgelistet - und die Liste wird mit der Zeit sicherlich länger werden... -\newline -Bezüglich der englischen Version finden Sie in dieser, hier werden nur diejenige -n, die die deutsche Version betreffen, aufgelistet. -\layout Itemize +\newline +Bezüglich der englischen Version finden + Sie in dieser, hier werden nur diejenigen, die die deutsche Version betreffen, + aufgelistet. +\end_layout +\begin_layout Itemize Nico Schottelius : Typo gefunden -\layout Itemize +\end_layout +\begin_layout Itemize Jens Nachtigall : Fehler gefunden -\layout Section +\end_layout +\begin_layout Section Zum Schluss -\layout Standard +\end_layout +\begin_layout Standard Danke für's Lesen. Hoffentlich ist es von Nutzen! -\layout Standard +\end_layout +\begin_layout Standard Falls Sie irgendeine Frage haben, abonnieren sie eine entsprechende \begin_inset LatexCommand \ref[maillist]{information-maillists} -\end_inset +\end_inset und diskutieren Sie ihr Problem unter Angabe möglichst vieler Informationen. -\the_end +\end_layout + +\end_body +\end_document diff --git a/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.fr.lyx b/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.fr.lyx index 0fbec4b4..0006cdd2 100644 --- a/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.fr.lyx +++ b/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.fr.lyx @@ -1,5 +1,7 @@ -#LyX 1.3 created this file. For more info see http://www.lyx.org/ -\lyxformat 221 +#LyX 1.4.1 created this file. For more info see http://www.lyx.org/ +\lyxformat 245 +\begin_document +\begin_header \textclass docbook-book \begin_preamble @@ -10,339 +12,510 @@ \fontscheme default \graphics default \paperfontsize default -\spacing single -\papersize Default -\paperpackage a4 -\use_geometry 0 -\use_amsmath 0 -\use_natbib 0 -\use_numerical_citations 0 +\spacing single +\papersize default +\use_geometry false +\use_amsmath 1 +\cite_engine basic +\use_bibtopic false \paperorientation portrait \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \defskip medskip \quotes_language swedish -\quotes_times 2 \papercolumns 1 \papersides 1 \paperpagestyle default +\tracking_changes false +\output_changes true +\end_header -\layout Title -\added_space_top vfill \added_space_bottom vfill +\begin_body + +\begin_layout Standard +\begin_inset VSpace vfill +\end_inset + + +\end_layout + +\begin_layout Title HOWTO IPv6 Linux (fr) -\layout SGML +\end_layout + +\begin_layout Standard +\begin_inset VSpace vfill +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout FirstName +\end_layout -Peter -\layout Surname +\end_inset + +\end_layout + +\begin_layout Standard +Peter +\end_layout + +\begin_layout Standard Bieringer -\layout SGML +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard
pb chez bieringer point de
 -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard 0.49.fr.126-02-2006 M B Voir \begin_inset LatexCommand \ref[l'historique des révisions]{revision-history} -\end_inset +\end_inset pour plus de détails -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard 0.48.1.fr.120-01-2005 MB Voir \begin_inset LatexCommand \ref[l'historique des révisions]{revision-history} -\end_inset +\end_inset pour plus de détails -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard 0.47.fr.105-09-2004 M B Voir \begin_inset LatexCommand \ref[l'historique des révisions]{revision-history} -\end_inset +\end_inset pour plus de détails -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard 0.44.fr.105-09-2003 M B Voir \begin_inset LatexCommand \ref[l'historique des révisions]{revision-history} -\end_inset +\end_inset pour plus de détails -\layout SGML +\end_layout + +\end_inset -\lang english +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard + -\layout SGML +\end_layout -\layout Abstract +\end_inset + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard + +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Abstract L'objet de cet HOWTO IPv6 Linux est de répondre à la fois aux questions basiques et avancées au sujet d'IPv6 sur le système d'exploitation Linux. Cet HOWTO fournira au lecteur assez d'information pour installer, configurer et utiliser les applications IPv6 sur les machines Linux. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-general} -\end_inset +\end_inset Généralités -\layout Comment +\end_layout +\begin_layout Standard +\begin_inset Note Comment +status collapsed + +\begin_layout Standard CVS-ID: $Id$ -\layout Standard +\end_layout +\end_inset + + +\end_layout + +\begin_layout Standard Vous trouverez les informations concernant les différentes traductions disponibl es dans la section \begin_inset LatexCommand \ref[Traductions]{general-translations} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-copright} -\end_inset +\end_inset Copyright, licence et autres -\layout Subsection +\end_layout +\begin_layout Subsection Copyright -\layout Standard +\end_layout +\begin_layout Standard Rédaction et Copyright (C) 2001-2006 Peter Bieringer, traduction francophone et Copyright (C) 2003-2006 Michel Boucey -\layout Subsection +\end_layout +\begin_layout Subsection Licence -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold Cet HOWTO IPv6 Linux est publié sous GPL GNU version 2 -\series default +\series default : -\newline +\newline -\newline +\newline -\newline +\newline -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard L'HOWTO IPv6 Linux, un guide sur la façon de configurer et d'utiliser IPv6 sur les systèmes Linux. -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Copyright (C) 2001-2006 Peter Bieringer -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Ce document est libre; vous pouvez le redistribuer et/ou le modifier dans les termes de la Licence Publique Générale GNU, telle que publiée par la Free Software Foundation; soit dans sa version 2, ou (c'est à votre convenance) une quelconque version postérieure. -\layout Standard +\end_layout +\begin_layout Standard Ce programme est distribué dans l'espoir qu'il sera utile, mais SANS AUCUNE GARANTIE; sans même de garantie impliquée par une COMMERCIALISATION ou d'ADÉQUATION A UNE FIN PARTICULIÈRE. Voir la Licence Publique Générale GNU pour de plus amples détails. -\layout Standard +\end_layout +\begin_layout Standard Vous devriez avoir reçu une copie de la Licence Publique Générale GNU allant de paire avec ce programme; sinon, écrivez à la Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -\layout Subsection +\end_layout +\begin_layout Subsection A propos de l'auteur -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'auteur, Internet et IPv6 -\layout Itemize +\end_layout +\begin_layout Itemize 1993: J'ai pris contact avec l'Internet par la pratique du mél et des news sur un client en mode texte (par exemple, rechercher "e91abier" sur groups.googl e.com, c'est moi). -\layout Itemize +\end_layout +\begin_layout Itemize 1996: J'ai été sollicité pour concevoir un cours sur IPv6, incluant des travaux pratiques sur le système d'exploitation Linux. -\layout Itemize +\end_layout +\begin_layout Itemize 1997: Début de la rédaction d'un guide sur la façon d'installer, de configurer et d'utiliser IPv6 sur les systèmes Linux, appelé \begin_inset LatexCommand \url[HowTo - IPv6 & Linux ]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset (voir \begin_inset LatexCommand \url[IPv6 & Linux - HowTo/History]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-0.html#history} -\end_inset +\end_inset pour plus d'information). -\layout Itemize +\end_layout +\begin_layout Itemize 2001: Début de la rédaction de cet HOWTO IPv6 Linux. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Contact -\layout Standard +\end_layout +\begin_layout Standard L'auteur peut être contacté par mél à mais aussi -\emph on +\emph on via -\emph default +\emph default \begin_inset LatexCommand \url[sa page personnelle]{http://www.bieringer.de/pb/} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Il vit actuellement à Munich [dans la partie nord du Schwabing] / Bavière / Allemagne (sud) / Europe (centrale) / Terre (surface/continent). -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-category} -\end_inset +\end_inset Catégorie -\layout Standard +\end_layout +\begin_layout Standard Cet HOWTO relève de la catégorie " -\emph on +\emph on Réseau/Protocoles -\emph default +\emph default ". -\layout Section +\end_layout +\begin_layout Section La version, l'historique et ce qu'il reste à faire -\layout Subsection +\end_layout +\begin_layout Subsection La version -\layout Standard +\end_layout +\begin_layout Standard La version actuelle est visible dès le début de ce document. -\layout Standard +\end_layout +\begin_layout Standard En ce qui concerne les autres versions/traductions, voir également \begin_inset LatexCommand \url[http://www.bieringer.de/linux/IPv6/]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection L'historique -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'essentiel de l'historique -\layout Standard +\end_layout +\begin_layout Standard 30-11-2001:Début de la conception du nouvel HOWTO. -\layout Standard +\end_layout +\begin_layout Standard 02-01-2002: Une quantité importante du contenu est achevée, publication de la première version du premier chapitre (version 0.10). -\layout Standard +\end_layout +\begin_layout Standard 14-01-2002: Plus achevé, avec relectures, publication de la première version complète du document (version 0.14). -\layout Standard +\end_layout +\begin_layout Standard 16-08-2002: La traduction polonaise est en cours -\layout Standard +\end_layout +\begin_layout Standard 31-10-2002: La traduction chinoise est disponible (voir \begin_inset LatexCommand \ref[les traductions]{general-translations} -\end_inset +\end_inset pour en savoir plus) -\layout Standard +\end_layout +\begin_layout Standard 10-11-2002: La traduction allemande est en cours -\layout Standard +\end_layout +\begin_layout Standard 10-02-2003: La traduction allemande est disponible -\layout Standard +\end_layout +\begin_layout Standard 09-04-2003: La traduction francophone est en cours -\layout Standard +\end_layout +\begin_layout Standard 09-05-2003: La traduction francophone est disponible -\layout Standard +\end_layout +\begin_layout Standard 15-08-2003: La traduction espagnole est en cours -\layout Standard +\end_layout +\begin_layout Standard 16-10-2003: La traduction italienne est en cours -\layout Standard +\end_layout +\begin_layout Standard 12-03-2004: La traduction italienne est disponible -\layout Standard +\end_layout +\begin_layout Standard 18-06-2004: La traduction grecque est en cours -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'historique complet -\layout Standard +\end_layout +\begin_layout Standard Voir \begin_inset LatexCommand \ref[l'historique des révisions]{revision-history} -\end_inset +\end_inset à la fin de ce document. -\layout Subsection +\end_layout +\begin_layout Subsection Ce qu'il reste à faire -\layout Itemize +\end_layout +\begin_layout Itemize Rédiger les contenus manquants -\layout Itemize +\end_layout +\begin_layout Itemize Achever la correction orthographique -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-translations} -\end_inset +\end_inset Les traductions -\layout Standard +\end_layout +\begin_layout Standard Les traductions doivent toujours contenir l'URL, le numéro de version et le copyright du document original (le vôtre aussi). Merci de ne pas traduire le journal original des modifications, ce n'est @@ -352,291 +525,332 @@ Les traductions doivent toujours contenir l'URL, le num Depuis la version 0.27, il apparaît aussi que la plus grande part du contenu fourni par moi-même a été rédigée. Les traductions doivent toujours prendre comme source la version anglo-saxonne. -\layout Subsection +\end_layout +\begin_layout Subsection Traductions disponibles -\layout Subsubsection +\end_layout +\begin_layout Subsubsection En langue française -\layout Standard +\end_layout +\begin_layout Standard La traduction francophone par Michel Boucey a été mise en chantier le 9 avril 2003, à partir de la révision 0.41.1. Elle est disponible depuis le 9 mai 2003 sur Deep Space 6, avec pour URL original \begin_inset LatexCommand \url[mirrors.deepspace6.net / Linux+IPv6-HOWTO-fr]{http://mirrors.deepspace6.net/Linux+IPv6-HOWTO-fr/} -\end_inset +\end_inset . Je ( -\emph on +\emph on Michel Boucey -\emph default +\emph default ) remercie par avance toute personne qui aidera, de quelque façon, à améliorer cette traduction. On peut me contacter à l'adresse mél . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les autres traductions disponibles -\layout Standard +\end_layout +\begin_layout Standard L'information concernant les traductions disponibles en d'autres langues que l'anglais et le français peut être trouvée dans le document original: \begin_inset LatexCommand \url[TLDP / Linux+IPv6-HOWTO / Translations]{http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/general-translations.html} -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section Un peu de technique -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{general-original-source} -\end_inset +\end_inset Le document original de cet HOWTO -\layout Standard +\end_layout +\begin_layout Standard Cet HOWTO est actuellement rédigé avec la version 1.2.0 de LyX sur un système Linux Red Hat 7.3 avec un patron SGML (livre DocBook). Il est disponible en vue des contributions à l'URL \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Modification des lignes de code propres à LyX -\layout Standard +\end_layout +\begin_layout Standard Les modifications des lignes de code propres à LyX sont réalisées par un script \begin_inset Quotes sld -\end_inset +\end_inset maison \begin_inset Quotes srd -\end_inset +\end_inset , \begin_inset Quotes sld -\end_inset +\end_inset lyxcodelinewrapper.pl \begin_inset Quotes srd -\end_inset +\end_inset , que vous pouvez obtenir par CVS pour votre propre compte: \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset ( -\emph on +\emph on NdT -\emph default +\emph default : ces lignes ne gênent pas la génération au format SGML, mais celles aux formats PS et PDF à partir du SGML généré couramment, -\emph on +\emph on i.e. -\emph default +\emph default sans ce script). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La génération du SGML -\layout Standard +\end_layout +\begin_layout Standard Le code SGML est généré en utilisant la fonction d'exportation de LyX. -\layout Standard +\end_layout +\begin_layout Standard Des solutions ont été apportées afin de créer un code SGML plus propre (voir aussi ici pour le programme Perl, \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset ): -\layout Itemize +\end_layout +\begin_layout Itemize L'exportation du document LyX ne créait pas proprement les balises \begin_inset Quotes sld -\end_inset +\end_inset colspan \begin_inset Quotes srd -\end_inset +\end_inset - l'outil qui règle le problème: \begin_inset Quotes sld -\end_inset +\end_inset sgmllyxtabletagfix.pl \begin_inset Quotes srd -\end_inset +\end_inset (le problème est définitivement réglé depuis la version 1.2.0 de LyX) -\layout Itemize +\end_layout +\begin_layout Itemize LyX utilise parfois des entités spéciales gauche/droite, à la place des guillemets habituels, qui seront présentes dans le code HTML. Certains navigateurs n'interprètent pas très bien ces balises (Opéra 6 TP 2 ou Konquéror sont connus pour ce problème) - l'outil qui règle le problème: \begin_inset Quotes sld -\end_inset +\end_inset sgmllyxquotefix.pl \begin_inset Quotes srd -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Les références en ligne à la version HTML de cet HOWTO (lien/ancrage) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La page d'index maître -\layout Standard +\end_layout +\begin_layout Standard Généralement, une référence vers la page d'index maître est recommandée. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les pages dédiées -\layout Standard +\end_layout +\begin_layout Standard Parce que les pages HTML sont générées à partir du fichier SGML, le nommage des fichiers HTML prend une tournure aléatoire. Et cependant, certaines pages ont des balises assignées par LyX, dont il résulte un nommage constant. Ces balises sont très utiles aux références et ne devraient pas être changées à l'avenir. -\layout Standard +\end_layout +\begin_layout Standard Si vous pensez que j'ai oublié une balise, merci de me le faire savoir, et je l'ajouterai. -\layout Section +\end_layout +\begin_layout Section Préface -\layout Standard +\end_layout +\begin_layout Standard Quelques petites choses d'abord: -\layout Subsection +\end_layout +\begin_layout Subsection Combien se promène-t-il de versions de l'HOWTO Linux & IPv6? -\layout Standard +\end_layout +\begin_layout Standard En incluant celui-ci, il y a trois documents HOWTO disponibles. Mes excuses si cela vous semble de trop ;) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La FAQ/HOWTO IPv6 Linux (obsolète) -\layout Standard +\end_layout +\begin_layout Standard Le premier document relatif à IPv6 a été écrit par -\emph on +\emph on Eric Osborne, -\emph default +\emph default et s'appelle \begin_inset LatexCommand \url[FAQ/HOWTO IPv6 Linux]{http://www.linuxhq.com/IPv6/} -\end_inset +\end_inset (merci de ne l'utiliser que pour des raisons historiques). -\series bold +\series bold La dernière version -\series default +\series default fut la 3.2.1, publiée le 14 juillet -\series bold +\series bold 1997 -\series default +\series default . -\layout Standard +\end_layout +\begin_layout Standard Merci de m'aider: si quelqu'un connaît la date anniversaire de cet HOWTO, merci de m'envoyer un mél (cette information est nécessaire à "l'historique"). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'HowTo - IPv6 & Linux (maintenu) -\layout Comment +\end_layout +\begin_layout Standard +\begin_inset Note Comment +status collapsed + +\begin_layout Standard Cet HOWTO est vraiment dénommé \begin_inset Quotes sld -\end_inset +\end_inset HowTo \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\end_inset + + +\end_layout + +\begin_layout Standard Il existe une seconde version appelée \begin_inset LatexCommand \url[HowTo - IPv6 & Linux - ]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset écrite par moi-même ( -\emph on +\emph on Peter Bieringer -\emph default +\emph default ) en pur HTML. -\series bold +\series bold Elle est née en -\series default +\series default avril -\series bold +\series bold 1997 -\series default +\series default et la première version anglo-saxonne a été publiée en juin 1997. Je continuerais à la -\series bold +\series bold maintenir -\series default +\series default , mais cela déclinera lentement (mais pas complètement) en faveur de l'HOWTO IPv6 Linux que vous lisez en ce moment. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'HOWTO IPv6 Linux (ce document) -\layout Standard +\end_layout +\begin_layout Standard Parce que l' \begin_inset LatexCommand \url[HowTo - IPv6 & Linux]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset est écrit en HTML pur, il n'est vraiment pas compatible avec le \begin_inset LatexCommand \url[Projet de Documentation Linux]{http://www.tldp.org/} -\end_inset +\end_inset ( -\emph on +\emph on Linux Documentation Project, -\emph default +\emph default ou TLDP). J'ai ( -\emph on +\emph on Peter Bieringer -\emph default +\emph default ) reçu une demande fin novembre 2001 de réécriture de l' \begin_inset LatexCommand \url[HowTo -IPv6 & Linux]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset en SGML. Cependant, à cause de la discontinuité de cet HOWTO ( \begin_inset LatexCommand \url[le future de l'HowTo - IPv6 & Linux]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-0.html#history} -\end_inset +\end_inset ), et de la standardisation croissante d'IPv6, je décidais d'écrire un nouveau document couvrant aussi bien les questions simples ou avancées qui resteront @@ -645,395 +859,457 @@ Peter Bieringer au second HOWTO ( \begin_inset LatexCommand \url[HowTo - IPv6 & Linux]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset ). -\layout Section +\end_layout +\begin_layout Section Termes employés, glossaire et abréviations -\layout Subsection +\end_layout +\begin_layout Subsection Relatifs aux réseaux -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 10 Le système bien connu des nombres décimaux, représentant n'importe quelle valeur avec les chiffres 0-9. -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 16 Habituellement utilisée dans les langages de programmation de bas et haut niveaux, connue encore en tant que système numérique hexadécimal, représentant les valeurs avec les chiffres 0-9 et les caractères A-F (insensibl e à la casse). -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 85 Représentation d'une valeur grâce à 85 différents chiffres/caractères, cela permet des chaînes de caractères plus courtes mais jamais vue dans la pratique. -\layout Description +\end_layout +\begin_layout Description Bit Unité minimale de stockage, allumée( -\emph on +\emph on on -\emph default +\emph default )/vraie (1) ou éteinte( -\emph on +\emph on off -\emph default +\emph default )/fausse (0). -\layout Description +\end_layout +\begin_layout Description Byte Le plus souvent, une collection de 8 bits (mais ce n'est pas réellement une nécessité - regardez les systèmes des anciens ordinateurs). -\layout Description +\end_layout +\begin_layout Description Périphérique ici, matériel de connexion réseau, voir aussi NIC. -\layout Description +\end_layout -Hôte\SpecialChar ~ -à\SpecialChar ~ -double\SpecialChar ~ +\begin_layout Description +Hôte\InsetSpace ~ +à\InsetSpace ~ +double\InsetSpace ~ résidence Un hôte à double résidence est un noeud ayant deux interfaces réseau (physique ou virtuelle) sur deux liens différents, mais qui ne réalise pas de renvoi de paquets entre les interfaces. -\layout Description +\end_layout +\begin_layout Description Hôte Généralement, un hôte simple résident, présent sur un lien. Normalement, il n'a seulement qu'une interface réseau active, par exemple Ethernet ou (non pas -\emph on +\emph on et -\emph default +\emph default ) PPP. -\layout Description +\end_layout +\begin_layout Description Interface quasi-synonyme de \begin_inset Quotes sld -\end_inset +\end_inset périphérique \begin_inset Quotes srd -\end_inset +\end_inset , voir aussi NIC. -\layout Description +\end_layout -En-tête\SpecialChar ~ +\begin_layout Description +En-tête\InsetSpace ~ IP En-tête d'un paquet IP (chaque paquet réseau a un en-tête, son type dépendant de la couche réseau). -\layout Description +\end_layout +\begin_layout Description Lien Un lien est un médium de transport de paquet réseau de la couche 2, des exemples en sont Ethernet, PPP, SLIP, ATM, RNIS, Frame Relay, -\emph on +\emph on etc. -\layout Description +\end_layout +\begin_layout Description Noeud Un noeud est soit un hôte, soit un routeur. -\layout Description +\end_layout +\begin_layout Description Octet Une collection véritable de 8 bits, aujourd'hui synonyme de "byte". -\layout Description +\end_layout +\begin_layout Description Port Information destinée au distributeur TCP/UDP (couche 4) afin de transporter l'information à la couche supérieure. -\layout Description +\end_layout +\begin_layout Description Protocole Chaque couche réseau contient la plupart du temps un champ \begin_inset Quotes sld -\end_inset +\end_inset protocole \begin_inset Quotes srd -\end_inset +\end_inset facilitant la distribution de l'information transportée à la couche supérieure, comme cela peut se voir dans la couche 2 (MAC) et 3 (IP) -\layout Description +\end_layout +\begin_layout Description Routeur Un routeur est un noeud possédant une ou plusieurs interface(s) réseau, capable d'envoyer les paquets entre ses interfaces. -\layout Description +\end_layout +\begin_layout Description Socket Une socket IP est définie par ses adresses source et destination, ses ports et (association) -\layout Description +\end_layout +\begin_layout Description Pile Une collection de couches relative au réseau. -\layout Description +\end_layout -Masque\SpecialChar ~ +\begin_layout Description +Masque\InsetSpace ~ -\series bold +\series bold de -\series default -\SpecialChar ~ +\series default +\InsetSpace ~ -\series bold +\series bold sous-réseau -\series default +\series default Les réseaux IP utilisent un masque de bits afin de distinguer le réseau local de ceux qui sont distants. -\layout Description +\end_layout +\begin_layout Description Tunnel Un tunnel est typiquement une connexion point-à-point sur laquelle les paquets échangés transportent les données d'un autre protocole, un tunnel IPv6-in-IPv4 en est un exemple. -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{Glossaire} -\end_inset +\end_inset Abréviations -\layout Description +\end_layout +\begin_layout Description ACL -\emph on +\emph on Access Control List -\emph default +\emph default , Liste de Contrôle d'Accès -\layout Description +\end_layout +\begin_layout Description API -\emph on +\emph on Application Programming Interface -\emph default +\emph default , Interface de Programmation d'Application -\layout Description +\end_layout +\begin_layout Description ASIC -\emph on +\emph on Application Specified Integrated Circuit -\emph default +\emph default , Circuit Intégré d'Application Spécifique -\layout Description +\end_layout +\begin_layout Description BSD -\emph on +\emph on Berkeley Software Distribution -\emph default +\emph default , Distribution des Logiciels Berkeley -\layout Description +\end_layout -Bus\SpecialChar ~ +\begin_layout Description +Bus\InsetSpace ~ CAN Système de bus physique contrôlant un réseau ( -\emph on +\emph on NdT -\emph default +\emph default : voir par exemple \begin_inset LatexCommand \url[ici]{http://edelaunay.chez.tiscali.fr/buscan.htm} -\end_inset +\end_inset pour plus d'information) -\layout Description +\end_layout +\begin_layout Description ISP -\emph on +\emph on Internet Service Provider -\emph default +\emph default , Fournisseur d'Accès à Internet (FAI) -\layout Description +\end_layout +\begin_layout Description KAME Projet - effort conjoint de six entreprises au Japon pour fournir, mondialement et dans le cadre du logiciel libre, une pile IPv6 et IPsec (pour IPv4 et IPv6) pour les variantes de BSD \begin_inset LatexCommand \url[www.kame.net]{http://www.kame.net/} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description LIR -\emph on +\emph on Local Internet Registry -\emph default +\emph default , Bureau local d'enregistrement Internet -\layout Description +\end_layout +\begin_layout Description NIC -\emph on +\emph on Network Interface Card -\emph default +\emph default , Carte d'interface réseau -\layout Description +\end_layout +\begin_layout Description RFC -\emph on +\emph on Request for comments -\emph default +\emph default , Appel à commentaires - jeu de notes techniques et organisationnelles au sujet d'Internet. -\layout Description +\end_layout +\begin_layout Description USAGI Projet \begin_inset Quotes sld -\end_inset +\end_inset UniverSAl playGround for IPv6 \begin_inset Quotes srd -\end_inset +\end_inset - travaille à rendre disponible une pile protocolaire IPv6 destinée au système Linux qui soit d'une qualité apte à la production. -\layout Subsection +\end_layout +\begin_layout Subsection Relatifs à ce document -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Balisage en vue de l'encodage PDF/PS -\layout Standard +\end_layout +\begin_layout Standard Le caractère \begin_inset Quotes sld -\end_inset +\end_inset ¬ \begin_inset Quotes srd -\end_inset +\end_inset est utilisé pour signaler que le code est enveloppé en vue d'un meilleur affichage dans les fichiers PDF et PS. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Conventions -\layout Standard +\end_layout +\begin_layout Standard Dans les exemples génériques vous trouverez parfois ce qui suit: -\layout Code +\end_layout +\begin_layout Code -\layout Standard +\end_layout +\begin_layout Standard Pour une utilisation réelle sur votre système, en ligne de commande ou dans des scripts, cela doit être remplacé par le contenu adéquate (ôtez bien sûr les chevrons), et le résultat devrait être par exemple -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les commandes dans l'interpréteur de commandes (le -\emph on +\emph on shell -\emph default +\emph default ) -\layout Standard +\end_layout +\begin_layout Standard Les commandes exécutables en tant qu'utilisateur non-root commencent avec un $, par exemple -\layout Code +\end_layout +\begin_layout Code $ whoami -\layout Standard +\end_layout +\begin_layout Standard Les commandes exécutables en tant qu'utilisateur root commencent avec un #, par exemple -\layout Code +\end_layout +\begin_layout Code # whoami -\layout Section +\end_layout +\begin_layout Section Pré-requis à l'usage de cet HOWTO -\layout Subsection +\end_layout +\begin_layout Subsection Pré-requis personnels -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une expérience des outils Unix -\layout Standard +\end_layout +\begin_layout Standard Vous devriez être familiarisé avec les outils essentiels d'Unix comme -\emph on +\emph on grep -\emph default +\emph default , -\emph on +\emph on awk -\emph default +\emph default , -\emph on +\emph on find -\emph default +\emph default , -\emph on +\emph on etc -\emph default +\emph default , et connaître les options de ligne de commande les plus communément employées. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une expérience de la théorie des réseaux -\layout Standard +\end_layout +\begin_layout Standard Vous devriez connaître les notions de couche, de protocole, d'adresse, de câble, de socket, -\emph on +\emph on etc -\emph default +\emph default . Si vous êtes nouveau, voici un bon point de départ pour vous: \begin_inset LatexCommand \url[linuxports/howto/intro_to_networking]{http://www.linuxports.com/howto/intro_to_networking/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une expérience de la configuration IPv4 -\layout Standard +\end_layout +\begin_layout Standard Vous devriez absolument avoir quelque expérience de la configuration IPv4, sinon ce sera difficile pour vous de comprendre ce qui se passe réellement. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une expérience du Système des Noms de Domaine (DNS) -\layout Standard +\end_layout +\begin_layout Standard Vous devriez aussi comprendre en quoi consiste le Système des Noms de Domaine (DNS), ce qu'il fournit et comment s'en servir. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une expérience des stratégies de déboguage réseau -\layout Standard +\end_layout +\begin_layout Standard Vous devriez au moins savoir comment utiliser -\emph on +\emph on tcpdump -\emph default +\emph default et avoir connaissance de ce qu'il peut vous montrer. Sinon, le déboguage réseau sera très difficile pour vous. -\layout Subsection +\end_layout +\begin_layout Subsection Le matériel compatible avec le système d'exploitation Linux -\layout Standard +\end_layout +\begin_layout Standard Vous espérez certainement pouvoir expérimenter tout cela avec du vrai matériel, et pas seulement lire cet HOWTO jusqu'à tomber de sommeil. ;-7) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-basics} -\end_inset +\end_inset Les bases -\layout Section +\end_layout +\begin_layout Section Qu'est-ce qu'IPv6? -\layout Standard +\end_layout +\begin_layout Standard IPv6 est un nouveau protocole de la couche 3 (voir \color red \begin_inset LatexCommand \url[le modèle OSI]{http://www.linuxports.com/howto/intro_to_networking/c4412.htm#PAGE103HTML} -\end_inset +\end_inset \color default @@ -1041,23 +1317,23 @@ IPv6 est un nouveau protocole de la couche 3 (voir IPv4 a été conçu il y a déjà un certain de temps ( \begin_inset LatexCommand \url[RFC 760 / Le protocole Internet]{http://www.faqs.org/rfcs/rfc760.html} -\end_inset +\end_inset à partir de janvier 1980), et, dès le début, il y a eu de nombreuses demandes pour accroître la quantité d'adresses disponible et augmenter les capacités. Le RFC le plus récent est le \begin_inset LatexCommand \url[RFC 2460 / spécification du protocole Internet version 6]{http://www.faqs.org/rfcs/rfc2460.html} -\end_inset +\end_inset ( -\emph on +\emph on NdT -\emph default +\emph default : \begin_inset LatexCommand \url[une version francophone de ce RFC]{http://abcdrfc.free.fr/rfc-vf/rfc2460.html} -\end_inset +\end_inset ). Le changement essentiel apporté par IPv6 est la nouvelle conception de @@ -1066,100 +1342,122 @@ NdT Parce que la couche 3 est responsable de bout en bout du transport des paquets dont le routage est basé sur des adresses, elle doit inclure les nouvelles adresses IPv6, comme pour IPv4. -\layout Standard +\end_layout +\begin_layout Standard Pour en savoir plus sur l'histoire d'IPv6, jetez un oeil aux anciens RFC concernant IPv6, par exemple dans le \begin_inset LatexCommand \url[Guide / Références IPv6 SWITCH ]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{basic-history-IPv6-Linux} -\end_inset +\end_inset Historique d'IPv6 pour Linux -\layout Standard +\end_layout +\begin_layout Standard Les années 1992, 1993 et 1994 de l'histoire d'IPv6 (dans ses généralités) sont couvertes par le document suivant: \begin_inset LatexCommand \url[IPv6 ou IPng (IP nouvelle génération)]{http://www.laynetworks.com/IPv6.htm#CH3} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard A faire: plus de détails historiques, plus de contenu... -\layout Subsection +\end_layout +\begin_layout Subsection Au début -\layout Standard +\end_layout +\begin_layout Standard Le premier code réseau relatif à IPv6 a été ajouté au noyau Linux 2.1.8 en novembre 1996 par Pedro Roque. Il était fondé sur l'API BSD: -\layout Code +\end_layout +\begin_layout Code diff -u --recursive --new-file v2.1.7/linux/include/linux/in6.h -\layout Code +\end_layout +\begin_layout Code ¬ linux/include/linux/in6.h -\layout Code +\end_layout +\begin_layout Code --- v2.1.7/linux/include/linux/in6.h Thu Jan 1 02:00:00 1970 -\layout Code +\end_layout +\begin_layout Code +++ linux/include/linux/in6.h Sun Nov 3 11:04:42 1996 -\layout Code +\end_layout +\begin_layout Code @@ -0,0 +1,99 @@ -\layout Code +\end_layout +\begin_layout Code +/* -\layout Code +\end_layout +\begin_layout Code + * Types and definitions for AF_INET6 -\layout Code +\end_layout +\begin_layout Code + * Linux INET6 implementation -\layout Code +\end_layout +\begin_layout Code + * + * Authors: -\layout Code +\end_layout +\begin_layout Code + * Pedro Roque <******> -\layout Code +\end_layout +\begin_layout Code + * -\layout Code +\end_layout +\begin_layout Code + * Source: -\layout Code +\end_layout +\begin_layout Code + * IPv6 Program Interfaces for BSD Systems -\layout Code +\end_layout +\begin_layout Code + * -\layout Standard +\end_layout +\begin_layout Standard Les lignes présentées sont copiées du patch-2.1.8 (l'adresse mél a été effacée au copier&coller). -\layout Subsection +\end_layout +\begin_layout Subsection Après -\layout Standard +\end_layout +\begin_layout Standard A cause du manque de bras, l'implémentation d'IPv6 dans le noyau était incapable de suivre les projets discutés ou les RFC nouvellement mis à jour. En novembre 2000, un projet débute au Japon, appelé \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset , dont le but était d'implémenter dans Linux tout le support IPv6 manquant ou obsolète. @@ -1167,23 +1465,25 @@ A cause du manque de bras, l'impl FreeBSD, réalisée par le \begin_inset LatexCommand \url[projet KAME ]{http://www.kame.net/} -\end_inset +\end_inset . De temps à autre, ils créaient des archives de développement ( -\emph on +\emph on snapshots -\emph default +\emph default ) à partir des sources courantes du noyau Linux. -\layout Subsection +\end_layout +\begin_layout Subsection Actuellement -\layout Standard +\end_layout +\begin_layout Standard Malheureusement, le patch \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset est très volumineux, à tel point que les personnes s'occupant actuellement de maintenir les fonctionnalités réseau de Linux sont incapables de l'inclure @@ -1193,39 +1493,46 @@ Malheureusement, le patch (voir \begin_inset LatexCommand \url[le groupe de travail IP Version 6 (ipv6)]{http://www.ietf.org/html.charters/ipv6-charter.html} -\end_inset +\end_inset ). Cela peut poser des problèmes d'interopérabilité avec les autres systèmes d'exploitation. -\layout Subsection +\end_layout +\begin_layout Subsection A l'avenir -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset fait maintenant usage de la série des noyaux de développement Linux 2.5.x afin d'incorporer toutes les extensions actuelles dans cette version de développement; dans l'espoir que la série des noyaux 2.6.x comprenne une véritable implémentation à jour d'IPv6. -\layout Section +\end_layout +\begin_layout Section A quoi ressemblent les adresses IPv6? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Comme cela a été mentionné précédemment, les adresses IPv6 ont une longueur de 128 bits. Ce nombre de bits génère de très grands nombres, dont la quantité de chiffres est supérieure à 39: -\layout Code +\end_layout +\begin_layout Code 2^128-1: 340282366920938463463374607431768211455 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left De tels nombres ne sont vraiment pas des adresses pouvant être mémorisées. L'adresse IPv6 en elle-même est faite à partir d'une collection de bits (comme pour IPv4, bien que cela soit rarement su). @@ -1233,140 +1540,174 @@ De tels nombres ne sont vraiment pas des adresses pouvant En hexadécimal, 4 bits (mot aussi connu sous la dénomination de "nibble") sont représentés par un chiffre ou un caractère de 0-9 et a-f (10-15). Ce format réduit la longueur de l'adresse IPv6 à 32 caractères. -\layout Code +\end_layout +\begin_layout Code 2^128-1: 0xffffffffffffffffffffffffffffffff -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Cette représentation est encore peu praticable (possibilité de confusion ou de perte d'un simple chiffre hexadécimal), c'est pourquoi les concepteurs d'IPv6 ont choisi un format hexadécimal scindé en blocs de 16 bits, avec comme séparateur le caractère ":". De plus, le préfixe "0x" (le marqueur des valeurs hexadécimales utilisé dans les langages de programmation) est ôté: -\layout Code +\end_layout +\begin_layout Code 2^128-1: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Une adresse utilisable (nous verrons les différents types d'adresse plus tard) est par exemple: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -\layout Standard +\end_layout +\begin_layout Standard Dans un but de simplification, les zéros non significatifs de chaque bloc de 16 bits sont omis: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -> -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100:f101:210:a4ff:fee3:9566 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Une séquence de blocs de 16 bits ne comprenant que des zéros peut être remplacée par \begin_inset Quotes eld -\end_inset +\end_inset -\family typewriter +\family typewriter :: -\family default +\family default \begin_inset Quotes eld -\end_inset +\end_inset . Mais pas plus d'une fois par adresse, sinon il ne s'agirait plus d'une représentation unique. -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:0:0:0:1 -> 3ffe:ffff:100:f101::1 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left La plus importante réduction qui peut être observée est celle de l'adresse localhost d'IPv6: -\layout Code +\end_layout +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0001 -> ::1 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Il existe aussi une représentation dite -\emph on +\emph on compacte -\emph default +\emph default , encodée en base85 ( \begin_inset LatexCommand \url[RFC 1924 / A Compact Representation of IPv6 Addresses]{http://www.faqs.org/rfcs/rfc1924.html} -\end_inset +\end_inset , publié le 1er avril 1996), jamais vue véritablement employée, sans doute une blague de 1er avril; en voici cependant un exemple: -\layout Code +\end_layout +\begin_layout Code # ipv6calc --addr_to_base85 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -\layout Code +\end_layout +\begin_layout Code Itu&-ZQ82s>J%s99FJXT -\layout Quotation +\end_layout +\begin_layout Quotation Info: -\emph on +\emph on ipv6calc -\emph default +\emph default est un programme de formatage d'adresse IPv6 et de conversion pouvant être trouvé ici: \lang ngerman \begin_inset LatexCommand \url[ipv6calc]{http://www.deepspace6.net/projects/ipv6calc.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[miroir]{http://mirrors.bieringer.de/www.deepspace6.net/projects/ipv6calc.html} -\end_inset +\end_inset ) -\layout Section +\end_layout +\begin_layout Section FAQ (Les bases) -\layout Subsection +\end_layout +\begin_layout Subsection Pourquoi IPv6 et non pas IPv5 comme successeur d'IPv4? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Dans tout en-tête IP, les 4 premiers bits sont réservés à la version du protocole. C'est ainsi qu'un numéro de protocole entre 0 et 15 est théoriquement possible: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left 4: est déjà pris pour IPv4 -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left 5: est réservé au protocole de flux ( -\emph on +\emph on Stream Protocol -\emph default +\emph default , ou STP - \begin_inset LatexCommand \url[RFC 1819 / Internet Stream Protocol Version 2]{http://www.faqs.org/rfcs/rfc1819.html} -\end_inset +\end_inset ) (qui n'a jamais véritablement conquis le public) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Le prochain numéro libre était 6. Et voilà comment IPv6 était né! -\layout Subsection +\end_layout +\begin_layout Subsection L'adresse IPv6: pourquoi un tel nombre de bits? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Lors de la conception d'IPv4, les gens pensaient que 32 bits seraient suffisants pour le monde, dans sa globalité. Rétrospectivement, 32 bits ont été jusqu'à maintenant suffisants, et seront @@ -1376,16 +1717,19 @@ Lors de la conception d'IPv4, les gens pensaient que 32 bits seraient suffisants Pensez aux téléphones mobiles, aux voitures (incluant les périphériques électroniques sur bus CAN), aux grille-pain, aux réfrigérateurs, aux interrupte urs d'éclairage, -\emph on +\emph on etc -\emph default +\emph default . -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Les concepteurs ont alors choisi 128 bits, 4 fois plus en longueur et une quantité 2^96 fois plus importante qu'IPv4 aujourd'hui. -\layout Standard +\end_layout +\begin_layout Standard La quantité utilisable est cependant inférieure à ce qu'il semble. La raison en est que, dans le schéma d'adresse défini actuellement, 64 bits sont utilisés pour l'identifiant d'interface, les 64 autres bits sont @@ -1393,24 +1737,27 @@ La quantit Compte tenu des niveaux stricts actuels d'agrégation (/48, /32, ...), il est encore possible d'"épuiser" cette quantité, mais bien heureusement, pas dans un avenir proche. -\layout Standard +\end_layout +\begin_layout Standard Voir aussi pour plus d'information le \begin_inset LatexCommand \url[RFC 1715 / The H Ratio for Address Assignment Efficiency]{http://www.faqs.org/rfcs/rfc1715.html} -\end_inset +\end_inset et le \begin_inset LatexCommand \url[RFC 3194 / The Host-Density Ratio for Address Assignment Efficiency]{http://www.faqs.org/rfcs/rfc3194.html} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection L'adresse IPv6: pourquoi un si petit nombre de bits pour sa nouvelle conception? -\layout Standard +\end_layout +\begin_layout Standard Pendant ce temps, il y a (c'est possible) des gens sur Internet (je n'en connais qu'un, Jim Fleming...) qui pensent déjà à IPv8, et même jusqu'à IPv16, dont les conceptions sont loin d'être couramment reçues et implémentées. @@ -1418,9 +1765,9 @@ Pendant ce temps, il y a (c'est possible) des gens sur Internet (je n'en regard de l'en-tête placé au-dessus des données transportées. En considérant le minimum de la taille de l'Unité Maximale de Transfert ( -\emph on +\emph on Maximum Transfer Uni -\emph default +\emph default t, ou MTU), la longueur de l'en-tête en IPv4 est de 20 octets (c'est le minimum, car elle peut monter à 60 octets avec les options IPv4), et en IPv6, elle est de 48 octets (longueur constante). @@ -1435,20 +1782,22 @@ t, ou MTU), la longueur de l'en-t Finalement, cela n'aurait pas été d'une conception correcte si 10% ou 20% des données transférées dans un paquet de la couche 3 avaient été utilisés pour les adresses et non pas pour la charge utile. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-addresstypes} -\end_inset +\end_inset Les types d'adresse IPv6 -\layout Standard +\end_layout +\begin_layout Standard Comme pour IPv4, l'adresse IPv6 peut être scindée en une partie réseau et une partie hôte, par l'usage d'un masque de sous-réseau. -\layout Standard +\end_layout +\begin_layout Standard IPv4 a montré que parfois cela serait bien si plus d'une adresse IP pouvaient être assignées à une interface, chacune à un but bien précis (alias, multi-cast ). @@ -1456,323 +1805,389 @@ IPv4 a montr à plus d'une adresse IPv6 d'être assignées à une interface. Il n'y a actuellement aucune limite définie par aucun RFC, mais seulement par l'implémentation de la pile IPv6 (afin de prévenir les attaques DoS). -\layout Standard +\end_layout +\begin_layout Standard Pour employer le grand nombre de bits constitutifs de son adresse, IPv6 définit des types d'adresse basés sur certains regroupements de ces bits, qui, avec un peu de chance, ne devraient pas être modifiés à l'avenir (à la différence d'aujourd'hui avec IPv4, et l'histoire des classes A, B et C). -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left C'est ainsi que la totalité des bits est divisée en une partie réseau (les 64 supérieurs) et en une partie hôte (les 64 inférieurs), afin de faciliter l'auto-configuration. -\layout Section +\end_layout +\begin_layout Section Les adresses sans préfixe spécial -\layout Subsection +\end_layout +\begin_layout Subsection L'adresse localhost -\layout Standard +\end_layout +\begin_layout Standard C'est une adresse spéciale pour l'interface de bouclage ( -\emph on +\emph on loopback -\emph default +\emph default ), similaire à IPv4 avec sa "127.0.0.1". -\layout Code +\end_layout +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0001 -\layout Standard +\end_layout +\begin_layout Standard ou compressée: -\layout Code +\end_layout +\begin_layout Code ::1 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Les paquets ayant cette adresse comme source ou destination ne devraient jamais quittés l'hôte émetteur. -\layout Subsection +\end_layout +\begin_layout Subsection L'adresse non spécifiée -\layout Standard +\end_layout +\begin_layout Standard C'est une adresse spéciale telle que \begin_inset Quotes sld -\end_inset +\end_inset n'importe laquelle \begin_inset Quotes srd -\end_inset +\end_inset ( \begin_inset Quotes sld -\end_inset +\end_inset any \begin_inset Quotes srd -\end_inset +\end_inset ) ou \begin_inset Quotes sld -\end_inset +\end_inset 0.0.0.0 \begin_inset Quotes srd -\end_inset +\end_inset en IPv4 . Il s'agit pour IPv6 de: -\layout Code +\end_layout +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0000 -\layout Standard +\end_layout +\begin_layout Standard ou: -\layout Code +\end_layout +\begin_layout Code :: -\layout Standard +\end_layout +\begin_layout Standard Ces adresses sont essentiellement utilisées/vues dans les sockets d'écoute (à toute adresse IPv6) ou dans les tables de routage. -\layout Standard +\end_layout +\begin_layout Standard Note: l'adresse non spécifiée ne peut pas être utilisée comme adresse de destination. -\layout Subsection +\end_layout +\begin_layout Subsection L'adresse IPv6 avec adresse IPv4 intégrée -\layout Standard +\end_layout +\begin_layout Standard Il y a deux types d'adresse contenant une adresse IPv4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'adresse IPv6 mappée IPv4 -\layout Standard +\end_layout +\begin_layout Standard Les adresses IPv6 compatibles seulement avec IPv4 sont parfois utilisées/vues pour la création de socket par un démon disposant d'IPv6, mais à l'écoute d'une adresse IPv4. -\layout Standard +\end_layout +\begin_layout Standard Ces adresses sont définies par un préfixe spécial d'une longueur de 96 (a.b.c.d est l'adresse IPv4): -\layout Code +\end_layout +\begin_layout Code 0:0:0:0:0:ffff:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard ou en format compressé: -\layout Code +\end_layout +\begin_layout Code ::ffff:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard Par exemple, l'adresse IPv4 1.2.3.4 ressemble à ceci: -\layout Code +\end_layout +\begin_layout Code ::ffff:1.2.3.4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'adresse IPv6 compatible IPv4 -\layout Standard +\end_layout +\begin_layout Standard Utilisée pour le tunnelage automatique ( \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset ), en cours de remplacement par \begin_inset LatexCommand \ref[le tunnelage 6to4]{tunneling-6to4} -\end_inset +\end_inset . -\layout Code +\end_layout +\begin_layout Code 0:0:0:0:0:0:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard ou en format compressé: -\layout Code +\end_layout +\begin_layout Code ::a.b.c.d/96 -\layout Section +\end_layout +\begin_layout Section La partie réseau, aussi appelée préfixe -\layout Standard +\end_layout +\begin_layout Standard Les concepteurs ont défini certains types d'adresse et laissé un vaste champ libre à de futures définitions, telles que l'émergence de nouvelles exigences encore aujourd'hui inconnues. L'architecture d'adressage IPv6 ( \begin_inset LatexCommand \url[RFC 2373 de juillet 1998]{http://www.faqs.org/rfcs/rfc2373.html} -\end_inset +\end_inset ) définit le schéma d'adressage actuel, mais il y a déjà un nouveau brouillon disponible: \begin_inset LatexCommand \url[draft-ietf-ipngwg-addr-arch-*.txt]{ftp://ftp.ietf.org/internet-drafts/} -\end_inset +\end_inset . -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Jetons maintenant un coup d'oeil aux différents types de préfixe (et par conséquent aux différents types d'adresse IPv6): -\layout Subsection +\end_layout +\begin_layout Subsection Le type d'adresse lien-local -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Ce sont des adresses particulières qui n'auront de validité que sur le lien d'une interface. En utilisant cette adresse comme adresse de destination le paquet ne devrait jamais franchir un routeur. C'est utile pour des communications sur un lien telles que: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Y a-t-il quelqu'un d'autre sur ce lien? -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Y a-t-il quelqu'un d'autre sur ce lien ayant une adresse spéciale (on cherche par exemple à détecter la présence d'un routeur)? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Elles commencent par (où -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset x \begin_inset Quotes srd -\end_inset +\end_inset -\emph default +\emph default est n'importe quel caractère hexadécimal, couramment -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset 0 -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Code +\end_layout +\begin_layout Code fe8 -\shape italic -\emph on +\shape italic +\emph on x: <- actuellement le seul en usage. -\layout Code +\end_layout +\begin_layout Code fe9 -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fea -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code feb -\shape italic -\emph on +\shape italic +\emph on x: -\layout Standard +\end_layout +\begin_layout Standard Ce type d'adresse se trouve sur chaque interface disposant d'IPv6 après une auto-configuration sans état (ce qui est couramment le cas). -\layout Subsection +\end_layout +\begin_layout Subsection Le type d'adresse site-local -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Ces adresses sont similaires à ce que le RFC 1918 ( \begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://www.faqs.org/rfcs/rfc1918.html} -\end_inset +\end_inset ) définit aujourd'hui pour IPv4, avec en plus l'avantage que celui qui utilise ce type d'adresse a la capacité d'utiliser les 16 bits fournis pour un maximum de 65536 sous-réseaux. Comparable au 10.0.0.0/8 aujourd'hui en IPv4. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Autre avantage: parce qu'il est possible avec IPv6 d'assigner plus d'une seule adresse par interface, vous pouvez assigner une telle adresse site-local en plus de l'adresse globale. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Il commence par: -\layout Code +\end_layout +\begin_layout Code fec -\shape italic -\emph on +\shape italic +\emph on x: <- le plus couramment utilisé. -\layout Code +\end_layout +\begin_layout Code fed -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fee -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fef -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout -\layout Standard +\begin_layout Code +\end_layout + +\begin_layout Standard (où -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset x \begin_inset Quotes srd -\end_inset +\end_inset -\emph default +\emph default est n'importe quel caractère hexadécimal, couramment -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset 0 -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Standard +\end_layout +\begin_layout Standard \lang english Notez que des discussions sont en cours concernant la dépréciation de ce @@ -1780,338 +2195,405 @@ Notez que des discussions sont en cours concernant la d Pour en savoir plus, lire: \begin_inset LatexCommand \url[draft-ietf-ipv6-deprecate-site-local-XY.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard \lang english Pour des tests en laboratoire, de telles adresses restent un bon choix, à mon humble avis. -\layout Subsection +\end_layout +\begin_layout Subsection Le type d'adresse \begin_inset Quotes srd -\end_inset +\end_inset unicast globale (agrégeable) " -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Aujourd'hui, il y a un type d'adresse globale de défini (la première conception, appelée \begin_inset Quotes sld -\end_inset +\end_inset basée sur le fournisseur \begin_inset Quotes srd -\end_inset +\end_inset a été abandonnée il y a déjà quelques années ( \begin_inset LatexCommand \url[RFC 1884 / IP Version 6 Addressing Architecture [obsolete]]{http://www.faqs.org/rfcs/rfc1884.html} -\end_inset +\end_inset ), vous en trouverez des traces dans des sources anciennes du noyau Linux). -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Il commence par (les -\emph on +\emph on x -\emph default +\emph default étant des caractères hexadécimaux) -\layout Code +\end_layout +\begin_layout Code 2 -\shape italic -\emph on +\shape italic +\emph on xxx -\shape default -\emph default +\shape default +\emph default : -\layout Code +\end_layout +\begin_layout Code 3 -\shape italic -\emph on +\shape italic +\emph on xxx -\shape default -\emph default +\shape default +\emph default : -\layout Standard +\end_layout +\begin_layout Standard Note: la dénomination \begin_inset Quotes sld -\end_inset +\end_inset agrégeable \begin_inset Quotes srd -\end_inset +\end_inset est abandonnée dans les brouillons actuels. -\newline -Il y a quelques sous-types définis en plus, ci-dessous: -\layout Subsubsection +\newline +Il y a quelques sous-types définis + en plus, ci-dessous: +\end_layout +\begin_layout Subsubsection Les adresses de test 6bone -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Elles ont été les premières adresses globales à être définies et mises en usage. Elles commencent toutes par -\layout Code +\end_layout +\begin_layout Code 3ffe: -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f102::1 -\layout Standard +\end_layout +\begin_layout Standard Une adresse spéciale de test 6bone, qui ne sera jamais globalement unique, commence par -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff: -\layout Standard +\end_layout +\begin_layout Standard Et elle est la plupart du temps montrée dans les exemples passés, car si des adresses réelles sont montrées, il est possible à quelqu'un de les copier/coller dans ses propres fichiers de configuration. Ce type d'inadvertance cause des duplications d'adresse globalement unique. Cela pose de graves problèmes à l'hôte d'origine (par exemple recevoir des paquets en réponse de requêtes qu'il n'a pas émises). -\newline -Parce qu'IPv6 est maintenant en production, ce préfixe ne sera plus délégué - et probablement retiré du routage après 6 juin 2006 (voir +\newline +Parce qu'IPv6 est + maintenant en production, ce préfixe ne sera plus délégué et probablement + retiré du routage après 6 juin 2006 (voir \begin_inset LatexCommand \url[RFC 3701 / 6bone Phaseout]{http://www.faqs.org/rfcs/rfc3701.html} -\end_inset +\end_inset pour plus d'information). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les adresses 6to4 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Ce type d'adresse, conçu pour un mécanisme précis de tunnelage ( \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset et \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset ), encode une adresse IPv4 donnée et un sous-réseau possible. Il commence par -\layout Code +\end_layout +\begin_layout Code 2002: -\layout Standard +\end_layout +\begin_layout Standard Par exemple, pour représenter 92.168.1.1/5: -\layout Code +\end_layout +\begin_layout Code 2002:c0a8:0101:5::1 -\layout Standard +\end_layout +\begin_layout Standard Une petite ligne de commande peut vous aider à générer une telle adresse à partir d'une adresse IPv4 donnée: -\layout Code +\end_layout +\begin_layout Code ipv4="1.2.3.4"; sla="5"; printf "2002:%02x%02x:%02x%02x:%04x::1" `echo $ipv4 -\layout Code +\end_layout +\begin_layout Code ¬ | tr "." " "` $sla -\layout Standard +\end_layout +\begin_layout Standard Voir aussi \begin_inset LatexCommand \ref[le tunnelage utilisant 6to4]{tunneling-6to4} -\end_inset +\end_inset et \begin_inset LatexCommand \ref[information concernant le relayage de 6to4 par les routeurs]{information-joinipv6-6to4-tunneling} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les adresses assignées par un fournisseur dans la hiérarchie de routage -\layout Standard +\end_layout +\begin_layout Standard Ces adresses sont déléguées aux Fournisseurs d'Accès à Internet (FAI) et commencent par -\layout Code +\end_layout +\begin_layout Code 2001: -\layout Standard +\end_layout +\begin_layout Standard Les préfixes fournis aux FAI (aussi connus en tant que LIR) les plus importants (propriétaires de backbone) sont délégués par les \begin_inset LatexCommand \ref[centres locaux d'enregistrement]{information-majorregionregistries} -\end_inset +\end_inset ( -\emph on +\emph on local registries -\emph default +\emph default ) et ils possèdent actuellement un préfixe d'une longueur de 32. -\layout Standard +\end_layout +\begin_layout Standard Tout client peut obtenir de son FAI un préfixe d'une longueur de 48. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english Adresses réservées aux exemples et à la documentation -\layout Standard +\end_layout +\begin_layout Standard \lang english Actuellement, deux blocs d'adresses sont réservés aux exemples et à la documenta tion: -\layout Code +\end_layout +\begin_layout Code \lang english 3ffe:ffff::/32 -\layout Code +\end_layout +\begin_layout Code \lang english 2001:0DB8::/32 EXAMPLENET-WF -\layout Standard +\end_layout +\begin_layout Standard \lang english Ces blocs d'adresses devraient être filtrés sur la base des adresses source et, si possible, NE devraient PAS être acheminés par les routeurs en bordure d'Internet vers ce dernier. -\layout Subsection +\end_layout +\begin_layout Subsection Les adresses multicast -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Les adresses multicast sont utilisées pour les services y afférents. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Elles commencent par (xx est la valeur de la portée) -\layout Code +\end_layout +\begin_layout Code ff -\shape italic -\emph on +\shape italic +\emph on x -\shape default -\emph default +\shape default +\emph default y: -\layout Standard +\end_layout +\begin_layout Standard Elles se répartissent en différentes portées et types: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La portée multicast -\layout Standard +\end_layout +\begin_layout Standard La portée multicast est un paramètre spécifiant la distance maximale qu'un paquet multicast peut prendre vis-à-vis de son entité émettrice. -\layout Standard +\end_layout +\begin_layout Standard Actuellement, les régions suivantes (portées) sont définies: -\layout Itemize +\end_layout +\begin_layout Itemize ffx1: noeud-local, ces paquets ne quittent jamais le noeud. -\layout Itemize +\end_layout +\begin_layout Itemize ffx2: lien-local, ces paquets ne sont jamais transmis par les routeurs, ils ne quittent par conséquent jamais le lien spécifié. -\layout Itemize +\end_layout +\begin_layout Itemize ffx5: site-local, ces paquets ne quittent jamais le site. -\layout Itemize +\end_layout +\begin_layout Itemize ffx8: organisation-locale, ces paquets ne quittent jamais l'organisation (pas si simple à implémenter, cela doit être par le protocole de routage). -\layout Itemize +\end_layout +\begin_layout Itemize ffxe: portée globale. -\layout Itemize +\end_layout +\begin_layout Itemize les autres sont réservées. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les types multicast -\layout Standard +\end_layout +\begin_layout Standard Il y a déjà de nombreux types définis/réservés (voir le \begin_inset LatexCommand \url[RFC 2373 / IP Version 6 Addressing Architecture]{http://www.faqs.org/rfcs/rfc2373.html} -\end_inset +\end_inset pour les détails). Quelques exemples en sont: -\layout Itemize +\end_layout +\begin_layout Itemize Adresse de tous les noeuds: ID = 1h, correspond aux adresses de tous les hôtes présents sur le noeud local (ff01:0:0:0:0:0:0:1) ou au lien connecté (ff02:0:0:0:0:0:0:1). -\layout Itemize +\end_layout +\begin_layout Itemize Adresse de tous les routeurs: ID = 2h, correspond aux adresses de tous les routeurs présents sur le noeud local (ff01:0:0:0:0:0:0:2), sur le lien connecté (ff02:0:0:0:0:0:0:2), ou encore sur le site local (ff05:0:0:0:0:0:0:2). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'adresse multicast de sollicitation du lien-local -\layout Standard +\end_layout +\begin_layout Standard Adresse multicast spéciale utilisée comme adresse de destination dans la découverte de voisinage, car à la différence d'IPv4, ARP n'existe plus dans IPv6. -\layout Standard +\end_layout +\begin_layout Standard Un exemple de cette adresse ressemble à ceci -\layout Code +\end_layout +\begin_layout Code ff02::1:ff00:1234 -\layout Standard +\end_layout +\begin_layout Standard Le préfixe utilisé montre qu'il s'agit d'une adresse multicast lien-local. Le suffixe est généré à partir de l'adresse de destination. Dans cet exemple, un paquet devrait être envoyé à l'adresse \begin_inset Quotes eld -\end_inset +\end_inset fe80::1234 \begin_inset Quotes erd -\end_inset +\end_inset , mais la pile réseau ne connaît pas l'actuelle adresse MAC de la couche 2. Elle remplace les 104 bits supérieurs par \begin_inset Quotes eld -\end_inset +\end_inset ff02:0:0:0:0:1:ff00::/104 \begin_inset Quotes erd -\end_inset +\end_inset et laisse les 24 bits inférieurs inchangés. Cette adresse est maintenant utilisée 'sur le lien' afin de trouver le noeud correspondant, lequel va devoir émettre une réponse contenant son adresse MAC de couche 2. -\layout Subsection +\end_layout +\begin_layout Subsection Les adresses anycast -\layout Standard +\end_layout +\begin_layout Standard Les adresses anycast sont des adresses spéciales utilisées pour couvrir des besoins tels que déterminer le serveur DNS le plus proche, le serveur DHCP le plus proche, ou tout groupe dynamique similaire. @@ -2119,53 +2601,66 @@ Les adresses anycast sont des adresses sp ou site-local pour le moment). Le mécanisme anycast (au regard du client) sera pris en compte par un protocole de routage dynamique. -\layout Standard +\end_layout +\begin_layout Standard Note: Les adresses anycast ne peuvent être utilisées comme adresse source, elles sont utilisables uniquement comme adresse de destination. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection L'adresse anycast de routeur de sous-réseau -\layout Standard +\end_layout +\begin_layout Standard Un simple exemple d'une adresse anycast est celle d'un routeur de sous-réseau. Soit un noeud avec l'adresse IPv6 suivante assignée: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:210:a4ff:fee3:9566/64 <- L'adresse du noeud -\layout Standard +\end_layout +\begin_layout Standard L'adresse anycast de routeur de sous-réseau sera créée en laissant totalement blanc le suffixe (les 64 bits inférieurs): -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::/64 <- l'adresse anycast de routeur de sous-réseau -\layout Section +\end_layout +\begin_layout Section Les types d'adresse (partie hôte) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left En ce qui concerne les questions d'auto-configuration et de mobilité, Il a été décidé d'utiliser les 64 bits inférieurs de la partie hôte de l'adresse pour la plupart des types d'adresse actuels. Conséquemment, chaque sous-réseau détient une grande quantité d'adresses. -\layout Standard -\align left -Cette partie hôte peut être différemment considérée: -\layout Subsection +\end_layout +\begin_layout Standard +\align left +Cette partie hôte peut être différemment considérée: +\end_layout + +\begin_layout Subsection L'adresse calculée automatiquement (dite aussi \begin_inset Quotes sld -\end_inset +\end_inset sans état \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Standard +\end_layout +\begin_layout Standard Avec l'auto-configuration, la partie hôte de l'adresse est calculée en convertis sant l'adresse MAC d'une interface (si disponible), avec la méthode EUI-64, en une adresse IPv6 unique. @@ -2173,109 +2668,131 @@ sant l'adresse MAC d'une interface (si disponible), avec la m (ce qui arrive par exemple sur les périphériques virtuels), quelque chose d'autre (comme l'adresse IPv4 ou l'adresse MAC d'une interface physique) est utilisée à la place. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Considérons à nouveau le premier exemple: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:210:a4ff:fee3:9566 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left ici, -\layout Code +\end_layout +\begin_layout Code 210:a4ff:fee3:9566 -\layout Standard -\align left -est la partie hôte calculée à partir de l'adresse MAC de la NIC -\layout Code +\end_layout +\begin_layout Standard +\align left +est la partie hôte calculée à partir de l'adresse MAC de la NIC +\end_layout + +\begin_layout Code 00:10:A4:E3:95:66 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left en utilisant \begin_inset LatexCommand \url[IEEE EUI-64]{http://standards.ieee.org/regauth/oui/tutorials/EUI64.html} -\end_inset +\end_inset conçue pour les identifiants EUI-48. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Le problème d'incursion possible dans la sphère privée ( -\emph on +\emph on privacy problem -\emph default +\emph default ) avec les adresses automatiquement calculées, et une solution -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Parce que la partie hôte "automatiquement calculée \begin_inset Quotes srd -\end_inset +\end_inset est globalement unique (sauf lorsqu'un fabriquant de NIC utilise la même adresse MAC sur plus d'une NIC), la traque grâce à un client ( -\emph on +\emph on client tracking -\emph default +\emph default ) est possible sur l'hôte, dès lors qu'aucun proxy d'aucune sorte n'est utilisé. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left C'est un problème connu, et une solution a été apportée: l'extension \begin_inset Quotes sld -\end_inset +\end_inset sphère privée \begin_inset Quotes srd -\end_inset +\end_inset , définie dans le RFC 3041 ( \begin_inset LatexCommand \url[RFC 3041 / Privacy Extensions for Stateless Address]{http://www.faqs.org/rfcs/rfc3041.html} -\end_inset +\end_inset ; il y a déjà aussi un brouillon plus récent disponible: \begin_inset LatexCommand \url[draft-ietf-ipngwg-temp-addresses-*.txt]{ftp://ftp.ietf.org/internet-drafts/} -\end_inset +\end_inset ). Le principe est d'utiliser une valeur aléatoire et une valeur statique à partir desquelles un nouveau suffixe est généré à intervalle régulier. Note: ce n'est raisonnable que pour des connexions client sortantes, et n'est pas vraiment utile pour des machines réputées être des serveurs. -\layout Subsection +\end_layout +\begin_layout Subsection La configuration manuelle -\layout Standard +\end_layout +\begin_layout Standard Pour les serveurs, il est probablement plus aisé de se rappeler d'adresses plus simples; cela peut aussi se faire. Il est possible d'assigner une adresse IPv6 additionnelle à une interface, par exemple -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::1 -\layout Standard +\end_layout +\begin_layout Standard Pour les suffixes tels que \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset , montré dans l'exemple ci-dessus, il est requis que le septième bit le plus significatif soit positionné à 0 (le bit universel/local d'un identifiant automatiquement généré). Certaines autres (à part celles qui n'ont pas étaient choisies) combinaisons de bits sont réservées aux adresses anycast. -\layout Section +\end_layout +\begin_layout Section La longueur de préfixe nécessaire au routage -\layout Standard +\end_layout +\begin_layout Standard Dans les premières phases de la conception, il était prévu d'utiliser une approche intégrale de routage hiérarchique, et ce, afin de réduire au maximum la taille des tables de routage. @@ -2284,225 +2801,278 @@ Dans les premi routeurs (supérieur à 104 000 en mai 2001), la nécessité de réduire ce nombre afin de diminuer le besoin en mémoire du matériel (piloté par Circuit Intégré d'Application Spécifique, -\emph on +\emph on Application Specified Integrated Circuit -\emph default +\emph default , ou ASIC) maintenant les tables de routage, et, en conséquence, d'accroître la vitesse (dans l'espoir que moins d'entrées génèrent des recherches plus rapides). -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Aujourd'hui, le point de vue est que le routage sera conçu quasi-hiérarchiquemen t pour les réseaux ayant seulement un fournisseur de service. Pour plus d'une connexion à un ISP, ce n'est pas possible, et cela relève du problème de la multi-résidence (des informations sur la multi-résidence: \begin_inset LatexCommand \url[drafts*multi6*]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset \begin_inset LatexCommand \url[ IPv6 Multihoming Solutions]{http://arneill-py.sacramento.ca.us/ipv6mh/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection La longueur du préfixe (aussi connue en tant que "masque de réseau") -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Comme pour IPv4, la notion de chemin de réseau routable nécessaire au routage a ici sa place. Parce que la notation standard d'un masque réseau n'est pas très agréable pour un adressage sur 128 bits, les concepteurs ont employé le schéma du Routage Inter-Domaines IPv4 Sans Classe ( -\emph on +\emph on IPv4 Classless Inter Domain Routing -\emph default +\emph default , ou CIDR, défini dans le \begin_inset LatexCommand \url[ RFC 1519 / Classless Inter-Domain Routing]{http://www.faqs.org/rfcs/rfc1519.html} -\end_inset +\end_inset ), dans lequel est spécifié le nombre de bits de l'adresse devant être utilisé pour le routage. Il est aussi connu comme notation \begin_inset Quotes sld -\end_inset +\end_inset slash \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Un exemple: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:1:2:3:4:5/48 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left De cette notation seront extraits: -\layout Itemize +\end_layout +\begin_layout Itemize le réseau: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0100:0000:0000:0000:0000:0000 -\layout Itemize +\end_layout +\begin_layout Itemize le masque de réseau: -\layout Code +\end_layout +\begin_layout Code ffff:ffff:ffff:0000:0000:0000:0000:0000 -\layout Subsection +\end_layout +\begin_layout Subsection La correspondance à une route -\layout Standard +\end_layout +\begin_layout Standard Dans des conditions normales ( -\emph on +\emph on i.e. -\emph default +\emph default sans QoS), de la recherche dans une table de routage résulte la route ayant le plus grand nombre de bits d'adresse significatifs; autrement dit, la route avec le plus grand préfixe correspond la première. -\layout Standard +\end_layout +\begin_layout Standard Par exemple, si une table de routage affiche les entrées suivantes (la liste est incomplète): -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::/48 :: U 1 0 0 sit1 -\layout Code +\end_layout +\begin_layout Code 2000::/3 ::192.88.99.1 UG 1 0 0 tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Ci-dessous, les adresses de destination des paquets IPv6 dont le trafic sera routé au travers du périphérique désigné -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:1:2:3:4:5/48 -> trafic routé au travers du périphérique sit1 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:200:1:2:3:4:5/48 -> trafic routé au travers du périphérique tun6to4 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-systemcheck} -\end_inset +\end_inset La vérification d'un système prêt pour IPv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Avant de commencer à utiliser IPv6 sur votre hôte Linux, vous avez à tester si votre système est prêt pour IPv6. Pour ce faire, vous aurez peut-être d'abord un peu de travail. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{systemcheck-kernel} -\end_inset +\end_inset Un noyau prêt pour IPv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Les distributions contemporaines de Linux comportent déjà un noyau prêt pour IPv6, les capacités IPv6 sont en général compilées dans un module, mais il est possible que ce module ne soit pas chargé automatiquement au démarrage. -\layout Standard +\end_layout +\begin_layout Standard Voir la page \begin_inset LatexCommand \url[IPv6+Linux-status-distributions]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset pour obtenir les informations les plus à jour. -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold Note: vous ne devriez plus utiliser les noyaux de la série 2.2.x; car ils ne sont pas assez à jour vis-à-vis d'IPv6. -\layout Subsection +\end_layout +\begin_layout Subsection Vérifier la présence du support IPv6 dans le noyau actuellement en cours d'utilisation -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Afin de vérifier si oui ou non votre actuel noyau supporte IPv6, jetez un coup d'oeil dans votre système de fichiers /proc. Les entrées qui suivent doivent être présentes: -\layout Code +\end_layout +\begin_layout Code /proc/net/if_inet6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Un bref test automatique ressemble à: -\layout Code +\end_layout +\begin_layout Code # test -f /proc/net/if_inet6 && echo "Running kernel is IPv6 ready" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Si cela échoue, cela peut être parce que le module IPv6 n'est pas chargé. -\layout Subsection +\end_layout +\begin_layout Subsection Essayer de charger le module IPv6 -\layout Standard -\align left -Vous pouvez tenter de charger le module IPv6 en exécutant -\layout Code +\end_layout +\begin_layout Standard +\align left +Vous pouvez tenter de charger le module IPv6 en exécutant +\end_layout + +\begin_layout Code # modprobe ipv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Si c'est un succès, la présence de ce module sera testée comme par magie par la ligne suivante: -\layout Code +\end_layout +\begin_layout Code # lsmod |grep -w 'ipv6' && echo "IPv6 module successfully loaded" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Et la vérification montrée plus haut devrait maintenant se faire elle aussi avec succès. -\layout Standard +\end_layout +\begin_layout Standard Note: enlever le module n'est actuellement pas supporté et peut aboutir, sous certaines conditions, au -\emph on +\emph on crash -\emph default +\emph default du noyau. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Le chargement automatique du module -\layout Standard +\end_layout +\begin_layout Standard Il est possible d'automatiser le chargement du module IPv6 à la demande. Vous avez juste à ajouter les lignes qui suivent dans le fichier de configurati on du chargeur de modules du noyau (normalement /etc/modules.conf ou /etc/conf.mod ules): -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 ipv6 # chargement automatique du module IPv6 à la demande -\layout Standard +\end_layout +\begin_layout Standard Il est aussi possible de mettre hors service le chargement automatique du module IPv6 en utilisant la ligne suivante -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 off # rend indisponible le chargement automatique du module IPv6 -\layout Standard +\end_layout +\begin_layout Standard Note additionnelle: pour les noyaux de la série 2.6,le mécanisme du chargeur de modules a été repensé. Le nouveau fichier de configuration s'appellera /etc/modprobe.conf au lieu @@ -2510,93 +3080,110 @@ Note additionnelle: pour les noyaux de la s Pour de plus amples détails voir \begin_inset LatexCommand \url[le module-init-tool]{http://his.luky.org/ftp/mirrors/linux/kernel/people/rusty/modules/} -\end_inset +\end_inset -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Compiler un noyau à partir des seules sources brutes (facile, si vous connaissez les options dont vous avez besoin) -\layout Itemize +\end_layout +\begin_layout Itemize Recompiler les sources du noyau fournies par votre distribution Linux (parfois, ce n'est si simple que ça) -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Compiler un noyau avec l'extension USAGI -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Si vous vous décidez à compiler un noyau, vous devriez avoir une certaine expérience dans la compilation de noyau et lire l' \begin_inset LatexCommand \url[HOWTO sur le noyau Linux]{http://www.tldp.org/HOWTO/Kernel-HOWTO.html} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard La comparaison pratiquement la plus à jour entre un noyau original et un noyau comprenant USAGI est disponible dans \begin_inset LatexCommand \url[IPv6+Linux-status-kernel]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Compiler un noyau uniquement à partir des sources originales (vanille) -\layout Standard +\end_layout +\begin_layout Standard Plus d'éléments concernant la compilation d'un noyau disposant d'IPv6 peuvent par exemple être trouvés dans \begin_inset LatexCommand \url[IPv6-HOWTO-2#kernel]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-2.html#kernel} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Note: vous devriez autant que possible utiliser les noyaux de la série 2.6.x ou supérieures,car le support IPv6 de la série 2.4.x n'obtiendra qu'un portage partielet celui de la série 2.2.x est désespérément obsolète.). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Compiler un noyau avec l'extension USAGI -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Comme pour le noyau vanille, seulement recommandé aux utilisateurs avancés, déjà familiarisés avec IPv6 et la compilation noyau. Voir aussi \begin_inset LatexCommand \url[la FAQ du projet USAGI]{http://www.linux-ipv6.org/faq.html} -\end_inset +\end_inset et \begin_inset LatexCommand \url[comment obtenir le meilleur support IPv6 avec Linux (article)]{http://www.deepspace6.net/docs/best_ipv6_support.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[miroir]{http://mirrors.bieringer.de/www.deepspace6.net/docs/best_ipv6_support.html} -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection Les périphériques réseau prêts pour IPv6 -\layout Standard +\end_layout +\begin_layout Standard Les périphériques réseau n'ont pas tous déjà (ou n'auront jamais, pour certains) la capacité de transporter des paquets IPv6. L'état actuel de la situation quant à ce sujet peut être trouvé \begin_inset LatexCommand \url[ici]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html#transport} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard A cause de l'implémentation de la structure de la couche réseau du noyau, un problème majeur est qu'un paquet IPv6 n'est pas réellement reconnu par son numéro d'en-tête IP (6 au lieu de 4). @@ -2606,97 +3193,119 @@ A cause de l'impl Note: le paquet est bien encore transporté sur le lien, mais, côté récepteur, la distribution ne fonctionne pas (vous pouvez observer cela par exemple avec tcpdump). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Actuellement connus pour ne jamais être \begin_inset Quotes sld -\end_inset +\end_inset capables de lien IPv6 \begin_inset Quotes srd -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize IP sur Ligne Série ( -\emph on +\emph on Serial Line IP -\emph default +\emph default , SLIP, \begin_inset LatexCommand \url[RFC 1055 / SLIP]{http://www.faqs.org/rfcs/rfc1055.html} -\end_inset +\end_inset ), serait aujourd'hui mieux dénommé SLIPv4, noms de périphérique: slX -\layout Itemize +\end_layout +\begin_layout Itemize IP sur Ligne Parallèle, comme pour SLIP, noms de périphérique: plipX -\layout Itemize +\end_layout +\begin_layout Itemize RNIS avec encapsulation -\emph on +\emph on rawip -\emph default +\emph default , noms de périphérique: isdnX -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Actuellement connu pour ne pas être \begin_inset Quotes sld -\end_inset +\end_inset capable de lien IPv6 \begin_inset Quotes srd -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize RNIS avec encapsulation -\emph on +\emph on syncppp -\emph default +\emph default , noms de périphérique: ipppX (au sujet de la conception de ipppd, il fusionnera dans une couche PPP plus abstraite dans la série des noyaux 2.5.x) -\layout Section +\end_layout +\begin_layout Section Les outils de configuration réseau prêts pour IPv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Vous n'irez pas loin si vous faites tourner un noyau prêt pour IPv6 mais sans avoir d'outils pour configurer IPv6. Il existe plusieurs paquetages pouvant servir à cette tâche. -\layout Subsection +\end_layout +\begin_layout Subsection Le paquetage net-tools -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Le paquetage net-tools inclut certains outils tels que ifconfig et route qui vous aideront à configurer IPv6 sur une interface. Regardez la sortie d'ifconfig? ou celle de route?, et si vous y voyez quelque chose comme IPv6, ou inet6, c'est que l'outil est prêt pour IPv6. -\layout Standard -\align left -Vérification magique: -\layout Code +\end_layout +\begin_layout Standard +\align left +Vérification magique: +\end_layout + +\begin_layout Code # /sbin/ifconfig -? 2>& 1 | grep -qw 'inet6' && echo "utility 'ifconfig' is -\layout Code +\end_layout +\begin_layout Code ¬ IPv6-ready" -\layout Standard -\align left -La même vérification peut être réalisée pour route: -\layout Code +\end_layout +\begin_layout Standard +\align left +La même vérification peut être réalisée pour route: +\end_layout + +\begin_layout Code # /sbin/route -? 2>& 1 | grep -qw 'inet6' && echo "utility 'route' is IPv6-ready " -\layout Subsection +\end_layout +\begin_layout Subsection Le paquetage iproute -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Alexey N. Kuznetsov (actuellement la personne qui maintient le code réseau de Linux) a créé un jeu d'outils qui configure le réseau à travers le périphérique @@ -2704,255 +3313,312 @@ Alexey N. Vous aurez plus de fonctionnalités en utilisant ce jeu d'outils que n'en fournit net-tools, mais il n'est pas très bien documenté et n'est pas vraiment fait pour les êtres pusillanimes. -\layout Code +\end_layout +\begin_layout Code # /sbin/ip 2>&1 | grep -qw 'inet6' && echo "utility 'ip' is IPv6-ready" -\layout Standard +\end_layout +\begin_layout Standard Si le programme /sbin/ip n'est pas trouvé, je vous recommande alors d'installer le paquetage iproute. -\layout Itemize +\end_layout +\begin_layout Itemize Vous pouvez le récupérer à partir de votre distribution Linux (s'il s'y trouve) -\layout Itemize +\end_layout +\begin_layout Itemize Vous pouvez télécharger l'archive tar et recompiler: \begin_inset LatexCommand \url[sources sur le FTP d'origine]{ftp://ftp.inr.ac.ru/ip-routing/} -\end_inset +\end_inset et miroir (manquant) -\layout Itemize +\end_layout +\begin_layout Itemize Vous pouvez rechercher le bon paquetage RPM ici, \begin_inset LatexCommand \url[RPMfind pour iproute]{http://rpmfind.net/linux/rpm2html/search.php?query=iproute} -\end_inset +\end_inset (parfois la reconstruction d'un paquetage SRPM est recommandée) -\layout Section +\end_layout +\begin_layout Section Les programmes de test/déboguage prêts pour IPv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Après avoir préparé votre système pour IPv6, vous voudrez établir des communicat ions en utilisant IPv6. Vous devriez d'abord apprendre comment examiner les paquets IPv6 avec un programme dit \begin_inset Quotes sld -\end_inset +\end_inset renifleur \begin_inset Quotes srd -\end_inset +\end_inset (un -\emph on +\emph on sniffer -\emph default +\emph default ). Cela est fortement conseillé, car cela peut aider à fournir très rapidement un diagnostic en cas de déboguage/dépannage. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-ping6} -\end_inset +\end_inset ping IPv6 -\layout Standard +\end_layout +\begin_layout Standard Ce programme est normalement inclus dans le paquetage -\emph on +\emph on iputils -\emph default +\emph default . Il est conçu pour réaliser de simples tests du transport en émettant des paquets de requête d'écho ( -\emph on +\emph on echo-request -\emph default +\emph default ) ICMPv6 et en attendant les paquets de réponse en écho ( -\emph on +\emph on echo-reply -\emph default +\emph default ) ICMPv6. -\layout Standard +\end_layout +\begin_layout Standard Usage -\layout Code +\end_layout +\begin_layout Code # ping6 -\layout Code +\end_layout +\begin_layout Code # ping6 -\layout Code +\end_layout +\begin_layout Code # ping6 [-I ] -\layout Standard +\end_layout +\begin_layout Standard Exemple -\layout Code +\end_layout +\begin_layout Code # ping6 -c 1 ::1 -\layout Code +\end_layout +\begin_layout Code PING ::1(::1) from ::1 : 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from ::1: icmp_seq=0 hops=64 time=292 usec -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code --- ::1 ping statistics --- -\layout Code +\end_layout +\begin_layout Code 1 packets transmitted, 1 packets received, 0% packet loss -\layout Code +\end_layout +\begin_layout Code round-trip min/avg/max/mdev = 0.292/0.292/0.292/0.000 ms -\layout Standard +\end_layout +\begin_layout Standard Info: ping6 a besoin d'un accès brut à la socket, il faut donc les permissions root. Par conséquent, s'il n'y a pas d'utilisateur root pouvant utiliser ping6, deux problèmes peuvent se poser ici: -\layout Enumerate +\end_layout +\begin_layout Enumerate ping6 n'est pas sur le chemin de l'utilisateur (probablement, car ping6 est généralement stocké dans /usr/sbin -> ajouter au chemin (pas vraiment recommandé) -\layout Enumerate +\end_layout +\begin_layout Enumerate ping6 ne s'exécute pas proprement, généralement, c'est qu'il y a des permissions root manquantes -> chmod u+s /usr/sbin/ping6 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Spécifier une interface à ping IPv6 -\layout Standard +\end_layout +\begin_layout Standard En spécifiant uniquement une adresse lien-local à ping IPv6, le noyau ne sait pas par quel périphérique (physique ou virtuel) il doit émettre le paquet - chaque périphérique a une adresse lien-local. Un essai aura pour résultat un message d'erreur: -\layout Code +\end_layout +\begin_layout Code # ping6 fe80::212:34ff:fe12:3456 -\layout Code +\end_layout +\begin_layout Code connect: Invalid argument -\layout Standard +\end_layout +\begin_layout Standard Dans ce cas vous devez en plus spécifier l'interface comme ci-dessous: -\layout Code +\end_layout +\begin_layout Code # ping6 -I eth0 -c 1 fe80::2e0:18ff:fe90:9205 -\layout Code +\end_layout +\begin_layout Code PING fe80::212:23ff:fe12:3456(fe80::212:23ff:fe12:3456) from -\layout Code +\end_layout +\begin_layout Code ¬ fe80::212:34ff:fe12:3478 eth0: 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from fe80::212:23ff:fe12:3456: icmp_seq=0 hops=64 time=445 usec -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code --- fe80::2e0:18ff:fe90:9205 ping statistics --- -\layout Code +\end_layout +\begin_layout Code 1 packets transmitted, 1 packets received, 0% packet loss round-trip -\layout Code +\end_layout +\begin_layout Code ¬ min/avg/max/mdev = 0.445/0.445/0.445/0.000 ms -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ping6 et les adresses multicast -\layout Standard +\end_layout +\begin_layout Standard Un mécanisme intéressant pour détecter les hôtes IPv6 actifs sur un lien est de lancer ping6 sur l'adresse multicast lien-local tous-noeuds ( -\emph on +\emph on all-node -\emph default +\emph default ): -\layout Code +\end_layout +\begin_layout Code # ping6 -I eth0 ff02::1 -\layout Code +\end_layout +\begin_layout Code PING ff02::1(ff02::1) from fe80:::2ab:cdff:feef:012356 eth0: 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.104 ms -\layout Code +\end_layout +\begin_layout Code 64 bytes from fe80::212:34ff:fe12:3450: icmp_seq=1 ttl=64 time=0.549 ms (DUP!) -\layout Standard +\end_layout +\begin_layout Standard A la différence d'IPv4, où les réponses à un ping sur l'adresse de diffusion ( -\emph on +\emph on broadcast -\emph default +\emph default ) peuvent être rendues indisponibles, en IPv6, ce comportement ne peut pas être actuellement rendu indisponible, sauf par un pare-feu IPv6 local. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-traceroute6} -\end_inset +\end_inset traceroute6 IPv6 -\layout Standard +\end_layout +\begin_layout Standard Ce programme est normalement inclus dans le paquetage -\emph on +\emph on iputils -\emph default +\emph default . C'est un programme similaire au traceroute d'IPv4. En voici un exemple: -\layout Code +\end_layout +\begin_layout Code # traceroute6 www.6bone.net -\layout Code +\end_layout +\begin_layout Code traceroute to 6bone.net (3ffe:b00:c18:1::10) from 3ffe:ffff:0000:f101::2, 30 -\layout Code +\end_layout +\begin_layout Code ¬ hops max, 16 byte packets -\layout Code +\end_layout +\begin_layout Code 1 localipv6gateway (3ffe:ffff:0000:f101::1) 1.354 ms 1.566 ms 0.407 ms -\layout Code +\end_layout +\begin_layout Code 2 swi6T1-T0.ipv6.switch.ch (3ffe:2000:0:400::1) 90.431 ms 91.956 ms 92.377 ms -\layout Code +\end_layout +\begin_layout Code 3 3ffe:2000:0:1::132 (3ffe:2000:0:1::132) 118.945 ms 107.982 ms 114.557 ms -\layout Code +\end_layout +\begin_layout Code 4 3ffe:c00:8023:2b::2 (3ffe:c00:8023:2b::2) 968.468 ms 993.392 ms 973.441 ms -\layout Code +\end_layout +\begin_layout Code 5 3ffe:2e00:e:c::3 (3ffe:2e00:e:c::3) 507.784 ms 505.549 ms 508.928 ms -\layout Code +\end_layout +\begin_layout Code 6 www.6bone.net (3ffe:b00:c18:1::10) 1265.85 ms * 1304.74 ms -\layout Standard +\end_layout +\begin_layout Standard Note: à la différence de certaines versions contemporaines du traceroute d'IPv4, qui peuvent utiliser les paquets de requête d'écho ICMPv4 aussi bien que les paquets UDP (défaut), l'actuel traceroute IPv6 ne peut qu'émettre @@ -2960,207 +3626,246 @@ Note: Comme vous le savez peut-être, les paquets de requête d'écho ICMP sont mieux acceptés par les pare-feu ou les ACL sur les routeurs intermédiaires que les paquets UDP. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-tracepath6} -\end_inset +\end_inset tracepath6 IPv6 -\layout Standard +\end_layout +\begin_layout Standard Ce programme est normalement inclus dans le paquetage -\emph on +\emph on iputils -\emph default +\emph default . C'est un programme comme traceroute6, il trace le chemin vers une destination donnée, découvrant la MTU le long de ce chemin. En voici un exemple: -\layout Code +\end_layout +\begin_layout Code # tracepath6 www.6bone.net -\layout Code +\end_layout +\begin_layout Code 1?: [LOCALHOST] pmtu 1480 -\layout Code +\end_layout +\begin_layout Code 1: 3ffe:401::2c0:33ff:fe02:14 150.705ms -\layout Code +\end_layout +\begin_layout Code 2: 3ffe:b00:c18::5 267.864ms -\layout Code +\end_layout +\begin_layout Code 3: 3ffe:b00:c18::5 asymm 2 266.145ms pmtu 1280 -\layout Code +\end_layout +\begin_layout Code 3: 3ffe:3900:5::2 asymm 4 346.632ms -\layout Code +\end_layout +\begin_layout Code 4: 3ffe:28ff:ffff:4::3 asymm 5 365.965ms -\layout Code +\end_layout +\begin_layout Code 5: 3ffe:1cff:0:ee::2 asymm 4 534.704ms -\layout Code +\end_layout +\begin_layout Code 6: 3ffe:3800::1:1 asymm 4 578.126ms !N -\layout Code +\end_layout +\begin_layout Code Resume: pmtu 1280 -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-tcpdump} -\end_inset +\end_inset tcpdump IPv6 -\layout Standard +\end_layout +\begin_layout Standard Sur Linux, tcpdump est l'outil majeur pour la capture de paquets. Vous allez trouver ci-dessous quelques exemples. Le support IPv6 est normalement intégré aux éditions actuelles de la version 3.6. -\layout Standard +\end_layout +\begin_layout Standard tcpdump utilise des expressions pour filtrer les paquets, minimisant le bruit: -\layout Itemize +\end_layout +\begin_layout Itemize icmp6: filtre le trafic ICMPv6 natif -\layout Itemize +\end_layout +\begin_layout Itemize ip6: filtre le trafic IPv6 natif (incluant ICMPv6) -\layout Itemize +\end_layout +\begin_layout Itemize proto ipv6: filtre le trafic IPv6-in-IPv4 tunnelé -\layout Itemize +\end_layout +\begin_layout Itemize not port ssh: supprime l'affichage des paquets SSH, pour lancer tcpdump à partir d'une session distante SSH -\layout Standard +\end_layout +\begin_layout Standard Certaines options en ligne de commande sont très utiles pour capter et afficher plus d'information concernant les paquets, essentiellement intéressant pour approfondir l'information des paquets ICMPv6: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -s 512 \begin_inset Quotes erd -\end_inset +\end_inset : augmente la quantité d'information capturée pour un paquet à 512 octets -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -vv \begin_inset Quotes erd -\end_inset +\end_inset : sortie vraiment verbeuse -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -n \begin_inset Quotes erd -\end_inset +\end_inset : ne pas résoudre les adresses en noms, utile si la résolution inversée ne fonctionne pas proprement -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ping IPv6 vers -\size footnotesize +\size footnotesize l'adresse native 3ffe:ffff:100:f101::1 -\size default +\size default sur un lien-local -\layout Code +\end_layout +\begin_layout Code # tcpdump -t -n -i eth0 -s 512 -vv ip6 or proto ipv6 -\layout Code +\end_layout +\begin_layout Code tcpdump: listening on eth0 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:2e0:18ff:fe90:9205 > 3ffe:ffff:100:f101::1: icmp6: echo -\layout Code +\end_layout +\begin_layout Code ¬ request (len 64, hlim 64) -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::1 > 3ffe:ffff:100:f101:2e0:18ff:fe90:9205: icmp6: echo -\layout Code +\end_layout +\begin_layout Code ¬ reply (len 64, hlim 64) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ping IPv6 vers -\size footnotesize +\size footnotesize 3ffe:ffff:100::1 -\size default +\size default routée au travers d'un tunnel IPv6-in-IPv4 -\layout Standard +\end_layout +\begin_layout Standard 1.2.3.4 et 5.6.7.8 sont les extrémités du tunnel (toutes les adresses sont des exemples) -\layout Code +\end_layout +\begin_layout Code # tcpdump -t -n -i ppp0 -s 512 -vv ip6 or proto ipv6 -\layout Code +\end_layout +\begin_layout Code tcpdump: listening on ppp0 -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 > 5.6.7.8: 2002:ffff:f5f8::1 > 3ffe:ffff:100::1: icmp6: echo request -\layout Code +\end_layout +\begin_layout Code ¬ (len 64, hlim 64) (DF) (ttl 64, id 0, len 124) -\layout Code +\end_layout +\begin_layout Code 5.6.7.8 > 1.2.3.4: 3ffe:ffff:100::1 > 2002:ffff:f5f8::1: icmp6: echo reply (len -\layout Code +\end_layout +\begin_layout Code ¬ 64, hlim 61) (ttl 23, id 29887, len 124) -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 > 5.6.7.8: 2002:ffff:f5f8::1 > 3ffe:ffff:100::1: icmp6: echo request -\layout Code +\end_layout +\begin_layout Code ¬ (len 64, hlim 64) (DF) (ttl 64, id 0, len 124) -\layout Code +\end_layout +\begin_layout Code 5.6.7.8 > 1.2.3.4: 3ffe:ffff:100::1 > 2002:ffff:f5f8::1: icmp6: echo reply (len -\layout Code +\end_layout +\begin_layout Code ¬ 64, hlim 61) (ttl 23, id 29919, len 124) -\layout Section +\end_layout +\begin_layout Section Les programmes prêts pour IPv6 -\layout Standard +\end_layout +\begin_layout Standard Les distributions actuelles comportent déjà les clients et les serveurs IPv6 les plus couramment utilisés. Allez d'abord voir sur \begin_inset LatexCommand \url[IPv6 & Linux / l'état actuel des distributions]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset . Si ce que vous cherchez n'y est pas encore, vous pouvez vérifier sur \begin_inset LatexCommand \url[IPv6 & Linux / l'état actuel des applications disponibles]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html} -\end_inset +\end_inset , où sont répertoriés les programmes déjà portés sur IPv6 et utilisables sous Linux. @@ -3168,27 +3873,31 @@ Les distributions actuelles comportent d disponibles dans \begin_inset LatexCommand \url[la troisième partie]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-3.html} -\end_inset +\end_inset et \begin_inset LatexCommand \url[la quatrième partie]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-4.html} -\end_inset +\end_inset de l'HowTo - IPv6 & Linux. -\layout Section +\end_layout +\begin_layout Section Les programmes client prêts pour IPv6 (une sélection) -\layout Standard +\end_layout +\begin_layout Standard Pour lancer les tests qui vont suivre, il est nécessaire que votre système dispose d'IPv6, et certains exemples montrent des adresses ne pouvant être atteintes que si une connexion au 6bone est disponible. -\layout Subsection +\end_layout +\begin_layout Subsection Vérifier la résolution DNS des adresses IPv6 -\layout Standard +\end_layout +\begin_layout Standard A cause des mises à jour de sécurité ces dernières années, tout serveur du Système des Noms de Domaine (DNS) devrait fonctionner avec un logiciel récent comprenant déjà le type (intermédiaire) d'adresse IPv6 AAAA (le @@ -3197,1410 +3906,1735 @@ A cause des mises de support du domaine racine IP6.ARPA). Un simple test pour savoir si le système utilisé peut résoudre les adresses IPv6 est -\layout Code +\end_layout +\begin_layout Code # host -t AAAA www.join.uni-muenster.de -\layout Standard +\end_layout +\begin_layout Standard et cela devrait affiché quelque chose comme ce qui suit: -\layout Code +\end_layout +\begin_layout Code www.join.uni-muenster.de. is an alias for tolot.join.uni-muenster.de. -\layout Code +\end_layout +\begin_layout Code tolot.join.uni-muenster.de. has AAAA address 2001:638:500:101:2e0:81ff:fe24:37c6 -\layout Subsection +\end_layout +\begin_layout Subsection Le client telnet prêt pour IPv6 -\layout Standard +\end_layout +\begin_layout Standard Des clients telnet prêts pour IPv6 sont disponibles. Un simple test peut être effectué par -\layout Code +\end_layout +\begin_layout Code $ telnet 3ffe:400:100::1 80 -\layout Code +\end_layout +\begin_layout Code Trying 3ffe:400:100::1... -\layout Code +\end_layout +\begin_layout Code Connected to 3ffe:400:100::1. -\layout Code +\end_layout +\begin_layout Code Escape character is '^]'. -\layout Code +\end_layout +\begin_layout Code HEAD / HTTP/1.0 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code HTTP/1.1 200 OK -\layout Code +\end_layout +\begin_layout Code Date: Sun, 16 Dec 2001 16:07:21 -\layout Code +\end_layout +\begin_layout Code GMT Server: Apache/2.0.28 (Unix) -\layout Code +\end_layout +\begin_layout Code Last-Modified: Wed, 01 Aug 2001 21:34:42 GMT -\layout Code +\end_layout +\begin_layout Code ETag: "3f02-a4d-b1b3e080" -\layout Code +\end_layout +\begin_layout Code Accept-Ranges: bytes -\layout Code +\end_layout +\begin_layout Code Content-Length: 2637 -\layout Code +\end_layout +\begin_layout Code Connection: close -\layout Code +\end_layout +\begin_layout Code Content-Type: text/html; charset=ISO-8859-1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code Connection closed by foreign host. -\layout Standard +\end_layout +\begin_layout Standard Si le client telnet ne comprend pas l'adresse IPv6 et dit quelque chose comme \begin_inset Quotes sld -\end_inset +\end_inset ne peut résoudre le nom d'hôte \begin_inset Quotes srd -\end_inset +\end_inset ( \begin_inset Quotes sld -\end_inset +\end_inset -\emph on +\emph on cannot resolve hostname -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset ), IPv6 n'est alors pas disponible. -\layout Subsection +\end_layout +\begin_layout Subsection Les clients ssh prêts pour IPv6 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection openssh -\layout Standard +\end_layout +\begin_layout Standard Les versions actuelles d'openssh sont prêtes pour IPv6. Selon la configuration précédant la compilation, il y a deux comportements possibles. -\layout Itemize +\end_layout +\begin_layout Itemize --without-ipv4-default: le client essaie automatiquement une connexion IPv6 en premier et revient à IPv4 en cas d'échec. -\layout Itemize +\end_layout +\begin_layout Itemize --with-ipv4-default: la connexion par défaut est IPv4, la connexion IPv6 doit être forcée comme dans l'exemple qui suit: -\layout Code +\end_layout +\begin_layout Code $ ssh -\series bold +\series bold -6 -\series default +\series default ::1 -\layout Code +\end_layout +\begin_layout Code user@::1's password: ****** -\layout Code +\end_layout +\begin_layout Code [user@ipv6host user]$ -\layout Standard +\end_layout +\begin_layout Standard Si votre client ssh ne comprend pas l'option \begin_inset Quotes sld -\end_inset +\end_inset -6 \begin_inset Quotes srd -\end_inset +\end_inset , c'est qu'il n'a pas IPv6 de disponible, comme la plupart des paquetages de ssh version 1. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ssh.com -\layout Standard +\end_layout +\begin_layout Standard Le client et le serveur SSH de chez SSH.com sont aussi prêts pour IPv6, et - gratuits pour les machines Linux et FreeBSD selon l'usage -\SpecialChar ~ + gratuits pour les machines Linux et FreeBSD selon l'usage -\InsetSpace ~ commercial ou - personnel\SpecialChar ~ + personnel\InsetSpace ~ - qui en est fait. -\layout Subsection +\end_layout +\begin_layout Subsection Les navigateurs web prêts pour IPv6 -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[L'état actuel de la liste des navigateurs web IPv6]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#HTTP} -\end_inset +\end_inset est disponible. -\layout Standard +\end_layout +\begin_layout Standard La plupart ont des problèmes irrésolues pour le moment -\layout Enumerate +\end_layout +\begin_layout Enumerate Si un seul proxy IPv4 est utilisé dans les réglages, les requêtes IPv6 seront bien envoyées vers le proxy, mais celui-ci échouera à comprendre la requête, laquelle échouera. Solution: mettre à jour le logiciel proxy (à voir plus tard). -\layout Enumerate +\end_layout +\begin_layout Enumerate Les réglages de configuration automatique de proxy (*.pac) ne peuvent être étendus afin de prendre en charge différemment les requêtes IPv6 (par exemple ne pas utiliser le proxy) à cause de leur nature (écrits en Java-script et bien encodés en dur dans les sources, comme cela peut être observé pour le code source de Maxilla). -\layout Standard +\end_layout +\begin_layout Standard C'est ainsi que les anciennes versions ne comprennent pas un URL avec une adresse encodée en IPv6 comme \begin_inset LatexCommand \url[http://[3ffe:400:100::1]/]{http://[3ffe:400:100::1]/} -\end_inset +\end_inset (cet URL ne fonctionne qu'avec un navigateur disposant d'IPv6!). -\layout Standard +\end_layout +\begin_layout Standard Un bref test est d'essayer l'URL fourni avec un navigateur donné, sans utiliser de proxy. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Un URL de test -\layout Standard +\end_layout +\begin_layout Standard Un bon point de départ pour tester la navigation IPv6 est \begin_inset LatexCommand \url[http://www.kame.net/]{http://www.kame.net/} -\end_inset +\end_inset . Si la tortue sur la page est animée, la connexion se fait -\emph on +\emph on via -\emph default +\emph default IPv6, sinon la tortue est statique. -\layout Section +\end_layout +\begin_layout Section Les programmes serveur prêts pour IPv6 -\layout Standard +\end_layout +\begin_layout Standard Dans cette partie, de nombreuses questions concernant des clients spécifiques ont été mentionnées. En conséquence, les éléments pour les serveurs prêts pour IPv6 sont fournis plus bas dans la section \begin_inset LatexCommand \ref[Eléments d'installation des démons prêts pour IPv6]{chapter-hints-daemons} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{faq-ipv6-ready-system-check} -\end_inset +\end_inset FAQ (vérification d'un système prêt pour IPv6) -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser les outils -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Q: impossible d'utiliser ping6 avec des adresses lien-local -\layout Standard +\end_layout +\begin_layout Standard Message d'erreur: " -\emph on +\emph on connect: Invalid argument -\emph default +\emph default " -\layout Standard +\end_layout +\begin_layout Standard Le noyau ne sait pas sur quel lien (physique ou virtuel) vous voulez l'utiliser et envoyer des paquets ICMPv6. C'est pourquoi est affiché un message d'erreur. -\layout Standard +\end_layout +\begin_layout Standard Solution: spécifier l'interface de cette façon: \begin_inset Quotes sld -\end_inset +\end_inset ping6 -\series bold +\series bold -I eth0 -\series default +\series default fe80::2e0:18ff:fe90:9205 \begin_inset Quotes srd -\end_inset +\end_inset , voir aussi \begin_inset LatexCommand \ref[l'usage du programme ping6]{program-ping6} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Q: impossible d'utiliser ping6 ou traceroute en tant qu'utilisateur courant -\layout Standard +\end_layout +\begin_layout Standard Message d'erreur: \begin_inset Quotes sld -\end_inset +\end_inset -\emph on +\emph on icmp socket: Operation not permitted -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Ces utilitaires créent des paquets spéciaux ICMPv6 et les émettent en dehors. Ceci est réalisé par l'emploi des sockets brutes du noyau. Ces dernières ne peuvent être utilisées que par l'utilisateur \begin_inset Quotes sld -\end_inset +\end_inset root \begin_inset Quotes srd -\end_inset +\end_inset . C'est pourquoi les utilisateurs courants obtiennent un tel message d'erreur. -\layout Standard +\end_layout +\begin_layout Standard Solution: s'il est vraiment nécessaire que tous les utilisateurs puissent utiliser ces utilitaires, vous pouvez ajouter le bit \begin_inset Quotes sld -\end_inset +\end_inset suid \begin_inset Quotes srd -\end_inset +\end_inset en faisant \begin_inset Quotes srd -\end_inset +\end_inset chmod u+s /chemin/vers/le/programme \begin_inset Quotes srd -\end_inset +\end_inset , voir aussi \begin_inset LatexCommand \ref[l'usage du programme]{program-ping6} -\end_inset +\end_inset . Si tous les utilisateurs ne doivent pas en être capables, vous pouvez changer ce programme de groupe, par exemple au profit du groupe \begin_inset Quotes sld -\end_inset +\end_inset wheel \begin_inset Quotes srd -\end_inset +\end_inset , ajouter les utilisateurs nécessaires à ce groupe et ôter le bit d'exécution aux autres utilisateurs par \begin_inset Quotes sld -\end_inset +\end_inset chmod o-rwx /chemin/vers/le/programme \begin_inset Quotes srd -\end_inset +\end_inset , ou bien configurer \begin_inset Quotes sld -\end_inset +\end_inset sudo \begin_inset Quotes srd -\end_inset +\end_inset pour mettre en place votre politique de sécurité. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-interface} -\end_inset +\end_inset Configurer les interfaces -\layout Section +\end_layout +\begin_layout Section Les différents périphériques réseau -\layout Standard +\end_layout +\begin_layout Standard Sur un noeud, il existe différents périphériques réseau. Ils peuvent être -\layout Itemize +\end_layout +\begin_layout Itemize Physiquement rattachés, comme eth0, tr0 -\layout Itemize +\end_layout +\begin_layout Itemize Virtuellement existants, comme ppp0, tun0, tap0, sit0, isdn0, ippp0 -\layout Subsection +\end_layout +\begin_layout Subsection Physiquement rattachés -\layout Standard +\end_layout +\begin_layout Standard Les interfaces physiquement rattachées, comme Ethernet ou Token-Ring, sont la norme et n'ont pas besoin d'un traitement particulier. -\layout Subsection +\end_layout +\begin_layout Subsection Virtuellement existants -\layout Standard +\end_layout +\begin_layout Standard Les interfaces virtuellement rattachées ont toujours besoin d'un traitement particulier. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les interfaces de tunnelage IPv6-in-IPv4 -\layout Standard +\end_layout +\begin_layout Standard Ces interfaces sont normalement dénommées -\series bold +\series bold sit -\emph on +\emph on x -\series default -\emph default +\series default +\emph default . -\emph on +\emph on sit -\emph default +\emph default est l'abréviation mise pour -\series bold +\series bold S -\series default +\series default imple -\series bold +\series bold T -\series default +\series default ransition -\series bold +\series bold I -\series default +\series default nternet -\series bold +\series bold ( -\emph on +\emph on S -\series default +\series default imple -\series bold +\series bold I -\series default +\series default nternet -\series bold +\series bold T -\series default +\series default ransition -\emph default +\emph default ). Ce périphérique a la capacité d'encapsuler les paquets IPv6 à l'intérieur de paquets IPv4 et de les tunneler vers une extrémité étrangère. -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold sit0 -\series default +\series default a une signification particulière et ne peut être utilisée pour des tunnels dédiés. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les interfaces PPP -\layout Standard +\end_layout +\begin_layout Standard Les interfaces PPP acquièrent leur capacité IPv6 grâce à un démon PPP disposant d'IPv6. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les interfaces RNIS HDLC -\layout Standard +\end_layout +\begin_layout Standard La capacité IPv6 pour HDLC avec encapsulation -\series bold +\series bold ip -\series default +\series default est déjà intégrée au noyau. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les interfaces PPP RNIS -\layout Standard +\end_layout +\begin_layout Standard Les interfaces PPP RNIS (ippp) ne sont pas disponibles pour IPv6 dans le noyau. Il n'est pas prévu que cela se fasse, puisqu'elles seront remplacées par une couche d'interface ppp plus générique. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection SLIP + PLIP -\layout Standard +\end_layout +\begin_layout Standard Comme il a déjà été dit, ces interfaces ne supportent pas le transport IPv6 (l'émission est OK, mais la distribution à la réception ne fonctionne pas). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Le périphérique Ether-tap -\layout Standard +\end_layout +\begin_layout Standard Les périphériques Ether-tap sont prêts pour IPv6, et sont de plus configurables sans état. Pour être utilisés, le module \begin_inset Quotes sld -\end_inset +\end_inset ethertap \begin_inset Quotes srd -\end_inset +\end_inset doit être chargé au préalable. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les périphériques tun -\layout Standard +\end_layout +\begin_layout Standard Actuellement, je ne les ai pas encore testés par moi-même. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ATM -\layout Standard +\end_layout +\begin_layout Standard 01/2002: non supporté par l'actuel noyau vanille, supporté par l'extension USAGI. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Autres -\layout Standard +\end_layout +\begin_layout Standard Ai-je oublié une interface?... -\layout Section +\end_layout +\begin_layout Section (dé)Montage des interfaces -\layout Standard +\end_layout +\begin_layout Standard Deux méthodes peuvent être utilisées pour (dé)monter les interfaces. -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # ip link set dev up -\layout Code +\end_layout +\begin_layout Code # ip link set dev down -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # ip link set dev eth0 up -\layout Code +\end_layout +\begin_layout Code # ip link set dev eth0 down -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig up -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig down -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 down -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-address} -\end_inset +\end_inset Configurer les adresses IPv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Il y a différentes façons de configurer une adresse IPv6 sur une interface. Vous pouvez utiliser "ifconfig" ou "ip". -\layout Section +\end_layout +\begin_layout Section Affichage des adresses IPv6 existantes -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Vous devriez d'abord vérifier s'il existe des adresses IPv6 configurées, et combien (peut-être y en a-t-il qui l'ont été, comme par magie, pendant l'auto-configuration sans état). -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show dev -\layout Standard +\end_layout +\begin_layout Standard Exemple pour un hôte configuré statiquement: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show dev eth0 -\layout Code +\end_layout +\begin_layout Code 2: eth0: -\layout Standard +\end_layout +\begin_layout Standard Exemple (la sortie est filtrée avec grep pour n'afficher que les adresses IPv6). vous pouvez voir ici des adresses IPv6 ayant des portées différentes. -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 |grep "inet6 addr:" -\layout Code +\end_layout +\begin_layout Code inet6 addr: fe80::210:a4ff:fee3:9566/10 Scope:Link -\layout Code +\end_layout +\begin_layout Code inet6 addr: 3ffe:ffff:0:f101::1/64 Scope:Global -\layout Code +\end_layout +\begin_layout Code inet6 addr: fec0:0:0:f101::1/64 Scope:Site -\layout Section +\end_layout +\begin_layout Section Ajouter une adresse IPv6 -\layout Standard +\end_layout +\begin_layout Standard Ajouter une adresse IPv6 est similaire au mécanisme des adresses \begin_inset Quotes sld -\end_inset +\end_inset ALIAS IP \begin_inset Quotes srd -\end_inset +\end_inset sur les interfaces configurées par IPv4 Linux. -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add / dev -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add 3ffe:ffff:0:f101::1/64 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig inet6 add / -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 inet6 add 3ffe:ffff:0:f101::1/64 -\layout Section +\end_layout +\begin_layout Section Ôter une adresse IPv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Rarement nécessaire, prenez garde de ne pas ôter une adresse IPv6 n'existant pas, il en résulte parfois un -\emph on +\emph on crash -\emph default +\emph default sur les anciens noyaux. -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr del / dev -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr del 3ffe:ffff:0:f101::1/64 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig inet6 del / -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 inet6 del 3ffe:ffff:0:f101::1/64 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-route} -\end_inset +\end_inset Configurer les routes IPv6 courantes -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Si vous voulez quitter votre lien et voulez émettre des paquets vers l'Internet mondial IPv6, vous avez besoin de routage. S'il existe déjà un routeur disposant d'IPv6 sur votre lien, il est possible que cela soit suffisant pour ajouter des routes IPv6. -\layout Section +\end_layout +\begin_layout Section Afficher les routes IPv6 existantes -\layout Standard +\end_layout +\begin_layout Standard Vous devriez d'abord vérifier s'il existe des routes IPv6 configurées, et combien (peut-être y en a-t-il qui l'ont été, comme par magie, pendant l'auto-configuration sans état). -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route show [dev ] -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route show dev eth0 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0:f101::/64 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code fe80::/10 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code ff00::/8 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code default proto kernel metric 256 mtu 1500 advmss 1440 -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "route" -\layout Standard -\align left -Usage: -\layout Code +\end_layout +\begin_layout Standard +\align left +Usage: +\end_layout + +\begin_layout Code # /sbin/route -A inet6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Exemple (la sortie est filtrée sur l'interface eth0). Ici vous pouvez voir différentes routes IPv6 pour différentes adresses sur une même interface. -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 |grep -w "eth0" -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0:f101 ::/64 :: UA 256 0 0 eth0 <- Route de l'interface de portée globale -\layout Code +\end_layout +\begin_layout Code ¬ address -\layout Code +\end_layout +\begin_layout Code fe80::/10 :: UA 256 0 0 eth0 <- Route de l'interface de portée lien-local -\layout Code +\end_layout +\begin_layout Code ¬ address -\layout Code +\end_layout +\begin_layout Code ff00::/8 :: UA 256 0 0 eth0 <- Route de l'interface destiné à tout le trafic multicast -\layout Code +\end_layout +\begin_layout Code ¬ addresses -\layout Code +\end_layout +\begin_layout Code ::/0 :: UDA 256 0 0 eth0 <- Route automatique par défaut -\layout Section +\end_layout +\begin_layout Section Ajouter une route IPv6 traversant une passerelle -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Nécessaire la plupart du temps pour atteindre l'extérieur grâce à IPv6 en utilisant un routeur IPv6 sur votre lien. -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add / via -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Code +\end_layout -\layout Standard +\begin_layout Code +\end_layout + +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 via 3ffe:ffff:0:f101::1 -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add / gw -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Un périphérique peut être nécessaire également, si l'adresse IPv6 de la passerelle est un lien-local. -\layout Standard +\end_layout +\begin_layout Standard Suivre l'exemple montré ajoute une route à toutes les adresses globales actuelles (2000::/3) à travers la passerelle -\family typewriter +\family typewriter \lang afrikaans 3ffe:ffff:0:f101::1 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 gw 3ffe:ffff:0:f101::1 -\layout Section +\end_layout +\begin_layout Section Ôter une route IPv6 traversant une passerelle -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Rarement nécessaire manuellement, la plupart du temps effectué par les scripts configurant le réseau à l'extinction (totale ou par interface) -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard -\align left -Usage: -\layout Code +\end_layout +\begin_layout Standard +\align left +Usage: +\end_layout + +\begin_layout Code # /sbin/ip -6 route del / via -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del 2000::/3 via 3ffe:ffff:0:f101::1 -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del / [dev ] -\layout Standard +\end_layout +\begin_layout Standard Exemple pour de nouveau ôter la route précédemment ajoutée: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 gw 3ffe:ffff:0:f101::1 -\layout Section +\end_layout +\begin_layout Section Ajouter une route IPv6 traversant une interface -\layout Standard +\end_layout +\begin_layout Standard Pas si fréquent, parfois en cas de création de lien point-à-point. -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add / dev -\layout Code +\end_layout +\begin_layout Code ¬ metric 1 -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 dev eth0 metric 1 -\layout Standard +\end_layout +\begin_layout Standard La distance ( -\emph on +\emph on metric -\emph default +\emph default ) \begin_inset Quotes sld -\end_inset +\end_inset 1 \begin_inset Quotes srd -\end_inset +\end_inset est utilisée ici par soucis de compatibilité avec la distance utilisée par route, car la distance par défaut fixée par \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset est \begin_inset Quotes sld -\end_inset +\end_inset 1024 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add / dev -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 dev eth0 -\layout Section +\end_layout +\begin_layout Section Ôter une route IPv6 traversant une interface -\layout Standard +\end_layout +\begin_layout Standard Rarement utiliser manuellement, les scripts de configuration font cela à l'extinction. -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del / dev -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del 2000::/3 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del / dev -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 dev eth0 -\layout Section +\end_layout +\begin_layout Section FAQ concernant les routes IPv6 -\layout Subsection +\end_layout +\begin_layout Subsection Support d'une route par défaut IPv6 -\layout Standard +\end_layout +\begin_layout Standard Une idée d'IPv6 était le routage hiérarchique, avec pour conséquence une quantité moindre d'entrées dans les tables de routage nécessaires aux routeurs. -\layout Standard +\end_layout +\begin_layout Standard Il y a certains problèmes dans les noyaux Linux actuels: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les clients (ne routent aucun paquet!) -\layout Standard +\end_layout +\begin_layout Standard Les clients peuvent installer une route par défaut avec pour préfixe \begin_inset Quotes sld -\end_inset +\end_inset ::/0 \begin_inset Quotes srd -\end_inset +\end_inset , ils peuvent aussi apprendre une telle route par auto-configuration, en utilisant par exemple radvd s'il est présent sur le lien, comme le montre ce qui suit: -\layout Code +\end_layout +\begin_layout Code # ip -6 route show | grep ^default -\layout Code +\end_layout +\begin_layout Code default via fe80::212:34ff:fe12:3450 dev eth0 proto kernel metric 1024 expires -\layout Code +\end_layout +\begin_layout Code ¬ 29sec mtu 1500 advmss 1440 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les routeurs en cas de renvoi de paquets -\layout Standard +\end_layout +\begin_layout Standard Dans ses grandes lignes, l'actuel noyau Linux (au moins <= 2.4.17) ne supporte pas les routes par défaut. Vous pouvez les installées, mais la recherche échouera quand un paquet devra être renvoyé (une intention normale pour un routeur). -\layout Standard +\end_layout +\begin_layout Standard Pour l'heure, le \begin_inset Quotes sld -\end_inset +\end_inset routage par défaut \begin_inset Quotes srd -\end_inset +\end_inset peut être installé en utilisant l'actuel et unique préfixe d'adresse globale \begin_inset Quotes sld -\end_inset +\end_inset 2000::/3 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Le projet USAGI supporte déjà cela dans leurs extensions grâce à une astuce de programmation ( -\emph on +\emph on NdT -\emph default +\emph default : -\emph on +\emph on a hack -\emph default +\emph default , -\emph on +\emph on i.e. -\emph default +\emph default littéralement, une \begin_inset Quotes srd -\end_inset +\end_inset bidouille \begin_inset Quotes srd -\end_inset +\end_inset ). -\layout Standard +\end_layout +\begin_layout Standard Note: prenez garde au routage par défaut sans filtrage d'adresse sur les routeurs de bordure, sinon du trafic multicast ou site-local quittera l'environ nement. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-Neighbor-Discovery} -\end_inset +\end_inset La découverte de voisinage -\layout Standard +\end_layout +\begin_layout Standard La découverte de voisinage est le successeur IPv6 de ARP ( -\emph on +\emph on Address Resolution Protocol -\emph default +\emph default , protocole de résolution d'adresse) pour IPv4. Vous pouvez récupérer l'information concernant le voisinage actuel, de plus, vous pouvez fixer ou détruire des entrées. Le noyau garde la trace de la détection d'un voisin (comme ARP pour IPv4). Vous pouvez faire des recherches dans la table apprise, en utilisant \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Section +\end_layout +\begin_layout Section Afficher le voisinage en utilisant "ip" -\layout Standard +\end_layout +\begin_layout Standard Avec la commande qui suit vous pouvez afficher les voisins IPv6 appris ou configurés -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh show [dev ] -\layout Standard +\end_layout +\begin_layout Standard L'exemple suivant montre un voisin, qui est un routeur pouvant être atteint -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh show -\layout Code +\end_layout +\begin_layout Code fe80::201:23ff:fe45:6789 dev eth0 lladdr 00:01:23:45:67:89 router nud reachable -\layout Section +\end_layout +\begin_layout Section Manipuler la table de voisinage en utilisant "ip" -\layout Subsection +\end_layout +\begin_layout Subsection Ajouter manuellement une entrée -\layout Standard +\end_layout +\begin_layout Standard La commande suivante vous permet d'ajouter manuellement une entrée -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh add lladdr dev -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh add fec0::1 lladdr 02:01:02:03:04:05 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Détruire manuellement une entrée -\layout Standard +\end_layout +\begin_layout Standard De même qu'une entrée peut être ajoutée, une entrée peut être détruite: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh del lladdr dev -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh del fec0::1 lladdr 02:01:02:03:04:05 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Pour plus de réglages avancés -\layout Standard +\end_layout +\begin_layout Standard L'outil \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset est sous-documenté, mais il est très puissant. Voir l'aide en ligne pour en savoir plus -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh help -\layout Code +\end_layout +\begin_layout Code Usage: ip neigh { add | del | change | replace } { ADDR [ lladdr LLADDR ] -\layout Code +\end_layout +\begin_layout Code [ nud { permanent | noarp | stale | reachable } ] -\layout Code +\end_layout +\begin_layout Code | proxy ADDR } [ dev DEV ] -\layout Code +\end_layout +\begin_layout Code ip neigh {show|flush} [ to PREFIX ] [ dev DEV ] [ nud STATE ] -\layout Standard +\end_layout +\begin_layout Standard Il semble que certaines options soient uniquement pour IPv4... si vous pouvez contribuer à en dire plus sur les drapeaux et l'emploi avancé, merci d'envoyer vos informations. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuring-ipv6-in-ipv4-tunnels} -\end_inset +\end_inset Configurer les tunnels IPv6-in-IPv4 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Si vous souhaitez quitter votre lien incapable d'accéder à IPv6 à partir de votre réseau local, vous avez besoin d'un tunnelage IPv6-in-IPv4 afin de rejoindre l'Internet mondial IPv6. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Il y a différents mécanismes de tunnelage, et conséquemment, différentes façons d'installer des tunnels. -\layout Section +\end_layout +\begin_layout Section Les types de tunnel -\layout Standard +\end_layout +\begin_layout Standard Il y a plus d'une façon de tunneler des paquets IPv6 sur des liens uniquement IPv4. -\layout Subsection +\end_layout +\begin_layout Subsection Tunnelage statique point-à-point: 6bone -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Un tunnel point-à-point est un tunnel dédié à un point de connexion terminal, qui connaît votre réseau IPv6 (pour le routage en retour) et l'adresse IPv4 de votre point de connexion (terminale), comme défini dans la \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset . Pré-requis: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left L'adresse IPv4 de votre point de connexion terminal doit être globalement unique, statique, et accessible à partir de l'autre point de connexion terminal distant -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Un préfixe IPv6 vous est assigné (voir le bureau d'enregistrement 6bone) -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Une extrémité distante du tunnel capable de router votre préfixe IPv6 jusqu'à votre extrémité locale du tunnel (la plupart du temps, une configuration manuelle distante est requise) -\layout Subsection +\end_layout +\begin_layout Subsection Le tunnelage automatique -\layout Standard +\end_layout +\begin_layout Standard Le cas du tunnelage automatique se présente quand un noeud se connecte directeme nt à un autre noeud en ayant obtenu au préalable l'adresse IPv4 de l'autre noeud. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{tunneling-6to4} -\end_inset +\end_inset Le tunnelage 6to4 -\layout Standard +\end_layout +\begin_layout Standard Le tunnelage 6to4 ( \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset ) utilise un mécanisme simple pour créer des tunnels automatiques. Tout noeud ayant une adresse unique globale IPv4 est capable d'être le point de connexion terminal d'un tunnel 6to4 (si aucun pare-feu IPv4 ne prohibe ce trafic). Foncièrement, le tunnelage 6to4 n'est pas un tunnel en binôme ( -\emph on +\emph on one-to-one tunnel -\emph default +\emph default ). Ce tunnelage se subdivise en un tunnelage d'un flux montant et d'un flux descendant. Une adresse IPv6 spéciale indique que ce noeud utilisera un tunnelage 6to4 pour se connnecter au réseau mondial IPv6. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La génération d'un préfixe 6to4 -\layout Standard +\end_layout +\begin_layout Standard Une adresse 6to4 est définie comme suit (le schéma provient du \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset ): -\layout Code +\end_layout +\begin_layout Code | 3+13 | 32 | 16 | 64 bits | -\layout Code +\end_layout +\begin_layout Code +---+------+-----------+--------+--------------------------------+ -\layout Code +\end_layout +\begin_layout Code | FP+TLA | V4ADDR | SLA ID | Interface ID | -\layout Code +\end_layout +\begin_layout Code | 0x2002 | | | | -\layout Code +\end_layout +\begin_layout Code +---+------+-----------+--------+--------------------------------+ -\layout Standard +\end_layout +\begin_layout Standard FP et TLA ensemble (16 bits) ont la valeur 0x2002. V4ADDR est l'adresse IPv4 globale et unique du noeud (en notation hexadécimale). SLA est l'identifiant de sous-réseau (65536 sous-réseaux locaux possibles). Ils sont utilisés pour représenter la structure locale de votre réseau. -\layout Standard +\end_layout +\begin_layout Standard Pour les passerelles, un tel préfixe est généré en utilisant normalement pour SLA \begin_inset Quotes sld -\end_inset +\end_inset 0000 \begin_inset Quotes srd -\end_inset +\end_inset , et pour suffixe \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset (ce n'est pas une nécessité, il peut être déterminé arbitrairement, mais d'une portée locale) et assigné à l'interface de tunnelage 6to4. Notez que Windows Microsoft utilise aussi V4ADDR comme préfixe. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Le flux de tunnelage ascendant 6to4 -\layout Standard +\end_layout +\begin_layout Standard Le noeud doit savoir à quel point de connexion terminal étranger ses paquets IPv6 dans IPv4 doivent être envoyés. Aux tout premiers jours du tunnelage 6to4, des routeurs dédiés au tunnelage @@ -4608,716 +5642,909 @@ Le noeud doit savoir Voir \begin_inset LatexCommand \url[l'information 6to4 de NSayer]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset pour une liste de ses routeurs. -\layout Standard +\end_layout +\begin_layout Standard De nos jours, les routeurs de flux ascendant 6to4 peuvent être découverts comme par magie par l'emploi de l'adresse anycast 192.88.99.1. Les protocoles de routage s'occupent de cela en arrière-plan, voir le \begin_inset LatexCommand \url[RFC 3068 / An Anycast Prefix for 6to4 Relay Routers]{http://www.faqs.org/rfcs/rfc3068.html} -\end_inset +\end_inset pour les détails. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Le flux de tunnelage descendant 6to4 -\layout Standard +\end_layout +\begin_layout Standard La méthode servant au flux descendant (du 6bone vers votre noeud disposant de 6to4) n'est pas vraiment bien fixée et peut varier selon l'hôte étranger vers qui sont envoyés les paquets originaux. Il existe deux possibilités: -\layout Itemize +\end_layout +\begin_layout Itemize l'hôte étranger utilise 6to4 et émet directement en retour les paquets à votre noeud (voir plus bas) -\layout Itemize +\end_layout +\begin_layout Itemize l'hôte étranger émet les paquets en retour vers le réseau mondial IPv6 et selon le routage dynamique qui a lieu alors, un routeur relais créera un tunnel automatique de retour vers votre noeud. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Le trafic possible avec 6to4 -\layout Itemize +\end_layout +\begin_layout Itemize de 6to4 vers 6to4: est normalement tunnelé directement entre chacun des hôtes disposant de 6to4 -\layout Itemize +\end_layout +\begin_layout Itemize de 6to4 vers un trafic non 6to4: est émis -\emph on +\emph on via -\emph default +\emph default le flux ascendant du tunnelage -\layout Itemize +\end_layout +\begin_layout Itemize un trafic non 6to4 vers 6to4: est émis -\emph on +\emph on via -\emph default +\emph default le flux descendant du tunnelage -\layout Section +\end_layout +\begin_layout Section Afficher les tunnels existants -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 tunnel show [] -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 tunnel show -\layout Code +\end_layout +\begin_layout Code sit0: ipv6/ip remote any local any ttl 64 nopmtudisc -\layout Code +\end_layout +\begin_layout Code sit1: ipv6/ip remote 195.226.187.50 local any ttl 64 -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser "route" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 -\layout Standard +\end_layout +\begin_layout Standard Exemple (la sortie est filtrée afin de ne laisser apparaître que les tunnels empreintant l'interface sit0): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 | grep " -\backslash +\backslash Wsit0 -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code ::/96 :: U 256 2 0 sit0 -\layout Code +\end_layout +\begin_layout Code 2002::/16 :: UA 256 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code 2000::/3 ::193.113.58.75 UG 1 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code fe80::/10 :: UA 256 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code ff00::/8 :: UA 256 0 0 sit0 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{conf-ipv6-in-ipv4-point-to-point-tunnels} -\end_inset +\end_inset Montage d'un tunnel point-à-point -\layout Standard -\align left -Il y a 3 possibilités pour ajouter ou ôter un tunnel point-à-point. -\layout Standard +\end_layout +\begin_layout Standard +\align left +Il y a 3 possibilités pour ajouter ou ôter un tunnel point-à-point. +\end_layout + +\begin_layout Standard Une bonne source d'information additionnelle à propos de l'installation de tunnel grâce à \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset est \begin_inset LatexCommand \url[configurer les tunnels avec iproute2 (article)]{http://www.deepspace6.net/docs/iproute2tunnel-en.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[miroir]{http://mirrors.bieringer.de/www.deepspace6.net/docs/iproute2tunnel-en.html} -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection Ajouter un tunnel point-à-point -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser "ip" -\layout Standard -\align left -La méthode la plus commune actuellement pour une petite quantité de tunnels. -\layout Standard +\end_layout +\begin_layout Standard +\align left +La méthode la plus commune actuellement pour une petite quantité de tunnels. +\end_layout + +\begin_layout Standard Usage en vue de créer un périphérique de tunnelage (mais il n'est pas monté pour autant, une TTL doit également être spécifiée, car la valeur par défaut est 0) -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add mode sit ttl remote -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Standard +\end_layout +\begin_layout Standard Usage (exemple générique pour trois tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add sit1 mode sit ttl remote -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit1 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit1 metric 1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip tunnel add sit2 mode sit ttl -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit2 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit2 metric 1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip tunnel add sit3 mode sit ttl -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit3 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit3 metric 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser "ifconfig" et "route" (méthode dépréciée) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Ce n'est véritablement pas une méthode recommandée pour ajouter un tunnel, car elle est plutôt étrange. Pas de problème lors de l'ajout d'un seul tunnel, mais si vous en montez plus d'un, il ne vous est pas possible facilement de démonter le premier tout en laissant les autres fonctionner. -\layout Standard +\end_layout +\begin_layout Standard Usage (exemple générique pour trois tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit1 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit2 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit2 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit3 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit3 -\layout Standard +\end_layout +\begin_layout Standard Important: NE JAMAIS FAIRE DE LA SORTE, car cette façon de faire rend implicitem ent disponible le "tunnelage automatique" à partir de n'importe où dans l'Internet, c'est un risque, et cela ne devrait jamais être préconisé. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser seulement "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Il est aussi possible d'installer des tunnels dans le style Accès Multiple Sans Diffusion ( -\emph on +\emph on Non Broadcast Multiple Access -\emph default +\emph default , ou NBMA), c'est un moyen facile d'ajouter de nombreux tunnels en une fois. -\layout Standard +\end_layout +\begin_layout Standard Usage (exemple générique pour trois tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Standard +\end_layout +\begin_layout Standard Important: NE JAMAIS FAIRE DE LA SORTE, car cette façon de faire rend implicitem ent disponible le "tunnelage automatique" à partir de n'importe où dans l'Internet, c'est un risque, et cela ne devrait jamais être préconisé. -\layout Subsection +\end_layout +\begin_layout Subsection Ôter des tunnels point-à-point -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Rarement réalisé manuellement, mais utilisé par les scripts pour une extinction propre ou un redémarrage de la configuration IPv6. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser "ip" -\layout Standard +\end_layout +\begin_layout Standard Pour ôter un périphérique de tunnelage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del -\layout Standard +\end_layout +\begin_layout Standard Usage (exemple générique pour trois tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del dev sit1 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit1 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip -6 route del dev sit2 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit2 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit2 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip -6 route del dev sit3 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit3 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit3 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser "ifconfig" et "route" (méthode dépréciée parce qu'elle n'est pas très drôle) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Ce n'est pas seulement la création qui est étrange, mais l'extinction aussi... vous devez ôter les tunnels dans l'ordre inverse, ce qui signifie que le premier créé doit être le premier ôté. -\layout Standard +\end_layout +\begin_layout Standard Usage (exemple générique pour trois tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del dev sit3 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit3 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 del dev sit2 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit2 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 add dev sit1 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit1 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Code +\end_layout -\layout Subsubsection +\begin_layout Code +\end_layout + +\begin_layout Subsubsection Utiliser "route" -\layout Standard +\end_layout +\begin_layout Standard Comme pour ôter des routes IPv6 courantes -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage (exemple générique pour trois tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Subsection +\end_layout +\begin_layout Subsection Attribution d'une adresse ( -\emph on +\emph on numbered -\emph default +\emph default ) à un tunnel point-à-point -\layout Standard +\end_layout +\begin_layout Standard Il est parfois nécessaire de configurer un tunnel point-à-point avec des adresses IPv6 comme pour IPv4 aujourd'hui. C'est seulement possible avec la première méthode (ifconfig+route - dépréciée) et la troisième méthode (ip+route) d'installation de tunnel. Dans de tels cas, vous pouvez ajouter l'adresse IPv6 à l'interface de tunnelage comme montré dans la configuration d'interface. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{configuring-ipv6to4-tunnels} -\end_inset +\end_inset Installation des tunnels 6to4 -\layout Standard +\end_layout +\begin_layout Standard Prenez garde au fait que le support des tunnels 6to4 est actuellement manquant sur la série des noyaux vanille 2.2.x (voir \begin_inset LatexCommand \ref[la vérification du système / noyau]{systemcheck-kernel} -\end_inset +\end_inset pour plus de détails). Notez aussi que la longueur du préfixe d'une adresse 6to4 est de 16, car, du point de vue du réseau, tous les autres hôtes 6to4 sont sur la même couche 2. -\layout Subsection +\end_layout +\begin_layout Subsection Ajouter un tunnel 6to4 -\layout Standard +\end_layout +\begin_layout Standard Vous avez premièrement à calculer votre préfixe 6to4 en utilisant votre adresse IPv4 routable assignée localement (si votre hôte n'a pas d'adresse IPv4 routable, dans des cas précis, NAT sur une passerelle est possible): -\layout Standard +\end_layout +\begin_layout Standard En considérant que votre adresse IPv4 soit -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 -\layout Standard +\end_layout +\begin_layout Standard le préfixe 6to4 généré sera -\layout Code +\end_layout +\begin_layout Code 2002:0102:0304:: -\layout Standard +\end_layout +\begin_layout Standard Les passerelles locales 6to4 devraient (mais cela n'est pas une nécessité, vous pouvez choisir un préfixe arbitraire de portée locale, si cela vous sied mieux) toujours assigner le suffixe \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset , ce qui vous donnera comme adresse 6to4 locale -\layout Code +\end_layout +\begin_layout Code 2002:0102:0304::1 -\layout Standard +\end_layout +\begin_layout Standard Utiliser par exemple ce qui suit pour une génération automatique: -\layout Code +\end_layout +\begin_layout Code ipv4="1.2.3.4"; printf "2002:%02x%02x:%02x%02x::1" `echo $ipv4 | tr "." " "` -\layout Standard +\end_layout +\begin_layout Standard Il y a maintenant deux façons possibles de mettre en place un tunnelage 6to4. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser "ip" et un périphérique tunnel dédié -\layout Standard +\end_layout +\begin_layout Standard C'est dorénavant la façon de faire qui est recommandée (une TTL doit être spécifiée, car le défaut est 0). -\layout Standard +\end_layout +\begin_layout Standard Créez un nouveau périphérique tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add tun6to4 mode sit ttl remote any local -\layout Standard +\end_layout +\begin_layout Standard Montez l'interface -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev tun6to4 up -\layout Standard +\end_layout +\begin_layout Standard Ajouter une adresse 6to4 locale à l'interface (note: la longueur du préfixe, 16, est importante!) -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add /16 dev tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Ajouter une route (par défaut) au réseau global IPv6 en utilisant l'adresse anycast tous-routeurs-6to4 ( -\emph on +\emph on all-6to4-routers -\emph default +\emph default ) -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 via ::192.88.99.1 dev tun6to4 metric 1 -\layout Standard +\end_layout +\begin_layout Standard Il a été rapporté que certaines versions de \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset (par exemple Linux SuSe 9.0) ne prennent pas en charge les adresses IPv6 compatibles IPv4 pour les passerelles. Dans ce cas, l'adresse IPv6 correspondante doit être employée: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 via -\series bold +\series bold 2002:c058:6301::1 -\series default +\series default dev tun6to4 metric 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser "ifconfig", "route" et le périphérique de tunnelage \begin_inset Quotes sld -\end_inset +\end_inset sit0 \begin_inset Quotes srd -\end_inset +\end_inset (méthode dépréciée) -\layout Standard +\end_layout +\begin_layout Standard Cela est déprécié car le périphérique de tunnel générique sit0 ne permet pas de spécifier un filtrage par périphérique. -\layout Standard +\end_layout +\begin_layout Standard Monter l'interface de tunnelage générique sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Standard +\end_layout +\begin_layout Standard Ajouter une adresse 6to4 locale à une interface -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 add /16 -\layout Standard +\end_layout +\begin_layout Standard Ajouter une route (par défaut) au réseau global IPv6 en utilisant l'adresse anycast IPv4 tous-relais-6to4 ( -\emph on +\emph on all-6to4-relays -\emph default +\emph default ) -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 gw ::192.88.99.1 dev sit0 -\layout Subsection +\end_layout +\begin_layout Subsection Ôter un tunnel 6to4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser "ip" et un périphérique de tunnelage dédié -\layout Standard +\end_layout +\begin_layout Standard Ôter toutes les routes traversant ce périphérique de tunnelage spécifique -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route flush dev tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Démonter l'interface -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev tun6to4 down -\layout Standard +\end_layout +\begin_layout Standard Ôter un périphérique tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del tun6to4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Utiliser \begin_inset Quotes sld -\end_inset +\end_inset ifconfig \begin_inset Quotes srd -\end_inset +\end_inset , \begin_inset Quotes sld -\end_inset +\end_inset route \begin_inset Quotes srd -\end_inset +\end_inset et un périphérique de tunnel générique \begin_inset Quotes sld -\end_inset +\end_inset sit0 \begin_inset Quotes srd -\end_inset +\end_inset (déprécié) -\layout Standard +\end_layout +\begin_layout Standard Ôter une route (par défaut) traversant une interface tunnel 6to4 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 gw ::192.88.99.1 dev sit0 -\layout Standard +\end_layout +\begin_layout Standard Ôter une adresse locale 6to4 d'une interface -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 del /16 -\layout Standard +\end_layout +\begin_layout Standard Démontage d'un périphérique de tunnelage générique (prenez garde, peut-être est-il utilisé...) -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuring-ipv4-in-ipv6-tunnels} -\end_inset +\end_inset Configurer les tunnels IPv4-in-IPv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Cela sera complété à l'avenir. Pour le moment, de tels tunnels sont essentiellement employés en environnement de test, mais il semble que le support soit actuellement manquant pour linux (03/2004). -\layout Standard +\end_layout +\begin_layout Standard Pour l'heure, plus d'information dans le \begin_inset LatexCommand \url[RFC 2473 / Generic Packet Tunneling in IPv6 Specification]{http://www.faqs.org/rfcs/rfc2473.html} -\end_inset +\end_inset -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-kernel-settings} -\end_inset +\end_inset Les réglages du noyau dans le système de fichiers /proc -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \label{proc-filesystem} -\end_inset +\end_inset Note: la source de cette section est essentiellement le fichier "ip-sysctl.txt", qui est inclus dans les sources du noyau actuel, dans le répertoire "Documentat @@ -5326,1714 +6553,2115 @@ ion/networking". à IPv6. D'autres textes sont aussi plus ou moins copier/coller dans cette partie de document. -\layout Section +\end_layout +\begin_layout Section Comment accéder au système de fichiers /proc -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset et \begin_inset Quotes sld -\end_inset +\end_inset echo \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Utiliser "cat" et "echo" est le moyen le plus simple d'accéder au système de fichiers /proc, mais certains pré-requis sont nécessaires à cela -\layout Itemize +\end_layout +\begin_layout Itemize Le système de fichiers /proc doit être rendu disponible dans le noyau, ce qui signifie qu'à la compilation le commutateur suivant doit avoir été positionné -\layout Code +\end_layout +\begin_layout Code CONFIG_PROC_FS=y -\layout Itemize +\end_layout +\begin_layout Itemize Le système de fichiers /proc doit être auparavant monté, ce qui peut être testé en faisant -\layout Code +\end_layout +\begin_layout Code # mount | grep "type proc" -\layout Code +\end_layout +\begin_layout Code none on /proc type proc (rw) -\layout Itemize +\end_layout +\begin_layout Itemize Vous devez pouvoir lire le système de fichiers /proc et parfois aussi y écrire (normalement seul root le peut) -\layout Standard +\end_layout +\begin_layout Standard Normalement, seules les entrées dans /proc/sys/* sont en écriture, les autres sont en lecture seule et servent seulement à la récupération de l'information. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Récupérer une valeur -\layout Standard +\end_layout +\begin_layout Standard La valeur de l'entrée peut être récupérée en utilisant "cat": -\layout Code +\end_layout +\begin_layout Code # cat /proc/sys/net/ipv6/conf/all/forwarding -\layout Code +\end_layout +\begin_layout Code 0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Fixer une valeur -\layout Standard +\end_layout +\begin_layout Standard Une nouvelle valeur peut être fixée (si l'entrée est en écriture) en utilisant echo: -\layout Code +\end_layout +\begin_layout Code # echo "1" >/proc/sys/net/ipv6/conf/all/forwarding -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Utiliser le programme "sysctl" pour accéder aux commutateurs du noyau est une méthode moderne aujourd'hui. Vous pouvez aussi l'utiliser même si le système de fichiers /proc n'est pas monté. Mais vous n'avez alors accès qu'à /proc/sys/*! -\layout Standard +\end_layout +\begin_layout Standard Le programme \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset est compris dans le paquetage \begin_inset Quotes sld -\end_inset +\end_inset procps \begin_inset Quotes srd -\end_inset +\end_inset (sur le système Red Hat). -\layout Itemize +\end_layout +\begin_layout Itemize L'interface sysctl doit être disponible dans le noyau, ce qui signifie qu'à la compilation le commutateur suivant a à être fixé -\layout Code +\end_layout +\begin_layout Code CONFIG_SYSCTL=y -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Récupérer une valeur -\layout Standard +\end_layout +\begin_layout Standard La valeur de l'entrée peut maintenant être récupérée: -\layout Code +\end_layout +\begin_layout Code # sysctl net.ipv6.conf.all.forwarding -\layout Code +\end_layout +\begin_layout Code net.ipv6.conf.all.forwarding = 0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Fixer une valeur -\layout Standard +\end_layout +\begin_layout Standard Une nouvelle valeur peut être fixée (si l'entrée est en écriture): -\layout Code +\end_layout +\begin_layout Code # sysctl -w net.ipv6.conf.all.forwarding=1 -\layout Code +\end_layout +\begin_layout Code net.ipv6.conf.all.forwarding = 1 -\layout Standard +\end_layout +\begin_layout Standard Note: n'utilisez pas d'espaces autour du signe "=" lorsque vous fixez les valeurs. De même pour une valeur multiple sur une même ligne, mettez des guillemets comme ceci -\layout Code +\end_layout +\begin_layout Code # sysctl -w net.ipv4.ip_local_port_range= -\series bold +\series bold " -\series default +\series default 32768 61000 -\series bold +\series bold " -\layout Code +\end_layout +\begin_layout Code net.ipv4.ip_local_port_range = 32768 61000 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection En plus -\layout Standard +\end_layout +\begin_layout Standard Note: il existe dans la pratique certaines versions de sysctl qui affichent \begin_inset Quotes sld -\end_inset +\end_inset / \begin_inset Quotes srd -\end_inset +\end_inset au lieu de \begin_inset Quotes sld -\end_inset +\end_inset . \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Pour plus de détails jetez un coup d'oeil dans la page de manuel de sysctl. -\layout Standard +\end_layout +\begin_layout Standard une astuce: pour une recherche rapide parmi les réglages, utiliser \begin_inset Quotes sld -\end_inset +\end_inset -a \begin_inset Quotes srd -\end_inset +\end_inset (afficher toutes les entrées) en conjonction avec \begin_inset Quotes sld -\end_inset +\end_inset grep \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Les types de valeur trouvés dans le système de fichiers /proc -\layout Standard +\end_layout +\begin_layout Standard IL y a plusieurs formats observés dans le système de fichiers /proc: -\layout Itemize +\end_layout +\begin_layout Itemize BOOLÉEN: simple \begin_inset Quotes sld -\end_inset +\end_inset 0 \begin_inset Quotes srd -\end_inset +\end_inset (faux) ou \begin_inset Quotes sld -\end_inset +\end_inset 1 \begin_inset Quotes srd -\end_inset +\end_inset (vrai) -\layout Itemize +\end_layout +\begin_layout Itemize ENTIER: une valeur entière, peut être également non signée -\layout Itemize +\end_layout +\begin_layout Itemize Des lignes plus sophistiquées avec plusieurs valeurs: parfois un en-tête est aussi affiché, sinon, jetez un coup d'oeil aux sources du noyau pour savoir quel sens possède telle ou telle valeur... -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-sys-net-ipv6} -\end_inset +\end_inset Les entrées de /proc/sys/net/ipv6/ -\layout Subsection +\end_layout +\begin_layout Subsection conf/default/* -\layout Standard +\end_layout +\begin_layout Standard Changer les réglages par défaut spécifiques à chaque interface. -\layout Subsection +\end_layout +\begin_layout Subsection conf/all/* -\layout Standard +\end_layout +\begin_layout Standard Changer tous les réglages spécifiques aux interfaces. -\layout Standard +\end_layout +\begin_layout Standard Exception: \begin_inset Quotes sld -\end_inset +\end_inset conf/all/forwarding \begin_inset Quotes srd -\end_inset +\end_inset a une signification différente ici -\layout Subsubsection +\end_layout +\begin_layout Subsubsection conf/all/forwarding -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLÉEN -\layout Standard +\end_layout +\begin_layout Standard Ceci rend disponible le renvoi global IPv6 entre toutes les interfaces. -\layout Standard +\end_layout +\begin_layout Standard En IPv6, vous ne pouvez contrôler le renvoi par périphérique, le contrôle du renvoi doit être réalisé en utilisant les jeux de règles de netfilter-IPv6 (contrôlés grâce à ip6tables) en spécifiant les périphériques d'entrée et de sortie (voir \begin_inset LatexCommand \ref[comment mettre en place un pare-feu/Netfilter6]{firewalling-netfilter6} -\end_inset +\end_inset pour plus d'information); à la différence d'IPv4, où vous pouvez contrôler le renvoi périphérique par périphérique (la décision est prise sur l'interface qui reçoit des paquets). -\layout Standard +\end_layout +\begin_layout Standard Ceci fixe aussi le réglage du renvoi Hôte/Routeur de toutes les interfaces à la valeur spécifiée. Voir plus bas pour plus de détails. Tout ceci relève du renvoi global. -\layout Standard +\end_layout +\begin_layout Standard Si cette valeur est à 0, aucun renvoi IPv6 n'est disponible, jamais aucun paquet ne part vers une autre interface, ni physique, ni logique, comme par exemple un tunnel. -\layout Subsection +\end_layout +\begin_layout Subsection conf/interface/* -\layout Standard +\end_layout +\begin_layout Standard Changer les réglages spécifiques à chaque interface. -\layout Standard +\end_layout +\begin_layout Standard Le comportement fonctionnel de certains réglages est dépendant du positionnement du renvoi local, disponible ou non. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection accept_ra -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLÉEN -\layout Itemize +\end_layout +\begin_layout Itemize Défaut fonctionnel: disponible si le renvoi local est disponible; indisponible si le renvoi local est disponible. -\layout Standard +\end_layout +\begin_layout Standard Accepter les annonces de routeur, et auto-configurer cette interface avec les données reçues. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection accept_redirects -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLÉEN -\layout Itemize +\end_layout +\begin_layout Itemize Défaut fonctionnel: disponible si le renvoi local est indisponible. Indisponible si le renvoi local est disponible. -\layout Standard +\end_layout +\begin_layout Standard Accepter les redirections émises par un routeur IPv6. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection autoconf -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLÉEN -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: VRAI -\layout Standard +\end_layout +\begin_layout Standard Configurer les adresses lien-local (voir aussi \begin_inset LatexCommand \ref[Les types d'adresse]{chapter-addresstypes} -\end_inset +\end_inset ) utilisant les adresses matérielles L2. Par exemple, ceci génère, comme par magie, une adresse telle que \begin_inset Quotes sld -\end_inset +\end_inset fe80::201:23ff:fe45:6789 \begin_inset Quotes srd -\end_inset +\end_inset sur une interface ayant une adresse MAC-L2. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dad_transmits -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 1 -\layout Standard +\end_layout +\begin_layout Standard Quantité de message de détection d'adresse dupliquée à émettre. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection forwarding -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLÉEN -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: FAUX si le renvoi global est indisponible (défaut), sinon VRAI -\layout Standard +\end_layout +\begin_layout Standard Configurer le comportement spécifique à chaque interface Hôte/Routeur. -\layout Standard +\end_layout +\begin_layout Standard Note: Il est recommandé d'avoir le même réglage sur toutes les interfaces; mélanger les scénarii routeur/hôte est plutôt atypique. -\layout Itemize +\end_layout +\begin_layout Itemize Valeur FAUX: Par défaut, le comportement d'hôte est assumé. Cela signifie que: -\layout Enumerate +\end_layout +\begin_layout Enumerate Le drapeau IsRouter n'est pas positionné dans les annonces de voisinage. -\layout Enumerate +\end_layout +\begin_layout Enumerate Les sollicitations de routeur sont envoyées dès que nécessaires. -\layout Enumerate +\end_layout +\begin_layout Enumerate Si accept_ra est VRAI (défaut), accepte les annonces de routeur (et réalise une auto-configuration). -\layout Enumerate +\end_layout +\begin_layout Enumerate Si accept_redirects est VRAI (défaut), accepte les redirections. -\layout Itemize +\end_layout +\begin_layout Itemize Valeur VRAI: si le renvoi local est disponible, le comportement d'un routeur est assumé. Ceci signifie l'opposé de ce qui précéde: -\layout Enumerate +\end_layout +\begin_layout Enumerate Le drapeau IsRouter est positionné dans les annonces de voisinage. -\layout Enumerate +\end_layout +\begin_layout Enumerate Les sollicitations de routeur ne sont pas émises. -\layout Enumerate +\end_layout +\begin_layout Enumerate Les annonces de routeur sont ignorées. -\layout Enumerate +\end_layout +\begin_layout Enumerate Les redirections sont ignorées. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection hop_limit -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 64 -\layout Standard +\end_layout +\begin_layout Standard Nombre limite de sauts par défaut. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mtu -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 1280 (minimum requis pour IPv6) -\layout Standard +\end_layout +\begin_layout Standard Unité de transfert maximum par défaut -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitation_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 1 -\layout Standard +\end_layout +\begin_layout Standard Nombre de secondes à attendre après le montage d'une interface avant d'émettre des sollicitations de routeur. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitation_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 4 -\layout Standard +\end_layout +\begin_layout Standard Nombre de secondes d'attente entre les émissions de sollicitations de routeur. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitations -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 3 -\layout Standard +\end_layout +\begin_layout Standard Nombre de sollicitation(s) de routeur à émettre avant de considérer qu'aucun routeur n'est présent. -\layout Subsection +\end_layout +\begin_layout Subsection neigh/default/* -\layout Standard +\end_layout +\begin_layout Standard Changer les réglages par défaut pour la détection de voisinage et certaines valeurs d'intervalle global et de déclenchement ( -\emph on +\emph on threshold -\emph default +\emph default ): -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh1 -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 128 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh2 -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 512 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh3 -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 1024 -\layout Standard +\end_layout +\begin_layout Standard Paramètre de réglage de la taille de la table du voisinage. -\layout Standard +\end_layout +\begin_layout Standard Augmenter cette valeur si vous avez de nombreuses interfaces et un problème avec des routes qui commencent à mystérieusement s'activer et échouer. Ou si un \begin_inset LatexCommand \url[démon de routage Zebra]{http://www.zebra.org/} -\end_inset +\end_inset en cours d'activité rapporte cette erreur: -\layout Code +\end_layout +\begin_layout Code ZEBRA: netlink-listen error: No buffer space available, type=RTM_NEWROUTE(24), seq=426, pid=0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 30 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsection +\end_layout +\begin_layout Subsection neigh/interface/* -\layout Standard +\end_layout +\begin_layout Standard Changez ces réglages spécifiques à chaque interface pour la détection de voisinage. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection anycast_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 100 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_stale_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 60 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection proxy_qlen -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 64 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection unres_qlen -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 3 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection app_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 0 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection locktime -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 0 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection retrans_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 100 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection base_reachable_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 30 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mcast_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 3 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ucast_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 3 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection delay_first_probe_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 5 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection proxy_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 80 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsection +\end_layout +\begin_layout Subsection route/* -\layout Standard +\end_layout +\begin_layout Standard Changer les réglages globaux du routage. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection flush -\layout Standard +\end_layout +\begin_layout Standard Retiré des nouvelles versions du noyau . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 30 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 1024 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mtu_expires -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 600 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_elasticity -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 0 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_min_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 5 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_timeout -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 60 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection min_adv_mss -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 12 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection max_size -\layout Itemize +\end_layout +\begin_layout Itemize Type: ENTIER -\layout Itemize +\end_layout +\begin_layout Itemize Défaut: 4096 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-sys-net-ipv4} -\end_inset +\end_inset Les entrées relatives à IPv6 dans /proc/sys/net/ipv4/ -\layout Standard +\end_layout +\begin_layout Standard Pour le moment (et cela sera valable jusqu'à ce qu'IPv4 soit complètement converti en un module indépendant du noyau), certains commutateurs IPv4 sont aussi utilisés par IPv6. -\layout Subsection +\end_layout +\begin_layout Subsection ip_* -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ip_local_port_range -\layout Standard +\end_layout +\begin_layout Standard Ce réglage sont aussi utilisé par IPv6. -\layout Subsection +\end_layout +\begin_layout Subsection tcp_* -\layout Standard +\end_layout +\begin_layout Standard Ces réglages sont aussi utilisés par IPv6. -\layout Subsection +\end_layout +\begin_layout Subsection icmp_* -\layout Standard +\end_layout +\begin_layout Standard Ces réglages ne sont pas utilisés par IPv6. Pour réaliser une limitation du trafic ICMPv6 (ce qui est très recommandé compte tenu de possibles engorgements ICMPv6), des règles netfilter-v6 doivent être utilisées. -\layout Subsection +\end_layout +\begin_layout Subsection autre(s) -\layout Standard +\end_layout +\begin_layout Standard Inconnu(s), mais probablement inutilisé(s) par IPv6. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-net} -\end_inset +\end_inset Les entrées relatives à IPv6 dans /proc/net/ -\layout Standard +\end_layout +\begin_layout Standard Dans /proc/net il y a plusieurs entrées disponibles en lecture seule. Vous ne pouvez pas utiliser ici \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset afin de récupérer des informations, utiliser \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection if_inet6 -\layout Itemize +\end_layout +\begin_layout Itemize Type: Une ligne par adresse comporte plusieurs valeurs -\layout Standard +\end_layout +\begin_layout Standard Ici toutes les adresses IPv6 configurées sont montrées sous un format particulie r. L'exemple affiche seulement l'interface loopback. Sa signification est détaillée ci-dessous (voir \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/addrconf.c \begin_inset Quotes srd -\end_inset +\end_inset pour en savoir plus). -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/if_inet6 -\layout Code +\end_layout +\begin_layout Code 00000000000000000000000000000001 01 80 10 80 lo -\layout Code +\end_layout +\begin_layout Code +------------------------------+ ++ ++ ++ ++ ++ -\layout Code +\end_layout +\begin_layout Code | | | | | | -\layout Code +\end_layout +\begin_layout Code 1 2 3 4 5 6 -\layout Enumerate +\end_layout +\begin_layout Enumerate L'adresse IPv6 affichée grâce à 32 caractères hexadécimaux sans le séparateur ":" -\layout Enumerate +\end_layout +\begin_layout Enumerate Numéro de périphérique Netlink (index d'interface) in hexadécimal (voir aussi \begin_inset Quotes sld -\end_inset +\end_inset ip addr \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Enumerate +\end_layout +\begin_layout Enumerate La longueur du préfixe en hexadécimal -\layout Enumerate +\end_layout +\begin_layout Enumerate La valeur de la portée (voir les sources du noyau "include/net/ipv6.h" et "net/ipv6/addrconf.c" pour plus de détails) -\layout Enumerate +\end_layout +\begin_layout Enumerate Les drapeaux de l'interface (voir \begin_inset Quotes sld -\end_inset +\end_inset include/linux/rtnetlink.h \begin_inset Quotes srd -\end_inset +\end_inset et \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/addrconf.c \begin_inset Quotes srd -\end_inset +\end_inset pour en savoir plus) -\layout Enumerate +\end_layout +\begin_layout Enumerate Le nom du périphérique -\layout Subsection +\end_layout +\begin_layout Subsection ipv6_route -\layout Itemize +\end_layout +\begin_layout Itemize Type: Une ligne par route comporte plusieurs valeurs -\layout Standard +\end_layout +\begin_layout Standard Ici toutes les routes IPv6 configurées sont montrées dans un format particulier. L'exemple affiche seulement l'interface loopback. Sa signification est détaillée ci-dessous (voir \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/route.c \begin_inset Quotes srd -\end_inset +\end_inset pour en savoir plus). -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/ipv6_route -\layout Code +\end_layout +\begin_layout Code 00000000000000000000000000000000 00 00000000000000000000000000000000 00 -\layout Code +\end_layout +\begin_layout Code +------------------------------+ ++ +------------------------------+ ++ -\layout Code +\end_layout +\begin_layout Code | | | | -\layout Code +\end_layout +\begin_layout Code 1 2 3 4 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code ¬ 00000000000000000000000000000000 ffffffff 00000001 00000001 00200200 lo -\layout Code +\end_layout +\begin_layout Code ¬ +------------------------------+ +------+ +------+ +------+ +------+ ++ -\layout Code +\end_layout +\begin_layout Code ¬ | | | | | | -\layout Code +\end_layout +\begin_layout Code ¬ 5 6 7 8 9 10 -\layout Enumerate +\end_layout +\begin_layout Enumerate Le réseau de destination IPv6 affiché grâce à 32 caractères hexadécimaux sans le séparateur ":" -\layout Enumerate +\end_layout +\begin_layout Enumerate La longueur du préfixe de destination IPv6 en hexadécimal -\layout Enumerate +\end_layout +\begin_layout Enumerate Le réseau source IPv6 affiché grâce à 32 caractères hexadécimaux sans le séparateur ":" -\layout Enumerate +\end_layout +\begin_layout Enumerate La longueur du préfixe de la source IPv6 en hexadécimal -\layout Enumerate +\end_layout +\begin_layout Enumerate Le prochain saut IPv6 affiché grâce à 32 caractères hexadécimaux sans le séparateur ":" -\layout Enumerate +\end_layout +\begin_layout Enumerate La distance en hexadécimal -\layout Enumerate +\end_layout +\begin_layout Enumerate Compteur de référence -\layout Enumerate +\end_layout +\begin_layout Enumerate Compteur d'utilisation -\layout Enumerate +\end_layout +\begin_layout Enumerate Les drapeaux -\layout Enumerate +\end_layout +\begin_layout Enumerate Nom du périphérique -\layout Subsection +\end_layout +\begin_layout Subsection sockstat6 -\layout Itemize +\end_layout +\begin_layout Itemize Type: Une ligne par protocole avec description et valeur -\layout Standard +\end_layout +\begin_layout Standard Statistiques à propos de l'utilisation des sockets IPv6. Exemple: -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/sockstat6 -\layout Code +\end_layout +\begin_layout Code TCP6: inuse 7 -\layout Code +\end_layout +\begin_layout Code UDP6: inuse 2 -\layout Code +\end_layout +\begin_layout Code RAW6: inuse 1 -\layout Code +\end_layout +\begin_layout Code FRAG6: inuse 0 memory 0 -\layout Subsection +\end_layout +\begin_layout Subsection tcp6 -\layout Standard +\end_layout +\begin_layout Standard A remplir. -\layout Subsection +\end_layout +\begin_layout Subsection udp6 -\layout Standard +\end_layout +\begin_layout Standard A remplir. -\layout Subsection +\end_layout +\begin_layout Subsection igmp6 -\layout Standard +\end_layout +\begin_layout Standard A remplir. -\layout Subsection +\end_layout +\begin_layout Subsection raw6 -\layout Standard +\end_layout +\begin_layout Standard A remplir. -\layout Subsection +\end_layout +\begin_layout Subsection ip6_flowlabel -\layout Standard +\end_layout +\begin_layout Standard A remplir. -\layout Subsection +\end_layout +\begin_layout Subsection rt6_stats -\layout Standard +\end_layout +\begin_layout Standard A remplir. -\layout Subsection +\end_layout +\begin_layout Subsection snmp6 -\layout Itemize +\end_layout +\begin_layout Itemize Type: Une ligne par description et valeur SNMP -\layout Standard +\end_layout +\begin_layout Standard Statistiques SNMP, peuvent être récupérées par un serveur SNMP et mis en rapport à une tableau MIB grâce à un logiciel d'administration réseau. -\layout Subsection +\end_layout +\begin_layout Subsection ip6_tables_names -\layout Standard +\end_layout +\begin_layout Standard Tables netfilter6 disponibles -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{netlink} -\end_inset +\end_inset L'interface de netlink vers le noyau -\layout Standard +\end_layout +\begin_layout Standard A remplir... je n'ai en cela pas d'expérience... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{network-debugging} -\end_inset +\end_inset Le déboguage réseau -\layout Section +\end_layout +\begin_layout Section Les sockets d'écoute de serveur -\layout Subsection +\end_layout +\begin_layout Subsection Utiliser \begin_inset Quotes sld -\end_inset +\end_inset netstat \begin_inset Quotes srd -\end_inset +\end_inset pour vérifier les sockets d'écoute de serveur -\layout Standard +\end_layout +\begin_layout Standard C'est toujours intéressant de savoir quelles sockets de serveur sont actives à un moment donné sur un noeud. Utiliser \begin_inset Quotes sld -\end_inset +\end_inset netstat \begin_inset Quotes srd -\end_inset +\end_inset est le moyen le plus court pour obtenir une telle information: -\layout Standard +\end_layout +\begin_layout Standard options employées: -nlptu -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # netstat -nlptu -\layout Code +\end_layout +\begin_layout Code Active Internet connections (only servers) -\layout Code +\end_layout +\begin_layout Code Proto Recv-Q Send-Q Local Address Foreign Address State -\layout Code +\end_layout +\begin_layout Code ¬ PID/Program name -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:32768 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1258/rpc.statd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1502/rpc.mountd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:515 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 22433/lpd Waiting -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:139 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1746/smbd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1230/portmap -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 3551/X -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:8081 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 18735/junkbuster -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:3128 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:1.2.3.1:993 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::13 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:1.2.3.1:143 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::53 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::22 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1410/sshd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::6010 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 13237/sshd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32768 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1258/rpc.statd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:2049 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ - -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32770 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1502/rpc.mountd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32771 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ - -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:137 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:137 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:138 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:138 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:33044 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:53 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 127.0.0.1:53 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:67 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1530/dhcpd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:67 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1530/dhcpd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32858 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:4827 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:111 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1230/portmap -\layout Code +\end_layout +\begin_layout Code udp 0 0 :::53 :::* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{examples-tcpdump} -\end_inset +\end_inset Des exemples de dump provenant de tcpdump -\layout Standard +\end_layout +\begin_layout Standard Suivent quelques exemples de paquets capturés, cela sera peut-être utile pour vos propres déboguages... -\layout Standard +\end_layout +\begin_layout Standard ...plus d'info à venir... -\layout Subsection +\end_layout +\begin_layout Subsection La découverte de routeur -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une annonce de routeur -\layout Code +\end_layout +\begin_layout Code 15:43:49.484751 fe80::212:34ff:fe12:3450 > ff02::1: icmp6: router -\layout Code +\end_layout +\begin_layout Code ¬ advertisement(chlim=64, router_ltime=30, reachable_time=0, -\layout Code +\end_layout +\begin_layout Code ¬ retrans_time=0)(prefix info: AR valid_ltime=30, preffered_ltime=20, -\layout Code +\end_layout +\begin_layout Code ¬ prefix=2002:0102:0304:1::/64)(prefix info: LAR valid_ltime=2592000, -\layout Code +\end_layout +\begin_layout Code ¬ preffered_ltime=604800, prefix=3ffe:ffff:0:1::/64)(src lladdr: -\layout Code +\end_layout +\begin_layout Code ¬ 0:12:34:12:34:50) (len 88, hlim 255) -\layout Standard +\end_layout +\begin_layout Standard Un routeur, avec pour adresse lien-local \begin_inset Quotes sld -\end_inset +\end_inset fe80::212:34ff:fe12:3450 \begin_inset Quotes srd -\end_inset +\end_inset , émet une annonce à l'adresse multicast tous-les-noeuds-du-lien ( -\emph on +\emph on all-node-on-link -\emph default +\emph default ) \begin_inset Quotes sld -\end_inset +\end_inset ff02::1 \begin_inset Quotes srd -\end_inset +\end_inset , contenant deux préfixes, \begin_inset Quotes sld -\end_inset +\end_inset 2002:0102:0304:1::/64 \begin_inset Quotes srd -\end_inset +\end_inset (d'une durée de vie de 30 s) et \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1::/64 \begin_inset Quotes srd -\end_inset +\end_inset (d'une durée de vie de 2592000 s), incluant sa propre adresse MAC de couche 2, \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:50 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une sollicitation de routeur -\layout Code +\end_layout +\begin_layout Code 15:44:21.152646 fe80::212:34ff:fe12:3456 > ff02::2: icmp6: router solicitation -\layout Code +\end_layout +\begin_layout Code ¬ (src lladdr: 0:12:34:12:34:56) (len 16, hlim 255) -\layout Standard +\end_layout +\begin_layout Standard Un noeud, avec pour adresse lien-local \begin_inset Quotes sld -\end_inset +\end_inset fe80::212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset et comme adresse de couche 2 \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:56 \begin_inset Quotes srd -\end_inset +\end_inset , est en quête d'un routeur présent sur le lien, en conséquence il émet cette sollicitation à l'adresse multicast tous-routeurs-présents-sur-le-lien ( -\emph on +\emph on all-router-on-link -\emph default +\emph default ) \begin_inset Quotes sld -\end_inset +\end_inset ff02::2 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection La découverte de voisinage -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une sollicitation de découverte de voisinage afin de détecter une possible duplication d'adresse -\layout Standard +\end_layout +\begin_layout Standard Les paquets suivants sont émis par un noeud sur la couche 2, adresse MAC \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:56 \begin_inset Quotes srd -\end_inset +\end_inset , pendant l'auto-configuration, afin de vérifier si une adresse potentielle est déjà employée ou non par un autre noeud sur le lien permettant d'émettre ces paquets, -\emph on +\emph on via -\emph default +\emph default l'adresse multicast lien-local du noeud sollicité. -\layout Itemize +\end_layout +\begin_layout Itemize Le noeud veut configurer son lien-local avec l'adresse \begin_inset Quotes sld -\end_inset +\end_inset fe80::212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset , il est en train de vérifier s'il y a duplication -\layout Code +\end_layout +\begin_layout Code 15:44:17.712338 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ fe80::212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Le noeud veut configurer son adresse globale \begin_inset Quotes sld -\end_inset +\end_inset 2002:0102:0304:1:212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset (après avoir reçu l'annonce montrée plus haut), il est en train de vérifier s'il y a ou non duplication -\layout Code +\end_layout +\begin_layout Code 15:44:21.905596 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ 2002:0102:0304:1:212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, -\layout Code +\end_layout +\begin_layout Code ¬ hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Le noeud veut configurer son adresse globale \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1:212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset (après avoir reçu l'annonce montrée plus haut), il est en train de vérifier s'il y a ou non duplication -\layout Code +\end_layout +\begin_layout Code 15:44:22.304028 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:0:1:212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, hlim -\layout Code +\end_layout +\begin_layout Code ¬ 255) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une sollicitation de découverte de voisinage à la recherche d'hôte(s) ou de passerelle(s) -\layout Itemize +\end_layout +\begin_layout Itemize Un noeud veut émettre des paquets à \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1::10 \begin_inset Quotes srd -\end_inset +\end_inset mais il n'a aucune adresse MAC de la couche 2 vers laquelle il pourrait émettre, il émet alors maintenant une sollicitation -\layout Code +\end_layout +\begin_layout Code 13:07:47.664538 2002:0102:0304:1:2e0:18ff:fe90:9205 > ff02::1:ff00:10: icmp6: -\layout Code +\end_layout +\begin_layout Code ¬ neighbor sol: who has 3ffe:ffff:0:1::10(src lladdr: 0:e0:18:90:92:5) (len 32, -\layout Code +\end_layout +\begin_layout Code ¬ hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Ce noeud recherche maintenant \begin_inset Quotes sld -\end_inset +\end_inset fe80::10 \begin_inset Quotes srd -\end_inset +\end_inset -\layout Code +\end_layout +\begin_layout Code 13:11:20.870070 fe80::2e0:18ff:fe90:9205 > ff02::1:ff00:10: icmp6: neighbor -\layout Code +\end_layout +\begin_layout Code ¬ sol: who has fe80::10(src lladdr: 0:e0:18:90:92:5) (len 32, hlim 255) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-support-persistent-configuration} -\end_inset +\end_inset Support à la configuration persistante IPv6 dans les distributions Linux -\layout Standard +\end_layout +\begin_layout Standard Certaines distributions Linux contiennent déjà un support à la configuration persistante IPv6 utilisant une configuration nouvelle ou préexistante, des fichiers de script, et des accroches dans les fichiers de script IPv4. -\layout Section +\end_layout +\begin_layout Section Linux Red Hat et ses "clones" -\layout Standard +\end_layout +\begin_layout Standard Depuis que j'ai commencé à écrire l' \begin_inset LatexCommand \url[Howto -IPv6 & Linux ]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset , il était dans mon intention de rendre disponible une configuration convenant aux cas les plus fréquents tels que hôte simple, routeur simple, hôte à double résidence, routeur avec un second tronçon réseau, tunnel typique, tunnel 6to4, -\emph on +\emph on etc -\emph default +\emph default . De nos jours, il existe des fichiers de configuration et des scripts qui font très bien ce travail (je n'ai jamais entendu parler de vrais problèmes, @@ -7042,12 +8670,12 @@ etc volume, ils ont leur propre page HOWTO: \begin_inset LatexCommand \url[initscripts-ipv6]{http://www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[miroir]{http://mirrors.bieringer.de/www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ). Parce que j'ai commencé mon expérience IPv6 sur un clone de la Linux Red @@ -7058,1085 +8686,1271 @@ etc Il est ainsi très facile d'étendre certains de ces fichiers de configuration, d'en créer de nouveaux et de créer de simples accroches d'appel à l'installatio n d'IPv6 à partir de l'installation d'IPV4. -\layout Standard +\end_layout +\begin_layout Standard Depuis la Red Hat 7.1, une archive de mes scripts y est incluse. Cela est dû, et cela sera encore vrai à l'avenir, à l'assistance de Pekka Savola. -\layout Standard +\end_layout +\begin_layout Standard La Mandrake, depuis la version 8.0, inclut aussi un paquetage initscript prêt pour IPv6, cependant un bogue mineur retient de l'employer (il manque 'inet6 \begin_inset Quotes srd -\end_inset +\end_inset à \begin_inset Quotes sld -\end_inset +\end_inset ifconfig \begin_inset Quotes srd -\end_inset +\end_inset avant \begin_inset Quotes sld -\end_inset +\end_inset add \begin_inset Quotes srd -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection Tester la présence des scripts de configuration IPv6 -\layout Standard +\end_layout +\begin_layout Standard Vous pouvez tester si votre distribution Linux contient le support pour la configuration persistante IPv6 utilisant mon jeu d'outils. Le script de la bibliothèque devrait exister: -\layout Code +\end_layout +\begin_layout Code /etc/sysconfig/network-scripts/network-functions-ipv6 -\layout Standard +\end_layout +\begin_layout Standard Un test magique: -\layout Code +\end_layout +\begin_layout Code # test -f /etc/sysconfig/network-scripts/network-functions-ipv6 && echo "Main -\layout Code +\end_layout +\begin_layout Code ¬ IPv6 script library exists" -\layout Standard +\end_layout +\begin_layout Standard La version de la bibliothèque est importante s'il vous manque certaines fonctionnalités. Vous pouvez l'obtenir en exécutant ce qui suit (ou d'une façon encore plus aisée en regardant le haut du fichier): -\layout Code +\end_layout +\begin_layout Code # source /etc/sysconfig/network-scripts/network-functions-ipv6 && -\layout Code +\end_layout +\begin_layout Code ¬ getversion_ipv6_functions -\layout Code +\end_layout +\begin_layout Code 20011124 -\layout Standard +\end_layout +\begin_layout Standard Dans l'exemple montré, la version utilisée est la -\series bold +\series bold 20011124 -\series default +\series default . Vérifiez cela par rapport à l'information la plus à jour sur la page \begin_inset LatexCommand \url[initscripts-ipv6]{http://www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[miroir]{http://mirrors.bieringer.de/www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ) afin de voir ce qui a changé. Vous y trouverez aussi un journal des modifications. -\layout Subsection +\end_layout +\begin_layout Subsection Quelques éléments pour rendre disponible IPv6 sur les actuelles RHL 7.1, 7.2, 7.3,... -\layout Itemize +\end_layout +\begin_layout Itemize Vérifiez si votre système a déjà le module IPv6 chargé -\layout Code +\end_layout +\begin_layout Code # modprobe -c | grep net-pf-10 -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 off -\layout Itemize +\end_layout +\begin_layout Itemize Si le résultat est \begin_inset Quotes sld -\end_inset +\end_inset off \begin_inset Quotes srd -\end_inset +\end_inset , alors rendez disponible la mise en réseau IPv6 en éditant /etc/sysconfig/netwo rk, ajoutez la nouvelle ligne -\layout Code +\end_layout +\begin_layout Code NETWORKING_IPV6=yes -\layout Itemize +\end_layout +\begin_layout Itemize Redémarrez la machine, ou simplement le réseau par -\layout Code +\end_layout +\begin_layout Code # service network restart -\layout Itemize +\end_layout +\begin_layout Itemize Maintenant le module IPv6 devrait être chargé -\layout Code +\end_layout +\begin_layout Code # modprobe -c | grep ipv6 -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 ipv6 -\layout Standard +\end_layout +\begin_layout Standard Si votre système est sur un lien fournissant l'annonce de routeur, la configurat ion sera réalisée automatiquement. Pour plus d'information sur les réglages supportées, voir /usr/share/doc/initsc ripts-$version/sysconfig.txt. -\layout Section +\end_layout +\begin_layout Section Linux SuSE -\layout Standard +\end_layout +\begin_layout Standard Dans les nouvelles versions, il n'y a véritablement qu'un support rudimentaire disponible, voir /etc/rc.config pour les détails. -\layout Standard +\end_layout +\begin_layout Standard A cause de sa configuration très différente et de la structure de ses scripts, il est difficile (voire impossible) d'utiliser le jeu d'outils de Linux Red Hat et de ses clones avec cette distribution. -\newline -Dans les versions 8.x, SuSE va complétement modifier l'installation de sa - configuration. +\newline +Dans les versions 8.x, SuSE + va complétement modifier l'installation de sa configuration. -\layout Subsection +\end_layout +\begin_layout Subsection Linux SuSE 7.3 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Comment installer IPv6 6to4 pour la SuSE 7.3]{http://www.feyrer.de/IPv6/SuSE73-IPv6+6to4-setup.html} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Linux SuSE 8.0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Configuration d'adresse IPv6 -\layout Standard +\end_layout +\begin_layout Standard Editez le fichier /etc/sysconfig/network/ifcfg- et fixez la valeur suivante -\layout Code +\end_layout +\begin_layout Code IP6ADDR="/" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Information supplémentaire -\layout Standard +\end_layout +\begin_layout Standard Voir le fichier /usr/share/doc/packages/sysconfig/README -\layout Subsection +\end_layout +\begin_layout Subsection Linux SuSE 8.1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Configuration d'adresse IPv6 -\layout Standard +\end_layout +\begin_layout Standard Editez le fichier /etc/sysconfig/network/ifcfg- et fixez la valeur suivante -\layout Code +\end_layout +\begin_layout Code IPADDR="/" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Information supplémentaire -\layout Standard +\end_layout +\begin_layout Standard Voir le fichier /usr/share/doc/packages/sysconfig/Network -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{Configuration-Debian-Linux} -\end_inset +\end_inset Linux Debian -\layout Standard +\end_layout +\begin_layout Standard Les informations qui suivent sont une contribution de Stéphane Bortzmeyer -\layout Enumerate +\end_layout +\begin_layout Enumerate Assurez-vous qu'IPv6 soit chargé; soit il est compilé dans le noyau, soit il est chargé comme module. Dans ce dernier cas, trois solutions, l'ajouter à /etc/modules, utiliser la configuration ci-dessous, ou utiliser kmod (non détaillé ici). -\layout Enumerate +\end_layout +\begin_layout Enumerate Configurez votre interface. Par exemple, ici, nous considérons la prise en compte de eth0, avec pour adresse \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:1234:5::1:1 \begin_inset Quotes srd -\end_inset +\end_inset . Editez /etc/network/interfaces : -\layout Code +\end_layout +\begin_layout Code iface eth0 inet6 static -\layout Code +\end_layout +\begin_layout Code pre-up modprobe ipv6 -\layout Code +\end_layout +\begin_layout Code address 3ffe:ffff:1234:5::1:1 -\layout Code +\end_layout +\begin_layout Code # Pour rendre complètement indisponible l'auto-configuration: -\layout Code +\end_layout +\begin_layout Code # up echo 0 > /proc/sys/net/ipv6/conf/all/autoconf -\layout Code +\end_layout +\begin_layout Code netmask 64 -\layout Code +\end_layout +\begin_layout Code # Le routeur est auto-configuré, et n'a pas d'adresse fixe. -\layout Code +\end_layout +\begin_layout Code # Il est déterminé comme par magie -\layout Code +\end_layout +\begin_layout Code # (/proc/sys/net/ipv6/conf/all/accept_ra). Sinon: -\layout Code +\end_layout +\begin_layout Code # gateway 3ffe:ffff:1234:5::1 -\layout Standard +\end_layout +\begin_layout Standard Puis vous rebootez, ou alors vous faites juste -\layout Code +\end_layout +\begin_layout Code # ifup --force eth0 -\layout Standard +\end_layout +\begin_layout Standard Et vous avez votre adresse statique. -\layout Subsection +\end_layout +\begin_layout Subsection Plus d'information -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 sur Linux Debian]{http://people.debian.org/~csmall/ipv6/} -\end_inset +\end_inset par Craig Small -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[HowTo pour Freenet6 & les utilisateurs Debian]{http://www.ruwenzori.net/ipv6/Jims_LAN_IPv6_global_connectivity_howto.html} -\end_inset +\end_inset de Jean-Marc Liotier (annoncé le 24.12.2002 sur \begin_inset LatexCommand \ref[la liste de diffusion]{information-maillists} -\end_inset +\end_inset users@ipv6.org ) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-autoconfiguration} -\end_inset +\end_inset L'auto-configuration et la mobilité -\layout Section +\end_layout +\begin_layout Section L'auto-configuration sans état -\layout Standard +\end_layout +\begin_layout Standard Est supportée et observée sur l'adresse lien-local assignée après le montage d'une interface sur laquelle IPv6 est disponible. -\layout Standard +\end_layout +\begin_layout Standard Exemple: -\layout Code +\end_layout +\begin_layout Code # ip -6 addr show dev eth0 scope link -\layout Code +\end_layout +\begin_layout Code 2: eth0: mtu 1500 qlen1000 -\layout Code +\end_layout +\begin_layout Code inet6 fe80::211:d8ff:fe6b:f0f5/64 scope link -\layout Code +\end_layout +\begin_layout Code valid_lft forever preferred_lft forever -\layout Section +\end_layout +\begin_layout Section L'auto-configuration avec état utilisant le Démon d'Annonce de Routeur -\layout Standard +\end_layout +\begin_layout Standard A compléter. Voir plus bas \begin_inset LatexCommand \ref[l'auto-configuration par le démon radvd]{hints-daemons-radvd} -\end_inset +\end_inset ( -\emph on +\emph on Router Advertisement Daemon -\emph default +\emph default ). -\layout Section +\end_layout +\begin_layout Section Le Protocole de Configuration Dynamique d'Hôte version 6 (DHCPv6) -\layout Standard +\end_layout +\begin_layout Standard Après de longues discussions concernant les difficultés, le \begin_inset LatexCommand \url[RFC 3315 / Dynamic Host Configuration Protocol for IPv6 (DHCPv6)]{http://www.faqs.org/rfcs/rfc3315.html} -\end_inset +\end_inset a finalement vu le jour. Au moment de la mise à jour de ce passage (10/2005), il existe deux implémentat ions: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Dibbler]{http://klub.com.pl/dhcpv6/} -\end_inset +\end_inset par Tomasz Mrugalski -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DHCPv6 chez Sourceforge]{http://dhcpv6.sourceforge.net/} -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section La mobilité -\layout Standard +\end_layout +\begin_layout Standard A compléter. -\layout Standard +\end_layout +\begin_layout Standard Pour le moment, voir \begin_inset LatexCommand \url[la page d'accueil sur la mobilité IPv6 sur Linux (MIPL)]{http://www.mipl.mediapoli.com/} -\end_inset +\end_inset pour plus de détails. Plus d'information peut être trouvée ici (merci de signaler les liens brisés): -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-oneill-mipv6-cao-??.txt / MIPv6 Care of Address Option]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-mccann-mobileip-80211fh-??.txt / Mobile IPv6 Fast Handovers for 802.11 Networks]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-haberman-ipv6-anycast-rr-??.txt / IPv6 Anycast Binding using Return Routability]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-mun-aaa-localkm-mobileipv6-??.txt / Localized Key Management for AAA in MobileIPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-thubert-nemo-ro-taxonomy-??.txt / Taxonomy of Route Optimization Models in the NEMO Context]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-le-aaa-diameter-mobileipv6-??.txt / Diameter Mobile IPv6 Application]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-wakikawa-manet-globalv6-??.txt / Global Connectivity for IPv6 Mobile Ad Hoc Networks]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ietf-mobileip-fast-mipv6-??.txt / Fast Handovers for Mobile IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ietf-mobileip-ipv6-??.txt / Mobility Support in IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ohnishi-mobileip-v6vpngateway-??.txt / Mobile IPv6 VPN using Gateway Home Agent]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ietf-mobileip-hmipv6-??.txt / Hierarchical MIPv6 mobility management (HMIPv6)]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-mkhalil-ipv6-fastra-??.txt / IPv6 Fast Router Advertisement]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-okazaki-mobileip-abk-??.txt / Securing MIPv6 Binding Updates Using Address Based Keys (ABKs)]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-vriz-mobileip-hbhlmap-??.txt / Hop-by-Hop Local Mobility Agents Probing for Mobile IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-thubert-nemo-reverse-routing-header-??.txt / IPv6 Reverse Routing Header and its application to Mobile Networks]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-ietf-mobileip-mipv6-ha-ipsec-??.txt / Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-suh-rmm-??.txt / Regional Mobile IPv6 mobility management]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-mccann-mobileip-ipv6mipv4-??.txt / IPv6 over Mobile IPv4]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-kempf-mobileip-fmipv6-sem-??.txt / Improving the Architectural Alignment for FMIPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-le-aaa-mipv6-requirements-??.txt / Mobile IPv6 Authentication, Authorization, and Accounting Requirements]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[draft-hwang-rohc-mipv6-??.txt / RObust Header Compression (ROHC): A Compression Profile for Mobile IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[LANCASTER MOBILE IPv6 PACKAGE]{http://www.cs-ipv6.lancs.ac.uk/ipv6/MobileIP/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Testbed for MIND project on IPv6]{http://gsyc.escet.urjc.es/Mobiquo/Mind/documentacion/MontajeMaquetaIPv6_en/MontajeMaquetaIPv6_en.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Mobile IPv6 Issue List]{http://www.piuha.net/~jarkko/publications/mipv6/MIPv6-Issues.html} -\end_inset +\end_inset -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-firewalling-security} -\end_inset +\end_inset Mettre en place le pare-feu -\layout Standard +\end_layout +\begin_layout Standard Mettre en place un pare-feu IPv6 est très important, tout spécialement si IPv6 est utilisé sur un intranet avec des adresses IPv6 globales. Car, à la différence des réseaux IPv4 où les hôtes internes courants sont protégés par l'usage d'adresses IPv4 privées comme défini par le \begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://www.faqs.org/rfcs/rfc1918.html} -\end_inset +\end_inset ou l'adressage IP privée automatique ( -\emph on +\emph on Automatic Private IP Addressin -\emph default +\emph default g, ou APIPA) \begin_inset LatexCommand \url[recherche Google "Microsoft + APIPA"]{http://www.google.com/search?q=apipa+microsoft} -\end_inset +\end_inset , en IPv6, les adresses globales sont normalement utilisées, et quelqu'un possédant une connectivité IPv6 peut atteindre tous les noeuds propres à un intranet disposant d'IPv6. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{firewalling-netfilter6} -\end_inset +\end_inset Mettre en place un pare-feu grâce à netfilter -\layout Standard +\end_layout +\begin_layout Standard La mise en place d'un pare-feu IPv6 est nativement supportée par les noyaux dont la version est supérieure à 2.4. Avec les anciennes versions inférieures à 2.2, vous pouvez seulement filtrer IPv6-in-IPv4 par le protocole 41. -\layout Standard +\end_layout +\begin_layout Standard Attention: il n'y a aucune garantie que les règles décrites ou les exemples fournis puissent protéger votre système! -\layout Standard +\end_layout +\begin_layout Standard Faites un audit de votre jeu de règles après son installation, voir \begin_inset LatexCommand \ref[l'audit de sécurité sur IPv6]{IPv6-security-auditing} -\end_inset +\end_inset pour en savoir plus. -\layout Standard +\end_layout +\begin_layout Standard Notez aussi que le projet USAGI finalise actuellement son travail sur la traque de connexion pour IPv6! Cela rendra la création de jeu de règles plus simple et plus sûre à l'avenir! -\layout Subsection +\end_layout +\begin_layout Subsection Plus d'information -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Le projet Netfilter]{http://www.netfilter.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[maillist archive of netfilter users]{https://lists.netfilter.org/mailman/listinfo/netfilter} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[maillist archive of netfilter developers]{https://lists.netfilter.org/mailman/listinfo/netfilter-devel} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Information non officielle concernant l'état de netfilter]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html#netfilter6 } -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section Préparation -\layout Subsection +\end_layout +\begin_layout Subsection Récupérer les sources -\layout Standard +\end_layout +\begin_layout Standard Récupérez les dernières sources du noyau: \begin_inset LatexCommand \url[http://www.kernel.org/]{http://www.kernel.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Récupérez le dernier paquetage d'iptables: -\layout Itemize +\end_layout +\begin_layout Itemize Les sources en archive tar (pour patcher le noyau): \begin_inset LatexCommand \url[http://www.netfilter.org/]{http://www.netfilter.org/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Les sources en RPM pour reconstruire les binaires (pour les systèmes RedHat): \begin_inset LatexCommand \url[ftp://ftp.redhat.com/redhat/linux/rawhide/SRPMS/SRPMS/]{ftp://ftp.redhat.com/redhat/linux/rawhide/SRPMS/SRPMS/} -\end_inset +\end_inset ou peut-être encore dans \begin_inset LatexCommand \url[http://www.netcore.fi/pekkas/linux/ipv6/ ]{http://www.netcore.fi/pekkas/linux/ipv6/ } -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Extraire les sources -\layout Standard +\end_layout +\begin_layout Standard Déplacez-vous dans le répertoire des sources: -\layout Code +\end_layout +\begin_layout Code # cd /chemin/vers/les/sources -\layout Standard +\end_layout +\begin_layout Standard Décompactez et renommez les sources du noyau -\layout Code +\end_layout +\begin_layout Code # tar z|jxf kernel-version.tar.gz|bz2 -\layout Code +\end_layout +\begin_layout Code # mv linux linux-version-iptables-version+IPv6 -\layout Standard +\end_layout +\begin_layout Standard Décompactez les sources d'iptables -\layout Code +\end_layout +\begin_layout Code # tar z|jxf iptables-version.tar.gz|bz2 -\layout Subsection +\end_layout +\begin_layout Subsection Appliquer les derniers patchs relatifs à iptables/IPv6 aux sources du noyau -\layout Standard +\end_layout +\begin_layout Standard Déplacez-vous dans le répertoire iptables -\layout Code +\end_layout +\begin_layout Code # cd iptables-version -\layout Standard +\end_layout +\begin_layout Standard Appliquez les patchs en attente -\layout Code +\end_layout +\begin_layout Code # make pending-patches KERNEL_DIR=/chemin/vers/les/sources/linux-version-iptable s-version+IPv6/ -\layout Standard +\end_layout +\begin_layout Standard Appliquez les patchs additionnels relatifs à IPv6 (pas encore inclus dans le noyau vanille) -\layout Code +\end_layout +\begin_layout Code # make patch-o-matic KERNEL_DIR=/path/to/src/linux-version-iptables-version/ -\layout Standard +\end_layout +\begin_layout Standard Répondez par l'affirmative aux options suivantes (iptables-1.2.2) -\layout Itemize +\end_layout +\begin_layout Itemize ah-esp.patch -\layout Itemize +\end_layout +\begin_layout Itemize masq-dynaddr.patch (nécessaire seulement sur les systèmes ayant une adresse IP dynamique à la connexion au WAN, comme pour PPP ou PPPoE) -\layout Itemize +\end_layout +\begin_layout Itemize ipv6-agr.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize ipv6-ports.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize LOG.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize REJECT.patch.ipv6 -\layout Standard +\end_layout +\begin_layout Standard Vérifier la présence des extensions IPv6 -\layout Code +\end_layout +\begin_layout Code # make print-extensions -\layout Code +\end_layout +\begin_layout Code Extensions found: IPv6:owner IPv6:limit IPv6:mac IPv6:multiport -\layout Subsection +\end_layout +\begin_layout Subsection Configurer, construire et installer un nouveau noyau -\layout Standard +\end_layout +\begin_layout Standard Déplacez-vous dans les sources du noyau -\layout Code +\end_layout +\begin_layout Code # cd /chemin/vers/les/sources/linux-version-iptables-version/ -\layout Standard +\end_layout +\begin_layout Standard Editez Makefile -\layout Code +\end_layout +\begin_layout Code - EXTRAVERSION = -\layout Code +\end_layout +\begin_layout Code + EXTRAVERSION = -iptables-version+IPv6-try -\layout Standard +\end_layout +\begin_layout Standard Lancez configure, avec IPv6 de disponible -\layout Code +\end_layout +\begin_layout Code Code maturity level options -\layout Code +\end_layout +\begin_layout Code Prompt for development and/or incomplete code/drivers : yes -\layout Code +\end_layout +\begin_layout Code Networking options -\layout Code +\end_layout +\begin_layout Code Network packet filtering: yes -\layout Code +\end_layout +\begin_layout Code The IPv6 protocol: module -\layout Code +\end_layout +\begin_layout Code IPv6: Netfilter Configuration -\layout Code +\end_layout +\begin_layout Code IP6 tables support: module -\layout Code +\end_layout +\begin_layout Code All new options like following: -\layout Code +\end_layout +\begin_layout Code limit match support: module -\layout Code +\end_layout +\begin_layout Code MAC address match support: module -\layout Code +\end_layout +\begin_layout Code Multiple port match support: module -\layout Code +\end_layout +\begin_layout Code Owner match support: module -\layout Code +\end_layout +\begin_layout Code netfilter MARK match support: module -\layout Code +\end_layout +\begin_layout Code Aggregated address check: module -\layout Code +\end_layout +\begin_layout Code Packet filtering: module -\layout Code +\end_layout +\begin_layout Code REJECT target support: module -\layout Code +\end_layout +\begin_layout Code LOG target support: module -\layout Code +\end_layout +\begin_layout Code Packet mangling: module -\layout Code +\end_layout +\begin_layout Code MARK target support: module -\layout Standard +\end_layout +\begin_layout Standard Configurez aussi tout ce qui concerne votre système -\layout Standard +\end_layout +\begin_layout Standard Compilez et installez: voir ici même la section noyau et autres HOWTO -\layout Subsection +\end_layout +\begin_layout Subsection Reconstruire et installer les binaires d'iptables -\layout Standard +\end_layout +\begin_layout Standard Assurez-vous que l'arborescence des sources du noyau existe aussi dans /usr/src/ linux/ -\layout Standard +\end_layout +\begin_layout Standard Renommez l'ancien répertoire -\layout Code +\end_layout +\begin_layout Code # mv /usr/src/linux /usr/src/linux.old -\layout Standard +\end_layout +\begin_layout Standard Créez un nouveau lien symbolique -\layout Code +\end_layout +\begin_layout Code # ln -s /chemin/vers/src/linux-version-iptables-version /usr/src/linux -\layout Standard +\end_layout +\begin_layout Standard Reconstruisez le SRPM -\layout Code +\end_layout +\begin_layout Code # rpm --rebuild /chemin/vers/SRPM/iptables-version-release.src.rpm -\layout Standard +\end_layout +\begin_layout Standard Installez les nouveaux paquetages iptables (iptables + iptables-ipv6) -\layout Itemize +\end_layout +\begin_layout Itemize Sur les systèmes RH 7.1, normalement, une ancienne version est installée, en conséquence utiliser "freshen" -\layout Code +\end_layout +\begin_layout Code # rpm -Fhv /chemin/vers/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Itemize +\end_layout +\begin_layout Itemize Si elle n'était pas installée, utiliser "install" -\layout Code +\end_layout +\begin_layout Code # rpm -ihv /chemin/vers/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Itemize +\end_layout +\begin_layout Itemize Sur les systèmes RH 6.2, normalement, aucun noyau 2.4.x n'est installé, conséquemme nt les pré-requis ne correspondent pas. Utiliser "--nodeps" pour l'installer -\layout Code +\end_layout +\begin_layout Code # rpm -ihv --nodeps /chemin/vers/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Standard +\end_layout +\begin_layout Standard Il sera peut-être nécessaire de créer un lien symbolique vers le lieu où les bibliothèques iptables sont -\layout Code +\end_layout +\begin_layout Code # ln -s /lib/iptables/ /usr/lib/iptables -\layout Section +\end_layout +\begin_layout Section Utilisation -\layout Subsection +\end_layout +\begin_layout Subsection Vérifier le support -\layout Standard +\end_layout +\begin_layout Standard Chargez le module, s'il est compilé -\layout Code +\end_layout +\begin_layout Code # modprobe ip6_tables -\layout Standard +\end_layout +\begin_layout Standard Vérifiez si le noyau courant prend en charge iptables -\layout Code +\end_layout +\begin_layout Code # [ ! -f /proc/net/ip6_tables_names ] && echo "Current kernel doesn't support -\layout Code +\end_layout +\begin_layout Code ¬ 'ip6tables' firewalling (IPv6)!" -\layout Subsection +\end_layout +\begin_layout Subsection Apprendre à utiliser ip6tables -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Lister toutes les entrées netfilter IPv6 -\layout Itemize +\end_layout +\begin_layout Itemize de façon abrégée -\layout Code +\end_layout +\begin_layout Code # ip6tables -L -\layout Itemize +\end_layout +\begin_layout Itemize de façon détaillée -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v --line-numbers -L -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Lister un filtre spécifique -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v --line-numbers -L INPUT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Insérer une règle de journal au filtre entrant, avec des options -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --append INPUT -j LOG --log-prefix "INPUT:" -\layout Code +\end_layout +\begin_layout Code ¬ --log-level 7 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Insérer une règle de destruction ( -\emph on +\emph on drop rule -\emph default +\emph default ) au filtre entrant -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --append INPUT -j DROP -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Détruire une règle par son numéro -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --delete INPUT 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Autoriser ICMPv6 -\layout Standard +\end_layout +\begin_layout Standard Avec les plus anciens noyaux (noyau non patché 2.4.5 et iptables-1.2.2), aucun type ne peut être spécifié -\layout Itemize +\end_layout +\begin_layout Itemize Accepter le trafic ICMPv6 entrant dans les tunnels -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -i sit+ -p icmpv6 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Autoriser le trafic ICMPv6 sortant des tunnels -\layout Code +\end_layout +\begin_layout Code # ip6tables -A OUTPUT -o sit+ -p icmpv6 -j ACCEPT -\layout Standard +\end_layout +\begin_layout Standard Les nouveaux noyaux permettent de spécifier les types ICMPv6: -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -p icmpv6 --icmpv6-type echo-request -j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La limitation du débit -\layout Standard +\end_layout +\begin_layout Standard Il peut arriver (l'auteur l'a déjà vu) qu'un engorgement ICMPv6 se produise, c'est pourquoi vous devriez utiliser la limitation de débit, puisqu'elle est disponible, et ce, au moins pour le jeu de règles ICMPv6. @@ -8144,1384 +9958,1707 @@ Il peut arriver (l'auteur l'a d pour garder trace d'attaques DoS, grâce à syslog et au stockage des fichiers de log. Un exemple de limitation du débit ICMPv6 ressemble à ceci: -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT --protocol icmpv6 --icmpv6-type echo-request -\layout Code +\end_layout +\begin_layout Code ¬ -j ACCEPT --match limit --limit 30/minute -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Permettre le trafic entrant SSH -\layout Standard +\end_layout +\begin_layout Standard Ici l'exemple montré est un jeu de règles permettant les connexions entrantes SSH par une adresse IPv6 donnée -\layout Itemize +\end_layout +\begin_layout Itemize Autoriser le trafic entrant SSH provenant de 3ffe:ffff:100::1/128 -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -i sit+ -p tcp -s 3ffe:ffff:100::1/128 --sport 512:65535 -\layout Code +\end_layout +\begin_layout Code ¬ --dport 22 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Autoriser les paquets réponse (pour le moment, la traque du trafic IPv6 n'est pas au coeur de l'implémentation de netfilter) -\layout Code +\end_layout +\begin_layout Code # ip6tables -A OUTPUT -o sit+ -p tcp -d 3ffe:ffff:100::1/128 --dport 512:65535 -\layout Code +\end_layout +\begin_layout Code ¬ --sport 22 ! --syn j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Rendre disponible le trafic tunnelé IPv6-in-IPv4 -\layout Standard +\end_layout +\begin_layout Standard Pour accepter les paquets tunnelés IPv6-in-IPv4, vous devez insérer des règles dans votre -\series bold +\series bold installation de pare-feu IPv4 -\series default +\series default relatives à de tels paquets, pour exemple -\layout Itemize +\end_layout +\begin_layout Itemize Accepter le trafic entrant IPv6-in-IPv4 sur l'interface ppp0 -\layout Code +\end_layout +\begin_layout Code # iptables -A INPUT -i ppp0 -p ipv6 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Permettre au trafic IPv6-in-IPv4 de sortir par l'interface ppp0 -\layout Code +\end_layout +\begin_layout Code # iptables -A OUTPUT -o ppp0 -p ipv6 -j ACCEPT -\layout Standard +\end_layout +\begin_layout Standard Si vous avez seulement un tunnel statique, vous pouvez aussi spécifier l'adresse IPv4, comme ici -\layout Itemize +\end_layout +\begin_layout Itemize Accepter le trafic entrant IPv6-in-IPv4 sur l'interface ppp0 et provenant de l'extrémité du tunnel 1.2.3.4 -\layout Code +\end_layout +\begin_layout Code # iptables -A INPUT -i ppp0 -p ipv6 -s 1.2.3.4 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Autoriser le trafic sortant IPv6-in-IPv4 vers l'interface ppp0 pour l'extrémité du tunnel 1.2.3.4 -\layout Code +\end_layout +\begin_layout Code # iptables -A OUTPUT -o ppp0 -p ipv6 -d 1.2.3.4 -j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Protection contre les requêtes de connexion entrante TCP -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold TRÈS RECOMMANDÉ! -\series default +\series default Pour des questions de sécurité, vous devriez vraiment insérer une règle qui bloque les requêtes de connexion TCP entrante. Ajouter l'option "-i", si d'autres noms d'interface sont utilisés! -\layout Itemize +\end_layout +\begin_layout Itemize Bloquer les requêtes de connexion entrante TCP vers cet hôte -\layout Code +\end_layout +\begin_layout Code # ip6tables -I INPUT -i sit+ -p tcp --syn -j DROP -\layout Itemize +\end_layout +\begin_layout Itemize Bloquer les requêtes de connexion entrante TCP allant vers les hôtes placés derrière ce routeur -\layout Code +\end_layout +\begin_layout Code # ip6tables -I FORWARD -i sit+ -p tcp --syn -j DROP -\layout Standard +\end_layout +\begin_layout Standard Peut-être ces règles doivent-elles être placées sous d'autres, mais ça, c'est votre travail. La meilleure façon de faire est de créer un script et d'exécuter les règles d'une manière spécifique. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Protection contre les requêtes de connexion entrante UDP -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold TRÈS RECOMMANDÉ AUSSI! -\series default +\series default Comme il a été dit dans la section concernant la mise en place d'un pare-feu, il est possible de contrôler les ports des sessions sortantes UDP/TCP. Si tous vos systèmes IPv6 locaux utilisent les ports locaux, par exemple de 32768 à 60999, vous êtes aussi capables de filtrer les connexions UDP (jusqu'à ce que la traque des connexions fonctionnent) comme suit: -\layout Itemize +\end_layout +\begin_layout Itemize Bloquer les paquets entrants UDP qui ne peuvent être des réponses de requêtes sortantes de cet hôte -\layout Code +\end_layout +\begin_layout Code # ip6tables -I INPUT -i sit+ -p udp ! --dport 32768:60999 -j DROP -\layout Itemize +\end_layout +\begin_layout Itemize Bloquer les paquets entrants UDP qui ne peuvent être des réponses de requêtes d'hôtes placés derrière ce routeur, et transitant à travers lui -\layout Code +\end_layout +\begin_layout Code # ip6tables -I FORWARD -i sit+ -p udp ! --dport 32768:60999 -j DROP -\layout Subsection +\end_layout +\begin_layout Subsection Un exemple plus conséquent -\layout Standard +\end_layout +\begin_layout Standard Les lignes qui suivent montrent en exemple une installation plus sophistiquée. Bonne création de jeux de règles netfilter6... -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v -L -\layout Code +\end_layout +\begin_layout Code Chain INPUT (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code 0 0 extIN all sit+ * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 4 384 intIN all eth0 * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::1/128 ::1/128 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all lo * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `INPUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain FORWARD (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 int2ext all eth0 sit+ ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ext2int all sit+ eth0 ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `FORWARD-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain OUTPUT (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 extOUT all * sit+ ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 4 384 intOUT all * eth0 ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::1/128 ::1/128 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * lo ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `OUTPUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain ext2int (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1:65535 dpts:1024:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `ext2int-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain extIN (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * 3ffe:400:100::1/128 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:512:65535 dpt:22 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * 3ffe:400:100::2/128 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:512:65535 dpt:22 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1:65535 dpts:1024:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ udp spts:1:65535 dpts:1024:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ limit: avg 5/min burst 5 LOG flags 0 level 7 prefix `extIN-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain extOUT (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100::1/128tcp spt:22 dpts:512:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100::2/128tcp spt:22 dpts:512:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ udp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `extOUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain int2ext (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `int2ext:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `int2ext-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain intIN (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ fe80::/ffc0:: -\layout Code +\end_layout +\begin_layout Code 4 384 ACCEPT all * * ::/0 ff02::/16 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain intOUT (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ fe80::/ffc0:: -\layout Code +\end_layout +\begin_layout Code 4 384 ACCEPT all * * ::/0 ff02::/16 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `intOUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-security} -\end_inset +\end_inset La sécurité -\layout Section +\end_layout +\begin_layout Section La sécurité d'un noeud -\layout Standard +\end_layout +\begin_layout Standard Il est très recommandé d'appliquer tous les patchs disponibles, de rendre indisponibles tous les services inutiles, d'associer les services nécessaires aux adresses IPv4/IPv6 et d'installer un pare-feu local. -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant... -\layout Section +\end_layout +\begin_layout Section Les limitations d'accès -\layout Standard +\end_layout +\begin_layout Standard De nombreux services utilisent la bibliothèque tcp_wrapper pour contrôler l'accès. Plus bas est décrite \begin_inset LatexCommand \ref[l'utilisation de tcp_wrapper]{hints-daemons-tcpwrapper} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant... -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{IPv6-security-auditing} -\end_inset +\end_inset L'audit de sécurité IPv6 -\layout Standard +\end_layout +\begin_layout Standard Actuellement, il n'existe pas d'outil véritablement adéquate aux questions de sécurité IPv6 et capable de vérifier un système monté sur le réseau. Ni \begin_inset LatexCommand \url[Nessus]{http://www.nessus.org/} -\end_inset +\end_inset ni aucun autre scanner de sécurité provenant du commerce n'est capable, autant que je sache, de scanner les adresses IPv6. -\layout Subsection +\end_layout +\begin_layout Subsection Question d'ordre légal -\layout Standard +\end_layout +\begin_layout Standard ATTENTION: Prenez bien garde d'uniquement scanner vos propres systèmes, ou alors seulement après avoir reçu une autorisation écrite, sinon des problèmes d'ordre juridique risquent de vous arriver. -\newline -VERIFIER A DEUX FOIS les adresses IPv6 avant de lancer un scan. -\layout Subsection +\newline +VERIFIER A DEUX FOIS + les adresses IPv6 avant de lancer un scan. +\end_layout +\begin_layout Subsection Audit de sécurité par l'emploi de netcat disposant d'IPv6 -\layout Standard +\end_layout +\begin_layout Standard Avec netcat disposant d'IPv6 (voir \begin_inset LatexCommand \url[IPv6+Linux-status-apps/security-auditing]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#security-auditing} -\end_inset +\end_inset pour en savoir plus), vous pouvez lancer un scan de ports -\emph on +\emph on via -\emph default +\emph default un script qui balaiera un intervalle de ports, captera des bannières, -\emph on +\emph on etc -\emph default +\emph default . Un exemple d'utilisation: -\layout Code +\end_layout +\begin_layout Code # nc6 ::1 daytime -\layout Code +\end_layout +\begin_layout Code 13 JUL 2002 11:22:22 CEST -\layout Subsection +\end_layout +\begin_layout Subsection Audit de sécurité par l'emploi de nmap disposant d'IPv6 -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[NMap]{http://www.insecure.org/nmap/} -\end_inset +\end_inset , l'un des meilleurs scanners de ports à travers le monde, supporte IPv6 depuis la version 3.10ALPHA1. Un exemple d'utilisation: -\layout Code +\end_layout +\begin_layout Code # nmap -6 -sT ::1 -\layout Code +\end_layout +\begin_layout Code Starting nmap V. 3.10ALPHA3 ( www.insecure.org/nmap/ ) -\layout Code +\end_layout +\begin_layout Code Interesting ports on localhost6 (::1): -\layout Code +\end_layout +\begin_layout Code (The 1600 ports scanned but not shown below are in state: closed) -\layout Code +\end_layout +\begin_layout Code Port State Service -\layout Code +\end_layout +\begin_layout Code 22/tcp open ssh -\layout Code +\end_layout +\begin_layout Code 53/tcp open domain -\layout Code +\end_layout +\begin_layout Code 515/tcp open printer -\layout Code +\end_layout +\begin_layout Code 2401/tcp open cvspserver -\layout Code +\end_layout +\begin_layout Code Nmap run completed -- 1 IP address (1 host up) scanned in 0.525 seconds -\layout Subsection +\end_layout +\begin_layout Subsection Audit de sécurité par l'emploi de strobe disposant d'IPv6 -\layout Standard +\end_layout +\begin_layout Standard Strobe est (comparé à NMap) un scanner de ports pour les petits budgets, mais il y a un patch disponible pour le rendre prêt pour IPv6 (voir \begin_inset LatexCommand \url[IPv6+Linux-status-apps/security-auditing]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#security-auditing} -\end_inset +\end_inset pour plus d'information). Un exemple d'utilisation: -\layout Code +\end_layout +\begin_layout Code # ./strobe ::1 strobe 1.05 (c) 1995-1999 Julian Assange . -\layout Code +\end_layout +\begin_layout Code ::1 2401 unassigned unknown -\layout Code +\end_layout +\begin_layout Code ::1 22 ssh Secure Shell - RSA encrypted rsh -\layout Code +\end_layout +\begin_layout Code ::1 515 printer spooler (lpd) -\layout Code +\end_layout +\begin_layout Code ::1 6010 unassigned unknown -\layout Code +\end_layout +\begin_layout Code ::1 53 domain Domain Name Server -\layout Standard +\end_layout +\begin_layout Standard Note: strobe n'est plus véritablement en développement, le numéro de version montré n'est pas le bon. -\layout Subsection +\end_layout +\begin_layout Subsection Le résultat de l'audit -\layout Standard +\end_layout +\begin_layout Standard Si le résultat de l'audit ne correspond pas à votre politique de sécurité IPv6, mettez en place le pare-feu IPv6 pour combler les trous de sécurité, par exemple en utilisant netfilter6 (voir \begin_inset LatexCommand \ref[Mettre en place un pare-feu grâce à Netfilter6]{firewalling-netfilter6} -\end_inset +\end_inset pour plus de détails). -\layout Standard +\end_layout +\begin_layout Standard Info: une information plus détaillée concernant la sécurité IPv6 peut être trouvée ici: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Firewalling Considerations for IPv6 / draft-savola-v6ops-firewalling-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Neighbour Discovery trust models and threats]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Security Considerations for 6to4]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Access Control Prefix Router Advertisement Option for IPv6]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Requirements for Plug and Play IPsec for IPv6 applications]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Security of IPv6 Routing Header and Home Address Options]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-encryption-authentication} -\end_inset +\end_inset L'encryptage et l'authentification -\layout Standard +\end_layout +\begin_layout Standard A la différence d'IPv4, l'encryptage et l'authentification sont des fonctionnali tés que ne fournit pas IPv6 lui-même. Elles sont normalement implémentées par l'utilisation d'IPsec (qui peut également être employé par IPv4). -\layout Section +\end_layout +\begin_layout Section Les modes d'emploi de l'encryptage et de l'authentification -\layout Standard +\end_layout +\begin_layout Standard Deux modes d'encryptage et d'authentification sont possibles: -\layout Subsection +\end_layout +\begin_layout Subsection Le mode transport -\layout Standard +\end_layout +\begin_layout Standard Le mode transport est un mode de connexion réellement de bout-en-bout. Ici, seule la charge utile (généralement ICMP, TCP ou UDP) est encryptée avec son en-tête particulier, tandis que l'en-tête IP n'est pas encrypté (mais couramment inclus dans l'authentification). -\layout Standard +\end_layout +\begin_layout Standard Utilisant AES-128 pour l'encryptage et SHA1 pour l'authentification, ce mode diminue la MTU de 42 octets. -\layout Subsection +\end_layout +\begin_layout Subsection Le mode tunnel -\layout Standard +\end_layout +\begin_layout Standard Le mode tunnel peut être utilisé soit dans un mode de connexion de bout-en-bout soit dans un mode de connexion de passerelle-à-passerelle. Ici, le paquet IP complet est encrypté et prend un nouvel en-tête IP, le tout constituant un nouveau paquet (ce mécanisme étant connu sous le nom d'encapsulation). -\layout Standard +\end_layout +\begin_layout Standard Cependant, à cause de l'indépendance de l'encryptage et de l'authentification à l'égard du protocole d'échange de clés, il existe actuellement des problèmes d'interopérabilité. Ce mode diminue actuellement de 40 octets par rapport au mode transport. Utiliser AES-128 pour l'encryptage et SHA1 pour l'authentification diminue donc au total de 82 octets la MTU courante. -\layout Section +\end_layout +\begin_layout Section Son support dans le noyau (ESP et AH) -\layout Subsection +\end_layout +\begin_layout Subsection Son support dans les noyaux Linux vanille 2.4.x -\layout Standard +\end_layout +\begin_layout Standard Manquant à ce jour jusqu'au noyau 2.4.28 vanille, le problème était de garder les sources du noyau Linux éloignées des questions de contrôles légaux d'import/export concernant le code d'encryptage en général. C'est une des raisons pour lesquelles \begin_inset LatexCommand \url[le projet FreeS/WAN]{http://www.freeswan.org/} -\end_inset +\end_inset (IPsec pour IPv4 seulement) n'était pas compris dans les sources vanille. Un rétro-portage à partir de 2.6.x sera peut-être réalisé un jour. -\layout Subsection +\end_layout +\begin_layout Subsection Son support dans les noyaux Linux vanille 2.6.x -\layout Standard +\end_layout +\begin_layout Standard Les versions actuelles (2.6.9 et supérieures, au moment de la rédaction) supporten t nativement IPsec pour IPv4 et IPv6. -\layout Standard +\end_layout +\begin_layout Standard Le projet USAGI a aidé à l'implémentation. -\layout Section +\end_layout +\begin_layout Section Echange automatique de clés (IKE) -\layout Standard +\end_layout +\begin_layout Standard IPsec requière un échange de clés afin de partager un secret. Ceci est essentiellement réalisé de façon automatisée par les démons IKE. Ils prennent également en charge l'authentification des entités en présence, soit par un secret commun (nommé \begin_inset Quotes sld -\end_inset +\end_inset secret pré-partagé \begin_inset Quotes srd -\end_inset +\end_inset ), soit par clés RSA (qui peuvent provenir de certificats X.509). -\layout Standard +\end_layout +\begin_layout Standard Actuellement, deux démons IKE sont disponibles pour Linux, lesquels différent totalement par la configuration et l'emploi. -\layout Standard +\end_layout +\begin_layout Standard Je préfère \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset à l'implémentation *S/WAN à cause de son installation plus simple et à son unique fichier de configuration. -\layout Subsection +\end_layout +\begin_layout Subsection Le démon IKE \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Le démon IKE \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset provient du projet KAME et a été porté sur Linux. Les distributions contemporaines de Linux comportent ce démon dans le paquetage \begin_inset Quotes sld -\end_inset +\end_inset ipsec-tools \begin_inset Quotes srd -\end_inset +\end_inset . Deux exécutables sont requis pour bien installer IPsec. Jetez aussi un oeil à \begin_inset LatexCommand \url[Linux Advanced Routing & Traffic Control HOWTO / IPSEC]{http://lartc.org/howto/lartc.ipsec.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Manipulation de la base de données IPsec SA/SP grâce à l'outil \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Le rôle important de \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset est de définir la politique de sécurité ( -\emph on +\emph on SP -\emph default +\emph default , -\emph on +\emph on security policy -\emph default +\emph default ) pour le noyau. -\layout Standard +\end_layout +\begin_layout Standard Fichier: /etc/racoon/setkey.sh -\layout Itemize +\end_layout +\begin_layout Itemize Exemple d'une connexion encryptée de boute-en-bout en mode transport -\layout Code +\end_layout +\begin_layout Code #!/sbin/setkey -f -\layout Code +\end_layout +\begin_layout Code flush; -\layout Code +\end_layout +\begin_layout Code spdflush; -\layout Code +\end_layout +\begin_layout Code spdadd 2001:db8:1:1::1 2001:db8:2:2::2 any -P out ipsec esp/transport//require; -\layout Code +\end_layout +\begin_layout Code spdadd 2001:db8:2:2::2 2001:db8:1:1::1 any -P in ipsec esp/transport//require; -\layout Code +\end_layout -\layout Itemize +\begin_layout Code +\end_layout + +\begin_layout Itemize Exemple d'une connexion encryptée de boute-en-bout en mode tunnel -\layout Code +\end_layout +\begin_layout Code #!/sbin/setkey -f -\layout Code +\end_layout +\begin_layout Code flush; -\layout Code +\end_layout +\begin_layout Code spdflush; -\layout Code +\end_layout +\begin_layout Code spdadd 2001:db8:1:1::1 2001:db8:2:2::2 any -P out ipsec -\layout Code +\end_layout +\begin_layout Code ¬ esp/tunnel/2001:db8:1:1::1-2001:db8:2:2::2/require; -\layout Code +\end_layout +\begin_layout Code spdadd 2001:db8:2:2::2 2001:db8:1:1::1 any -P in ipsec -\layout Code +\end_layout +\begin_layout Code ¬ esp/tunnel/2001:db8:2:2::2-2001:db8:1:1::1/require; -\layout Standard +\end_layout +\begin_layout Standard Pour l'autre machine, vous avez juste à échanger \begin_inset Quotes sld -\end_inset +\end_inset in \begin_inset Quotes srd -\end_inset +\end_inset et \begin_inset Quotes sld -\end_inset +\end_inset out \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La configuration du démon IKE \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Pour sa bonne exécution, \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset requière d'être configuré. Ceci inclus les réglages relatifs à la politique de sécurité, qui doit être précédemment mise en place grâce à \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Fichier: /etc/racoon/racoon.conf -\layout Code +\end_layout +\begin_layout Code # Fichier de configuration du démon IKE racoon. -\layout Code +\end_layout +\begin_layout Code # Voir 'man racoon.conf' pour une description du format et des entrées. -\layout Code +\end_layout +\begin_layout Code path include "/etc/racoon"; -\layout Code +\end_layout +\begin_layout Code path pre_shared_key "/etc/racoon/psk.txt"; -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code listen -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code isakmp 2001:db8:1:1::1; -\layout Code +\end_layout +\begin_layout Code } -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code remote 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code exchange_mode main; -\layout Code +\end_layout +\begin_layout Code lifetime time 24 hour; -\layout Code +\end_layout +\begin_layout Code proposal -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code hash_algorithm md5; -\layout Code +\end_layout +\begin_layout Code authentication_method pre_shared_key; -\layout Code +\end_layout +\begin_layout Code dh_group 2; -\layout Code +\end_layout +\begin_layout Code } -\layout Code +\end_layout +\begin_layout Code } -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # De passerelle-à-passerelle -\layout Code +\end_layout +\begin_layout Code sainfo address 2001:db8:1:1::1 any address 2001:db8:2:2::2 any -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code lifetime time 1 hour; -\layout Code +\end_layout +\begin_layout Code encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code authentication_algorithm hmac_md5; -\layout Code +\end_layout +\begin_layout Code compression_algorithm deflate; -\layout Code +\end_layout +\begin_layout Code } -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code sainfo address 2001:db8:2:2::2 any address 2001:db8:1:1::1 any -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code lifetime time 1 hour; -\layout Code +\end_layout +\begin_layout Code encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code authentication_algorithm hmac_md5; -\layout Code +\end_layout +\begin_layout Code compression_algorithm deflate; -\layout Code +\end_layout +\begin_layout Code } -\layout Standard +\end_layout +\begin_layout Standard Fixez aussi un secret pré-partagé: -\layout Standard +\end_layout +\begin_layout Standard Fichier: /etc/racoon/psk.txt -\layout Code +\end_layout +\begin_layout Code # Fichier des clés pré-partagées utilisées pour l'authentification IKE -\layout Code +\end_layout +\begin_layout Code # Le format est: 'identificateur' 'clé' -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code 2001:db8:2:2::2 absolumentsecret -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Démarrer IPsec grâce au démon IKE \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Il faut pour le moins que le démon soit démarré. Au premier démarrage, utiliser les modes déboguage et premier plan ( -\emph on +\emph on debug and foreground -\emph default +\emph default ). L'exemple suivant montre une négociation IKE réussie dans ses phases 1 (ISAKMP-SA, -\emph on +\emph on Internet Security Association Key Management Security Association -\emph default +\emph default ) and 2 (IPsec-SA, -\emph on +\emph on IPsec -\emph default +\emph default -\emph on +\emph on Security Association -\emph default +\emph default ): -\layout Code +\end_layout +\begin_layout Code # racoon -F -v -f /etc/racoon/racoon.conf -\layout Code +\end_layout +\begin_layout Code Foreground mode. -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:30:15: INFO: @(#)ipsec-tools 0.3.3 (http://ipsec-tools.sourceforge.net ) -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:30:15: INFO: @(#)This product linked -\layout Code +\end_layout +\begin_layout Code ¬ OpenSSL 0.9.7a Feb 19 2003 (http://www.openssl.org/) -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:30:15: INFO: 2001:db8:1:1::1[500] used as isakmp port (fd=7) -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:06: INFO: IPsec-SA request for 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code ¬ queued due to no phase1 found. -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:06: INFO: initiate new phase 1 negotiation: -\layout Code +\end_layout +\begin_layout Code ¬ 2001:db8:1:1::1[500]<=>2001:db8:2:2::2[500] -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:06: INFO: begin Identity Protection mode. -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:09: INFO: ISAKMP-SA established -\layout Code +\end_layout +\begin_layout Code ¬ 2001:db8:1:1::1[500]-2001:db8:2:2::2[500] spi:da3d3693289c9698:ac039a402b2db40 1 -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:09: INFO: initiate new phase 2 negotiation: -\layout Code +\end_layout +\begin_layout Code ¬ 2001:6f8:900:94::2[0]<=>2001:db8:2:2::2[0] -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:10: INFO: IPsec-SA established: -\layout Code +\end_layout +\begin_layout Code ¬ ESP/Tunnel 2001:db8:2:2::2->2001:db8:1:1::1 spi=253935531(0xf22bfab) -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:10: INFO: IPsec-SA established: -\layout Code +\end_layout +\begin_layout Code ¬ ESP/Tunnel 2001:db8:1:1::1->2001:db8:2:2::2 spi=175002564(0xa6e53c4) -\layout Standard +\end_layout +\begin_layout Standard Chaque direction a sa propre IPsec-SA (comme définie dans le standard IPsec). Avec \begin_inset Quotes sld -\end_inset +\end_inset tcpdump \begin_inset Quotes srd -\end_inset +\end_inset à l'écoute de la bonne interface, vous devriez voir comme résultat d'un ping IPv6: -\layout Code +\end_layout +\begin_layout Code 20:35:55.305707 2001:db8:1:1::1 > 2001:db8:2:2::2: ESP(spi=0x0a6e53c4,seq=0x3) -\layout Code +\end_layout +\begin_layout Code 20:35:55.537522 2001:db8:2:2::2 > 2001:db8:1:1::1: ESP(spi=0x0f22bfab,seq=0x3) -\layout Standard +\end_layout +\begin_layout Standard Comme prévu, les SPI ( -\emph on +\emph on Security Parameter Index -\emph default +\emph default ) négociés sont utilisés ici. -\layout Standard +\end_layout +\begin_layout Standard Et en utilisant \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset , les paramètres actifs courants: -\layout Code +\end_layout +\begin_layout Code # setkey -D -\layout Code +\end_layout +\begin_layout Code 2001:db8:1:1::1 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code esp mode=tunnel spi=175002564(0x0a6e53c4) reqid=0(0x00000000) -\layout Code +\end_layout +\begin_layout Code E: 3des-cbc bd26bc45 aea0d249 ef9c6b89 7056080f 5d9fa49c 924e2edd -\layout Code +\end_layout +\begin_layout Code A: hmac-md5 60c2c505 517dd8b7 c9609128 a5efc2db -\layout Code +\end_layout +\begin_layout Code seq=0x00000000 replay=4 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code created: Jan 1 20:31:10 2005 current: Jan 1 20:40:47 2005 -\layout Code +\end_layout +\begin_layout Code diff: 577(s) hard: 3600(s) soft: 2880(s) -\layout Code +\end_layout +\begin_layout Code last: Jan 1 20:35:05 2005 hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code current: 540(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code allocated: 3 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code sadb_seq=1 pid=22358 refcnt=0 -\layout Code +\end_layout +\begin_layout Code 2001:db8:2:2::2 2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code esp mode=tunnel spi=253935531(0x0f22bfab) reqid=0(0x00000000) -\layout Code +\end_layout +\begin_layout Code E: 3des-cbc c1ddba65 83debd62 3f6683c1 20e747ac 933d203f 4777a7ce -\layout Code +\end_layout +\begin_layout Code A: hmac-md5 3f957db9 9adddc8c 44e5739d 3f53ca0e -\layout Code +\end_layout +\begin_layout Code seq=0x00000000 replay=4 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code created: Jan 1 20:31:10 2005 current: Jan 1 20:40:47 2005 -\layout Code +\end_layout +\begin_layout Code diff: 577(s) hard: 3600(s) soft: 2880(s) -\layout Code +\end_layout +\begin_layout Code last: Jan 1 20:35:05 2005 hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code current: 312(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code allocated: 3 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code sadb_seq=0 pid=22358 refcnt=0 -\layout Subsection +\end_layout +\begin_layout Subsection Le démon IKE \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Le démon IKE \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset est inclus dans les distributions des projets *S/WAN, qui ont pour origine \begin_inset LatexCommand \url[FreeS/WAN]{http://www.freeswan.org/} -\end_inset +\end_inset . Le développement du projet FreeS/WAN a malheureusement été stoppé en 2004. @@ -9529,803 +11666,1001 @@ pluto nt: \begin_inset LatexCommand \url[strongSwan]{http://www.strongswan.org/} -\end_inset +\end_inset et \begin_inset LatexCommand \url[Openswan]{http://www.openswan.org/} -\end_inset +\end_inset . Aujourd'hui, des paquetages d'installation sont disponibles, au moins pour Openswan (inclus dans Fedora Core 3). -\layout Standard +\end_layout +\begin_layout Standard Une différence importante par rapport à \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset , un seul et unique fichier de configuration est requis. Il y a bien sûr un script d'initialisation qui automatise le lancement au démarrage de la machine. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La configuration du démon IKE \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard La configuration est très similaire à celle nécessaire pour IPv4, à part une importante et nécessaire option. -\layout Standard +\end_layout +\begin_layout Standard Fichier: /etc/ipsec.conf -\layout Code +\end_layout +\begin_layout Code # /etc/ipsec.conf - Fichier de configuration d'IPsec Openswan -\layout Code +\end_layout +\begin_layout Code # -\layout Code +\end_layout +\begin_layout Code # Manuel: ipsec.conf.5 -\layout Code +\end_layout +\begin_layout Code version 2.0 # conforme à la seconde version de la spécification d'ipsec.conf -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # configuration de base -\layout Code +\end_layout +\begin_layout Code config setup -\layout Code +\end_layout +\begin_layout Code # Contrôles du déboguage / journalisation : "none" pour (presque) rien, "all" pour beaucoup. -\layout Code +\end_layout +\begin_layout Code # klipsdebug=none -\layout Code +\end_layout +\begin_layout Code # plutodebug="control parsing" -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code #Rendre indisponible l'encryptage opportuniste -\layout Code +\end_layout +\begin_layout Code include /etc/ipsec.d/examples/no_oe.conf -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code conn ipv6-p1-p2 -\layout Code +\end_layout +\begin_layout Code connaddrfamily=ipv6 # Important pour IPv6! -\layout Code +\end_layout +\begin_layout Code left=2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code right=2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code authby=secret -\layout Code +\end_layout +\begin_layout Code esp=aes128-sha1 -\layout Code +\end_layout +\begin_layout Code ike=aes128-sha-modp1024 -\layout Code +\end_layout +\begin_layout Code type=transport -\layout Code +\end_layout +\begin_layout Code #type=tunnel -\layout Code +\end_layout +\begin_layout Code compress=no -\layout Code +\end_layout +\begin_layout Code #compress=yes -\layout Code +\end_layout +\begin_layout Code auto=add -\layout Code +\end_layout +\begin_layout Code #auto=start -\layout Code +\end_layout -\layout Standard +\begin_layout Code +\end_layout + +\begin_layout Standard N'oubliez pas ici également de définir un secret pré-partagé. -\layout Standard +\end_layout +\begin_layout Standard Fichier: /etc/ipsec.secrets -\layout Code +\end_layout +\begin_layout Code 2001:db8:1:1::1 2001:db8:2:2::2 : PSK "absolumentsecret" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Démarrer IPsec grâce au démon IKE \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Si l'installation d'Openswan s'est achevée avec succès, un script d'initialisati on doit exister permettant le démarrage d'IPsec, lancez simplement (sur chaque machine) par: -\layout Code +\end_layout +\begin_layout Code # /etc/rc.d/init.d/ipsec start -\layout Standard +\end_layout +\begin_layout Standard Ensuite, démarrez une connexion sur l'une des machines. Si vous pouvez voir la ligne \begin_inset Quotes sld -\end_inset +\end_inset IPsec SA established \begin_inset Quotes srd -\end_inset +\end_inset , c'est que tout fonctionne parfaitement. -\layout Code +\end_layout +\begin_layout Code # ipsec auto --up ipv6-peer1-peer2 -\layout Code +\end_layout +\begin_layout Code 104 "ipv6-p1-p2" #1: STATE_MAIN_I1: initiate -\layout Code +\end_layout +\begin_layout Code 106 "ipv6-p1-p2" #1: STATE_MAIN_I2: sent MI2, expecting MR2 -\layout Code +\end_layout +\begin_layout Code 108 "ipv6-p1-p2" #1: STATE_MAIN_I3: sent MI3, expecting MR3 -\layout Code +\end_layout +\begin_layout Code 004 "ipv6-p1-p2" #1: STATE_MAIN_I4: ISAKMP SA established -\layout Code +\end_layout +\begin_layout Code 112 "ipv6-p1-p2" #2: STATE_QUICK_I1: initiate -\layout Code +\end_layout +\begin_layout Code 004 "ipv6-p1-p2" #2: STATE_QUICK_I2: sent QI2, -\layout Code +\end_layout +\begin_layout Code ¬ IPsec SA established {ESP=>0xa98b7710 <0xa51e1f22} -\layout Standard +\end_layout +\begin_layout Standard Parce que *S/WAN et setkey/racoon sont basés sur la même implémentation d'IPsec dans les noyaux 2.6.x, \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset peut être utilisé pour afficher les paramètres actifs courants: -\layout Code +\end_layout +\begin_layout Code # setkey -D -\layout Code +\end_layout +\begin_layout Code 2001:db8:1:1::1 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code esp mode=transport spi=2844489488(0xa98b7710) reqid=16385(0x00004001) -\layout Code +\end_layout +\begin_layout Code E: aes-cbc 082ee274 2744bae5 7451da37 1162b483 -\layout Code +\end_layout +\begin_layout Code A: hmac-sha1 b7803753 757417da 477b1c1a 64070455 ab79082c -\layout Code +\end_layout +\begin_layout Code seq=0x00000000 replay=64 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code created: Jan 1 21:16:32 2005 current: Jan 1 21:22:20 2005 -\layout Code +\end_layout +\begin_layout Code diff: 348(s) hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code last: hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code current: 0(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code allocated: 0 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code sadb_seq=1 pid=23825 refcnt=0 -\layout Code +\end_layout +\begin_layout Code 2001:db8:2:2::2 2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code esp mode=transport spi=2770214690(0xa51e1f22) reqid=16385(0x00004001) -\layout Code +\end_layout +\begin_layout Code E: aes-cbc 6f59cc30 8d856056 65e07b76 552cac18 -\layout Code +\end_layout +\begin_layout Code A: hmac-sha1 c7c7d82b abfca8b1 5440021f e0c3b335 975b508b -\layout Code +\end_layout +\begin_layout Code seq=0x00000000 replay=64 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code created: Jan 1 21:16:31 2005 current: Jan 1 21:22:20 2005 -\layout Code +\end_layout +\begin_layout Code diff: 349(s) hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code last: hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code current: 0(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code allocated: 0 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code sadb_seq=0 pid=23825 refcnt=0 -\layout Section +\end_layout +\begin_layout Section Informations complémentaires -\layout Standard +\end_layout +\begin_layout Standard Pour les noyaux Linux 2.6.x, vous pouvez également obtenir la politique et l'état d'IPsec en utilisant \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset : -\layout Code +\end_layout +\begin_layout Code # ip xfrm policy -\layout Code +\end_layout +\begin_layout Code ... -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # ip xfrm state -\layout Code +\end_layout +\begin_layout Code ... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-qos} -\end_inset +\end_inset La Qualité de Service (QoS) -\layout Standard +\end_layout +\begin_layout Standard IPv6 supporte QoS par l'utilisation des labels de flux et des classes de trafic. Ceci peut être contrôlé en utilisant \begin_inset Quotes sld -\end_inset +\end_inset tc \begin_inset Quotes srd -\end_inset +\end_inset (compris dans le paquetage \begin_inset Quotes sld -\end_inset +\end_inset iproute \begin_inset Quotes srd -\end_inset +\end_inset ). -\layout Standard +\end_layout +\begin_layout Standard Information complémentaire: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[RFC 3697 / IPv6 Flow Label Specification]{http://www.faqs.org/rfcs/rfc3697.html} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-hints-daemons} -\end_inset +\end_inset Eléments d'installation des démons prêts pour IPv6 -\layout Standard +\end_layout +\begin_layout Standard Ici quelques éléments d'installation des démons prêts pour IPv6 sont exposés. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-bind} -\end_inset +\end_inset Le Démon de Nom Internet Berkeley (named) -\layout Standard +\end_layout +\begin_layout Standard IPv6 est supporté depuis la version 9. Utilisez toujours la dernière version disponible. Il faut au moins utiliser la version 9, les versions plus anciennes peuvent contenir des trous de sécurité exploitables à distance. -\layout Subsection +\end_layout +\begin_layout Subsection A l'écoute des adresses IPv6 -\layout Standard +\end_layout +\begin_layout Standard Note: à la différence d'IPv4, les versions actuelles ne permettent pas d'associe r une socket de serveur à des adresses IPv6 données, par conséquent, seule l'alternative -\emph on +\emph on toutes -\emph default +\emph default ou -\emph on +\emph on aucune -\emph default +\emph default adresse(s) IPv6 est valide. Parce que cela peut poser un problème de sécurité, consultez aussi plus bas la section concernant la liste de contrôle d'accès (ACL)! -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Rendre disponible l'écoute sur adresse IPv6 -\layout Standard +\end_layout +\begin_layout Standard Pour rendre disponible à named l'écoute IPv6, les options suivantes demandent à être modifiées -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # certainement que d'autres options sont aussi ici -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { any; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Il doit en résulter après redémarrage -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu |grep "named -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::53 :::* LISTEN 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming TCP requests -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.4:53 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP requests to IPv4 1.2.3.4 -\layout Code +\end_layout +\begin_layout Code udp 0 0 127.0.0.1:53 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP requests to IPv4 localhost -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32868 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # dynamic chosen port for outgoing queries -\layout Code +\end_layout +\begin_layout Code udp 0 0 :::53 :::* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP request to any IPv6 -\layout Standard +\end_layout +\begin_layout Standard Un test simple ressemble à -\layout Code +\end_layout +\begin_layout Code # dig localhost @::1 -\layout Standard +\end_layout +\begin_layout Standard et doit vous afficher un résultat. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Rendre indisponible l'écoute sur adresse IPv6 -\layout Standard +\end_layout +\begin_layout Standard Pour rendre indisponible l'écoute IPv6, l'option suivante demande à être modifiée -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # certainement que d'autres options sont aussi ici -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { none; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Subsection +\end_layout +\begin_layout Subsection Les Listes de Contrôle d'Accès IPv6 (ACL) -\layout Standard +\end_layout +\begin_layout Standard Les ACL IPv6 sont disponibles et devraient être utilisées dès que possible. Un exemple ressemble à ce qui suit: -\layout Code +\end_layout +\begin_layout Code acl internal-net { -\layout Code +\end_layout +\begin_layout Code 127.0.0.1; -\layout Code +\end_layout +\begin_layout Code 1.2.3.0/24; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::/56; -\layout Code +\end_layout +\begin_layout Code ::1/128; -\layout Code +\end_layout +\begin_layout Code ::ffff:1.2.3.4/128; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code acl ns-internal-net { -\layout Code +\end_layout +\begin_layout Code 1.2.3.4; -\layout Code +\end_layout +\begin_layout Code 1.2.3.5; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::4/128; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::5/128; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Ces ACL peuvent être utilisées par exemple pour les requêtes des clients ou pour le transfert de zones aux serveurs de noms de domaine secondaires. Ceci prévient aussi contre l'utilisation de votre serveur cache de noms de domaine à partir de l'extérieur grâce à IPv6. -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # certainement que d'autres options sont aussi ici -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { none; }; -\layout Code +\end_layout +\begin_layout Code allow-query { internal-net; }; -\layout Code +\end_layout +\begin_layout Code allow-transfer { ns-internal-net; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Il est aussi possible de positionner les options -\emph on +\emph on allow-query -\emph default +\emph default et -\emph on +\emph on allow-transfer -\emph default +\emph default pour la plupart des définitions par fichier de zone. -\layout Subsection +\end_layout +\begin_layout Subsection Emettre des requêtes avec une adresse IPv6 dédiée -\layout Standard +\end_layout +\begin_layout Standard Cette option n'est pas requise, mais peut être nécessaire: -\layout Code +\end_layout +\begin_layout Code query-source-v6 address port ; -\layout Subsection +\end_layout +\begin_layout Subsection Adresses IPv6 dédiées définies par zone -\layout Standard +\end_layout +\begin_layout Standard Il est aussi possible de définir des adresses IPv6 par zone. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Adresse de la source de transfert -\layout Standard +\end_layout +\begin_layout Standard L'adresse de la source de transfert est utilisée pour aller chercher les zones transférées: -\layout Code +\end_layout +\begin_layout Code transfer-source-v6 [port port]; -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Adresse de la source à notifier -\layout Standard +\end_layout +\begin_layout Standard L'adresse de la source à notifier est utilisée pour les messages de notification : -\layout Code +\end_layout +\begin_layout Code notify-source-v6 [port port]; -\layout Subsection +\end_layout +\begin_layout Subsection Des exemples de fichiers de zone DNS IPv6 -\layout Standard +\end_layout +\begin_layout Standard Des informations peuvent être aussi trouvées dans cet article concernant l' \begin_inset LatexCommand \url[information d'installation d'un DNS IPv6]{http://www.isi.edu/~bmanning/v6DNS.html} -\end_inset +\end_inset . Le \begin_inset LatexCommand \url[constructeur de zone inverse IPv6 pour BIND 8/9 (outil web)]{http://tools.fpsn.net/ipv6-inaddr/} -\end_inset +\end_inset peut aussi être d'une aide précieuse. -\layout Subsection +\end_layout +\begin_layout Subsection Servir des données DNS relatives à IPv6 -\layout Standard +\end_layout +\begin_layout Standard Pour IPv6, de nouveaux types et la zone racine nécessaire à la recherche inversée sont définis: -\layout Itemize +\end_layout +\begin_layout Itemize AAAA et IP6.INT inversée: specifiés dans le \begin_inset LatexCommand \url[RFC 1886 / DNS Extensions to support IP version 6]{http://www.faqs.org/rfcs/rfc1886.html} -\end_inset +\end_inset , utilisés depuis BIND version 4.9.6 -\layout Itemize +\end_layout +\begin_layout Itemize A6, DNAME (DORÉNAVANT DÉPRECIÉ!) et IP6.ARPA inversé: spécifiés dans le \begin_inset LatexCommand \url[RFC 2874 / DNS Extensions to Support IPv6 Address Aggregation and Renumbering]{http://www.faqs.org/rfcs/rfc2874.html} -\end_inset +\end_inset , utilisable depuis BIND 9, mais vous pouvez trouver de l'information sur l'état actuel dans \begin_inset LatexCommand \url[draft-ietf-dnsext-ipv6-addresses-00.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Peut-être complété plus tard, pour le moment, jetez un coup d'oeil aux RFC fournis et -\layout Itemize +\end_layout +\begin_layout Itemize AAAA et IP6.INT inversé: \begin_inset LatexCommand \url[l'installation d'un DNS IPv6]{http://www.isi.edu/~bmanning/v6DNS.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize A6, DNAME (DORÉNAVANT DÉPRECIÉ!) et IP6.ARPA inversé: jetez un coup d'oeil aux chapitres 4 et 6 du manuel de référence de l'administrateur BIND 9 (ARM), distributé avec le paquetage bind, ou bien récupérez-le : \begin_inset LatexCommand \url[BIND version 9 ARM (PDF)]{http://www.nominum.com/content/documents/bind9arm.pdf} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Parce que IP6.INT est déprécié (mais encore en usage), un serveur DNS qui supportera l'information IPv6 aura à servir tous les types de zones inversées. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La meilleure pratique courante -\layout Standard +\end_layout +\begin_layout Standard Parce qu'il y a encore quelques problèmes qui existent lorsque les nouveaux formats sont utilisés, la meilleure pratique courante est: -\layout Standard +\end_layout +\begin_layout Standard Support de recherche: -\layout Itemize +\end_layout +\begin_layout Itemize AAAA -\layout Standard +\end_layout +\begin_layout Standard La recherche inversée supporte: -\layout Itemize +\end_layout +\begin_layout Itemize Le format réduit inversé ( -\emph on +\emph on reverse nibble format -\emph default +\emph default ) pour la zone ip6.int (POUR LA COMPATIBILITÉ ASCENDANTE) -\layout Itemize +\end_layout +\begin_layout Itemize Le format réduit inversé ( -\emph on +\emph on reverse nibble format -\emph default +\emph default ) pour la zone ip6.arpa (RECOMMANDÉ) -\layout Subsection +\end_layout +\begin_layout Subsection Vérifier la connectivité IPv6 -\layout Standard +\end_layout +\begin_layout Standard Pour vérifier si BIND est à l'écoute sur une socket IPv6 et sert des données, voir les exemples suivants. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Connecté -\emph on +\emph on via -\emph default +\emph default IPv6, mais refusé par les ACL -\layout Standard +\end_layout +\begin_layout Standard En spécifiant un serveur pour les requêtes, une connexion IPv6 peut être forcée: -\layout Code +\end_layout +\begin_layout Code $ host -t aaaa www.6bone.net 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Using domain server: -\layout Code +\end_layout +\begin_layout Code Name: 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Address: 3ffe:ffff:200:f101::1#53 -\layout Code +\end_layout +\begin_layout Code Aliases: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code Host www.6bone.net. not found: 5(REFUSED) -\layout Standard +\end_layout +\begin_layout Standard L'entrée relative dans le journal ressemble à ce qui suit: -\layout Code +\end_layout +\begin_layout Code Jan 3 12:43:32 gate named[12347]: client -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:200:f101:212:34ff:fe12:3456#32770: -\layout Code +\end_layout +\begin_layout Code query denied -\layout Standard +\end_layout +\begin_layout Standard Si vous observez de telles entrées dans le journal, vérifiez si les requêtes provenant de ce client doivent être autorisées, pour revoir, si nécessaire, votre configuration ACL. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une connexion IPv6 réussie -\layout Standard +\end_layout +\begin_layout Standard Une connexion IPv6 réussie ressemble à ce qui suit: -\layout Code +\end_layout +\begin_layout Code $ host -t aaaa www.6bone.net 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Using domain server: -\layout Code +\end_layout +\begin_layout Code Name: 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Address: 3ffe:ffff:200:f101::1#53 -\layout Code +\end_layout +\begin_layout Code Aliases: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code www.6bone.net. is an alias for 6bone.net. -\layout Code +\end_layout +\begin_layout Code 6bone.net. has AAAA address 3ffe:b00:c18:1::10 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-xinetd} -\end_inset +\end_inset Le super démon Internet (xinetd) -\layout Standard +\end_layout +\begin_layout Standard IPv6 est supporté, approximativement, depuis la version 1.8.9 de \begin_inset LatexCommand \url[xinetd]{http://www.xinetd.org/} -\end_inset +\end_inset . Utilisez toujours la version disponible la plus récente. Seules les versions antérieures à la version 2.3.3 doivent être utilisées, les versions plus anciennes peuvent contenir des trous de sécurité exploitables à distance. -\layout Standard +\end_layout +\begin_layout Standard Certaines distributions Linux contiennent un paquetage supplémentaire pour xinetd prêt pour IPv6, d'autres démarrent xinetd prêt pour IPv6 si la variable suivante est positionnée: NETWORKING_IPV6="yes", chose normalement réalisée @@ -10333,1415 +12668,1665 @@ Certaines distributions Linux contiennent un paquetage suppl Hat et ses dérivées). Dans les nouvelles livraisons des distributions, un binaire supporte à la fois IPv4 et IPv6. -\layout Standard +\end_layout +\begin_layout Standard Si vous rendez disponible un service fourni avec xinetd, comme par exemple daytime, en modifiant la configuration dans le fichier /etc/xinetd.d/daytime comme suit -\layout Code +\end_layout +\begin_layout Code # diff -u /etc/xinetd.d/daytime.orig /etc/xinetd.d/daytime -\layout Code +\end_layout +\begin_layout Code --- /etc/xinetd.d/daytime.orig Sun Dec 16 19:00:14 2001 -\layout Code +\end_layout +\begin_layout Code +++ /etc/xinetd.d/daytime Sun Dec 16 19:00:22 2001 -\layout Code +\end_layout +\begin_layout Code @@ -10,5 +10,5 @@ -\layout Code +\end_layout +\begin_layout Code protocol = tcp -\layout Code +\end_layout +\begin_layout Code user = root -\layout Code +\end_layout +\begin_layout Code wait = no -\layout Code +\end_layout +\begin_layout Code - disable = yes -\layout Code +\end_layout +\begin_layout Code + disable = no -\layout Code +\end_layout +\begin_layout Code } -\layout Standard +\end_layout +\begin_layout Standard vous devriez recevoir, après le redémarrage de xinetd, une réponse positive telle que: -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu -A inet6 |grep "xinetd*" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:192.168.1.1:993 :::* LISTEN 12345/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::13 :::* LISTEN 12345/xinetd-ipv6 <- service -\layout Code +\end_layout +\begin_layout Code ¬ daytime/tcp -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:192.168.1.1:143 :::* LISTEN 12345/xinetd-ipv6 -\layout Standard +\end_layout +\begin_layout Standard L'exemple montre aussi que xinetd écoute pour IMAP et IMAP-SSL sur IPv4 seulement. -\layout Standard +\end_layout +\begin_layout Standard Note: un serveur xinetd uniquement IPv4 ne démarrera pas sur un noeud disposant d'IPv6 et inversement, un serveur xinetd IPv6 ne démarrera pas sur un noeud uniquement IPv4. Ce problème est réputé réglé dans les versions postérieures, au moins à partir de la version 2.3.11. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-apache2} -\end_inset +\end_inset Le serveur web Apache2 (httpd2) -\layout Standard +\end_layout +\begin_layout Standard Le serveur web Apache supporte nativement IPv6 depuis la version 2.0.14. Des patchs disponibles pour l'ancienne série 1.3.x ne sont pas courants et ne devraient pas être employés dans un contexte public, mais ils sont disponibl es sur ce serveur ftp, \begin_inset LatexCommand \url[KAME / Misc]{ftp://ftp.kame.net/pub/kame/misc/} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection A l'écoute sur les adresses IPv6 -\layout Standard +\end_layout +\begin_layout Standard Note: Les hôtes virtuels sur adresses IPv6 ne fonctionnent pas pour les versions inférieures à la 2.0.28 (un patch est disponible pour la 2.0.28). Mais en tout premier lieu, récupérez toujours la dernière version disponible, parce que les premières versions ont des problèmes de sécurité. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Un hôte virtuel écoute sur une adresse IPv6 uniquement -\layout Code +\end_layout +\begin_layout Code Listen [3ffe:ffff:100::1]:80 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code ServerName ipv6seul.votredomaine.votretld -\layout Code +\end_layout +\begin_layout Code # certainement des lignes de configuration en plus... -\layout Code +\end_layout +\begin_layout Code -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Un hôte virtuel écoute sur une adresse IPv6 et sur une adresse IPv4 -\layout Code +\end_layout +\begin_layout Code Listen [3ffe:ffff:100::2]:80 -\layout Code +\end_layout +\begin_layout Code Listen 1.2.3.4:80 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code ServerName ipv6etipv4.votredomaine.votretld -\layout Code +\end_layout +\begin_layout Code # certainement des lignes de configuration en plus... -\layout Code +\end_layout +\begin_layout Code -\layout Standard +\end_layout +\begin_layout Standard Il devrait en résulter après redémarrage -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu | grep "httpd2 -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.4:80 0.0.0.0:* LISTEN 12345/httpd2 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 3ffe:ffff:100::1:80 :::* LISTEN 12345/httpd2 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 3ffe:ffff:100::2:80 :::* LISTEN 12345/httpd2 -\layout Standard +\end_layout +\begin_layout Standard Pour de simples tests, utiliser l'exemple telnet déjà montré. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Note additionnelle -\layout Itemize +\end_layout +\begin_layout Itemize D'une part, Apache2 supporte une méthode appelée \begin_inset Quotes sld -\end_inset +\end_inset sendfile \begin_inset Quotes srd -\end_inset +\end_inset , accélérant la fourniture des données. D'autre part, certains pilotes de NIC supportent la vérification différée des sommes de contrôle ( -\emph on +\emph on offline checksumming -\emph default +\emph default ). Dans certains cas, cela peut conduire à des problèmes de connexion et invalider les sommes de contrôle TCP. Il faut alors rendre indisponible \begin_inset Quotes sld -\end_inset +\end_inset sendfile \begin_inset Quotes srd -\end_inset +\end_inset , ou bien en recompilant par l'utilisation de l'option de configure \begin_inset Quotes sld -\end_inset +\end_inset --without-sendfile \begin_inset Quotes srd -\end_inset +\end_inset , ou bien en utilisant la directive du fichier de configuration "EnableSendfile off". -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-radvd} -\end_inset +\end_inset Le Démon d'Annonce de Routeur (radvd) -\layout Standard +\end_layout +\begin_layout Standard Le Démon d'Annonce de Routeur est très utile sur un LAN, à partir du moment où les clients doivent être auto-configurés. Le démon lui-même doit tourner sur la passerelle par défaut IPv6 Linux (il n'est pas requis qu'elle soit aussi la passerelle IPv4, aussi prenez garde à qui émet des annonces de routeur sur votre LAN). -\layout Standard +\end_layout +\begin_layout Standard Vous avez à spécifier certaines informations et drapeaux qui doivent être compris dans l'annonce. Les plus employés sont -\layout Itemize +\end_layout +\begin_layout Itemize Le préfixe (nécessaire) -\layout Itemize +\end_layout +\begin_layout Itemize La durée de vie du préfixe -\layout Itemize +\end_layout +\begin_layout Itemize La fréquence des envois d'annonce (optionnelle) -\layout Standard +\end_layout +\begin_layout Standard Après une configuration convenable, le démon émet des annonces au travers des interfaces spécifiées, dans l'espoir que les clients les reçoivent et auto-configurent comme par magie leurs adresses avec le préfixe reçu et le routeur par défaut. -\layout Subsection +\end_layout +\begin_layout Subsection Configurer radvd -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Configuration simple -\layout Standard +\end_layout +\begin_layout Standard Le fichier de configuration de radvd est généralement /etc/radvd.conf. Un exemple simple ressemble à ce qui suit: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code AdvSendAdvert on; -\layout Code +\end_layout +\begin_layout Code MinRtrAdvInterval 3; -\layout Code +\end_layout +\begin_layout Code MaxRtrAdvInterval 10; -\layout Code +\end_layout +\begin_layout Code prefix 3ffe:ffff:0100:f101::/64 { -\layout Code +\end_layout +\begin_layout Code AdvOnLink on; -\layout Code +\end_layout +\begin_layout Code AdvAutonomous on; -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr on; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Ce qui a pour résultat côté client -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show eth0 -\layout Code +\end_layout +\begin_layout Code 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 -\layout Code +\end_layout +\begin_layout Code inet6 3ffe:ffff:100:f101:2e0:12ff:fe34:1234/64 scope global dynamic -\layout Code +\end_layout +\begin_layout Code valid_lft 2591992sec preferred_lft 604792sec -\layout Code +\end_layout +\begin_layout Code inet6 fe80::2e0:12ff:fe34:1234/10 scope link -\layout Standard +\end_layout +\begin_layout Standard Parce qu'aucune limite de vie n'a été définie, une très grande valeur est utilisée. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Configuration spéciale 6to4 -\layout Standard +\end_layout +\begin_layout Standard Les versions à partir de la 0.6.2pl3 supportent la (ré)génération des préfixes dépendant d'une adresse IPv4 propre à une interface spécifique. Ceci peut être utilisé afin de distribuer les annonces dans un LAN après que le tunnelage 6to4 ait changé. Surtout employé derrière un routeur de connexion dynamique à la demande ( -\emph on +\emph on dial-on-demand -\emph default +\emph default ). Avec l'assurance d'un temps de vie très bref pour un tel préfixe (après chaque reconnexion -\emph on +\emph on , dial-up -\emph default +\emph default , un autre préfixe est valide), la durée de vie est configurée aux valeurs minimales: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code AdvSendAdvert on; -\layout Code +\end_layout +\begin_layout Code MinRtrAdvInterval 3; -\layout Code +\end_layout +\begin_layout Code MaxRtrAdvInterval 10; -\layout Code +\end_layout +\begin_layout Code prefix 0:0:0:f101::/64 { -\layout Code +\end_layout +\begin_layout Code AdvOnLink off; -\layout Code +\end_layout +\begin_layout Code AdvAutonomous on; -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr on; -\layout Code +\end_layout +\begin_layout Code Base6to4Interface ppp0; -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime 20; -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime 30; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard Il en résulte pour le client situé à l'intérieur (en considérant que ppp0 a actuellement 1.2.3.4 comme adresse IPv4 locale): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show eth0 -\layout Code +\end_layout +\begin_layout Code 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 -\layout Code +\end_layout +\begin_layout Code inet6 2002:0102:0304 -\series bold +\series bold : -\series default +\series default f101:2e0:12ff:fe34:1234/64 scope global dynamic -\layout Code +\end_layout +\begin_layout Code valid_lft 22sec preferred_lft 12sec -\layout Code +\end_layout +\begin_layout Code inet6 fe80::2e0:12ff:fe34:1234/10 scope link -\layout Standard +\end_layout +\begin_layout Standard Parce qu'un bref temps de vie a été défini, un tel préfixe sera rapidement jeté si aucune annonce s'y rapportant n'est reçue. -\layout Standard +\end_layout +\begin_layout Standard Note additionnelle: si vous n'utilisez pas de support spécifique 6to4 dans les scripts d'initialisation, vous avez à mettre en place une route spécifique sur l'interface interne du routeur, sinon vous aurez des problèmes de routage retour. En ce qui concerne l'exemple ci-après: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2002:0102:0304 -\series bold +\series bold : -\series default +\series default f101::/64 dev eth0 metric 1 -\layout Standard +\end_layout +\begin_layout Standard Cette route a besoin d'être remplacée chaque fois que le préfixe change, ce qui est le cas à chaque fois qu'une nouvelle adresse IPv4 est assignée à une interface numérotée automatiquement ( -\emph on +\emph on dial-up interface -\emph default +\emph default ). -\layout Subsection +\end_layout +\begin_layout Subsection Le déboguage -\layout Standard +\end_layout +\begin_layout Standard Un programme appelé \begin_inset Quotes sld -\end_inset +\end_inset radvdump \begin_inset Quotes srd -\end_inset +\end_inset peut vous aider à observer les annonces émises ou reçues. Simple à utiliser: -\layout Code +\end_layout +\begin_layout Code # radvdump -\layout Code +\end_layout +\begin_layout Code Router advertisement from fe80::280:c8ff:feb9:cef9 (hoplimit 255) -\layout Code +\end_layout +\begin_layout Code AdvCurHopLimit: 64 -\layout Code +\end_layout +\begin_layout Code AdvManagedFlag: off -\layout Code +\end_layout +\begin_layout Code AdvOtherConfigFlag: off -\layout Code +\end_layout +\begin_layout Code AdvHomeAgentFlag: off -\layout Code +\end_layout +\begin_layout Code AdvReachableTime: 0 -\layout Code +\end_layout +\begin_layout Code AdvRetransTimer: 0 -\layout Code +\end_layout +\begin_layout Code Prefix 2002:0102:0304:f101::/64 -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime: 30 -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime: 20 -\layout Code +\end_layout +\begin_layout Code AdvOnLink: off -\layout Code +\end_layout +\begin_layout Code AdvAutonomous: on -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr: on -\layout Code +\end_layout +\begin_layout Code Prefix 3ffe:ffff:100:f101::/64 -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime: 2592000 -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime: 604800 -\layout Code +\end_layout +\begin_layout Code AdvOnLink: on -\layout Code +\end_layout +\begin_layout Code AdvAutonomous: on -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr: on -\layout Code +\end_layout +\begin_layout Code AdvSourceLLAddress: 00 80 12 34 56 78 -\layout Standard +\end_layout +\begin_layout Standard Cette sortie vous montre que chaque paquetage d'annonce se présente dans un format lisible. Vous devriez voir à nouveau ici vos valeurs configurées, sinon, ce n'est peut-être pas votre radvd qui émet l'annonce... vérifiez s'il n'y a pas un autre routeur sur le lien (pour traquer ce routeur, prenez l'adresse LL, AdvSourceLLAddress, qui est son adresse MAC). -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-dhcpv6} -\end_inset +\end_inset Le serveur de Configuration Dynamique d'Hôte v6 (dhcp6s) -\layout Standard +\end_layout +\begin_layout Standard DHCPv6 peut être utilisé pour réaliser des configurations avec état. Le démon par lui-même n'a pas nécessairement à tourner sur la passerelle routeur Linux par défaut. -\layout Standard +\end_layout +\begin_layout Standard Vous pouvez spécifier plus d'information qu'avec radvd. Il est plus similaire à un serveur DHCP IPv4. -\layout Standard +\end_layout +\begin_layout Standard Après une configuration correcte, le démon réagit lors de la réception de paquets multicast envoyés par un client à l'adresse ff02::16. -\layout Subsection +\end_layout +\begin_layout Subsection La configuration du serveur DHCPv6 (dhcp6s) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une configuration simple -\layout Standard +\end_layout +\begin_layout Standard Le fichier de configuration de dhcp6s est normalement /etc/dhcp6s.conf. Un exemple simple ressemble à ce qui suit: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code server-preference 255; -\layout Code +\end_layout +\begin_layout Code renew-time 60; -\layout Code +\end_layout +\begin_layout Code rebind-time 90; -\layout Code +\end_layout +\begin_layout Code prefer-life-time 130; -\layout Code +\end_layout +\begin_layout Code valid-life-time 200; -\layout Code +\end_layout +\begin_layout Code allow rapid-commit; -\layout Code +\end_layout +\begin_layout Code option dns_servers 2001:db8:0:f101::1 sub.domain.example; -\layout Code +\end_layout +\begin_layout Code link AAA { -\layout Code +\end_layout +\begin_layout Code range 2001:db8:0:f101::1000 to 2001:db8:0:f101::ffff/64; -\layout Code +\end_layout +\begin_layout Code prefix 2001:db8:0:f101::/64; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Subsection +\end_layout +\begin_layout Subsection La configuration du client DHCPv6 (dhcp6c) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Une configuration simple -\layout Standard +\end_layout +\begin_layout Standard Le fichier de configuration de dhcp6c est normalement /etc/dhcp6c.conf. Un exemple simple ressemble à ce qui suit: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code send rapid-commit; -\layout Code +\end_layout +\begin_layout Code request domain-name-servers; -\layout Code +\end_layout +\begin_layout Code }; -\layout Subsection +\end_layout +\begin_layout Subsection Usage -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dhcpv6_server -\layout Standard +\end_layout +\begin_layout Standard Démarrage du serveur, -\layout Code +\end_layout +\begin_layout Code # service dhcp6s start -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dhcpv6_client -\layout Standard +\end_layout +\begin_layout Standard Démarrage du client en premier plan, -\layout Code +\end_layout +\begin_layout Code # dhcp6c -f eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Déboguage -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dhcpv6_server -\layout Standard +\end_layout +\begin_layout Standard Le serveur a un drapeau pour passer en premier plan et deux pour le déboguage (tout deux devraient être utilisés pour le déboguage). Voici un exemple: -\layout Code +\end_layout +\begin_layout Code # dhcp6c -d -D -f eth0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dhcpv6_client -\layout Standard +\end_layout +\begin_layout Standard Le client a un drapeau pour passer en premier plan et deux pour le déboguage. Voici un exemple: -\layout Code +\end_layout +\begin_layout Code # dhcp6c -d -f eth0 -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:16 dhcpv6 doesn't support hardware type 776 -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:16 doesn't support sit0 address family 0 -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:16 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:16 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 status code for this address is: success -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 status code: success -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 assigned address 2001:db8:0:f101::1002 prefix len isnot in any RAs prefix length using 64 bit instead -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 renew time 60, rebind time 9 -\layout Standard +\end_layout +\begin_layout Standard Notez que les messages d'erreur n'ont aucun impact. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-tcpwrapper} -\end_inset +\end_inset tcp_wrapper -\layout Standard +\end_layout +\begin_layout Standard tcp_wrapper est une bibliothèque qui peut vous aider à protéger vos services contre les usages abusifs. -\layout Subsection +\end_layout +\begin_layout Subsection Les capacités de filtrage -\layout Standard +\end_layout +\begin_layout Standard Vous pouvez utiliser tcp_wrapper pour -\layout Itemize +\end_layout +\begin_layout Itemize Le filtrage à partir des adresses source (IPv4 ou IPv6) -\layout Itemize +\end_layout +\begin_layout Itemize Le filtrage des utilisateurs (réclame un démon ident en état de fonctionnement sur le client) -\layout Subsection +\end_layout +\begin_layout Subsection Les programmes utilisant tcp_wrapper -\layout Standard +\end_layout +\begin_layout Standard Les suivants sont connus: -\layout Itemize +\end_layout +\begin_layout Itemize Chaque service appelé par xinetd (si xinetd est compilé en utilisant la bibliothèque tcp_wrapper) -\layout Itemize +\end_layout +\begin_layout Itemize sshd (si compilé en utilisant tcp_wrapper) -\layout Subsection +\end_layout +\begin_layout Subsection Utilisation -\layout Standard +\end_layout +\begin_layout Standard tcp_wrapper est contrôlé par deux fichiers nommés /etc/hosts.allow et /etc/hosts.d eny. Pour plus d'information voir -\layout Code +\end_layout +\begin_layout Code $ man hosts.allow -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Exemple de fichier /etc/hosts.allow -\layout Standard +\end_layout +\begin_layout Standard Dans ce fichier, chaque service qui doit être positivement filtré ( -\emph on +\emph on i.e., -\emph default +\emph default dont les connexions doivent être acceptées) a besoin d'une ligne. -\layout Code +\end_layout +\begin_layout Code sshd: 1.2.3. [3ffe:ffff:100:200::]/64 -\layout Code +\end_layout +\begin_layout Code daytime-stream: 1.2.3. [3ffe:ffff:100:200::]/64 -\layout Standard +\end_layout +\begin_layout Standard Note: ils existent des implémentations cassées qui utilisent la mauvaise description réseau IPv6 suivante: [3ffe:ffff:100:200::/64]. -\layout Standard +\end_layout +\begin_layout Standard Heureusement, de telles versions seront rapidement corrigées. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Exemple de fichier /etc/hosts.deny -\layout Standard +\end_layout +\begin_layout Standard Ce fichier contient toutes les entrées de filtre négative et devrait dénier l'accès à tout le reste en utilisant -\layout Code +\end_layout +\begin_layout Code ALL: ALL -\layout Standard +\end_layout +\begin_layout Standard Si ce noeud est très sensible, vous pouvez remplacer la ligne stantard ci-dessus par celle-ci, mais cela peut être cause d'attaque DoS (charge de serveur de courrier et répertoire spool), si trop de connexions sont réalisées en un temps très bref. Peut-être un observateur de journaux ( -\emph on +\emph on a logwatch -\emph default +\emph default ) serait-il meilleur dans de tels cas. -\layout Code +\end_layout +\begin_layout Code ALL: ALL: spawn (echo "Attempt from %h %a to %d at `date`" -\layout Code +\end_layout +\begin_layout Code | tee -a /var/log/tcp.deny.log | mail root@localhost) -\layout Subsection +\end_layout +\begin_layout Subsection La journalisation -\layout Standard +\end_layout +\begin_layout Standard Selon l'entrée du fichier de configuration du démon syslog /etc/syslog.conf, la journalisation de tcp_wrapper se fait normalement dans /var/log/secure. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Connexion refusée -\layout Standard +\end_layout +\begin_layout Standard Une connexion refusée -\emph on +\emph on via -\emph default +\emph default IPv4 au service daytime, couvert par xinetd, produit des lignes telles que celles de l'exemple suivant -\layout Code +\end_layout +\begin_layout Code Jan 2 20:40:44 gate xinetd-ipv6[12346]: FAIL: daytime-stream libwrap -\layout Code +\end_layout +\begin_layout Code ¬ from=::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:32:06 gate xinetd-ipv6[12346]: FAIL: daytime-stream libwrap -\layout Code +\end_layout +\begin_layout Code from=3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Standard +\end_layout +\begin_layout Standard Une connexion refusée -\emph on +\emph on via -\emph default +\emph default IPv4 à sshd en double écoute produit des lignes telles que celles de l'exemple suivant -\layout Code +\end_layout +\begin_layout Code Jan 2 20:24:17 gate sshd[12345]: refused connect from ::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code ¬ (::ffff:1.2.3.4) -\layout Code +\end_layout +\begin_layout Code Jan 2 20:39:33 gate sshd[12345]: refused connect -\layout Code +\end_layout +\begin_layout Code from 3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Code +\end_layout +\begin_layout Code ¬ (3ffe:ffff:100:200::212:34ff:fe12:3456) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Connexion autorisée -\layout Standard +\end_layout +\begin_layout Standard Une connexion autorisée -\emph on +\emph on via -\emph default +\emph default IPv4 vers le service daytime, couvert par xinetd, produit des lignes telles que celles de l'exemple suivant -\layout Code +\end_layout +\begin_layout Code Jan 2 20:37:50 gate xinetd-ipv6[12346]: START: daytime-stream pid=0 -\layout Code +\end_layout +\begin_layout Code ¬ from=::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:37:56 gate xinetd-ipv6[12346]: START: daytime-stream pid=0 -\layout Code +\end_layout +\begin_layout Code from=3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Standard +\end_layout +\begin_layout Standard Une connexion autorisée -\emph on +\emph on via -\emph default +\emph default IPv4 vers sshd en double écoute produit des lignes telles que celles de l'exemple suivant -\layout Code +\end_layout +\begin_layout Code Jan 2 20:43:10 gate sshd[21975]: Accepted password for user from ::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code ¬ port 33381 ssh2 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:42:19 gate sshd[12345]: Accepted password for user -\layout Code +\end_layout +\begin_layout Code from 3ffe:ffff:100:200::212:34ff:fe12:3456 port 33380 ssh2 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-vsftpd} -\end_inset +\end_inset vsftpd -\layout Subsection +\end_layout +\begin_layout Subsection A l'écoute des adresses IPv6 -\layout Standard +\end_layout +\begin_layout Standard Editer le fichier de configuration, couramment /etc/vsftpd/vsftpd.conf, et ajuster l'option \begin_inset Quotes sld -\end_inset +\end_inset listen \begin_inset Quotes srd -\end_inset +\end_inset -\layout Code +\end_layout +\begin_layout Code listen_ipv6=yes -\layout Standard +\end_layout +\begin_layout Standard C'est tout. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-proftpd} -\end_inset +\end_inset proftpd -\layout Subsection +\end_layout +\begin_layout Subsection A l'écoute des adresses IPv6 -\layout Standard +\end_layout +\begin_layout Standard Editer le fichier de configuration, couramment /etc/proftpd.conf, mais prenez garde, tout n'est pas tout à fait logique dans la mise en place des hôtes virtuels -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code ... -\layout Code +\end_layout +\begin_layout Code Bind 2001:0DB8::1 -\layout Code +\end_layout +\begin_layout Code ... -\layout Code +\end_layout +\begin_layout Code -\layout Standard +\end_layout +\begin_layout Standard C'est tout. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-others} -\end_inset +\end_inset Autres démons -\layout Standard +\end_layout +\begin_layout Standard De nos jours c'est généralement simple, cherchez une ligne de commande d'option ou bien une valeur de configuration pour rendre disponible l'écoute IPv6. Cherchez dans la page du manuel du démon ou dans les FAQ concernées. Il peut arriver que vous ne puissiez lier le démon qu'à une adresse IPv6 \begin_inset Quotes sld -\end_inset +\end_inset any \begin_inset Quotes srd -\end_inset +\end_inset (::) et pas à une adresse IPv6 précise, par manque de support (ça dépend de la façon dont le développeur à implémenter...). -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-programming-using-API} -\end_inset +\end_inset Programmer (en utilisant l'API) -\layout Standard +\end_layout +\begin_layout Standard Je n'ai aucune expérience de la programmation IPv6, peut-être que ce chapitre sera rempli par d'autres, ou déplacé vers un autre HOWTO -\layout Standard +\end_layout +\begin_layout Standard Plus d'information peut être trouvée ici: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[RFC 2553 / Basic Socket Interface Extensions for IPv6]{http://www.faqs.org/rfcs/rfc2553.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Draft / Advanced Sockets API for IPv6 / draft-ietf-ipngwg-rfc2292bis-XY.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard \lang ngerman - \begin_inset LatexCommand \url[Porting applications to IPv6 HowTo]{http://jungla.dit.upm.es/~ecastro/IPv6-web/} -\end_inset +\end_inset by Eva M. Castro -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-interoperability} -\end_inset +\end_inset L'interopérabilité -\layout Standard +\end_layout +\begin_layout Standard Il y a à travers le monde quelques projets qui vérifient l'interopérabilité des différents systèmes d'exploitation vis-à-vis de l'implémentation des fonctionnalités d'IPv6: Voici un URL: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Le projet TAHI]{http://www.tahi.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard D'autres arriveront prochainement... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-information} -\end_inset +\end_inset Plus d'information et d'URL -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-books} -\end_inset +\end_inset Livres en édition papier, articles, revues en ligne (mélangés) -\layout Subsection +\end_layout +\begin_layout Subsection Livres édités (en anglais) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Cisco -\layout Itemize +\end_layout +\begin_layout Itemize Cisco Self-Study: \begin_inset LatexCommand \url[Implementing IPv6 Networks (IPV6)]{http://www.amazon.com/exec/obidos/tg/detail/-/1587050862/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset , par Regis Desmeules. Cisco Press; ISBN 1587050862; 500 pages; 1ère édition (11 avril 11 2003). -\newline -Note: cet ouvrage sera publié le 11 avril 2003. -\layout Itemize - +\newline +Note: + cet ouvrage sera publié le 11 avril 2003. +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Configuring IPv6 with Cisco IOS]{http://www.amazon.com/exec/obidos/tg/detail/-/1928994849/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset , par Sam Brown, Sam Browne, Neal Chen, Robbie Harrell, Edgar, Jr. Parenti (Editeur), Eric Knipp (Editeur), Paul Fong (Editeur) 362 pages; Syngress Media Inc; ISBN 1928994849; (12 juillet 2002). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Généraux -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Essentials]{http://www.sunny.ch/publications/f_ipv6.htm} -\end_inset +\end_inset par Silvia Hagen, juillet 2002, O'Reilly, \begin_inset LatexCommand \url[référence pour la commande: 1258]{http://www.oreilly.com/catalog/ipv6ess/} -\end_inset +\end_inset , ISBN 0-5960-0125-8, 352 pages. -\newline +\newline \begin_inset LatexCommand \url[Table des matières, index, exemple de chapitre, etc.]{http://www.oreilly.com/catalog/ipv6ess/} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[Les derniers livres sortis chez O'Reilly]{http://press.oreilly.com/ipv6ess.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize IPv6: The New Internet Protocol. Par Christian Huitema; Publié chez Prentice-Hall; ISBN 0138505055. -\newline -Description: Ce livre, écrit par Christian Huitema - membre du Comité Architectu -re Internet ( -\emph on +\newline +Description: Ce livre, écrit par Christian Huitema - membre du Comité Architect +ure Internet ( +\emph on Internet Architecture Board -\emph default +\emph default , ou IAB), offre une excellente description d'IPv6, de ses différences d'avec IPv4, du comment et du pourquoi de son développement. -\newline +\newline Source: \begin_inset LatexCommand \url[http://www.cs.uu.nl/wais/html/na-dir/internet/tcp-ip/resource-list.html]{http://www.cs.uu.nl/wais/html/na-dir/internet/tcp-ip/resource-list.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Networks]{http://www.epinions.com/book_mu-3402412/display_~full_specs} -\end_inset +\end_inset par Niles, Kitty; (ISBN 0070248079); 550 pages; Date de publication 05/01/1998. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Implementing IPV6. Supporting the Next Generation Internet Protocols]{http://www.amazon.com/exec/obidos/tg/detail/-/0764545892/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset par P. E. Miller, Mark A. Miller; éd. John Wiley & Sons; ISBN 0764545892; 2ème édition (15 mars 2000); 402 pages. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Big Book of Ipv6 Addressing Rfcs]{http://www.amazon.com/exec/obidos/tg/detail/-/0126167702/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset par Peter H. Salus (compilateur), Morgan Kaufmann Publishers, avril 2000, 450 pages, ISBN 0126167702. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Understanding IPV6]{http://www.epinions.com/book_mu-3922588/display_~full_specs} -\end_inset +\end_inset par Davies, Joseph; ISBN 0735612455; Date de publication 01/05/2001; 350 pages. -\newline +\newline \begin_inset LatexCommand \url[Understanding IPV6]{http://www.microsoft.com/MSPress/books/4883.asp} -\end_inset +\end_inset par Davies, Joseph; ISBN 0735612455; Date de publication 11/13/2002; 544 pages. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migrating to IPv6 - IPv6 in Practice]{http://www.amazon.com/exec/obidos/tg/detail/-/0471498920/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset . par Marc Blanchet; éd. John Wiley & Sons; ISBN 0471498920; 1ère édition (novembre 2002); 368 pages. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Ipv6 Network Programming]{http://www.amazon.com/exec/obidos/ASIN/1555583180/} -\end_inset +\end_inset par Jun-ichiro Hagino; ISBN 1555583180 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Wireless boosting IPv6]{http://www.nwfusion.com/news/2000/1023ipv6.html} -\end_inset +\end_inset par Carolyn Duffy Marsan, 23/10/2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[la recherche avec le mot clé IPv6 sur O'reilly réseau]{http://www.oreillynet.com/search/index.ncsp?sp-q=IPv6} -\end_inset +\end_inset donne 29 résultats (au 28 Janvier 2002). -\layout Subsection +\end_layout +\begin_layout Subsection Livres édités (en allemand) -\layout Itemize +\end_layout +\begin_layout Itemize Technik der IP-Netze (TCP/IP incl. IPv6) \begin_inset LatexCommand \url[bei Amazon.de]{http://www.amazon.de/exec/obidos/ASIN/3446215018/} -\end_inset +\end_inset -\newline +\newline Anatol Badach, Erwin Hoffmann -\newline -Carl Hanser Verlag München, Wien, 2001 ISBN 3-446-21501-8 -\newline +\newline +Carl Hanser Verlag München, Wien, 2001 ISBN + 3-446-21501-8 +\newline Kap. 6: Protokoll IPv6 S.205-242 -\newline +\newline Kap. 7: Plug&Play-Unterstützung bei IPv6 S.243-276 -\newline +\newline Kap. 8: Migration zum IPv6-Einsatz S.277-294 -\newline +\newline Kap. 9.3.4: RIP für das Protokoll IPv6 (RIPng) S.349-351 -\newline +\newline Kap. 9.4.6: OSPF für IPv6 S.384-385 -\newline +\newline Kommentar: tw. nicht ganz up-to-date bzw. nicht ganz fehlerfreie Abbildungen -\newline +\newline \begin_inset LatexCommand \url[Homepage des Buches und Tabelle mit Fixes]{http://www.fehcom.de/tipn/tipn.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Internet-Sicherheit (Browser, Firewalls und Verschlüsselung) \begin_inset LatexCommand \url[bei Amazon.de]{http://www.amazon.de/exec/obidos/ASIN/3446217258/} -\end_inset +\end_inset -\newline +\newline Kai Fuhrberg -\newline +\newline 2. akt. Auflage 2000 Carl Hanser Verlag München, Wien, ISBN 3-446-21333-3 -\newline +\newline Kap.2.3.1.4. IPv6 S.18-22 -\newline -Kurz angerissen werden: RFC 1825 - Security Association Konzept RFC1826 - - IP authentication Header RFC 1827 - IP Encapsulation Security Payload -\layout Itemize +\newline +Kurz angerissen werden: RFC 1825 - Security Association Konzept + RFC1826 - IP authentication Header RFC 1827 - IP Encapsulation Security + Payload +\end_layout +\begin_layout Itemize IPv6. Das neue Internet- Protokoll. Technik, Anwendung, Migration \begin_inset LatexCommand \url[bei Amazon]{http://www.amazon.de/exec/obidos/ASIN/389864149X} -\end_inset +\end_inset -\newline +\newline Hans Peter Dittler -\newline +\newline 2. akt. und erweiterte Auflage 2002 dpunkt.verlag, ISBN 3-89864-149-X -\layout Itemize +\end_layout +\begin_layout Itemize Das neue Internetprotokoll IPv6 \begin_inset LatexCommand \url[bei Amazon]{http://www.amazon.de/exec/obidos/ASIN/3446216855} -\end_inset +\end_inset -\newline +\newline Herbert Wiese -\newline +\newline 2002 Carl Hanser Verlag, ISBN 3446216855 -\layout Subsection +\end_layout +\begin_layout Subsection Articles, livres électroniques, revues en ligne (mélangés) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Getting Connected with 6to4]{http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html} -\end_inset +\end_inset par Huber Feyrer, 01/06/2001 -\layout Itemize +\end_layout +\begin_layout Itemize Transient Addressing for Related Processes: Improved Firewalling by Using IPv6 and Multiple Addresses per Host; écrit par Peter M. Gleiz, Steven M. Bellovin ( \begin_inset LatexCommand \url[version PDF pour PC]{http://www.securiteinfo.com/ebooks/pdf/tarp.pdf} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[version PDF pour Palm]{http://www.securiteinfo.com/ebooks/palm/tarp.pdf} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[version PDB]{http://www.securiteinfo.com/ebooks/pdb/tarp.pdb} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6, théorie et pratique]{http://www.oreilly.fr/catalogue/ipv6-3ed.html} -\end_inset +\end_inset (en français) 3ème édition, mars 2002, O'Reilly, ISBN 2-84177-139-3 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPSec]{http://www.securiteinfo.com/crypto/IPSec.shtml} -\end_inset +\end_inset (en langue française) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internetworking IPv6 with Cisco Routers]{http://www.ip6.com/index.html} -\end_inset +\end_inset par Silvano Gai, McGrawHill Italia, 1997. Le chapitre 13 et les appendices A-D sont téléchargables au format PDF. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Secure and Dynamic Tunnel Broker]{http://www.vermicelli.pasta.cs.uit.no/ipv6/students/vegars/} -\end_inset +\end_inset par Vegar Skaerven Wang, thèse de maîtrise en sciences informatiques, 2 Juin 2000, Faculté des Sciences, Département des sciences informatiques, Université de Tromso, Norvège. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Aufbruch in die neue Welt - IPv6 in IPv4 Netzen]{http://www.old.netobjectdays.org/pdf/99/stja/doering.pdf} -\end_inset +\end_inset par Dipl.Ing. Ralf Döring, TU Illmenau, 1999 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migration and Co-existence of IPv4 and IPv6 in Residential Networks]{http://www.csc.fi/~psavola/residential.html} -\end_inset +\end_inset par Pekka Savola, CSC/FUNET, 2002 -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-sciencepublication} -\end_inset +\end_inset Publications scientifiques (résumés, bibliographies, ressources en ligne) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Plan de travail du projet IPv6 GEANT]{http://www.ipv6.ac.uk/gtpv6/workplan.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A simulation study on the performance of Mobile IPv6 in a WLAN-based cellular network]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=1} -\end_inset +\end_inset , par Perez Costa X.; Hartenstein H. -- Computer Networks, Septembre 2002, vol. 40, no. 1, pp. 191-204(14) -- Elsevier Science. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Tests IPv6 sur le réseau universitaire britannique: Projet Bermudes 2 Août 2002]{http://www.ipv6.ac.uk/bermuda2/} -\end_inset +\end_inset : Participants - Se connecter - Project deliverables - Network topology - adresse assignments - Wireless IPv6 access - IPv6 migration - Project presentations - Internet 2 - Other IPv6 projects - IPv6 fora and standards Bermuda 2... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[http://www.ipv6.ac.uk/]{http://www.ipv6.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A scalable parallel internet router that enables the QoS through merging ATM with IPv6]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=2} -\end_inset +\end_inset . par Song S. @@ -11749,12 +14334,12 @@ Publications scientifiques (r 25, no. 7, pp. 647-651(5) -- Elsevier Science. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Linux IPv6: Which One to Deploy?]{http://liinwww.ira.uka.de/mpsbib?query=ti%3D(Linux+IPv6+Which+One+Deploy)} -\end_inset +\end_inset journal Linux, Vol. 96, p. @@ -11762,15 +14347,15 @@ Publications scientifiques (r (pour plus d'information, voir aussi \begin_inset LatexCommand \url[liinwww.ira.uka.de/ipv6]{http://liinwww.ira.uka.de/mpsbib?query=ipv6&maxnum=200} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[An overview and analysis of mobile Internet protocols in cellular environments]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=3} -\end_inset +\end_inset . Chao H-C. @@ -11779,12 +14364,12 @@ Publications scientifiques (r 11, no. 5, pp. 435-450(16) -- MCB University Press -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 for Future Wireless networks]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=5} -\end_inset +\end_inset Toftegaard Nielsen T. -- Wireless Personal Communications, Juin 2001, vol. @@ -11792,20 +14377,20 @@ Toftegaard Nielsen T. 2/3, pp. 237-247(11) -- éd. Kluwer Academic, Dordrecht, Les Pays-Bas -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 at the University of Southampton]{http://www.ipv6.ecs.soton.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Seamless Support for Mobile Internet Protocol Based Cellular Environments]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=4} -\end_inset +\end_inset Chao H-C.; Chu Y-M. -- International Journal of Wireless Information Networks, Juillet 2001, @@ -11814,23 +14399,23 @@ Chao H-C.; Chu Y-M. 3, pp. 133-153(21) -- éd. Kluwer Academic/Plenum, New York, U.S.A. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: The Solution for Future Universal Networks]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1818, p. 82-??, 2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Modeling and performance analysis for IPv6 traffic with multiple QoS classes]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=8} -\end_inset +\end_inset . Zhang L.; Zheng L. @@ -11838,42 +14423,43 @@ Chao H-C.; Chu Y-M. 24, no. 15, pp. 1626-1636(11) -- Elsevier Science. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Threshold-Based Registration (TBR) in Mobile IPv6]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1818, p. 150-??, 2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Performance Analysis on FreeBSD Workstation Using Simple Applications]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1961, p. 33-??, 2000. -\layout Itemize +\end_layout +\begin_layout Itemize Microsoft Research IPv6 Implementation (MSRIPv6): \begin_inset LatexCommand \url[MSRIPv6 Configuring 6to4 - Connectivity with MSR IPv6 - Our 6Bone Node... ]{http://www.research.microsoft.com/msripv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[New frontiers in cybersegmentation: marketing success in cyberspace depends on IP address]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=9} -\end_inset +\end_inset . Louvieris P.; Driver J. @@ -11882,895 +14468,937 @@ Microsoft Research IPv6 Implementation (MSRIPv6): 4, no. 3, pp. 169-181(13) -- MCB University Press. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[QoS-Conditionalized Handoff for Mobile IPv6]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3113c/vojrvf} -\end_inset +\end_inset . Notes de conférence en sciences informatiques, Vol. 2345, p. 721-??, 2002. -\layout Subsection +\end_layout +\begin_layout Subsection Autres -\layout Standard +\end_layout +\begin_layout Standard Voir l'URL suivant pour en savoir plus: \begin_inset LatexCommand \url[SWITCH Pilote IPv6 Pilot / Références]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-conferences} -\end_inset +\end_inset Conférences, rencontres, sommets -\layout Subsection +\end_layout +\begin_layout Subsection 2002 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Renater - Conférence IPv6 2002]{http://www.renater.fr/IPv6-2002/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Sommet déploiement IPv6 à INET 2002]{http://www.ipv6summit.com/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Quelque chose manque? Les suggestions sont les bienvenues! -\layout Subsection +\end_layout +\begin_layout Subsection 2003 -\layout Standard +\end_layout +\begin_layout Standard Les suggestions sont les bienvenues! -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlineinformation} -\end_inset +\end_inset L'information en ligne -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-joinipv6} -\end_inset +\end_inset Rejoindre le backbone IPv6 -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant et plus tard... Les suggestions sont les bienvenues! -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-globalregistries} -\end_inset +\end_inset Les bureaux d'enregistrement global -\layout Itemize +\end_layout +\begin_layout Itemize Backbone de test IPv6: \begin_inset LatexCommand \url[6bone]{http://www.6bone.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Comment rejoindre 6bone]{http://www.6bone.net/6bone_hookup.html} -\end_inset +\end_inset , -\newline +\newline \begin_inset LatexCommand \url[Teilnahme am 6bone]{http://www.join.uni-muenster.de/6bone/6bone-teilnahme.html} -\end_inset +\end_inset (en langue allemande), -\newline +\newline \begin_inset LatexCommand \url[La participation au 6bone]{http://www.join.uni-muenster.de/6bone/6bone-participation.html} -\end_inset +\end_inset (en langue anglaise) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-majorregionregistries} -\end_inset +\end_inset Les centres d'enregistrement de noms de domaine les plus importants, par régions -\layout Itemize +\end_layout +\begin_layout Itemize Amérique: \begin_inset LatexCommand \url[ARIN]{http://www.arin.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[ARIN / page d'enregistement]{http://www.arin.net/registration/ipv6/index.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[ARIN / IPv6 guidelines]{http://www.arin.net/registration/ipv6/index.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize EMEA: \begin_inset LatexCommand \url[Ripe NCC]{http://www.ripe.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Ripe NCC / page d'enregistrement]{http://www.ripe.net/ripencc/mem-services/registration/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Ripe NCC / IPv6 registration]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Asie/Pacifique: \begin_inset LatexCommand \url[APNIC]{http://www.apnic.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[APNIC / guide de ressources IPv6]{http://www.apnic.net/services/ipv6_guide.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Amérique latine et les Caraïbes: \begin_inset LatexCommand \url[LACNIC]{http://lacnic.org/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Service d'enregistrement IPv6]{http://lacnic.net/en/bt-IPv6.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Politique d'allocation IPv6]{http://lacnic.net/en/chapter-4-en.pdf} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Afrique: \begin_inset LatexCommand \url[AfriNIC]{http://www.afrinic.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Il existe aussi une liste des principales allocations (préfixe de 32 bits) par bureau d'enregistrement régional ici: \begin_inset LatexCommand \url[Ripe NCC / allocations IPv6]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6allocs.html} -\end_inset +\end_inset . -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-joinipv6-tunnelbrokers} -\end_inset +\end_inset Les fournisseurs de tunnel ( -\emph on +\emph on tunnel brokers -\emph default +\emph default ) -\layout Standard +\end_layout +\begin_layout Standard Note: une liste de fournisseurs de tunnel peut être trouvée plus bas dans l' \begin_inset LatexCommand \ref[information concernant les fournisseurs de tunnel]{information-Tunnelbroker} -\end_inset +\end_inset . -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Code source]{http://www.vermicelli.pasta.cs.uit.no/ipv6/students/vegars/TunnelBroker/} -\end_inset +\end_inset utilisé dans une thèse de maîtrise dans le cadre du projet Vermicelli au sujet des fournisseurs de tunnels, Université de Tromso. -\layout Itemize +\end_layout +\begin_layout Itemize Fondation IPng. Fournisseurs de tunnel et ressources IPv6, dorénavant migré au \begin_inset LatexCommand \url[système SixXs]{http://www.sixxs.net/main/} -\end_inset +\end_inset . -\layout Itemize +\end_layout +\begin_layout Itemize La page de Eckes \begin_inset LatexCommand \url[Linux-avec-IPv6]{http://sites.inka.de/lina/linux/ipv6.html} -\end_inset +\end_inset . -\layout Itemize +\end_layout +\begin_layout Itemize tunnelc - client de tunnelage basé sur perl: -\newline +\newline freshmeat.net: \begin_inset LatexCommand \url[détails sur ce client de tunnelage]{http://freshmeat.net/projects/tunnelc} -\end_inset +\end_inset -\newline +\newline SourceForge: \begin_inset LatexCommand \url[Projet Info - tunnelc]{http://sourceforge.net/projects/tunnelc} -\end_inset +\end_inset (aussi \begin_inset LatexCommand \url[ici]{http://tunnelc.sourceforge.net/} -\end_inset +\end_inset ) -\layout Itemize +\end_layout +\begin_layout Itemize L'HOWTO Routage avancée Linux & contrôle du trafic, \begin_inset LatexCommand \url[Chapitre 6: Le tunnelage IPv6 avec Cisco et/ou 6bone]{http://howtos.linuxbroker.com/howtoreader.shtml?file=Adv-Routing-HOWTO.html#LARTC.TUNNEL-IPV6.ADDRESSING} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Voir aussi ici pour plus d'information et d'URL: \begin_inset LatexCommand \url[ipv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset . -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-joinipv6-6to4-tunneling} -\end_inset +\end_inset 6to4 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[information 6to4 de NSayer]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[RFC 3068 / An Anycast Prefix for 6to4 Relay Routers]{http://www.faqs.org/rfcs/rfc3068.html} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-joinipv6-isatap-tunneling} -\end_inset +\end_inset ISATAP -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ISATAP (Intra-Site Automatic Tunnel Access Protocol) Information]{http://www.join.uni-muenster.de/Dokumente/Howtos/Howto_ISATAP.php?lang=en} -\end_inset +\end_inset by \begin_inset LatexCommand \url[JOIN]{http://www.join.uni-muenster.de/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Les dernières nouvelles -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant et plus tard... Les suggestions sont les bienvenues! -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset , est aussi la page d'accueil du canal #IPv6 sur EFnet -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Nombreux URLs vers d'autres documents]{http://www.estoile.com/links/ipv6} -\end_inset +\end_inset par Anil Edathara -\layout Subsection +\end_layout +\begin_layout Subsection Les références aux protocoles -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les appels à commentaires (RFC) relatifs à IPv6 -\layout Standard +\end_layout +\begin_layout Standard La publication de la liste des RFC relatifs à IPv6 outrepasse la portée de ce document, mais les URL fournis vous guiderons vers de telles listes: -\layout Itemize +\end_layout +\begin_layout Itemize Listes classées par \begin_inset LatexCommand \url[Etat de la standardisation IPng]{http://playground.sun.com/pub/ipng/html/specs/standards.html} -\end_inset +\end_inset ou \begin_inset LatexCommand \url[Spécifications actuelles d'IPng]{http://playground.sun.com/pub/ipng/html/specs/specifications.html} -\end_inset +\end_inset par Robert Hinden -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Spécifications relatives à IPv6]{http://www.ipv6.org/specs.html} -\end_inset +\end_inset on IPv6.org -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les brouillons actuels des groupes de travail -\layout Standard +\end_layout +\begin_layout Standard Les brouillons actuels concernant (aussi) IPv6 peuvent être trouvés ici: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IP Version 6 (ipv6)]{http://www.ietf.org/ids.by.wg/ipv6.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Transition vers la nouvelle génération (ngtrans)]{http://www.ietf.org/ids.by.wg/ngtrans.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Dynamic Host Configuration (dhc)]{http://www.ietf.org/ids.by.wg/dhc.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Extension du Système des Noms de Domaine]{http://www.ietf.org/ids.by.wg/dnsext.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Mobile IP (mobileip)]{http://www.ietf.org/ids.by.wg/mobileip.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Obtenir toute l'information à propos d'IPv6, depuis des vues d'ensemble, en passant par les brouillons et les RFC, jusqu'aux implémentations]{http://playground.sun.com/pub/ipng/html/ipng-main.html} -\end_inset +\end_inset (comprenant la disponibilité de la pile sur différentes plates-formes & le code source de la pile IPv6) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Autres -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Network Sorcery / IPv6, Protocole Internet IP version 6]{http://www.networksorcery.com/enp/protocol/ipv6.htm} -\end_inset +\end_inset , l'en-tête du protocole IPv6 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Guide / Références IPv6 SWITCH]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset , importante liste de références IPv6, maintenue par Simon Leinen -\layout Subsection +\end_layout +\begin_layout Subsection Plus d'information -\layout Standard +\end_layout +\begin_layout Standard A remplir plus avant et plus tard... les suggestions sont les bienvenues! -\layout Standard +\end_layout +\begin_layout Standard \lang ngerman - \begin_inset LatexCommand \url[DeepSpace6 / plus de liens intéressants]{http://www.deepspace6.net/sections/links.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Relative à Linux -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / Portail Linux IPv6 (pas uniquement)]{http://www.deepspace6.net/} -\end_inset +\end_inset - Italie ( \begin_inset LatexCommand \url[miroir]{http://mirrors.bieringer.de/www.deepspace6.net/} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-HowTo pour Linux par Peter Bieringer]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset - Allemagne et son \begin_inset LatexCommand \url[archive logiciel - Bieringer / IPv6]{ftp://ftp.bieringer.de/pub/linux/IPv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[L'état de Linux+IPv6 par Peter Bieringer]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status.html} -\end_inset +\end_inset - Allemagne (en cours d'obsolescence) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / La page concernant l'état IPv6]{ttp://www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset - Italie ( \begin_inset LatexCommand \url[mirroir]{http://mirrors.bieringer.de/www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset ) (remplacera la page ci-dessus) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Projet USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset - Japon, et son \begin_inset LatexCommand \url[archive logiciel - projet USAGI]{ftp://ftp.linux-ipv6.org/pub/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[HOWTO IPv6 Protocole de routage à état de lien optimisé (OLSR)]{http://www.tldp.org/HOWTO/OLSR-IPv6-HOWTO/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Relative à Linux, par distribution -\layout Description +\end_layout +\begin_layout Description PLD \begin_inset LatexCommand \url[PLD Linux Distribution]{http://www.pld-linux.org/} -\end_inset +\end_inset ( \begin_inset Quotes sld -\end_inset +\end_inset leader du marché \begin_inset Quotes srd -\end_inset +\end_inset quant aux paquetages disposant d'IPv6) -\layout Description +\end_layout -Red\SpecialChar ~ +\begin_layout Description +Red\InsetSpace ~ Hat \begin_inset LatexCommand \url[Linux Red Hat]{http://www.redhat.com/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[ les paquetages IPv6 de Pekka Savola]{http://www.netcore.fi/pekkas/linux/ipv6/} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description Debian \begin_inset LatexCommand \url[Linux Debian]{http://www.debian.org/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Etat et information IPv6 par Craig Small]{http://people.debian.org/~csmall/ipv6/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[HOWTO Connectivité globale d'un LAN IPv6]{} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description Novell/SuSE \begin_inset LatexCommand \url[Linux Novell/SuSE]{http://www.novell.com/linux/suse/} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description Mandriva \begin_inset LatexCommand \url[Mandriva]{http://www.mandriva.com} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Pour en savoir plus voir la page \begin_inset LatexCommand \url[état des distributions Linux+IPv6]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Général -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6.org]{http://www.ipv6.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6bone]{http://www.6bone.net/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Centre de ressources britanique IPv6]{http://www.cs-ipv6.lancs.ac.uk/} -\end_inset +\end_inset - Royaume-Uni -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Projet WIDE]{http://www.v6.wide.ad.jp/} -\end_inset +\end_inset - Japon -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SWITCH IPv6 Pilot]{http://www.switch.ch/lan/ipv6/} -\end_inset +\end_inset - Suisse -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Le coin IPv6 de Hubert Feyrer]{http://www.feyrer.de/IPv6/} -\end_inset +\end_inset - Allemagne -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Projet Vermicelli]{http://www.vermicelli.pasta.cs.uit.no/ipv6/} -\end_inset +\end_inset - Norvège -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Forum]{http://www.ipv6forum.com/} -\end_inset +\end_inset - un consortium mondial d'importants fournisseurs Internet, Research & Education Networks... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Playground.sun.com / Page d'info IPv6]{http://playground.sun.com/pub/ipng/html/ipng-main.html} -\end_inset +\end_inset - maintenu par Robert Hinden, Nokia. Obtenir toute information au sujet d'IPv6, depuis de simples vues d'ensemble, en passant par les RFC et brouillons, jusqu'aux implémentations (incluant la disponibilité des piles sur différentes plates-formes & le code source des piles IPv6). -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6INIT]{http://www.6init.com/} -\end_inset +\end_inset - Initiative Internet IPv6 - le 5ème programme-cadre européenne R&D de l'IST. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Task Force (Union Européenne)]{http://www.ipv6-taskforce.org/} -\end_inset +\end_inset ( -\emph on +\emph on NdT -\emph default +\emph default : \begin_inset LatexCommand \url[IPv6 Task Force France]{http://www.france.ipv6tf.org/index.php} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Projet de Documentation IPv6]{http://www.v6.sfc.wide.ad.jp/v6doc/} -\end_inset +\end_inset (langue japonaise) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6init]{http://www.6init.org/} -\end_inset +\end_inset - IniTiative INternet IPv6 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Vue d'ensemble d'IP Nouvelle Génération]{http://www.isoc.org/HMP/PAPER/PT1/html/pt1.html.hinden} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: La nouvelle version du protocole Internet]{http://www.usenix.org/publications/library/proceedings/ana97/summaries/deering.html} -\end_inset +\end_inset , par Steve Deering. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: Le protocole Internet Nouvelle Génération]{http://www.garykessler.net/library/ipv6_exp.html} -\end_inset +\end_inset , par Gary C. Kessler. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: Le protocole Internet Nouvelle Génération]{http://www.3com.com/nsc/ipv6.html} -\end_inset +\end_inset - 3Com -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Initiative Internet Nouvelle Génération]{http://www.ngi.gov/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[internet || site]{http://www.internet2.org/} -\end_inset +\end_inset et \begin_inset LatexCommand \url[Groupe de travail internet2]{http://ipv6.internet2.edu/} -\end_inset +\end_inset - \begin_inset LatexCommand \url[Presentation (HTML + PPT)]{http://ipv6.internet2.edu/presentations/} -\end_inset +\end_inset de l'atelier IPv6: (auto-configuration sans état, adressage IPv6, USAGI, fournisseur d'adressage IPv6 indépendant et autres thèmes). -\layout Itemize +\end_layout +\begin_layout Itemize NetworkWorldFusion: \begin_inset LatexCommand \url[rechercher IPv6]{http://search.nwfusion.com/query.html?qt=IPv6&qp=&ch=cn&} -\end_inset +\end_inset (102 documents trouvés au 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[The Register]{http://www.theregister.co.uk/} -\end_inset +\end_inset (la recherche pour IPv6 donne 30 documents, 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[recherche chez ZDNet pour IPv6]{http://zdnet.search.com/search?cat=279&q=IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Recherche chez TechTarget pour IPv6]{http://whatis.techtarget.com/wsearchResults/1,290214,sid9,00.html?query=IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Liste de resssources IPv6 & TCP]{http://www.faqs.org/faqs/internet/tcp-ip/resource-list/index.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Les outils IPv6 Klingon]{http://ipv6.klingon.nl/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[les outils IPv6 Klingon (accessible seulement en IPv6 natif)]{http://www.ipv6.klingon.nl/} -\end_inset +\end_inset : exemples de pare-feu IPv6, test de bande passante et scanner de ports -\layout Standard +\end_layout +\begin_layout Standard Quelque chose manque? Les suggestions sont les bienvenues! -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-marketresearch} -\end_inset +\end_inset Etudes de marché -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A Tale of Two Wireless Technology Trends: Processor Development Outsourcing and IPv6]{http://www.seminarinformation.com/wconnect/wc.dll?sis~details0~194045~TSN} -\end_inset +\end_inset Groupe Yankee - 1/4/2002 - 12 Pages - ID: YANL768881 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[The World Atlas of the Internet: Americas]{http://www.marketresearch.com/product/display.asp?SID=88602378-241489274-186851952&ProductID=803907} -\end_inset +\end_inset ; IDATE - 2/1/2002 - 242 Pages - ID: IDT803907. Les pays couverts: Amérique Centrale, Amérique du Nord, Amérique du Sud; @@ -12779,1597 +15407,1650 @@ t Estimation du marché et prévions jusqu'en 2006 pour 34 pays: structure du marché: les principaux ISP et le partage du marché; nombre de souscripteurs, d'ISP. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Earlier Interest Rising for IPv6]{http://www.amazon.com/exec/obidos/tg/detail/-/B000065T8E/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset par IDC (Auteur); prix: $1,500.00; support: e-book (Acrobat Reader); éd. IDC; ISBN B000065T8E; ( 1 mars 2002) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-patents} -\end_inset +\end_inset Les brevets -\layout Itemize +\end_layout +\begin_layout Itemize Base de données des brevets canadiens: \begin_inset LatexCommand \url[Accueil]{http://patents1.ic.gc.ca/intro-e.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Recherche]{http://patents1.ic.gc.ca/srch_sim-e.html} -\end_inset +\end_inset (Recherche simple, entrez juste \begin_inset Quotes sld -\end_inset +\end_inset IPv6 \begin_inset Quotes srd -\end_inset +\end_inset dans le champs recherche ;-); 84 documents trouvés au 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Espacenet]{http://www.european-patent-office.org/espacenet/info/index.htm} -\end_inset +\end_inset - information sur les brevets européens: -\newline +\newline \begin_inset LatexCommand \url[Offices nationaux, membres d'Espacenet]{http://www.european-patent-office.org/espacenet/info/access.htm} -\end_inset +\end_inset (IPv6: 84 documents, au 22.12.2002) -\layout Itemize +\end_layout +\begin_layout Itemize Delphion: \begin_inset LatexCommand \url[Recherche de brevets]{http://www.delphion.com/research/} -\end_inset +\end_inset . Un simple enregistrement (gratuit) est nécessaire. Exemples trouvés au 21.12.2002 par une recherche sur l'expression IPv6: -\newline +\newline \begin_inset LatexCommand \url[Méthode de communication entre terminal IPv4 et terminal IPv6, mécanisme de conversion IPv4-IPv6]{http://www.delphion.com/details?pn=US06118784__} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Traducteur pour réseaux IP, système réseau utilisant le traducteur, mais aussi une méthode de couplage de réseaux IP]{http://www.delphion.com/details?pn=US06038233__} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Par pays -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Europe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[www.ist-ipv6.org]{http://www.ist-ipv6.org/} -\end_inset +\end_inset : IST IPv6 Cluster, recherche européenne IPv6 et développement de projets -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Euro6IX]{http://www.euro6ix.org/} -\end_inset +\end_inset : Backbone européenne d'interconnexion Internet IPv6 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Autriche -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6@IKNnet et le groupe de recherche MIPv6]{http://www.ikn.tuwien.ac.at/~ipv6/} -\end_inset +\end_inset : Vienne , Autriche (IPv6: projets, publications, diplômes / thèses de doctorat, actes de conférence, -\emph on +\emph on etc. -\emph default +\emph default )é -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Australie -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Les pages IPv6 australiennes de Carl]{http://oversteer.bl.echidna.id.au/IPv6/} -\end_inset +\end_inset (contenu ancien) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Belgique -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Brésil -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[BR6bone]{http://www.6bone.rnp.br/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[IPv6 Summit in Brazil]{http://www.ipv6summit.com.br/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[IPv6 do Brasil]{http://www.ipv6dobrasil.com.br/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Chine -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Tchèque -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Allemagne -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset : Forum IPv6 allemand -\layout Subsubsection +\end_layout +\begin_layout Subsubsection France -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Renater]{http://www.renater.fr/Projets/IPv6/index.htm} -\end_inset +\end_inset : La page d'accueil du projet IPv6 Renater -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 - RSVP - ATM à l'INRIA]{http://www.inria.fr/recherche/equipes/ipv6.fr.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Documentation IPv6 NetBSD IPv6]{http://www.netbsd.org/fr/Documentation/network/ipv6/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Hongrie -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Tester la technologie expérimentale IPv6 et ses services en Hongrie]{http://tipster6.ik.bme.hu/tipster6_en.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Inde -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Italie -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Japon -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Groupe d'utilisateurs IPv6 Linux JP]{http://www.v6.linux.or.jp/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Yamaha IPv6]{http://www.rtpro.yamaha.co.jp/RT/ipv6/} -\end_inset +\end_inset (désolès, tout en japonais...) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Corée -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ETRI]{http://www.krv6.net/} -\end_inset +\end_inset : Institut de Recherche en Electronique et Télécommunications -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Forum IPv6 koréen]{http://www.ipv6.or.kr/english/index.new.htm} -\end_inset +\end_inset : Projet de déploiement coréen d'IPv6 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Mexique -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Mexique IPv6]{http://www.ipv6.unam.mx/} -\end_inset +\end_inset (versions espagnole et anglaise): Accueil du projet IPv6 de l'Université nationale autonome du Mexique (UNAM) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Pays-Bas -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SURFnet]{http://www.ipv6.surfnet.nl/} -\end_inset +\end_inset : Backbone IPv6 SURFnet -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[STACK]{http://www.stack.nl/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[STACK (IPv6)]{http://www.stack.nl/ipv6/} -\end_inset +\end_inset : Association d'étudiants en informatique de l' Université de Technologie, Pays-Bas -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPng.nl]{http://www.ipng.nl/} -\end_inset +\end_inset : collaboration entre WiseGuys et Intouch -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Portugal -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[FCCN (Fondation Nationale pour le Calcul Scientifique)]{http://www.fccn.pt/projectos/ipv6/index_html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Russie -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Forum IPv6 pour la Russie]{http://www.ipv6.ru/} -\end_inset +\end_inset : Centre Internet de l'Université publique de Yaroslavl -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Suisse -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SWITCH]{http://www.switch.ch/network/ipv6/references.html} -\end_inset +\end_inset : L'éducation suisse & les recherches réseau -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Royaume-Uni -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 au Royaume-Uni]{http://www.ipv6.org.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Centre de resources IPv6 britanique]{http://www.cs-ipv6.lancs.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[La page d'accueil de British Telecom IPv6]{http://www.bt.com/ipv6/} -\end_inset +\end_inset : essai de BT en tant que fournisseur de service IPv6, premier point d'interconn exion Internet au Royaume-Uni, ... -\layout Subsection +\end_layout +\begin_layout Subsection Par systèmes d'exploitation -\layout Subsubsection +\end_layout +\begin_layout Subsubsection *BSD -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Le projet KAME ]{http://www.kame.net/} -\end_inset +\end_inset (*BSD) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[FAQ de la mise en réseau IPv6 de NetBSD]{http://www.netbsd.org/Documentation/network/ipv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Le port FreeBSD d'Ipv6]{http://www.freebsd.org/ports/ipv6.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize BUGAT - Groupe d'utilisateurs Australiens BSD - \begin_inset LatexCommand \url[www.bugat.at]{http://www.bugat.at/} -\end_inset +\end_inset : \begin_inset LatexCommand \url[Tunnel IPv6 FreeBSD]{http://www.bugat.at/inforum/contentview.php/mini-howto/freebsd-ipv6.ihtml} -\end_inset +\end_inset (langue allemande) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Cisco IOS -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Cisco IOS IPv6]{http://www.cisco.com/warp/public/732/Tech/ipv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 pour IOS de Cisco]{http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/ftipv6c.htm} -\end_inset +\end_inset , Fichier 2 sur 3: août 2002 -- Table des Matières: IPv6 pour IOS de Cisco; documentation des caractéristiques de configuration; Rendre disponible et configurer le routage IPv6; l'adressage IPv6; Rendre globalement le fonctionnement IPv6 disponible. -\layout Itemize +\end_layout +\begin_layout Itemize Manuel de la mise en réseau Internet Cisco, \begin_inset LatexCommand \url[chapitre IPv6]{http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/ipv6.htm} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Compaq -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 chez Compaq]{http://www.compaq.com/ipv6/} -\end_inset +\end_inset - Présentations, livres blancs, documentation, ... -\layout Subsubsection +\end_layout +\begin_layout Subsubsection HPUX -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[FAQ comp.sys.hp.hpux]{http://www.faqs.org/faqs/hp/hpux-faq/index.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IBM -\layout Itemize +\end_layout +\begin_layout Itemize Maintenant c'est IBM qui annonce la disponibilité de z/OS V1.4, \begin_inset LatexCommand \url[Quoi de neuf dans cette version?]{http://search390.techtarget.com/ateQuestionNResponse/0,289625,sid10_cid486367_tax292523,00.html} -\end_inset +\end_inset Cette question a été posée le 15 août 2002 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Microsoft -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Microsoft Windows 2000 IPv6]{http://www.microsoft.com/windows2000/technologies/communications/ipv6/default.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[MSRIPv6]{http://www.research.microsoft.com/msripv6} -\end_inset +\end_inset - Accueil IPv6 des recherches réseau de Microsoft -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Débuter avec la technologie IPv6 Microsoft prévue pour Windows 2000]{http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Le pare-feu servant à la connexion Internet ne bloque pas le trafic IPv6]{http://support.microsoft.com/default.aspx?scid=kb;en-us;306203} -\end_inset +\end_inset (au 6.11.2001) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internet Protocol Numbers]{http://support.microsoft.com/default.aspx?scid=kb;en-us;289892} -\end_inset +\end_inset (au 8.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Technology Preview Refresh]{http://support.microsoft.com/default.aspx?scid=kb;en-us;273826} -\end_inset +\end_inset (au 16.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Comment: installer et configurer IP version 6 pour Windows .NET Enterprise Server]{http://support.microsoft.com/default.aspx?scid=kb;en-us;325449} -\end_inset +\end_inset (au 26.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Le service de routage 6to4 du serveur Windows .NET quitte lorsque vous publiez une adresse 2002 sur une interface publique]{http://support.microsoft.com/default.aspx?scid=kb;en-us;329984} -\end_inset +\end_inset (au 28.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[msdn - Microsoft Windows CE .NET - commandes IPv6]{http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcetcpip/htm/cmconIPv6exe.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[msdn - recherche pour IPv6]{http://search.microsoft.com/default.asp?qu=IPv6&boolean=ALL&nq=NEW&so=RECCNT&p=1&ig=01&i=00&i=01&i=02&i=03&i=04&i=05&i=06&i=07&i=08&i=09&i=10&i=11&i=12&i=13&i=14&i=15&i=16&i=17&i=18&i=19&i=20&i=21&i=22&i=23&i=24&i=25&i=26&i=27&i=28&i=29&i=30&i=31&i=32&i=33&i=34&i=35&i=36&i=37&i=38&i=39&i=40&i=41&siteid=us/dev} -\end_inset +\end_inset (100 résultats, au 22.12.2002) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Solaris -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Solaris Sun Microsystems]{http://www.sun.com/software/solaris/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Solaris 2 Frequently Asked Questions (FAQ) 1.73]{http://www.cs.uu.nl/wais/html/na-dir/Solaris2/FAQ.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Sumitoma é -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Sumitomo Electric a implémenté IPv6 sur la famille des routeurs Suminet 3700]{http://playground.sun.com/pub/ipng/html/ipng-implementations.html#Sumitomo} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ZebOS -\layout Itemize +\end_layout +\begin_layout Itemize IpInfusion's \begin_inset LatexCommand \url[ZebOS Logiciel de serveur de routage]{http://www.ipinfusion.com/products/server/products_server.html} -\end_inset +\end_inset -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-ipv6andsecurity} -\end_inset +\end_inset La sécurité IPv6 -\layout Itemize +\end_layout +\begin_layout Itemize Internet Security Systems: Centre Sécurité, \begin_inset LatexCommand \url[recherche dans la base de donnée X-Force]{http://www.iss.net/security_center/search.php?type=3&type=3&pattern=IPv6} -\end_inset +\end_inset (21.12.2002 - 6 thèmes relatifs à IPv6) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Projet IPsec NIST]{http://csrc.nist.gov/ipsec/} -\end_inset +\end_inset ( Institut National des Standards et Technologie, NIST) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Information Security]{http://www.infosecuritymag.com/index.shtml} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NewOrder.box.sk (recherche pour IPv6)]{http://neworder.box.sk/search.php3?srch=IPv6} -\end_inset +\end_inset (Articles, exploits, files database, etc.) -\layout Subsection +\end_layout +\begin_layout Subsection Les listes d'applications -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6.org / Ies applications disposant d'Pv6]{http://www.ipv6.org/v6-apps.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Freshmeat / recherche IPv6]{http://freshmeat.net/search/?q=IPv6} -\end_inset +\end_inset , actuellement (au 14 décembre 2002), 62 projets -\layout Itemize +\end_layout +\begin_layout Itemize Forum IPv6 : \begin_inset LatexCommand \url[IPv6 Router List]{http://www.ipv6forum.com/navbar/links/v6routerlist.htm} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les outils d'analyse -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Ethereal]{http://ethereal.planetmirror.com/} -\end_inset +\end_inset - Ethereal est un analyseur libre de protocoles réseaux pour Unix et Windows -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Radcom RC100-WL]{http://www.ip6.com/us/analyzer.htm} -\end_inset +\end_inset - Téléchargez l'analyseur de protocoles RC100-WL Radcom version 3.20 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Les produits IPv6 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6wind]{http://www.6wind.com/} -\end_inset +\end_inset - solutions pour routeur IPv4/IPv6, QoS, Multicast, Mobilité, Sécurité/VPN/Pare -feu. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Fefe's patches for IPv6 with djbdns]{http://www.fefe.de/dns/} -\end_inset +\end_inset Août 2002 -- Qu'est-ce que djbdns et a-t-il besoin d'IPv6? djbdns est un serveur DNS complet qui outrepasse les performances de BIND. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Suite de serveurs de routage ZebOS ]{http://www.ipinfusion.com/products/server/products_server.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Serveur de courrier SPA 2.21 ]{http://download.com.com/3000-2165-10153543.html?tag=lst-0-21} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Inframail (Advantage Server Edition) 6.0 ]{http://download.com.com/3000-2165-8202652.html?tag=lst-0-2} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[HTTrack Website Copier]{http://download.com.com/3000-2377-10149393.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[CommView 5.0]{http://download.com.com/3000-2085-10132748.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Posadis 0.50.6]{http://download.com.com/3000-2104-10149750.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TCP Wrapper (prêt pour IPv6)]{ftp://ftp.porcupine.org/pub/ipv6/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-snmp} -\end_inset +\end_inset SNMP -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[comp.protocpols.snmp SNMP FAQ Parties 1 of 2]{http://www.cs.uu.nl/wais/html/na-dir/snmp-faq/part1.html} -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section L'infrastructure IPv6 -\layout Subsection +\end_layout +\begin_layout Subsection Statistiques -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Histoire de la table de routage IPv6]{http://www.space.net/~gert/RIPE/} -\end_inset +\end_inset créée par Gert Döring, \begin_inset LatexCommand \url[Space.Net]{http://www.space.net/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Official 6bone Webserver list Statisic]{http://6bone.informatik.uni-leipzig.de/ipv6/stats/stats.php3} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Allocation Data & Survey Results]{http://www.ripe.net/ripe/meetings/archive/ripe-42/presentations/ripe42-ipv6-survey/sld001.html} -\end_inset +\end_inset , IPv6 WG, Ripe 42, Ripe NCC -\layout Subsection +\end_layout +\begin_layout Subsection Points d'interconnexion Internet -\layout Standard +\end_layout +\begin_layout Standard Une autre liste de points d'interconnexion IPv6 peut être trouvée ici: \begin_inset LatexCommand \url[Site web des points d'interconnexion IPv6]{http://www.v6nap.net/} -\end_inset +\end_inset \lang english ou \begin_inset LatexCommand \url[Statut IPv6 des IXP en Europe]{http://www.euro-ix.net/isp/choosing/search/matrix.php} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-estonia} -\end_inset +\end_inset Estonie -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TIX]{http://tix.estpak.ee/} -\end_inset +\end_inset (point d'interconnexion Internet Tallinn avec support IPv6) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-europe} -\end_inset +\end_inset Europe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Euro6IX]{http://www.euro6ix.net/} -\end_inset +\end_inset , Backbone des points d'interconnexion Internet IPv6 européen -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-france} -\end_inset +\end_inset France -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Point d'interconnexion Internet IPv6 français]{http://www.fnix6.net/} -\end_inset +\end_inset (actif depuis le 1.11.2002). -\newline +\newline FNIX6 fournit une interconnexion haut débit FastEthernet gratuite et fiable entre ISP situés chez TeleCity, Paris. -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-germany} -\end_inset +\end_inset Allemagne -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[INXS]{http://www.inxs.de/} -\end_inset +\end_inset : Munich et Hamburg (câble & sans fil) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-japan} -\end_inset +\end_inset Japon -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NSPIXP-6]{http://www.wide.ad.jp/nspixp6/} -\end_inset +\end_inset : point d'interconnexion Internet basé sur IPv6, à Tokyo -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[JPIX]{http://www.jpix.co.jp/} -\end_inset +\end_inset , Tokyo -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-korea} -\end_inset +\end_inset Korée -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6NGIX]{http://www.ngix.ne.kr/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-netherlands} -\end_inset +\end_inset Les Pays-Bas -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[AMS-IX]{http://www.ams-ix.net/} -\end_inset +\end_inset : Point d'interconnexion à Amsterdam -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-uk} -\end_inset +\end_inset Royaume-Uni -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UK6X]{http://www.uk6x.com/} -\end_inset +\end_inset : Londres -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XchangePoint]{http://www.xchangepoint.net/} -\end_inset +\end_inset : Londres -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-usa} -\end_inset +\end_inset USA -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6TAP]{http://www.6tap.net} -\end_inset +\end_inset : Chicago. Supporte le -\emph on +\emph on peering -\emph default +\emph default à travers tout le globe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NY6IX]{http://www.ny6ix.net/} -\end_inset +\end_inset : Point d'interconnexion IPv6 basé à New York -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[PAIX]{http://www.paix.net/} -\end_inset +\end_inset : Palo Alto -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-Tunnelbroker} -\end_inset +\end_inset Les fournisseurs de tunnel ( -\emph on +\emph on tunnelbrokers -\emph default +\emph default ) -\layout Standard +\end_layout +\begin_layout Standard \lang english Voir aussi: \begin_inset LatexCommand \url[http://www.deepspace6.net/docs/tunnelbrokers.html]{http://www.deepspace6.net/docs/tunnelbrokers.html} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-belgium} -\end_inset +\end_inset Belgique -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Wanadoo]{http://tunnel.be.wanadoo.com/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-canada} -\end_inset +\end_inset Canada -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Freenet6]{http://www.freenet6.net/} -\end_inset +\end_inset - délégation /48, Canada -\newline +\newline \begin_inset LatexCommand \url[Accéder à IPv6 en utilisant Freenet6 sur Debian]{http://www.linuxjournal.com/article.php?sid=5963&mode=thread&order=0} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Création Freenet6]{http://www.viagenie.qc.ca/en/index.shtml} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-china} -\end_inset +\end_inset Chine -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[CERNET-Nokia]{http://tb.6test.edu.cn/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-estonia} -\end_inset +\end_inset Estonie -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Estpak]{http://tunnelbroker.ipv6.estpak.ee/?tunnel&PHPSESSID=aa2184190cc2cc6d3a6f6ddd01ae3635} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Europe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Fournisseur de tunnel distribué XS26]{http://www.xs26.net/} -\end_inset +\end_inset , USA & Europeé -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-germany} -\end_inset +\end_inset Allemagne -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6bone Knoten Leipzig]{http://6bone.informatik.uni-leipzig.de/} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Info bez. Hackangriff (2001)]{http://www.mail-archive.com/ipv6@uni-muenster.de/msg00056.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Berkom]{http://fix.ipv6.berkom.de/cgi-bin/tb.pl} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-italy} -\end_inset +\end_inset Italie -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Centro Studi e Laboratory Telecomunicazioni]{https://carmen.cselt.it/ipv6tb/} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[page de téléchargement TunnelBroker Version 2.1.]{http://carmen.cselt.it/cgi-bin/download.pl?pkg=TunnelBroker} -\end_inset +\end_inset ) -\newline +\newline Fournisseur de tunnel IPv6: \begin_inset LatexCommand \url[instructions d'installation]{http://carmen.cselt.it/ipv6/tools/ipv6tb/Installing-ipv6tb.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Comv6]{http://www.comv6.com/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Bersafe]{http://www.bersafe.it} -\end_inset +\end_inset (langue italienne) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Telecom Italia LAB]{http://carmen.ipv6.tilab.com/} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[page de téléchargement du logiciel Tunnelbroker]{http://carmen.ipv6.tilab.com/cgi-bin/download.pl?pkg=TunnelBroker} -\end_inset +\end_inset ) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-japan} -\end_inset +\end_inset Japon -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Initiative Internet au Japon]{http://www.iij.ad.jp/en/IPv6} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[en langue japonaise]{http://www.iij.ad.jp/IPv6/} -\end_inset +\end_inset ) - avec fourniture de lignes IPv6 natives et tunnelage IPv6 -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-malaysia} -\end_inset +\end_inset Malaisie -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Manis]{http://tbroker.manis.net.my/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-netherlands} -\end_inset +\end_inset Les Pays-Bas -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XS26 - "Accès à Six"]{http://www.xs26.net/} -\end_inset +\end_inset - avec des POP (Points De Présence) en République slovaque, en République Tchèque, aux Pays-Bas, en Allemagne et en Hongrie. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPng Pays-Bas]{http://www.ipng.nl/} -\end_inset +\end_inset - Intouch, SurfNet, AMS-IX, UUNet, Cistron, RIPE NCC et AT&T sont connectés au AMS-IX. Il est possible (sous certaines conditions) d'obtenir un tunnel statique. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Clients SURFnet]{http://www.ipv6.surfnet.nl/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-norway} -\end_inset +\end_inset Norvège -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UNINETT]{http://www.uninett.no/testnett/index.en.html} -\end_inset +\end_inset , Guide concernant le service IPv6 (pour les clients): fournisseur de tunnel et allocation d'adresse -\newline +\newline \begin_inset LatexCommand \url[Uninett-Autoupdate-HOWTO]{http://www.guruz.de/Uninett-Autoupdate-HOWTO} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english - \begin_inset LatexCommand \label{information-tunnelbroker-spain} -\end_inset +\end_inset Espagne -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Consulintel]{http://tb.consulintel.euro6ix.org/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-switzerland} -\end_inset +\end_inset Suisse -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Fournisseur de tunnel AS8758]{http://tunnelbroker.as8758.net/} -\end_inset +\end_inset , Dolphins Network Systems (en ligne depuis le 20.12.2002) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-uk} -\end_inset +\end_inset Royaume-Uni -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NTT Europe]{http://www.uk.v6.ntt.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[NTT]{http://www.nttv6.net/} -\end_inset +\end_inset , Royaume-Uni - essai IPv6. Tunnel IPv4 et IPv6 natif and native IPv6 leased Line connexions. Les POP sont situés à Londres au Royaume Uni, Düssenldorf en Allemagne, New Jersey aux USA (Côte Est), Cupertino aux USA (Côte Ouest), Tokyo au Japon -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Interface d'administration du fourniseur de tunnel IPv6 BtexacT]{https://tb.ipv6.btexact.com/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Royaume-Uni IPng]{http://ipng.org.uk/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-usa} -\end_inset +\end_inset USA -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ESnet]{http://www.es.net/hypertext/welcome/pr/ipv6.html} -\end_inset +\end_inset , USA - Réseau des Sciences de l'Energie: Tunnel Registry & adresse Delegation for directly connected ESnet sites and ESnet collaborators. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6REN]{http://www.6ren.net/} -\end_inset +\end_inset , USA - l'initiative 6ren est coordonnée par Réseau des Sciences de l'Energie (ESnet), the network for the Energy Research program of the US Dept. of Energy, located at the University of California's Lawrence Berkeley National Laboratory. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XS26 Distributed Tunnel Broker]{http://www.xs26.net/} -\end_inset +\end_inset , USA & Europe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Hurricane Electric]{http://ipv6tb.he.net/} -\end_inset +\end_inset , backbone US; -\newline +\newline \begin_inset LatexCommand \url[Fournisseur de tunnel Hurrican Electric]{http://tunnelbroker.net/} -\end_inset +\end_inset (aussi disponible \begin_inset LatexCommand \url[ici]{http://tunnelbroker.com/} -\end_inset +\end_inset ) -\newline +\newline Press Version: \begin_inset LatexCommand \url[Hurricane Electric devient fournisseur de tunnel IPv6 (communiqué de presse)]{http://www.he.net/releases/release6.html} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Mise à jour d'extrémité de tunnel, pour fournisseur de tunnel]{http://ipv6.he.net/tunnelbroker-update.php} -\end_inset +\end_inset , script Perl -\layout Subsubsection +\end_layout +\begin_layout Subsubsection \lang english - \begin_inset LatexCommand \label{information-tunnelbroker-singapore} -\end_inset +\end_inset Singapour -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[http://tunnel-broker.singnet.com.sg/]{http://tunnel-broker.singnet.com.sg/} -\end_inset +\end_inset , avec en option NAT et IPsec -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-more} -\end_inset +\end_inset Plus de fournisseurs de tunnel... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Routeurs relais 6to4 publiques]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset (boycott MS IIE!) -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-infrastructure-nativeipv6service} -\end_inset +\end_inset Services nativement accessibles par IPv6 -\layout Standard +\end_layout +\begin_layout Standard Note: Ces services sont uniquement disponibles grâce à une connexion IPv6 valide! -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6gameserver} -\end_inset +\end_inset Serveur de jeu -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Quake2]{http://www.viagenie.qc.ca/en/ipv6/quake2/ipv6-quake2.shtml} -\end_inset +\end_inset sur IPv6 -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6ircserver} -\end_inset +\end_inset IRC Server -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Cyconet]{http://ipv6.cyconet.org/?id=server} -\end_inset +\end_inset (serveurs IRCnet Cyconet sur IPv6) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Stations Radio, flux de musique -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Flux IPv6 expérimental en direct!]{http://aopteryx.informatik.uni-leipzig.de:8000/live.mp3} -\end_inset +\end_inset , Université de Leipzig, Allemagne -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6webserver} -\end_inset +\end_inset Serveur web -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[la page d'accueil de l'HOWTO IPv6 Linux de Peter Bieringer ]{http://www.ipv6.bieringer.de/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Quelque chose manque? Les suggestions sont les bienvenues! -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-maillists} -\end_inset +\end_inset Les listes de diffusion -\layout Standard +\end_layout +\begin_layout Standard Des listes de listes de diffusion sont disponibles: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / liste de listes de diffusion]{http://www.deepspace6.net/sections/lists.html} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Les listes de diffusion essentielles sont listées dans le tableau suivant: -\layout Standard +\end_layout - -\begin_inset Tabular +\begin_layout Standard +\begin_inset Tabular @@ -14382,838 +17063,920 @@ Les listes de diffusion essentielles sont list \begin_inset Text -\layout Standard - +\begin_layout Standard Centre d'intérêt -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Adresse mél de la requête d'inscription -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard A quoi souscrire -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Adresse mél de la liste de diffusion -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Langue -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard accès par WWW -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard L'activité réseau du noyau Linux incluant IPv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) oss.sgi.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard netdev -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard netdev (chez) oss.sgi.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Archive]{http://oss.sgi.com/projects/netdev/archive/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Linux et IPv6 en général (1) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) list.f00f.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard linux-ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard linux-ipv6 (chez) list.f00f.org (modérée) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard L'implémentation Linux du protocole IPv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard interface web, voir l'URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard project6 (chez) ferrara.linux.it -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://project6.ferrara.linux.it/sections/lists.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Subscription]{http://mailman.ferrara.linux.it/listinfo/project6} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard La mobilité IP(v6) sur Linux -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) list.mipl.mediapoli.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard mipl -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard mipl (chez) list.mipl.mediapoli.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.mipl.mediapoli.com/mailinglist.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.mipl.mediapoli.com/mail-archive/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Utilisateurs Linux IPv6 avec l'extension USAGI -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard usagi-users-ctl (chez) linux-ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard usagi-users (chez) linux-ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info / Recherche]{http://www.linux-ipv6.org/ml/index.html#usagi-users} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.linux-ipv6.org/ml/usagi-users/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard IPv6 sur Debian Linux -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard interface web, voir l'URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard debian-ipv6 (chez) lists.debian.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info/Souscription/Archive]{http://lists.debian.org/debian-ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard IPv6/6bone en Allemagne -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) atlan.uni-muenster.de -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 (chez) uni-muenster.de -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard German/English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.join.uni-muenster.de/JOIN/ipv6/texte-englisch/mailingliste.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.join.uni-muenster.de/local/majordomo/ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard 6bone -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) isi.edu -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard 6bone -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard 6bone (chez) isi.edu -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.6bone.net/6bone_email.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://mailman.isi.edu/pipermail/6bone/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Discussions IPv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) sunroof.eng.sun.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipng -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipng (chez) sunroof.eng.sun.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://playground.sun.com/pub/ipng/html/instructions.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{ftp://playground.sun.com/pub/ipng/mail-archive/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Mirroir des archives]{http://www.wcug.wwu.edu/lists/ipng/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Les utilisateurs d'IPv6 en général -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard users -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard users (chez) ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.ipv6.org/mailing-lists.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://news.gmane.org/thread.php?group=gmane.network.ipv6.general} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Recherche des bogues des applications Internet (2) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard bugtraq-subscribe (chez) securityfocus.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard bugtraq (chez) securityfocus.com (moderated) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://online.securityfocus.com/popups/forums/bugtraq/intro.shtml} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://online.securityfocus.com/archive/1} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard IPv6 en général -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard interface web, voir l'URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 (chez) ipng.nl -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Anglaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info/Subscription]{http://mailman.ipng.nl/mailman/listinfo/ipv6/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://mailman.ipng.nl/pipermail/ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (chez) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 (chez) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Portugaise -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.marcelo.pro.br/mailman/listinfo/ipv6} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard (1) recommandé pour les questions d'ordre général Linux & IPv6. -\layout Standard +\end_layout +\begin_layout Standard (2) très recommandé si vous êtes fournisseur d'applications serveur. -\layout Standard +\end_layout +\begin_layout Standard Quelque chose manque? Les suggestions sont les bienvenues! -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Les listes de diffusion et newsgroups suivants sont disponibles -\emph on +\emph on via -\emph default +\emph default le web: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (France)]{http://www.tile.net/lists/showlists.php?list_id=35905} -\end_inset +\end_inset -\newline +\newline Description: Cette liste IPv6 permet de discuter d'IPv6 en langue française. Elle s'adresse aux personnes désirant démarrer dès aujourd'hui des tests IPv6. @@ -15221,165 +17984,165 @@ Description: Cette liste IPv6 permet de discuter d'IPv6 en langue fran Pour de plus amples informations: \begin_inset LatexCommand \url[http://www.urec.fr/IPng]{http://www.urec.fr/IPng} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Tunnelbroker Maillingliste (Allemagne)]{http://www.ipv6.uni-leipzig.de/~6bone/tb/maillist.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (Hongrie)]{http://www.tile.net/lists/showlists.php?list_id=36611} -\end_inset +\end_inset -\newline +\newline Description: ipv6 Az IPv6 protokoll listaja Konfiguracios es adminisztracios kerdesek az IPv6-al kapcsolatban. \begin_inset LatexCommand \url[(Archivum)]{http://www.ipv6.fsz.bme.hu/mlists/ipv6/ipv6.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[student-ipv6 (Inde)]{http://groups.yahoo.com/group/student-ipv6} -\end_inset +\end_inset -\newline +\newline Description: groupe d'étudiants intéressé par IPv6 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPV6-CNR@LISTSERV.CNR.IT (Italie)]{http://www.lsoft.com/scripts/wl.exe?SL1=IPV6-CNR&H=LISTSERV.CNR.IT} -\end_inset +\end_inset -\newline +\newline Description: Groupe IPv6 au CNR -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-jp (Japon)]{http://www.tile.net/lists/showlists.php?list_id=14761} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (Japon)]{http://www.tile.net/lists/showlists.php?list_id=37305} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[sun-ipv6-users]{http://groups.yahoo.com/group/sun-ipv6-users} -\end_inset +\end_inset -\newline +\newline Description: Merci de rapporter les problèmes/suggestions concernant l'implément ation IPng SUN Microsystems -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-BITS]{http://groups.yahoo.com/group/IPv6-BITS} -\end_inset +\end_inset -\newline +\newline Description: Cette liste coordonnera le travail du Verebrae. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[openbsd-ipv6]{http://www.tile.net/lists/showlists.php?list_id=23220} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6]{http://www.tile.net/lists/showlists.php?list_id=35203} -\end_inset +\end_inset -\newline +\newline Description: Cette liste de diffusion consiste en discussions techniques au sujet des possibilités d'IPv6/IPsec WRT OpenBSD. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[linux-bangalore-ipv6]{http://groups.yahoo.com/group/linux-bangalore-ipv6} -\end_inset +\end_inset -\newline +\newline Description: La liste concernant le déploiement d'IPv6 du groupe d'utilisateurs Linux Bangalore -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[gab]{http://www.tile.net/lists/showlists.php?list_id=32034} -\end_inset +\end_inset -\newline +\newline Description: L'intention est de discuter du plan géographique d'adressage IPv6. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-bsd-user]{http://www.tile.net/lists/showlists.php?list_id=37430} -\end_inset +\end_inset -\newline +\newline Description: Cette liste de diffusion concerne l \begin_inset Quotes srd -\end_inset +\end_inset implémentation INéRIA/IMAG d'IPv6. Elle est bilingue, Francais/Anglais. Si vous souhaitez contacter les implémenteurs, essayez ipv6-bsd-core@imag.fr -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[gated-ipv6]{http://www.tile.net/lists/showlists.php?list_id=41375} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[La commutation de paquets]{http://groups.yahoo.com/group/packet-switching} -\end_inset +\end_inset -\newline +\newline Description: cette liste de diffusion fournit un forum de discussion au sujet de l'implémentation, de la technologie et de la théorie de la commutation de paquets et l'application à tout domaine, LAPB, X.25, SDLC, P802.1d, LLC, @@ -15388,477 +18151,531 @@ Description: cette liste de diffusion fournit un forum de discussion au fenêtre transparent au réseau, implémentation de protocoles, vérification de protocoles, tests de conformité et outils utilisés dans la maintenance ou dans le développement des systèmes de commutation de paquets. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[mumbaiinternetgroup]{http://groups.yahoo.com/group/mumbaiinternetgroup} -\end_inset +\end_inset -\newline +\newline Description: Ce forum discutera des problèmes et des développements actuels concernant Internet dans la région de l'Asie pacifique. Cela couvrira IPv4, IPv6, le DNS multilingue, les numéros de systèmes autonomes , la gouvernance Internet et bien plus... -\layout Itemize +\end_layout +\begin_layout Itemize de.comm.protocols.tcp-ip -\newline +\newline Description: Umstellung auf IPv6 -\newline +\newline Source: \begin_inset LatexCommand \url[Chartas der Newsgruppen in de.*]{http://www.faqs.org/faqs/de-newsgroups/chartas/index.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Groupe Google: \begin_inset LatexCommand \url[comp.protocols.tcp-ip]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=comp.protocols.tcp-ip} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Groupe Google: \begin_inset LatexCommand \url[linux.debian.maint.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=linux.debian.maint.ipv6} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Groupe Google: \begin_inset LatexCommand \url[microsoft.public.platformsdk.networking.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=microsoft.public.platformsdk.networking.ipv6} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Groupe Google: \begin_inset LatexCommand \url[fa.openbsd.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=fa.openbsd.ipv6} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlinetesttools} -\end_inset +\end_inset Outils en ligne -\layout Subsection +\end_layout +\begin_layout Subsection Outils de test -\layout Itemize +\end_layout +\begin_layout Itemize finger, nslookup, ping, traceroute, whois: \begin_inset LatexCommand \url[Centre de ressources IPv6 britanique / la page de test]{http://www.cs-ipv6.lancs.ac.uk/ipv6/testing/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize ping, traceroute, tracepath, whois 6bone, DNS: \begin_inset LatexCommand \url[JOIN / outils de test]{http://www.join.uni-muenster.de/lab/testtools.html} -\end_inset +\end_inset (en langue allemande seulement, mais en l'occurrence cela ne devrait pas être un problème pour les non germanistes) -\layout Itemize +\end_layout +\begin_layout Itemize traceroute6, whois: \begin_inset LatexCommand \url[IPng.nl]{http://www.ipng.nl/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english Vérificateur de résolution AAAA \begin_inset LatexCommand \url[http://www.cnri.dit.ie/cgi-bin/check_aaaa.pl]{http://www.cnri.dit.ie/cgi-bin/check_aaaa.pl} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english Outils divers : \begin_inset LatexCommand \url[IPv6tools]{http://www.ipv6tools.com/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang english - \begin_inset LatexCommand \url[Outil d'analyse d'adresse IPv6]{http://doc.tavian.com/ipv6util/index.htm} -\end_inset +\end_inset (assez similaire à l'option d'information d'ipv6calc) -\layout Subsection +\end_layout +\begin_layout Subsection Recherche d'information -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Le bureau d'enregistrement 6BONE]{http://www.kessens.com/~david/6bone/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Liste mondiale d'attribution de tout bloc d'adresses IPv6]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6allocs.html} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Outils d'observation des réseaux IPv6 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Observer IPv6 chez SURRIEL]{http://linux.uninet.edu/lg/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Observer IPv6 chez DRENv6]{http://www.v6.dren.net/lg/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Applications venant en aide -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Calculatrice de préfixe IPv6]{http://www.tdoi.org/prefcalc.php} -\end_inset +\end_inset par \begin_inset LatexCommand \url[TDOI]{http://www.tdoi.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Vérificateur d'enregistrement DNS]{http://www.maths.tcd.ie/cgi-bin/check_dns.pl} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-trainingsandseminars} -\end_inset +\end_inset Pratique, séminaires -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[formation et atelier IPv6]{http://www.aerasec.de/workshops/ipv6.html} -\end_inset +\end_inset , AERAsec, Allemagne (en langue allemande pour l'instant) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migrer vers IPv6]{http://www.seminarinformation.com/wconnect/wc.dll?sis~details0~307} -\end_inset +\end_inset , Learning Tree International -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Formation professionnelle CIW la maintenance Internet CBT CD]{http://www.e-trainonline.com/html/ciw_internetworking_profession.html#IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Pages concernant la formation]{http://www.trainingpages.net/x/category.html?kw=125} -\end_inset +\end_inset , Royaume-Uni - recherche à partir du mot clé \begin_inset Quotes sld -\end_inset +\end_inset IPv6 \begin_inset Quotes srd -\end_inset +\end_inset (13 cours, au 22.12.2002) -\layout Standard +\end_layout +\begin_layout Standard Quelque chose manque? Les suggestions sont les bienvenues! -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlinediscovery} -\end_inset +\end_inset 'La découverte en ligne'... -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[IPv6: Addressing The Needs Of the Future]{http://www.amazon.com/exec/obidos/tg/detail/-/B00006334Y/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset [DOWNLOAD: PDF] -\newline +\newline par le groupe Yankee (Auteur) -\newline +\newline Prix: $595.00 -\newline -Edition: e-book (Acrobat Reader) -\newline +\newline +Edition: e-book + (Acrobat Reader) +\newline Pages: 3 (trois) -\newline -Editeur: MarketResearch.com; ISBN B00006334Y; (1 novembre 2001) -\newline +\newline +Editeur: MarketResearch.com; ISBN B00006334Y; + (1 novembre 2001) +\newline -\layout Standard +\end_layout +\begin_layout Standard ;-) Le nombre de copies serait intéressant à connaître... -\newline +\newline -\layout Chapter +\end_layout +\begin_layout Chapter Historique des Révisions / Crédits / La Fin -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{revision-history} -\end_inset +\end_inset Historique des Révisions -\layout Subsection +\end_layout +\begin_layout Subsection Révisions 0.x -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La version anglo-saxonne (document original de Peter Bieringer) -\layout Standard +\end_layout +\begin_layout Standard Un historique des modifications de la version anglo-saxonne originale peut être trouvé ici: \begin_inset LatexCommand \url[TLDP / Linux+IPv6-HOWTO / Revision History]{http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/revision-history.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection La version francophone -\layout Description +\end_layout +\begin_layout Description 0.49.fr.1 26-02-2006/MB: Mise à jour au profit de la révision 0.49. -\layout Description +\end_layout +\begin_layout Description 0.48.1.fr.1 20-01-2005/MB: Mise à jour au profit de la révision 0.48.1. -\layout Description +\end_layout +\begin_layout Description 0.47.fr.1 05-09-2004/MB: Mise à jour au profit de la révision 0.47. -\layout Description +\end_layout +\begin_layout Description 0.45.1.fr.1 14-03-2004/MB: Mise à jour au profit de la révision 0.45.1. Corrections et améliorations diverses. -\layout Description +\end_layout +\begin_layout Description 0.44.fr.1 05-09-2003/MB: Mise à jour au profit de la révision 0.44. A cette occasion, une révision non systématique est réalisée. -\layout Description +\end_layout +\begin_layout Description 0.43.2.fr.2 17-07-2003/MB: Correction de quelques coquilles, amélioration de la traduction de quelques passages. -\layout Description +\end_layout +\begin_layout Description 0.43.2.fr.1 20-06-2003/MB: Mise à jour au profit de la révision 0.43.2. A cette occasion, une révision non systématique est réalisée. -\layout Description +\end_layout +\begin_layout Description 0.41.1.fr.2 06-06-2003/MB: Première révision générale; à savoir, correction de coquilles, bogues, fautes d'orthographe, -\emph on +\emph on etc. -\layout Description +\end_layout +\begin_layout Description 0.41.1.fr.1 09-05-2003/MB: Cette version est la première. Son contenu, rédigé sur LyX version 1.3.2, est basé sur celui de la version anglo-saxonne 0.41.1. Cependant un certain nombre de mes suggestions ( -\emph on +\emph on Michel Boucey -\emph default +\emph default ) ayant été prises en compte par Peter Bieringer lors du travail de traduction, il existe d'ores et déjà, ça et là, des modifications mineures qui seront présentes dans les futures versions du document original. Le suffixe .fr.x indique le numéro de révision de la traduction francophone. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{credits} -\end_inset +\end_inset Crédits -\layout Standard +\end_layout +\begin_layout Standard Le moyen le plus rapide d'être ajouté à cette sympathique liste est de m'envoyer des corrections (de bogue), et/ou mises à jour ;-). -\layout Standard +\end_layout +\begin_layout Standard Si vous voulez réaliser un réexamen important, vous pouvez utiliser le fichier natif LyX (voir \begin_inset LatexCommand \ref[le document original]{general-original-source} -\end_inset +\end_inset ) et envoyez les diffs s'y rapportant, car les diffs en rapport au code SGML ne sont pas d'une grande utilité ( -\emph on +\emph on NdT -\emph default +\emph default : merci d'envoyer les diffs à l'adresse ). -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{major-credits} -\end_inset +\end_inset Crédits majeurs -\layout Itemize +\end_layout +\begin_layout Itemize David Ranch : pour m'avoir encouragé à écrire cet HOWTO, pour ses commentaires sur quelques premières des révisions, et ses contributions à de différents résultats de test IPv6 sur mon site web IPv6. Mais aussi pour ses relectures et suggestions. -\layout Itemize +\end_layout +\begin_layout Itemize Pekka Savola : pour ses relectures essentielles, apports et suggestions. -\layout Itemize +\end_layout +\begin_layout Itemize Martin F. Krafft : pour la vérification orthographique et sa relecture générale du document. -\layout Itemize +\end_layout +\begin_layout Itemize John Ronan : pour la vérification orthographiq ue. -\layout Itemize +\end_layout +\begin_layout Itemize Georg Käfer : pour la détection de la création défectueuse au format PDF (problème réglé maintenant par Greg Ferguson, travaillant au LDP), les références de livres en langue allemande, une grande liste d'URL, leurs vérifications, une grande quantité de suggestions, de corrections, de contributions, et pour sa traduction en langue allemande. -\layout Itemize +\end_layout +\begin_layout Itemize Michel Boucey : pour la correction orthographique, la découverte de liens brisés, sa contribution grâce à ses suggestions, ses apports de nouveaux liens, et pour sa traduction en langue française. -\layout Itemize +\end_layout +\begin_layout Itemize Michele Ferritto : pour avoir découvert des bogues, et pour sa traduction en langue italienne. -\layout Itemize +\end_layout +\begin_layout Itemize Daniel Roesen : pour ses vérifications orthographiques. -\layout Subsection +\end_layout +\begin_layout Subsection Autres crédits -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Crédits relatifs aux documents techniques -\layout Standard +\end_layout +\begin_layout Standard Ecrire, en étant débutant, un HOWTO LDP (dans LyX et en exportant le travail vers DocBook pour se conformer au SGML) n'est pas si facile que certains pourraient le dire. Il y a d'étranges pièges... malgré tout, merci: -\layout Itemize +\end_layout +\begin_layout Itemize Aux auteurs du \begin_inset LatexCommand \url[Guide de l'auteur LDP]{http://www.tldp.org/LDP/LDP-Author-Guide/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize A B. Guillon: pour l' \begin_inset LatexCommand \url[HOWTO DocBook avec LyX]{http://perso.libertysurf.fr/bgu/doc/db4lyx/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{content-related-credits} -\end_inset +\end_inset Crédits relatifs à la traduction francophone -\layout Standard +\end_layout +\begin_layout Standard Les crédits concernant les corrections/suggestions apportées à la version francophone viendront ici (peut-être un jour...). Merci par avance pour vos contributions. -\layout Section +\end_layout +\begin_layout Section La Fin -\layout Standard +\end_layout +\begin_layout Standard Merci de m'avoir lu. Dans l'espoir que cela puisse aider! -\layout Standard +\end_layout +\begin_layout Standard Si vous avez des questions, souscrivez à la bonne \begin_inset LatexCommand \ref[liste de diffusion]{information-maillists} -\end_inset +\end_inset et décrivez votre problème en fournissant autant d'information que possible. -\the_end +\end_layout + +\end_body +\end_document diff --git a/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.lyx b/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.lyx index 22d02690..7a98a463 100644 --- a/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.lyx +++ b/LDP/users/Peter-Bieringer/Linux+IPv6-HOWTO.lyx @@ -1,5 +1,7 @@ -#LyX 1.3 created this file. For more info see http://www.lyx.org/ -\lyxformat 221 +#LyX 1.4.1 created this file. For more info see http://www.lyx.org/ +\lyxformat 245 +\begin_document +\begin_header \textclass docbook-book \begin_preamble @@ -10,753 +12,942 @@ \fontscheme default \graphics default \paperfontsize default -\spacing single -\papersize Default -\paperpackage a4 -\use_geometry 0 -\use_amsmath 0 -\use_natbib 0 -\use_numerical_citations 0 +\spacing single +\papersize default +\use_geometry false +\use_amsmath 1 +\cite_engine basic +\use_bibtopic false \paperorientation portrait \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \defskip medskip \quotes_language swedish -\quotes_times 2 \papercolumns 1 \papersides 1 \paperpagestyle default +\tracking_changes false +\output_changes true +\end_header -\layout Title -\added_space_top vfill \added_space_bottom vfill +\begin_body + +\begin_layout Standard +\begin_inset VSpace vfill +\end_inset + + +\end_layout + +\begin_layout Title Linux IPv6 HOWTO (en) -\layout SGML +\end_layout + +\begin_layout Standard +\begin_inset VSpace vfill +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout FirstName +\end_layout +\end_inset + + +\end_layout + +\begin_layout Standard Peter -\layout Surname +\end_layout +\begin_layout Standard Bieringer -\layout SGML +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard
pb at bieringer dot de
 -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard -\layout SGML +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard + + Release 0.49.1 2006-06-13 PB +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard Release 0.49 2005-10-03 PB See -\begin_inset LatexCommand \ref[revision history]{revision-history} +tials>PB +\end_layout -\end_inset +\end_inset - for more -\layout SGML + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status inlined + +\begin_layout Standard Release 0.48.1 2005-01-15 PB See -\begin_inset LatexCommand \ref[revision history]{revision-history} +itials>PB +\end_layout -\end_inset +\end_inset - for more -\layout SGML - Release 0.48 2005-01-11 PB See -\begin_inset LatexCommand \ref[revision history]{revision-history} +\end_layout -\end_inset +\begin_layout Standard +\begin_inset ERT +status inlined - for more -\layout SGML +\begin_layout Standard Release 0.47.1 2005-01-01 PB See -\begin_inset LatexCommand \ref[revision history]{revision-history} +itials>PB +\end_layout -\end_inset +\end_inset - for more -\layout SGML - Release 0.47 2004-08-30 PB See -\begin_inset LatexCommand \ref[revision history]{revision-history} +\end_layout -\end_inset +\begin_layout Standard +\begin_inset ERT +status inlined - for more -\layout SGML - - Release 0.46 2004-03-16 PB See -\begin_inset LatexCommand \ref[revision history]{revision-history} - -\end_inset - - for more -\layout SGML - -\layout SGML - -\layout SGML +\begin_layout Standard -\layout Abstract +\end_layout +\end_inset + + +\end_layout + +\begin_layout Abstract The goal of the Linux IPv6 HOWTO is to answer both basic and advanced questions about IPv6 on the Linux operating system. This HOWTO will provide the reader with enough information to install, configure, and use IPv6 applications on Linux machines. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-general} -\end_inset +\end_inset General -\layout Comment +\end_layout +\begin_layout Standard +\begin_inset Note Comment +status collapsed + +\begin_layout Standard CVS-ID: $Id$ -\layout Standard +\end_layout +\end_inset + + +\end_layout + +\begin_layout Standard Information about available translations you will find in section \begin_inset LatexCommand \ref[Translations]{general-translations} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-copright} -\end_inset +\end_inset Copyright, license and others -\layout Subsection +\end_layout +\begin_layout Subsection Copyright -\layout Standard +\end_layout -Written and Copyright (C) 2001-2005 by Peter Bieringer -\layout Subsection +\begin_layout Standard +Written and Copyright (C) 2001-2006 by Peter Bieringer +\end_layout +\begin_layout Subsection License -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold This Linux IPv6 HOWTO is published under GNU GPL version 2 -\series default +\series default : -\newline +\newline -\newline +\newline -\newline +\newline -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard The Linux IPv6 HOWTO, a guide how to configure and use IPv6 on Linux systems. -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Copyright (C) 2001-2004 Peter Bieringer -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard This documentation is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. -\layout Standard +\end_layout +\begin_layout Standard This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. -\layout Standard +\end_layout +\begin_layout Standard You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -\layout Subsection +\end_layout +\begin_layout Subsection About the author -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Internet/IPv6 history of the author -\layout Itemize +\end_layout +\begin_layout Itemize 1993: I got in contact with the Internet using console based e-mail and news client (e.g. look for \begin_inset Quotes sld -\end_inset +\end_inset e91abier \begin_inset Quotes srd -\end_inset +\end_inset on \begin_inset LatexCommand \url[groups.google.com]{http://groups.google.com/} -\end_inset +\end_inset , that's me). -\layout Itemize +\end_layout +\begin_layout Itemize 1996: I got a request for designing a course on IPv6, including a workshop with the Linux operating system. -\layout Itemize +\end_layout +\begin_layout Itemize 1997: Started writing a guide on how to install, configure and use IPv6 on Linux systems, called \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset (see \begin_inset LatexCommand \url[IPv6 & Linux - HowTo/History]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-0.html#history} -\end_inset +\end_inset for more information). -\layout Itemize +\end_layout +\begin_layout Itemize 2001: Started writing this new Linux IPv6 HOWTO. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Contact -\layout Standard +\end_layout +\begin_layout Standard The author can be contacted via e-mail at and also via his \begin_inset LatexCommand \url[homepage]{http://www.bieringer.de/pb/} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard He's currently living in Munich [northern part of Schwabing] / Bavaria / Germany (south) / Europe (middle) / Earth (surface/mainland). -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-category} -\end_inset +\end_inset Category -\layout Standard +\end_layout +\begin_layout Standard This HOWTO should be listed in category \begin_inset Quotes sld -\end_inset +\end_inset -\emph on +\emph on Networking -\emph default +\emph default / -\emph on +\emph on Protocols -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Section +\end_layout +\begin_layout Section Version, History and To-Do -\layout Subsection +\end_layout +\begin_layout Subsection Version -\layout Standard +\end_layout +\begin_layout Standard The current version is shown at the beginning of the document. -\layout Standard +\end_layout +\begin_layout Standard For other available versions/translations see also \begin_inset LatexCommand \url[http://www.bieringer.de/linux/IPv6/]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection History -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Major history -\layout Standard +\end_layout +\begin_layout Standard 2001-11-30: Starting to design new HOWTO. -\layout Standard +\end_layout +\begin_layout Standard 2002-01-02: A lot of content completed, first public release of chapter 1 (version 0.10). -\layout Standard +\end_layout +\begin_layout Standard 2002-01-14: More completed, some reviews, public release of the whole document (version 0.14). -\layout Standard +\end_layout +\begin_layout Standard 2002-08-16: Polish translation is in progress -\layout Standard +\end_layout +\begin_layout Standard 2002-10-31: Chinese translation is available (see \begin_inset LatexCommand \ref[Translations]{general-translations} -\end_inset +\end_inset for more) -\layout Standard +\end_layout +\begin_layout Standard 2002-11-10: German translation is in progress -\layout Standard +\end_layout +\begin_layout Standard 2003-02-10: German translation is available -\layout Standard +\end_layout +\begin_layout Standard 2003-04-09: French translation is in progress -\layout Standard +\end_layout +\begin_layout Standard 2003-05-09: French translation is available -\layout Standard +\end_layout +\begin_layout Standard 2003-08-15: Spanish translation is in progress -\layout Standard +\end_layout +\begin_layout Standard 2003-10-16: Italian translation is in progress -\layout Standard +\end_layout +\begin_layout Standard 2004-03-12: Italian translation is available -\layout Standard +\end_layout +\begin_layout Standard 2004-06-18: Greek translation is in progress -\layout Standard +\end_layout +\begin_layout Standard 2004-08-29: Spanish translation is still NOT in progress -\layout Standard +\end_layout +\begin_layout Standard 2005-07-25: Turkish translation is availble -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Full history -\layout Standard +\end_layout +\begin_layout Standard See \begin_inset LatexCommand \ref[revision history]{revision-history} -\end_inset +\end_inset at the end of this document. -\layout Subsection +\end_layout +\begin_layout Subsection To-Do -\layout Itemize +\end_layout +\begin_layout Itemize Fill in missing content -\layout Itemize +\end_layout +\begin_layout Itemize Finishing grammar checking -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{general-translations} -\end_inset +\end_inset Translations -\layout Standard +\end_layout +\begin_layout Standard 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 - also do not translate the full section about available translations, can be run out-of-date, add an URL to this section here in the English howto. -\layout Standard +\end_layout +\begin_layout Standard 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. Translations always have to use the English version as source. -\layout Subsection +\end_layout +\begin_layout Subsection To language -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Chinese -\layout Standard +\end_layout +\begin_layout Standard A Chinese translation by Burma Chen (announced to me at 2002-10-31) can be found on the CLDP: \begin_inset LatexCommand \url[http://cldp.linuxforum.net/Linux-IPv6-HOWTO.html (broken)]{http://cldp.linuxforum.net/Linux-IPv6-HOWTO.html} -\end_inset +\end_inset . It's a snapshot translation, don't know whether kept up-to-date. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Polish -\layout Standard +\end_layout +\begin_layout Standard Since 2002-08-16 a Polish translation was started and is still in progress by Lukasz Jokiel . Taken source: CVS-version 1.29 of LyX file, which was source for howto version 0.27. Status is still work-in-progress (2004-08-30). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection German -\layout Standard +\end_layout +\begin_layout Standard With 2002-11-10 a German translation was started by Georg Käfer and the first public version was published 2003-02-10. It's originally available on Deep Space 6 at \begin_inset LatexCommand \url[http://mirrors.deepspace6.net/Linux+IPv6-HOWTO-de/]{http://mirrors.deepspace6.net/Linux+IPv6-HOWTO-de/} -\end_inset +\end_inset (mirrored e.g. on \begin_inset LatexCommand \url[http://mirrors.bieringer.de/Linux+IPv6-HOWTO-de/]{http://mirrors.bieringer.de/Linux+IPv6-HOWTO-de/} -\end_inset +\end_inset ). This version will stay up-to-date as much as possible. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection French -\layout Standard +\end_layout +\begin_layout Standard With 2003-04-09 a French translation was started by Michel Boucey and the first public version was published 2003-05-09. It's originally available on Deep Space 6 at \begin_inset LatexCommand \url[http://mirrors.deepspace6.net/Linux+IPv6-HOWTO-fr/]{http://mirrors.deepspace6.net/Linux+IPv6-HOWTO-fr/} -\end_inset +\end_inset (mirrored e.g. on \begin_inset LatexCommand \url[http://mirrors.bieringer.de/Linux+IPv6-HOWTO-fr/]{http://mirrors.bieringer.de/Linux+IPv6-HOWTO-fr/} -\end_inset +\end_inset ). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Spanish -\layout Standard +\end_layout +\begin_layout Standard The first try of a Spanish translations ran into ressource problem, currently I got two other ones, status will be updated when more information is available. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Italian -\layout Standard +\end_layout +\begin_layout Standard With 2003-10-16 a Italian translation was started by Michele Ferritto for the \begin_inset LatexCommand \url[ILDP]{http://ildp.pluto.linux.it/} -\end_inset +\end_inset (Italian Linux Documentation Project) and the first public version was published 2004-03-12. It's originally available on the ILDP at \begin_inset LatexCommand \url[http://it.tldp.org/HOWTO/Linux+IPv6-HOWTO/]{http://it.tldp.org/HOWTO/Linux+IPv6-HOWTO/} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Japanese -\layout Standard +\end_layout +\begin_layout Standard On 2003-05-14 Shino Taketani send me a note that he planned to translate the HowTo into Japanese. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Greek -\layout Standard +\end_layout +\begin_layout Standard On 2004-06-18 Nikolaos Tsarmpopoulos send me a note that he planned to translate the HowTo into Greek. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Turkish -\layout Standard +\end_layout +\begin_layout Standard On 2005-07-18 Necdet Yucel send me a note that a Turkish translation is available. It's a snapshot translation and can be found at \begin_inset LatexCommand \url[http://docs.comu.edu.tr/homemade/Linux+IPv6-HOWTO-tr.html]{http://docs.comu.edu.tr/homemade/Linux+IPv6-HOWTO-tr.html} -\end_inset +\end_inset . -\layout Section +\end_layout +\begin_layout Section Technical -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{general-original-source} -\end_inset +\end_inset Original source of this HOWTO -\layout Standard +\end_layout +\begin_layout Standard This HOWTO is currently written with LyX version 1.2.0 on a Red Hat Linux 7.3 system with template SGML (DocBook book). It's available on \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset for contribution. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Code line wrapping -\layout Standard +\end_layout +\begin_layout Standard Code line wrapping is done using selfmade utility \begin_inset Quotes sld -\end_inset +\end_inset lyxcodelinewrapper.pl \begin_inset Quotes srd -\end_inset +\end_inset , you can get it from CVS for your own usage: \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection SGML generation -\layout Standard +\end_layout +\begin_layout Standard SGML is generated using export function in LyX. -\layout Standard +\end_layout +\begin_layout Standard Also some fixes are have to be made to create proper SGML code (see also here for the Perl programs \begin_inset LatexCommand \url[TLDP-CVS / users / Peter-Bieringer]{http://cvsview.tldp.org/index.cgi/LDP/users/Peter-Bieringer/} -\end_inset +\end_inset ): -\layout Itemize +\end_layout +\begin_layout Itemize Export of LyX table does not create proper \begin_inset Quotes sld -\end_inset +\end_inset colspan \begin_inset Quotes srd -\end_inset +\end_inset tags - tool for fixing: \begin_inset Quotes sld -\end_inset +\end_inset sgmllyxtabletagfix.pl \begin_inset Quotes srd -\end_inset +\end_inset (fixed since LyX 1.2.0) -\layout Itemize +\end_layout +\begin_layout Itemize LyX sometimes uses special left/right entities for quotes instead the normal one, which will still exist in generated HTML. Some browsers don't parse this very well (known: Opera 6 TP 2 or Konqueror) - tool for fixing: \begin_inset Quotes sld -\end_inset +\end_inset sgmllyxquotefix.pl \begin_inset Quotes srd -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection On-line references to the HTML version of this HOWTO (linking/anchors) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Master index page -\layout Standard +\end_layout +\begin_layout Standard Generally, a reference to the master index page is recommended. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Dedicated pages -\layout Standard +\end_layout +\begin_layout Standard Because the HTML pages are generated out of the SGML file, the HTML filenames turn out to be quite random. However, some pages are tagged in LyX, resulting in static names. These tags are useful for references and shouldn't be changed in the future. -\layout Standard +\end_layout +\begin_layout Standard If you think that I have forgotten a tag, please let me know, and I will add it. -\layout Section +\end_layout +\begin_layout Section Preface -\layout Standard +\end_layout +\begin_layout Standard Some things first: -\layout Subsection +\end_layout +\begin_layout Subsection How many versions of a Linux & IPv6 related HOWTO are floating around? -\layout Standard +\end_layout +\begin_layout Standard Including this, there are three (3) HOWTO documents available. Apologies, if that is too many ;-) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Linux IPv6 FAQ/HOWTO (outdated) -\layout Standard +\end_layout +\begin_layout Standard The first IPv6 related document was written by -\emph on +\emph on Eric Osborne -\emph default +\emph default and called \begin_inset LatexCommand \url[Linux IPv6 FAQ/HOWTO]{http://www.linuxhq.com/IPv6/} -\end_inset +\end_inset (please use it only for historical issues). -\series bold +\series bold Latest -\series default +\series default -\series bold +\series bold version -\series default +\series default was 3.2.1 released July, 14 -\series bold +\series bold 1997 -\series default +\series default . -\layout Standard +\end_layout +\begin_layout Standard Please help: if someone knows the date of birth of this HOWTO, please send me an e-mail (information will be needed in \begin_inset Quotes sld -\end_inset +\end_inset history \begin_inset Quotes srd -\end_inset +\end_inset ). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 & Linux - HowTo (maintained) -\layout Comment +\end_layout +\begin_layout Standard +\begin_inset Note Comment +status collapsed + +\begin_layout Standard This HOWTO is really named \begin_inset Quotes sld -\end_inset +\end_inset HowTo \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\end_inset + + +\end_layout + +\begin_layout Standard There exists a second version called \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset written by me ( -\emph on +\emph on Peter Bieringer -\emph default +\emph default ) in pure HTML. -\series bold +\series bold It was born -\series default +\series default April -\series bold +\series bold 1997 -\series default +\series default and the first English version was published in June 1997. I will continue to -\series bold +\series bold maintain -\series default +\series default it, but it will slowly fade (but not full) in favour of the Linux IPv6 HOWTO you are currently reading. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Linux IPv6 HOWTO (this document) -\layout Standard +\end_layout +\begin_layout Standard Because the \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset is written in pure HTML it's not really compatible with the \begin_inset LatexCommand \url[The Linux Documentation Project (TLDP)]{http://www.tldp.org/} -\end_inset +\end_inset . I ( -\emph on +\emph on Peter Bieringer -\emph default +\emph default ) got a request in late November 2001 to rewrite the \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset in SGML. However, because of the discontinuation of that HOWTO ( \begin_inset LatexCommand \url[Future of IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-0.html#history} -\end_inset +\end_inset ), 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 @@ -765,326 +956,388 @@ Peter Bieringer the second HOWTO ( \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset ). -\layout Section +\end_layout +\begin_layout Section Used terms, glossary and shortcuts -\layout Subsection +\end_layout +\begin_layout Subsection Network related -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 10 Well known decimal number system, represent any value with digit 0-9. -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 16 Usually used in lower and higher programming languages, known also as hexadecimal number system, represent any value with digit 0-9 and char A-F (case insensitive). -\layout Description +\end_layout -Base\SpecialChar ~ +\begin_layout Description +Base\InsetSpace ~ 85 Representation of a value with 85 different digits/chars, this can lead to shorter strings but never seen in the wild. -\layout Description +\end_layout +\begin_layout Description Bit Smallest storage unit, on/true (1) or off/false (0) -\layout Description +\end_layout +\begin_layout Description Byte Mostly a collection of 8 (but not really a must - see older computer systems) bits -\layout Description +\end_layout +\begin_layout Description Device Here, hardware of network connection, see also NIC -\layout Description +\end_layout -Dual\SpecialChar ~ -homed\SpecialChar ~ +\begin_layout Description +Dual\InsetSpace ~ +homed\InsetSpace ~ host A dual homed host is a node with two network (physical or virtual) interfaces on two different links, but does not forward any packets between the interfaces. -\layout Description +\end_layout +\begin_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. -\layout Description +\end_layout +\begin_layout Description Interface Mostly same as \begin_inset Quotes sld -\end_inset +\end_inset device \begin_inset Quotes srd -\end_inset +\end_inset , see also NIC -\layout Description +\end_layout -IP\SpecialChar ~ +\begin_layout Description +IP\InsetSpace ~ Header Header of an IP packet (each network packet has a header, kind of is depending on network layer) -\layout Description +\end_layout +\begin_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 +\end_layout +\begin_layout Description Node A node is a host or a router. -\layout Description +\end_layout +\begin_layout Description Octet A collection of 8 real bits, today also similar to \begin_inset Quotes sld -\end_inset +\end_inset byte \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Description +\end_layout +\begin_layout Description Port Information for the TCP/UDP dispatcher (layer 4) to transport information to upper layers -\layout Description +\end_layout +\begin_layout Description Protocol Each network layer contains mostly a protocol field to make life easier on dispatching transported information to upper layer, seen in layer 2 (MAC) and 3 (IP) -\layout Description +\end_layout +\begin_layout Description Router A router is a node with two or more network (physical or virtual) interfaces, capable of forwarding packets between the interfaces. -\layout Description +\end_layout +\begin_layout Description Socket An IP socket is defined by source and destination IP addresses and Ports and (binding) -\layout Description +\end_layout +\begin_layout Description Stack Network related a collection of layers -\layout Description +\end_layout +\begin_layout Description Subnetmask IP networks uses bit masks to separate local networks from remote ones -\layout Description +\end_layout +\begin_layout Description Tunnel A tunnel is typically a point-to-point connection over which packets are exchanged which carry the data of another protocol, e.g. an IPv6-in-IPv4 tunnel. -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{Glossar} -\end_inset +\end_inset Shortcuts -\layout Description +\end_layout +\begin_layout Description ACL Access Control List -\layout Description +\end_layout +\begin_layout Description API Application Programming Interface -\layout Description +\end_layout +\begin_layout Description ASIC Application Specified Integrated Circuit -\layout Description +\end_layout +\begin_layout Description BSD Berkeley Software Distribution -\layout Description +\end_layout +\begin_layout Description CAN-Bus Controller Area Network Bus (physical bus system) -\layout Description +\end_layout +\begin_layout Description ISP Internet Service Provider -\layout Description +\end_layout +\begin_layout Description KAME Project - a joint effort of six companies in Japan to provide a free IPv6 and IPsec (for both IPv4 and IPv6) stack for BSD variants to the world \begin_inset LatexCommand \url[www.kame.net]{http://www.kame.net/} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description LIR Local Internet Registry -\layout Description +\end_layout +\begin_layout Description NIC Network Interface Card -\layout Description +\end_layout +\begin_layout Description RFC Request For Comments - set of technical and organizational notes about the Internet -\layout Description +\end_layout +\begin_layout Description USAGI UniverSAl playGround for Ipv6 Project - works to deliver the production quality IPv6 protocol stack for the Linux system. -\layout Subsection +\end_layout +\begin_layout Subsection Document related -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Long code line wrapping signal char -\layout Standard +\end_layout +\begin_layout Standard The special character \begin_inset Quotes sld -\end_inset +\end_inset ¬ \begin_inset Quotes srd -\end_inset +\end_inset is used for signaling that this code line is wrapped for better viewing in PDF and PS files. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Placeholders -\layout Standard +\end_layout +\begin_layout Standard In generic examples you will sometimes find the following: -\layout Code +\end_layout +\begin_layout Code -\layout Standard +\end_layout +\begin_layout Standard For real use on your system command line or in scripts this has to be replaced with relevant content (removing the < and > of course), the result would be e.g. -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Commands in the shell -\layout Standard +\end_layout +\begin_layout Standard Commands executable as non-root user begin with $, e.g. -\layout Code +\end_layout +\begin_layout Code $ whoami -\layout Standard +\end_layout +\begin_layout Standard Commands executable as root user begin with #, e.g. -\layout Code +\end_layout +\begin_layout Code # whoami -\layout Section +\end_layout +\begin_layout Section Requirements for using this HOWTO -\layout Subsection +\end_layout +\begin_layout Subsection Personal prerequisites -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Experience with Unix tools -\layout Standard +\end_layout +\begin_layout Standard You should be familiar with the major Unix tools e.g. -\emph on +\emph on grep -\emph default +\emph default , -\emph on +\emph on awk -\emph default +\emph default , -\emph on +\emph on find -\emph default +\emph default , ... , and know about their most commonly used command-line options. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Experience with networking theory -\layout Standard +\end_layout +\begin_layout Standard You should know about layers, protocols, addresses, cables, plugs, etc. If you are new to this field, here is one good starting point for you: \begin_inset LatexCommand \url[linuxports/howto/intro_to_networking]{http://www.linuxports.com/howto/intro_to_networking/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Experience with IPv4 configuration -\layout Standard +\end_layout +\begin_layout Standard You should definitely have some experience in IPv4 configuration, otherwise it will be hard for you to understand what is really going on. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Experience with the Domain Name System (DNS) -\layout Standard +\end_layout +\begin_layout Standard Also you should understand what the Domain Name System (DNS) is, what it provides and how to use it. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Experience with network debugging strategies -\layout Standard +\end_layout +\begin_layout Standard You should at least understand how to use -\emph on +\emph on tcpdump -\emph default +\emph default and what -\emph on +\emph on -\emph default +\emph default it can show you. Otherwise, network debugging will very difficult for you. -\layout Subsection +\end_layout +\begin_layout Subsection Linux operating system compatible hardware -\layout Standard +\end_layout +\begin_layout Standard Surely you wish to experiment with real hardware, and not only read this HOWTO to fall asleep here and there. ;-7) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-basics} -\end_inset +\end_inset Basics -\layout Section +\end_layout +\begin_layout Section What is IPv6? -\layout Standard +\end_layout +\begin_layout Standard IPv6 is a new layer 3 protocol (see \color red \begin_inset LatexCommand \url[linuxports/howto/intro_to_networking/ISO - OSI Model]{http://www.linuxports.com/howto/intro_to_networking/c4412.htm#PAGE103HTML} -\end_inset +\end_inset -\color default +\color none ) which will supersede IPv4 (also known as IP). IPv4 was designed long time ago ( \begin_inset LatexCommand \url[RFC 760 / Internet Protocol]{http://www.faqs.org/rfcs/rfc760.html} -\end_inset +\end_inset from January 1980) and since its inception, there have been many requests for more addresses and enhanced capabilities. Latest RFC is \begin_inset LatexCommand \url[RFC 2460 / Internet Protocol Version 6 Specification]{http://www.faqs.org/rfcs/rfc2460.html} -\end_inset +\end_inset . Major changes in IPv6 are the redesign of the header, including the increase @@ -1092,120 +1345,144 @@ IPv6 is a new layer 3 protocol (see Because layer 3 is responsible for end-to-end packet transport using packet routing based on addresses, it must include the new IPv6 addresses (source and destination), like IPv4. -\layout Standard +\end_layout +\begin_layout Standard For more information about the IPv6 history take a look at older IPv6 related RFCs listed e.g. at \begin_inset LatexCommand \url[SWITCH IPv6 Pilot / References]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{basic-history-IPv6-Linux} -\end_inset +\end_inset History of IPv6 in Linux -\layout Standard +\end_layout +\begin_layout Standard The years 1992, 1993 and 1994 of the IPv6 History (in general) are covered by following document: \begin_inset LatexCommand \url[IPv6 or IPng (IP next generation)]{http://www.laynetworks.com/IPv6.htm#CH3} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard To-do: better time-line, more content... -\layout Subsection +\end_layout +\begin_layout Subsection Beginning -\layout Standard +\end_layout +\begin_layout Standard The first IPv6 related network code was added to the Linux kernel 2.1.8 in November 1996 by Pedro Roque. It was based on the BSD API: -\layout Code +\end_layout +\begin_layout Code diff -u --recursive --new-file v2.1.7/linux/include/linux/in6.h -\layout Code +\end_layout +\begin_layout Code ¬ linux/include/linux/in6.h -\layout Code +\end_layout +\begin_layout Code --- v2.1.7/linux/include/linux/in6.h Thu Jan 1 02:00:00 1970 -\layout Code +\end_layout +\begin_layout Code +++ linux/include/linux/in6.h Sun Nov 3 11:04:42 1996 -\layout Code +\end_layout +\begin_layout Code @@ -0,0 +1,99 @@ -\layout Code +\end_layout +\begin_layout Code +/* -\layout Code +\end_layout +\begin_layout Code + * Types and definitions for AF_INET6 -\layout Code +\end_layout +\begin_layout Code + * Linux INET6 implementation -\layout Code +\end_layout +\begin_layout Code + * + * Authors: -\layout Code +\end_layout +\begin_layout Code + * Pedro Roque <******> -\layout Code +\end_layout +\begin_layout Code + * -\layout Code +\end_layout +\begin_layout Code + * Source: -\layout Code +\end_layout +\begin_layout Code + * IPv6 Program Interfaces for BSD Systems -\layout Code +\end_layout +\begin_layout Code + * -\layout Standard +\end_layout +\begin_layout Standard The shown lines were copied from patch-2.1.8 (e-mail address was blanked on copy&paste). -\layout Subsection +\end_layout +\begin_layout Subsection In between -\layout Standard +\end_layout +\begin_layout Standard Because of lack of manpower, the IPv6 implementation in the kernel was unable to follow the discussed drafts or newly released RFCs. In October 2000, a project was started in Japan, called \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset , whose aim was to implement all missing, or outdated IPv6 support in Linux. It tracks the current IPv6 implementation in FreeBSD made by the \begin_inset LatexCommand \url[KAME project]{http://www.kame.net/} -\end_inset +\end_inset . From time to time they create snapshots against current vanilla Linux kernel sources. -\layout Subsection +\end_layout +\begin_layout Subsection Current -\layout Standard +\end_layout +\begin_layout Standard Unfortunately, the \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset patch is so big, that current Linux networking maintainers are unable to include it in the production source of the Linux kernel 2.4.x series. @@ -1213,182 +1490,224 @@ Unfortunately, the not confirm to all current drafts and RFCs (see \begin_inset LatexCommand \url[IP Version 6 Working Group (ipv6) Charter]{http://www.ietf.org/html.charters/ipv6-charter.html} -\end_inset +\end_inset ). This can cause some interoperability problems with other operating systems. -\layout Subsection +\end_layout +\begin_layout Subsection Future -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[USAGI]{http://www.linux-ipv6.org/} -\end_inset +\end_inset is now making use of the new Linux kernel development series 2.5.x to insert all of their current extensions into this development release. Hopefully the 2.6.x kernel series will contain a true and up-to-date IPv6 implementation. -\layout Section +\end_layout +\begin_layout Section What do IPv6 addresses look like? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left As previously mentioned, IPv6 addresses are 128 bits long. This number of bits generates very high decimal numbers with up to 39 digits: -\layout Code +\end_layout +\begin_layout Code 2^128-1: 340282366920938463463374607431768211455 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left 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 \begin_inset Quotes sld -\end_inset +\end_inset nibble \begin_inset Quotes srd -\end_inset +\end_inset ) are represented by a digit or character from 0-9 and a-f (10-15). This format reduces the length of the IPv6 address to 32 characters. -\layout Code +\end_layout +\begin_layout Code 2^128-1: 0xffffffffffffffffffffffffffffffff -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left This representation is still not very convenient (possible mix-up or loss of single hexadecimal digits), so the designers of IPv6 chose a hexadecimal format with a colon as separator after each block of 16 bits. In addition, the leading " -\family typewriter +\family typewriter 0x -\family default +\family default " (a signifier for hexadecimal values used in programming languages) is removed: -\layout Code +\end_layout +\begin_layout Code 2^128-1: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff -\layout Standard -\align left -A usable address (see address types later) is e.g.: -\layout Code +\end_layout +\begin_layout Standard +\align left +A usable address (see address types later) is e.g.: +\end_layout + +\begin_layout Code 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left For simplifications, leading zeros of each 16 bit block can be omitted: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -> -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100:f101:210:a4ff:fee3:9566 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left One sequence of 16 bit blocks containing only zeroes can be replaced with \begin_inset Quotes eld -\end_inset +\end_inset -\family typewriter +\family typewriter :: -\family default +\family default \begin_inset Quotes eld -\end_inset +\end_inset . But not more than one at a time, otherwise it is no longer a unique representat ion. -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:0:0:0:1 -> 3ffe:ffff:100:f101::1 -\layout Standard -\align left -The biggest reduction is seen by the IPv6 localhost address: -\layout Code +\end_layout +\begin_layout Standard +\align left +The biggest reduction is seen by the IPv6 localhost address: +\end_layout + +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0001 -> ::1 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left There is also a so-called -\emph on +\emph on compact -\emph default +\emph default (base85 coded) representation defined \begin_inset LatexCommand \url[RFC 1924 / A Compact Representation of IPv6 Addresses]{http://www.faqs.org/rfcs/rfc1924.html} -\end_inset +\end_inset (published on 1. April 1996), never seen in the wild, probably an April fool's joke, but here is an example: -\layout Code +\end_layout +\begin_layout Code # ipv6calc --addr_to_base85 3ffe:ffff:0100:f101:0210:a4ff:fee3:9566 -\layout Code +\end_layout +\begin_layout Code Itu&-ZQ82s>J%s99FJXT -\layout Quotation +\end_layout +\begin_layout Quotation Info: -\emph on +\emph on ipv6calc -\emph default +\emph default is an IPv6 address format calculator and converter program and can be found here: \lang ngerman \begin_inset LatexCommand \url[ipv6calc homepage]{http://www.deepspace6.net/projects/ipv6calc.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/projects/ipv6calc.html} -\end_inset +\end_inset ) -\layout Section +\end_layout +\begin_layout Section FAQ (Basics) -\layout Subsection +\end_layout +\begin_layout Subsection Why is the name IPv6 and not IPv5 as successor for IPv4? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left On any IP header, the first 4 bits are reserved for protocol version. So theoretically a protocol number between 0 and 15 is possible: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left 4: is already used for IPv4 -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left 5: is reserved for the Stream Protocol (STP, \begin_inset LatexCommand \url[RFC 1819 / Internet Stream Protocol Version 2]{http://www.faqs.org/rfcs/rfc1819.html} -\end_inset +\end_inset ) (which never really made it to the public) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left The next free number was 6. Hence IPv6 was born! -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 addresses: why such a high number of bits? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left During the design of IPv4, people thought that 32 bits were enough for the world. Looking back into the past, 32 bits were enough until now and will perhaps @@ -1397,12 +1716,15 @@ During the design of IPv4, people thought that 32 bits were enough for the address in the future. Think about mobile phones, cars (including electronic devices on its CAN-bus), toasters, refrigerators, light switches, and so on... -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left So designers have chosen 128 bits, 4 times more in length and 2^96 greater in size than in IPv4 today. -\layout Standard +\end_layout +\begin_layout Standard The usable size is smaller than it may appear however. This is because in the currently defined address schema, 64 bits are used for interface identifiers. @@ -1410,31 +1732,35 @@ The usable size is smaller than it may appear however. Assuming the current strict levels of aggregation (/48, /32, ...), it is still possible to \begin_inset Quotes sld -\end_inset +\end_inset run out \begin_inset Quotes srd -\end_inset +\end_inset of space, but hopefully not in the near future. -\layout Standard +\end_layout +\begin_layout Standard See also for more information \begin_inset LatexCommand \url[RFC 1715 / The H Ratio for Address Assignment Efficiency]{http://www.faqs.org/rfcs/rfc1715.html} -\end_inset +\end_inset and \begin_inset LatexCommand \url[RFC 3194 / The Host-Density Ratio for Address Assignment Efficiency]{http://www.faqs.org/rfcs/rfc3194.html} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 addresses: why so small a number of bits on a new design? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left While, there are (possibly) some people (only know about Jim Fleming...) on the Internet who are thinking about IPv8 and IPv16, their design is far away from acceptance and implementation. @@ -1451,20 +1777,22 @@ While, there are (possibly) some people (only know about Jim Fleming...) on 1500 octets (in special cases: 9k octets using Jumbo frames). Ultimately, it wouldn't be a proper design if 10 % or 20 % of transported data in a Layer-3 packet were used for addresses and not for payload. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-addresstypes} -\end_inset +\end_inset Address types -\layout Standard +\end_layout +\begin_layout Standard Like IPv4, IPv6 addresses can be split into network and host parts using subnet masks. -\layout Standard +\end_layout +\begin_layout Standard IPv4 has shown that sometimes it would be nice, if more than one IP address can be assigned to an interface, each for a different purpose (aliases, multi-cast). @@ -1472,1059 +1800,1302 @@ IPv4 has shown that sometimes it would be nice, if more than one IP address than one IPv6 address to be assigned to an interface. There is currently no limit defined by an RFC, only in the implementation of the IPv6 stack (to prevent DoS attacks). -\layout Standard +\end_layout +\begin_layout Standard Using this large number of bits for addresses, IPv6 defines address types based on some leading bits, which are hopefully never going to be broken in the future (unlike IPv4 today and the history of class A, B, and C). -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Also the number of bits are separated into a network part (upper 64 bits) and a host part (lower 64 bits), to facilitate auto-configuration. -\layout Section +\end_layout +\begin_layout Section Addresses without a special prefix -\layout Subsection +\end_layout +\begin_layout Subsection Localhost address -\layout Standard +\end_layout +\begin_layout Standard This is a special address for the loopback interface, similiar to IPv4 with its \begin_inset Quotes sld -\end_inset +\end_inset 127.0.0.1 \begin_inset Quotes srd -\end_inset +\end_inset . With IPv6, the localhost address is: -\layout Code +\end_layout +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0001 -\layout Standard +\end_layout +\begin_layout Standard or compressed: -\layout Code +\end_layout +\begin_layout Code ::1 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Packets with this address as source or destination should never leave the sending host. -\layout Subsection +\end_layout +\begin_layout Subsection Unspecified address -\layout Standard +\end_layout +\begin_layout Standard This is a special address like \begin_inset Quotes sld -\end_inset +\end_inset any \begin_inset Quotes srd -\end_inset +\end_inset or \begin_inset Quotes sld -\end_inset +\end_inset 0.0.0.0 \begin_inset Quotes srd -\end_inset +\end_inset in IPv4 . For IPv6 it's: -\layout Code +\end_layout +\begin_layout Code 0000:0000:0000:0000:0000:0000:0000:0000 -\layout Standard +\end_layout +\begin_layout Standard or: -\layout Code +\end_layout +\begin_layout Code :: -\layout Standard +\end_layout +\begin_layout Standard These addresses are mostly used/seen in socket binding (to any IPv6 address) or routing tables. -\layout Standard +\end_layout +\begin_layout Standard Note: the unspecified address cannot be used as destination address. -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 address with embedded IPv4 address -\layout Standard +\end_layout +\begin_layout Standard There are two addresses which contain an IPv4 address. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv4-mapped IPv6 address -\layout Standard +\end_layout +\begin_layout Standard IPv4-only IPv6-compatible addresses are sometimes used/shown for sockets created by an IPv6-enabled daemon, but only binding to an IPv4 address. -\layout Standard +\end_layout +\begin_layout Standard These addresses are defined with a special prefix of length 96 (a.b.c.d is the IPv4 address): -\layout Code +\end_layout +\begin_layout Code 0:0:0:0:0:ffff:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard or in compressed format -\layout Code +\end_layout +\begin_layout Code ::ffff:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard For example, the IPv4 address 1.2.3.4 looks like this: -\layout Code +\end_layout +\begin_layout Code ::ffff:1.2.3.4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv4-compatible IPv6 address -\layout Standard +\end_layout +\begin_layout Standard Used for automatic tunneling ( \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset ), which is being replaced by \begin_inset LatexCommand \ref[6to4 tunneling]{tunneling-6to4} -\end_inset +\end_inset . -\layout Code +\end_layout +\begin_layout Code 0:0:0:0:0:0:a.b.c.d/96 -\layout Standard +\end_layout +\begin_layout Standard or in compressed format -\layout Code +\end_layout +\begin_layout Code ::a.b.c.d/96 -\layout Section +\end_layout +\begin_layout Section Network part, also known as prefix -\layout Standard +\end_layout +\begin_layout Standard Designers defined some address types and left a lot of scope for future definitions as currently unknown requirements arise. \begin_inset LatexCommand \url[RFC 2373 [July 1998] / IP Version 6 Addressing Architecture]{http://www.faqs.org/rfcs/rfc2373.html} -\end_inset +\end_inset defines the current addressing scheme but there is already a new draft available: \begin_inset LatexCommand \url[draft-ietf-ipngwg-addr-arch-*.txt]{ftp://ftp.ietf.org/internet-drafts/} -\end_inset +\end_inset . -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Now lets take a look at the different types of prefixes (and therefore address types): -\layout Subsection +\end_layout +\begin_layout Subsection Link local address type -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left These are special addresses which will only be valid on a link of an interface. Using this address as destination the packet would never pass through a router. It's used for link communications such as: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left anyone else here on this link? -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left anyone here with a special address (e.g. looking for a router)? -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left They begin with ( where -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset x \begin_inset Quotes srd -\end_inset +\end_inset -\emph default +\emph default is any hex character, normally -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset 0 -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Code +\end_layout +\begin_layout Code fe8 -\shape italic -\emph on +\shape italic +\emph on x: <- currently the only one in use. -\layout Code +\end_layout +\begin_layout Code fe9 -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fea -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code feb -\shape italic -\emph on +\shape italic +\emph on x: -\layout Standard +\end_layout +\begin_layout Standard An address with this prefix is found on each IPv6-enabled interface after stateless auto-configuration (which is normally always the case). -\layout Subsection +\end_layout +\begin_layout Subsection Site local address type -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left These are addresses similar to the \begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://www.faqs.org/rfcs/rfc1918.html} -\end_inset +\end_inset in IPv4 today, with the added advantage that everyone who use this address type has the capability to use the given 16 bits for a maximum number of 65536 subnets. Comparable with the -\family typewriter +\family typewriter 10.0.0.0/8 -\family default +\family default in IPv4 today. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left 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. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left It begins with: -\layout Code +\end_layout +\begin_layout Code fec -\shape italic -\emph on +\shape italic +\emph on x: <- most commonly used. -\layout Code +\end_layout +\begin_layout Code fed -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fee -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout +\begin_layout Code fef -\shape italic -\emph on +\shape italic +\emph on x: -\layout Code +\end_layout -\layout Standard +\begin_layout Code +\end_layout + +\begin_layout Standard (where -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset x \begin_inset Quotes srd -\end_inset +\end_inset -\emph default +\emph default is any hex character, normally -\emph on +\emph on \begin_inset Quotes sld -\end_inset +\end_inset 0 -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset ) -\layout Standard +\end_layout +\begin_layout Standard Note that there are discussions going on in deprecating this kind of addresses because there are several issues. Read the current draft for more: \begin_inset LatexCommand \url[draft-ietf-ipv6-deprecate-site-local-XY.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard For test in labs, such addresses are still a good choice in my humble opinion. -\layout Subsection +\end_layout +\begin_layout Subsection Global address type "(Aggregatable) global unicast" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Today, there is one global address type defined (the first design, called "provider based," was thrown away some years ago \begin_inset LatexCommand \url[RFC 1884 / IP Version 6 Addressing Architecture [obsolete]]{http://www.faqs.org/rfcs/rfc1884.html} -\end_inset +\end_inset , you will find some remains in older Linux kernel sources). -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left It begins with ( -\emph on +\emph on x -\emph default +\emph default are hex characters) -\layout Code +\end_layout +\begin_layout Code 2 -\shape italic -\emph on +\shape italic +\emph on xxx -\shape default -\emph default +\shape default +\emph default : -\layout Code +\end_layout +\begin_layout Code 3 -\shape italic -\emph on +\shape italic +\emph on xxx -\shape default -\emph default +\shape default +\emph default : -\layout Standard +\end_layout +\begin_layout Standard Note: the prefix \begin_inset Quotes sld -\end_inset +\end_inset aggregatable \begin_inset Quotes srd -\end_inset +\end_inset is thrown away in current drafts. -\newline -There are some further subtypes defined, see below: -\layout Subsubsection +\newline +There are some further subtypes defined, + see below: +\end_layout +\begin_layout Subsubsection 6bone test addresses -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left These were the first global addresses which were defined and in use. They all start with -\layout Code +\end_layout +\begin_layout Code 3ffe: -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f102::1 -\layout Standard +\end_layout +\begin_layout Standard A special 6bone test address which will be never be globally unique begins with -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff: -\layout Standard +\end_layout +\begin_layout Standard and is mostly shown in older examples, because if real addresses are shown, its possible for someone to do a copy & paste to their configuration files. Thus inadvertently causing duplicates on a globally unique address. This would cause serious problems for the original host (e.g. getting answer packets for request that were never sent). -\newline -Because IPv6 is now in production, this prefix will no longer be delegated - and probably removed routing after 6.6.2006 (see +\newline +Because IPv6 is + now in production, this prefix will no longer be delegated and probably + removed routing after 6.6.2006 (see \begin_inset LatexCommand \url[RFC 3701 / 6bone Phaseout]{http://www.faqs.org/rfcs/rfc3701.html} -\end_inset +\end_inset for more). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection 6to4 addresses -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left These addresses, designed for a special tunneling mechanism [ \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset and \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset ], encode a given IPv4 address and a possible subnet and begin with -\layout Code +\end_layout +\begin_layout Code 2002: -\layout Standard +\end_layout +\begin_layout Standard For example, representing 192.168.1.1/5: -\layout Code +\end_layout +\begin_layout Code 2002:c0a8:0101:5::1 -\layout Standard +\end_layout +\begin_layout Standard A small shell command line can help you generating such address out of a given IPv4 one: -\layout Code +\end_layout +\begin_layout Code ipv4="1.2.3.4"; sla="5"; printf "2002:%02x%02x:%02x%02x:%04x::1" `echo $ipv4 -\layout Code +\end_layout +\begin_layout Code ¬ | tr "." " "` $sla -\layout Standard +\end_layout +\begin_layout Standard See also \begin_inset LatexCommand \ref[tunneling using 6to4]{tunneling-6to4} -\end_inset +\end_inset and \begin_inset LatexCommand \ref[information about 6to4 relay routers]{information-joinipv6-6to4-tunneling} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Assigned by provider for hierarchical routing -\layout Standard +\end_layout +\begin_layout Standard These addresses are delegated to Internet service providers (ISP) and begin with -\layout Code +\end_layout +\begin_layout Code 2001: -\layout Standard +\end_layout +\begin_layout Standard Prefixes to major (backbone owning) ISPs (also known as LIRs) are delegated by \begin_inset LatexCommand \ref[local registries]{information-majorregionregistries} -\end_inset +\end_inset and currently they got a prefix with length 32 assigned. -\layout Standard +\end_layout +\begin_layout Standard Any ISP customer can get a prefix with length 48. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Addresses reserved for examples and documentation -\layout Standard +\end_layout +\begin_layout Standard Currently, two address ranges are reserved for examples and documentation: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff::/32 -\layout Code +\end_layout +\begin_layout Code 2001:0DB8::/32 EXAMPLENET-WF -\layout Standard +\end_layout +\begin_layout Standard These address ranges should be filtered based on source addresses and should NOT be routed on border routers to the internet, if possible. -\layout Subsection +\end_layout +\begin_layout Subsection Multicast addresses -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Multicast addresses are used for related services. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left They alway start with ( -\emph on +\emph on xx -\emph default +\emph default is the scope value) -\layout Code +\end_layout +\begin_layout Code ff -\shape italic -\emph on +\shape italic +\emph on x -\shape default -\emph default +\shape default +\emph default y: -\layout Standard +\end_layout +\begin_layout Standard They are split into scopes and types: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Multicast scopes -\layout Standard +\end_layout +\begin_layout Standard Multicast scope is a parameter to specify the maximum distance a multicast packet can travel from the sending entity. -\layout Standard +\end_layout +\begin_layout Standard Currently, the following regions (scopes) are defined: -\layout Itemize +\end_layout +\begin_layout Itemize ffx1: node-local, packets never leave the node. -\layout Itemize +\end_layout +\begin_layout Itemize ffx2: link-local, packets are never forwarded by routers, so they never leave the specified link. -\layout Itemize +\end_layout +\begin_layout Itemize ffx5: site-local, packets never leave the site. -\layout Itemize +\end_layout +\begin_layout Itemize ffx8: organization-local, packets never leave the organization (not so easy to implement, must be covered by routing protocol). -\layout Itemize +\end_layout +\begin_layout Itemize ffxe: global scope. -\layout Itemize +\end_layout +\begin_layout Itemize others are reserved -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Multicast types -\layout Standard +\end_layout +\begin_layout Standard There are many types already defined/reserved (see \begin_inset LatexCommand \url[RFC 2373 / IP Version 6 Addressing Architecture]{http://www.faqs.org/rfcs/rfc2373.html} -\end_inset +\end_inset for details). Some examples are: -\layout Itemize +\end_layout +\begin_layout Itemize All Nodes Address: ID = 1h, addresses all hosts on the local node (ff01:0:0:0:0: 0:0:1) or the connected link (ff02:0:0:0:0:0:0:1). -\layout Itemize +\end_layout +\begin_layout Itemize All Routers Address: ID = 2h, addresses all routers on the local node (ff01:0:0: 0:0:0:0:2), on the connected link (ff02:0:0:0:0:0:0:2), or on the local site (ff05:0:0:0:0:0:0:2) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Solicited node link-local multicast address -\layout Standard +\end_layout +\begin_layout Standard Special multicast address used as destination address in neighborhood discovery, because unlike in IPv4, ARP no longer exists in IPv6. -\layout Standard +\end_layout +\begin_layout Standard An example of this address looks like -\layout Code +\end_layout +\begin_layout Code ff02::1:ff00:1234 -\layout Standard +\end_layout +\begin_layout Standard 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 \begin_inset Quotes eld -\end_inset +\end_inset fe80::1234 \begin_inset Quotes erd -\end_inset +\end_inset , but the network stack doesn't know the current layer 2 MAC address. It replaces the upper 104 bits with \begin_inset Quotes eld -\end_inset +\end_inset ff02:0:0:0:0:1:ff00::/104 \begin_inset Quotes erd -\end_inset +\end_inset and leaves the lower 24 bits untouched. This address is now used `on-link' to find the corresponding node which has to send a reply containing its layer 2 MAC address. -\layout Subsection +\end_layout +\begin_layout Subsection Anycast addresses -\layout Standard +\end_layout +\begin_layout Standard Anycast addresses are special addresses and are used to cover things like nearest DNS server, nearest DHCP server, or similar dynamic groups. Addresses are taken out of the unicast address space (aggregatable global or site-local at the moment). The anycast mechanism (client view) will be handled by dynamic routing protocols. -\layout Standard +\end_layout +\begin_layout Standard Note: Anycast addresses cannot be used as source addresses, they are only used as destination addresses. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Subnet-router anycast address -\layout Standard +\end_layout +\begin_layout Standard A simple example for an anycast address is the subnet-router anycast address. Assuming that a node has the following global assigned IPv6 address: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:210:a4ff:fee3:9566/64 <- Node's address -\layout Standard +\end_layout +\begin_layout Standard The subnet-router anycast address will be created blanking the suffix (least significant 64 bits) completely: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::/64 <- subnet-router anycast address -\layout Section +\end_layout +\begin_layout Section Address types (host part) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left For auto-configuration and mobility issues, it was decided to use the lower 64 bits as host part of the address in most of the current address types. Therefore each single subnet can hold a large amount of addresses. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left This host part can be inspected differently: -\layout Subsection +\end_layout +\begin_layout Subsection Automatically computed (also known as stateless) -\layout Standard +\end_layout +\begin_layout Standard With auto-configuration, the host part of the address is computed by converting the MAC address of an interface (if available), with the EUI-64 method, to a unique IPv6 address. If no MAC address is available for this device (happens e.g. on virtual devices), something else (like the IPv4 address or the MAC address of a physical interface) is used instead. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Consider again the first example -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:210:a4ff:fee3:9566 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left here, -\layout Code +\end_layout +\begin_layout Code 210:a4ff:fee3:9566 -\layout Standard -\align left -is the host part and computed from the NIC's MAC address -\layout Code +\end_layout +\begin_layout Standard +\align left +is the host part and computed from the NIC's MAC address +\end_layout + +\begin_layout Code 00:10:A4:E3:95:66 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left using the \begin_inset LatexCommand \url[IEEE-Tutorial EUI-64]{http://standards.ieee.org/regauth/oui/tutorials/EUI64.html} -\end_inset +\end_inset design for EUI-48 identifiers. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Privacy problem with automatically computed addresses and a solution -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Because the "automatically computed" host part is globally unique (except when a vendor of a NIC uses the same MAC address on more than one NIC), client tracking is possible on the host when not using a proxy of any kind. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left This is a known problem, and a solution was defined: privacy extension, defined in \begin_inset LatexCommand \url[RFC 3041 / Privacy Extensions for Stateless Address Autoconfiguration in IPv6]{http://www.faqs.org/rfcs/rfc3041.html} -\end_inset +\end_inset (there is also already a newer draft available: \begin_inset LatexCommand \url[draft-ietf-ipngwg-temp-addresses-*.txt]{ftp://ftp.ietf.org/internet-drafts/} -\end_inset +\end_inset ). Using a random and a static value a new suffix is generated from time to time. Note: this is only reasonable for outgoing client connections and isn't really useful for well-known servers. -\layout Subsection +\end_layout +\begin_layout Subsection Manually set -\layout Standard +\end_layout +\begin_layout Standard For servers it's probably easier to remember simpler addresses, this can also be accommodated. It is possible to assign an additional IPv6 address to an interface, e.g. -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::1 -\layout Standard +\end_layout +\begin_layout Standard For manual suffixes like \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset shown in the above example it's required that the 7th 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. -\layout Section +\end_layout +\begin_layout Section Prefix lengths for routing -\layout Standard +\end_layout +\begin_layout Standard In the early design phase it was planned to use a fully hierarchical routing approach to reduce the size of the routing tables maximally. The reasoning behind this approach were the number of current IPv4 routing entries in core routers (> 104 thousand in May 2001), reducing the need of memory in hardware routers (ASIC \begin_inset Quotes sld -\end_inset +\end_inset Application Specified Integrated Circuit \begin_inset Quotes srd -\end_inset +\end_inset driven) to hold the routing table and increase speed (fewer entries hopefully result in faster lookups). -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Todays view is that routing will be mostly hierarchically designed for networks with only one service provider. With more than one ISP connections, this is not possible, and subject to an issue named multi-homing (infos on multi-homing: \begin_inset LatexCommand \url[drafts*multi6*]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[IPv6 Multihoming Solutions]{http://arneill-py.sacramento.ca.us/ipv6mh/} -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection Prefix lengths (also known as "netmasks") -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Similar to IPv4, the routable network path for routing to take place. Because standard netmask notation for 128 bits doesn't look nice, designers employed the IPv4 Classless Inter Domain Routing (CIDR, \begin_inset LatexCommand \url[RFC 1519 / Classless Inter-Domain Routing]{http://www.faqs.org/rfcs/rfc1519.html} -\end_inset +\end_inset ) scheme, which specifies the number of bits of the IP address to be used for routing. It is also called the "slash" notation. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left An example: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:1:2:3:4:5/48 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left This notation will be expanded: -\layout Itemize +\end_layout +\begin_layout Itemize Network: -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0100:0000:0000:0000:0000:0000 -\layout Itemize +\end_layout +\begin_layout Itemize Netmask: -\layout Code +\end_layout +\begin_layout Code ffff:ffff:ffff:0000:0000:0000:0000:0000 -\layout Subsection +\end_layout +\begin_layout Subsection Matching a route -\layout Standard +\end_layout +\begin_layout Standard Under normal circumstances (no QoS) a lookup in a routing table results in the route with the most significant number of address bits means the route with the biggest prefix length matches first. -\layout Standard +\end_layout +\begin_layout Standard For example if a routing table shows following entries (list is not complete): -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::/48 :: U 1 0 0 sit1 -\layout Code +\end_layout +\begin_layout Code 2000::/3 ::192.88.99.1 UG 1 0 0 tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Shown destination addresses of IPv6 packets will be routed through shown device -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:1:2:3:4:5/48 -> routed through device sit1 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:200:1:2:3:4:5/48 -> routed through device tun6to4 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-systemcheck} -\end_inset +\end_inset IPv6-ready system check -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Before you can start using IPv6 on a Linux host, you have to test, whether your system is IPv6-ready. You may have to do some work to enable it first. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{systemcheck-kernel} -\end_inset +\end_inset IPv6-ready kernel -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Modern Linux distributions already contain IPv6-ready kernels, the IPv6 capability is generally compiled as a module, but it's possible that this module is not loaded automatically on startup. -\layout Standard +\end_layout +\begin_layout Standard See \begin_inset LatexCommand \url[IPv6+Linux-Status-Distribution]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset page for most up-to-date information. -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold Note: you shouldn't anymore use kernel series 2.2.x, because it's not IPv6-up-to-d ate anymore. -\layout Subsection +\end_layout +\begin_layout Subsection Check for IPv6 support in the current running kernel -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left To check, whether your current running kernel supports IPv6, take a look into your -\family typewriter +\family typewriter /proc -\family default +\family default -file-system. Following entry must exists: -\layout Code +\end_layout +\begin_layout Code /proc/net/if_inet6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left A short automatical test looks like: -\layout Code +\end_layout +\begin_layout Code # test -f /proc/net/if_inet6 && echo "Running kernel is IPv6 ready" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left If this fails, it is quite likely, that the IPv6 module is not loaded. -\layout Subsection +\end_layout +\begin_layout Subsection Try to load IPv6 module -\layout Standard -\align left -You can try to load the IPv6 module executing -\layout Code +\end_layout +\begin_layout Standard +\align left +You can try to load the IPv6 module executing +\end_layout + +\begin_layout Code # modprobe ipv6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left If this is successful, this module should be listed, testable with following auto-magically line: -\layout Code +\end_layout +\begin_layout Code # lsmod |grep -w 'ipv6' && echo "IPv6 module successfully loaded" -\layout Standard -\align left -And the check shown above should now run successfully. -\layout Standard +\end_layout +\begin_layout Standard +\align left +And the check shown above should now run successfully. +\end_layout + +\begin_layout Standard Note: unloading the module is currently not supported and can result, under some circumstances, in a kernel crash. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Automatically loading of module -\layout Standard +\end_layout +\begin_layout Standard Its possible to automatically load the IPv6 module on demand. You only have to add following line in the configuration file of the kernel module loader (normally /etc/modules.conf or /etc/conf.modules): -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 ipv6 # automatically load IPv6 module on demand -\layout Standard +\end_layout +\begin_layout Standard It's also possible to disable automatically loading of the IPv6 module using following line -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 off # disable automatically load of IPv6 module on demand -\layout Standard +\end_layout +\begin_layout Standard Additional note: in kernels series 2.6.x, the module loader mechanism was changed. The new configuration file has to be named /etc/modprobe.conf instead of /etc/modules.conf. -\layout Subsection +\end_layout +\begin_layout Subsection Compile kernel with IPv6 capabilities -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left If both above shown results were negative and your kernel has no IP6 support, than you have the following options: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Update your distribution to a current one which supports IPv6 out-of-the-box (recommended for newbies), see here again: \begin_inset LatexCommand \url[IPv6+Linux-Status-Distribution]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Compile a new vanilla kernel (easy, if you know which options you needed) -\layout Itemize +\end_layout +\begin_layout Itemize Recompile kernel sources given by your Linux distribution (sometimes not so easy) -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left Compile a kernel with USAGI extensions -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left If you decide to compile a kernel, you should have previous experience in kernel compiling and read the \begin_inset LatexCommand \url[Linux Kernel HOWTO]{http://www.tldp.org/HOWTO/Kernel-HOWTO.html} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard A mostly up-to-time comparison between vanilla and USAGI extended kernels is available on \begin_inset LatexCommand \url[IPv6+Linux-Status-Kernel]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Compiling a vanilla kernel -\layout Standard +\end_layout +\begin_layout Standard More detailed hints about compiling an IPv6-enabled kernel can be found e.g. on \begin_inset LatexCommand \url[IPv6-HOWTO-2#kernel]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-2.html#kernel} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Note: you should use whenever possible kernel series 2.6.x or above, because the IPv6 support in series 2.4.x only will get only partially backporting and IPv6 support in series 2.2.x is hopeless outdated. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Compiling a kernel with USAGI extensions -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Same as for vanilla kernel, only recommend for advanced users, which are already familiar with IPv6 and kernel compilation. See also \begin_inset LatexCommand \url[USAGI project / FAQ]{http://www.linux-ipv6.org/faq.html} -\end_inset +\end_inset and \begin_inset LatexCommand \url[Obtaining the best IPv6 support with Linux (Article)]{http://www.deepspace6.net/docs/best_ipv6_support.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/docs/best_ipv6_support.html} -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection IPv6-ready network devices -\layout Standard +\end_layout +\begin_layout Standard Not all existing network devices have already (or ever) the capability to transport IPv6 packets. A current status can be found at \begin_inset LatexCommand \url[IPv6+Linux-status-kernel.html#transport]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html#transport} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard A major issue is that because of the network layer structure of kernel implement ation an IPv6 packet isn't really recognized by it's IP header number (6 instead of 4). @@ -2534,1627 +3105,2022 @@ ation an IPv6 packet isn't really recognized by it's IP header number (6 Note: the packet is still transported over the link, but on receivers side, the dispatching won't work (you can see this e.g. using tcpdump). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Currently known never \begin_inset Quotes sld -\end_inset +\end_inset IPv6 capable links \begin_inset Quotes srd -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Serial Line IP (SLIP, \begin_inset LatexCommand \url[RFC 1055 / SLIP]{http://www.faqs.org/rfcs/rfc1055.html} -\end_inset +\end_inset ), should be better called now to SLIPv4, device named: slX -\layout Itemize +\end_layout +\begin_layout Itemize Parallel Line IP (PLIP), same like SLIP, device names: plipX -\layout Itemize +\end_layout +\begin_layout Itemize ISDN with encapsulation -\emph on +\emph on rawip -\emph default +\emph default , device names: isdnX -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Currently known \begin_inset Quotes sld -\end_inset +\end_inset not supported IPv6 capable links \begin_inset Quotes srd -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize ISDN with encapsulation -\emph on +\emph on syncppp -\emph default +\emph default , device names: ipppX (design issue of the ipppd, will be merged into more general PPP layer in kernel series 2.5.x) -\layout Section +\end_layout +\begin_layout Section IPv6-ready network configuration tools -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left You wont get very far, if you are running an IPv6-ready kernel, but have no tools to configure IPv6. There are several packages in existence which can configure IPv6. -\layout Subsection +\end_layout +\begin_layout Subsection net-tools package -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left The net-tool package includes some tools like -\family typewriter +\family typewriter ifconfig -\family default +\family default and -\family typewriter +\family typewriter route -\family default +\family default , which helps you to configure IPv6 on an interface. Look at the output of -\family typewriter +\family typewriter ifconfig -? -\family default +\family default or -\family typewriter +\family typewriter route -? -\family default +\family default , if something is shown like IPv6 or inet6, then the tool is IPv6-ready. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Auto-magically check: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig -? 2>& 1|grep -qw 'inet6' && echo "utility 'ifconfig' is -\layout Code +\end_layout +\begin_layout Code ¬ IPv6-ready" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Same check can be done for -\family typewriter +\family typewriter route -\family default +\family default : -\layout Code +\end_layout +\begin_layout Code # /sbin/route -? 2>& 1|grep -qw 'inet6' && echo "utility 'route' is IPv6-ready" -\layout Subsection +\end_layout +\begin_layout Subsection iproute package -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Alexey N. Kuznetsov (current a maintainer of the Linux networking code) created a tool-set which configures networks through the netlink device. Using this tool-set you have more functionality than net-tools provides, but its not very well documented and isn't for the faint of heart. -\layout Code +\end_layout +\begin_layout Code # /sbin/ip 2>&1 |grep -qw 'inet6' && echo "utility 'ip' is IPv6-ready" -\layout Standard +\end_layout +\begin_layout Standard If the program /sbin/ip isn't found, then I strongly recommend you install the iproute package. -\layout Itemize +\end_layout +\begin_layout Itemize You can get it from your Linux distribution (if contained) -\layout Itemize +\end_layout +\begin_layout Itemize You can download the tar-ball and recompile it: \begin_inset LatexCommand \url[Original FTP source]{ftp://ftp.inr.ac.ru/ip-routing/} -\end_inset +\end_inset and mirror (missing) -\layout Itemize +\end_layout +\begin_layout Itemize 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 +\end_inset (sometimes rebuilding of a SRPMS package is recommended) -\layout Section +\end_layout +\begin_layout Section IPv6-ready test/debug programs -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left After you have prepared your system for IPv6, you now want to use IPv6 for network communications. First you should learn how to examine IPv6 packets with a sniffer program. This is strongly recommended because for debugging/troubleshooting issues this can aide in providing a diagnosis very quickly. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-ping6} -\end_inset +\end_inset IPv6 ping -\layout Standard +\end_layout +\begin_layout Standard This program is normally included in package -\emph on +\emph on iputils -\emph default +\emph default . It is designed for simple transport tests sending ICMPv6 echo-request packets and wait for ICMPv6 echo-reply packets. -\layout Standard +\end_layout +\begin_layout Standard Usage -\layout Code +\end_layout +\begin_layout Code # ping6 -\layout Code +\end_layout +\begin_layout Code # ping6 -\layout Code +\end_layout +\begin_layout Code # ping6 [-I ] -\layout Standard +\end_layout +\begin_layout Standard Example -\layout Code +\end_layout +\begin_layout Code # ping6 -c 1 ::1 -\layout Code +\end_layout +\begin_layout Code PING ::1(::1) from ::1 : 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from ::1: icmp_seq=0 hops=64 time=292 usec -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code --- ::1 ping statistics --- -\layout Code +\end_layout +\begin_layout Code 1 packets transmitted, 1 packets received, 0% packet loss -\layout Code +\end_layout +\begin_layout Code round-trip min/avg/max/mdev = 0.292/0.292/0.292/0.000 ms -\layout Standard +\end_layout +\begin_layout Standard Hint: ping6 needs raw access to socket and therefore root permissions. So if non-root users cannot use ping6 then there are two possible problems: -\layout Enumerate +\end_layout +\begin_layout Enumerate ping6 is not in users path (probably, because ping6 is generally stored in /usr/sbin -> add path (not really recommended) -\layout Enumerate +\end_layout +\begin_layout Enumerate ping6 doesn't execute properly, generally because of missing root permissions -> chmod u+s /usr/sbin/ping6 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Specifying interface for IPv6 ping -\layout Standard +\end_layout +\begin_layout Standard Using link-local addresses for an IPv6 ping, the kernel does not know through which (physically or virtual) device it must send the packet - each device has a link-local address. A try will result in following error message: -\layout Code +\end_layout +\begin_layout Code # ping6 fe80::212:34ff:fe12:3456 -\layout Code +\end_layout +\begin_layout Code connect: Invalid argument -\layout Standard +\end_layout +\begin_layout Standard In this case you have to specify the interface additionally like shown here: -\layout Code +\end_layout +\begin_layout Code # ping6 -I eth0 -c 1 fe80::2e0:18ff:fe90:9205 -\layout Code +\end_layout +\begin_layout Code PING fe80::212:23ff:fe12:3456(fe80::212:23ff:fe12:3456) from -\layout Code +\end_layout +\begin_layout Code ¬ fe80::212:34ff:fe12:3478 eth0: 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from fe80::212:23ff:fe12:3456: icmp_seq=0 hops=64 time=445 usec -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code --- fe80::2e0:18ff:fe90:9205 ping statistics --- -\layout Code +\end_layout +\begin_layout Code 1 packets transmitted, 1 packets received, 0% packet loss round-trip -\layout Code +\end_layout +\begin_layout Code ¬ min/avg/max/mdev = 0.445/0.445/0.445/0.000 ms -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ping6 to multicast addresses -\layout Standard +\end_layout +\begin_layout Standard An interesting mechanism to detect IPv6-active hosts on a link is to ping6 to the link-local all-node multicast address: -\layout Code +\end_layout +\begin_layout Code # ping6 -I eth0 ff02::1 -\layout Code +\end_layout +\begin_layout Code PING ff02::1(ff02::1) from fe80:::2ab:cdff:feef:0123 eth0: 56 data bytes -\layout Code +\end_layout +\begin_layout Code 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.104 ms -\layout Code +\end_layout +\begin_layout Code 64 bytes from fe80::212:34ff:fe12:3450: icmp_seq=1 ttl=64 time=0.549 ms (DUP!) -\layout Standard +\end_layout +\begin_layout Standard Unlike in IPv4, where replies to a ping on the broadcast address can be disabled, in IPv6 currently this behavior cannot be disable except by local IPv6 firewalling. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-traceroute6} -\end_inset +\end_inset IPv6 traceroute6 -\layout Standard +\end_layout +\begin_layout Standard This program is normally included in package -\emph on +\emph on iputils -\emph default +\emph default . It's a program similar to IPv4 traceroute. Below you will see an example: -\layout Code +\end_layout +\begin_layout Code # traceroute6 www.6bone.net -\layout Code +\end_layout +\begin_layout Code traceroute to 6bone.net (3ffe:b00:c18:1::10) from 3ffe:ffff:0000:f101::2, 30 -\layout Code +\end_layout +\begin_layout Code ¬ hops max, 16 byte packets -\layout Code +\end_layout +\begin_layout Code 1 localipv6gateway (3ffe:ffff:0000:f101::1) 1.354 ms 1.566 ms 0.407 ms -\layout Code +\end_layout +\begin_layout Code 2 swi6T1-T0.ipv6.switch.ch (3ffe:2000:0:400::1) 90.431 ms 91.956 ms 92.377 ms -\layout Code +\end_layout +\begin_layout Code 3 3ffe:2000:0:1::132 (3ffe:2000:0:1::132) 118.945 ms 107.982 ms 114.557 ms -\layout Code +\end_layout +\begin_layout Code 4 3ffe:c00:8023:2b::2 (3ffe:c00:8023:2b::2) 968.468 ms 993.392 ms 973.441 ms -\layout Code +\end_layout +\begin_layout Code 5 3ffe:2e00:e:c::3 (3ffe:2e00:e:c::3) 507.784 ms 505.549 ms 508.928 ms -\layout Code +\end_layout +\begin_layout Code 6 www.6bone.net (3ffe:b00:c18:1::10) 1265.85 ms * 1304.74 ms -\layout Standard +\end_layout +\begin_layout Standard Note: unlike some modern versions of IPv4 traceroute, which can use ICMPv4 echo-request packets as well as UDP packets (default), current IPv6-traceroute is only able to send UDP packets. As you perhaps already know, ICMP echo-request packets are more accepted by firewalls or ACLs on routers inbetween than UDP packets. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-tracepath6} -\end_inset +\end_inset IPv6 tracepath6 -\layout Standard +\end_layout +\begin_layout Standard This program is normally included in package -\emph on +\emph on iputils -\emph default +\emph default . It's a program like traceroute6 and traces the path to a given destination discovering the MTU along this path. Below you will see an example: -\layout Code +\end_layout +\begin_layout Code # tracepath6 www.6bone.net -\layout Code +\end_layout +\begin_layout Code 1?: [LOCALHOST] pmtu 1480 -\layout Code +\end_layout +\begin_layout Code 1: 3ffe:401::2c0:33ff:fe02:14 150.705ms -\layout Code +\end_layout +\begin_layout Code 2: 3ffe:b00:c18::5 267.864ms -\layout Code +\end_layout +\begin_layout Code 3: 3ffe:b00:c18::5 asymm 2 266.145ms pmtu 1280 -\layout Code +\end_layout +\begin_layout Code 3: 3ffe:3900:5::2 asymm 4 346.632ms -\layout Code +\end_layout +\begin_layout Code 4: 3ffe:28ff:ffff:4::3 asymm 5 365.965ms -\layout Code +\end_layout +\begin_layout Code 5: 3ffe:1cff:0:ee::2 asymm 4 534.704ms -\layout Code +\end_layout +\begin_layout Code 6: 3ffe:3800::1:1 asymm 4 578.126ms !N -\layout Code +\end_layout +\begin_layout Code Resume: pmtu 1280 -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{program-tcpdump} -\end_inset +\end_inset IPv6 tcpdump -\layout Standard +\end_layout +\begin_layout Standard On Linux, tcpdump is the major tool for packet capturing. Below you find some examples. IPv6 support is normally built-in in current releases of version 3.6. -\layout Standard +\end_layout +\begin_layout Standard tcpdump uses expressions for filtering packets to minimize the noise: -\layout Itemize +\end_layout +\begin_layout Itemize icmp6: filters native ICMPv6 traffic -\layout Itemize +\end_layout +\begin_layout Itemize ip6: filters native IPv6 traffic (including ICMPv6) -\layout Itemize +\end_layout +\begin_layout Itemize proto ipv6: filters tunneled IPv6-in-IPv4 traffic -\layout Itemize +\end_layout +\begin_layout Itemize not port ssh: to suppress displaying SSH packets for running tcpdump in a remote SSH session -\layout Standard +\end_layout +\begin_layout Standard Also some command line options are very useful to catch and print more informati on in a packet, mostly interesting for digging into ICMPv6 packets: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -s 512 \begin_inset Quotes erd -\end_inset +\end_inset : increase the snap length during capturing of a packet to 512 bytes -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -vv \begin_inset Quotes erd -\end_inset +\end_inset : really verbose output -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset Quotes eld -\end_inset +\end_inset -n \begin_inset Quotes erd -\end_inset +\end_inset : don't resolve addresses to names, useful if reverse DNS resolving isn't working proper -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 ping to -\size footnotesize +\size footnotesize 3ffe:ffff:100:f101::1 -\size default +\size default native over a local link -\layout Code +\end_layout +\begin_layout Code # tcpdump -t -n -i eth0 -s 512 -vv ip6 or proto ipv6 -\layout Code +\end_layout +\begin_layout Code tcpdump: listening on eth0 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101:2e0:18ff:fe90:9205 > 3ffe:ffff:100:f101::1: icmp6: echo -\layout Code +\end_layout +\begin_layout Code ¬ request (len 64, hlim 64) -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100:f101::1 > 3ffe:ffff:100:f101:2e0:18ff:fe90:9205: icmp6: echo -\layout Code +\end_layout +\begin_layout Code ¬ reply (len 64, hlim 64) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 ping to -\size footnotesize +\size footnotesize 3ffe:ffff:100::1 -\size default +\size default routed through an IPv6-in-IPv4-tunnel -\layout Standard +\end_layout +\begin_layout Standard 1.2.3.4 and 5.6.7.8 are tunnel endpoints (all addresses are examples) -\layout Code +\end_layout +\begin_layout Code # tcpdump -t -n -i ppp0 -s 512 -vv ip6 or proto ipv6 -\layout Code +\end_layout +\begin_layout Code tcpdump: listening on ppp0 -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 > 5.6.7.8: 2002:ffff:f5f8::1 > 3ffe:ffff:100::1: icmp6: echo request -\layout Code +\end_layout +\begin_layout Code ¬ (len 64, hlim 64) (DF) (ttl 64, id 0, len 124) -\layout Code +\end_layout +\begin_layout Code 5.6.7.8 > 1.2.3.4: 3ffe:ffff:100::1 > 2002:ffff:f5f8::1: icmp6: echo reply (len -\layout Code +\end_layout +\begin_layout Code ¬ 64, hlim 61) (ttl 23, id 29887, len 124) -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 > 5.6.7.8: 2002:ffff:f5f8::1 > 3ffe:ffff:100::1: icmp6: echo request -\layout Code +\end_layout +\begin_layout Code ¬ (len 64, hlim 64) (DF) (ttl 64, id 0, len 124) -\layout Code +\end_layout +\begin_layout Code 5.6.7.8 > 1.2.3.4: 3ffe:ffff:100::1 > 2002:ffff:f5f8::1: icmp6: echo reply (len -\layout Code +\end_layout +\begin_layout Code ¬ 64, hlim 61) (ttl 23, id 29919, len 124) -\layout Section +\end_layout +\begin_layout Section IPv6-ready programs -\layout Standard +\end_layout +\begin_layout Standard Current distributions already contain the most needed IPv6 enabled client and servers. See first on \begin_inset LatexCommand \url[IPv6+Linux-Status-Distribution]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset . If still not included, you can check \begin_inset LatexCommand \url[IPv6 & Linux - Current Status - Applications]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html} -\end_inset +\end_inset whether the program is already ported to IPv6 and usable with Linux. For common used programs there are some hints available at \begin_inset LatexCommand \url[IPv6 & Linux - HowTo - Part 3]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-3.html} -\end_inset +\end_inset and \begin_inset LatexCommand \url[IPv6 & Linux - HowTo - Part 4]{http://www.bieringer.de/linux/IPv6/IPv6-HOWTO/IPv6-HOWTO-4.html} -\end_inset +\end_inset . -\layout Section +\end_layout +\begin_layout Section IPv6-ready client programs (selection) -\layout Standard +\end_layout +\begin_layout Standard To run the following shown tests, it's required that your system is IPv6 enabled, and some examples show addresses which only can be reached if a connection to the 6bone is available. -\layout Subsection +\end_layout +\begin_layout Subsection Checking DNS for resolving IPv6 addresses -\layout Standard +\end_layout +\begin_layout Standard Because of security updates in the last years every Domain Name System (DNS) server should run newer software which already understands the (intermediate) 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 test whether the used system can resolve IPv6 addresses is -\layout Code +\end_layout +\begin_layout Code # host -t AAAA www.join.uni-muenster.de -\layout Standard +\end_layout +\begin_layout Standard and should show something like following: -\layout Code +\end_layout +\begin_layout Code www.join.uni-muenster.de. is an alias for tolot.join.uni-muenster.de. -\layout Code +\end_layout +\begin_layout Code tolot.join.uni-muenster.de. has AAAA address 2001:638:500:101:2e0:81ff:fe24:37c6 -\layout Subsection +\end_layout +\begin_layout Subsection IPv6-ready telnet clients -\layout Standard +\end_layout +\begin_layout Standard IPv6-ready telnet clients are available. A simple test can be done with -\layout Code +\end_layout +\begin_layout Code $ telnet 3ffe:400:100::1 80 -\layout Code +\end_layout +\begin_layout Code Trying 3ffe:400:100::1... -\layout Code +\end_layout +\begin_layout Code Connected to 3ffe:400:100::1. -\layout Code +\end_layout +\begin_layout Code Escape character is '^]'. -\layout Code +\end_layout +\begin_layout Code HEAD / HTTP/1.0 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code HTTP/1.1 200 OK -\layout Code +\end_layout +\begin_layout Code Date: Sun, 16 Dec 2001 16:07:21 -\layout Code +\end_layout +\begin_layout Code GMT Server: Apache/2.0.28 (Unix) -\layout Code +\end_layout +\begin_layout Code Last-Modified: Wed, 01 Aug 2001 21:34:42 GMT -\layout Code +\end_layout +\begin_layout Code ETag: "3f02-a4d-b1b3e080" -\layout Code +\end_layout +\begin_layout Code Accept-Ranges: bytes -\layout Code +\end_layout +\begin_layout Code Content-Length: 2637 -\layout Code +\end_layout +\begin_layout Code Connection: close -\layout Code +\end_layout +\begin_layout Code Content-Type: text/html; charset=ISO-8859-1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code Connection closed by foreign host. -\layout Standard +\end_layout +\begin_layout Standard If the telnet client don't understand the IPv6 address and says something like \begin_inset Quotes sld -\end_inset +\end_inset cannot resolve hostname \begin_inset Quotes srd -\end_inset +\end_inset , then it's not IPv6-enabled. -\layout Subsection +\end_layout +\begin_layout Subsection IPv6-ready ssh clients -\layout Subsubsection +\end_layout +\begin_layout Subsubsection openssh -\layout Standard +\end_layout +\begin_layout Standard Current versions of openssh are IPv6-ready. Depending on configuring before compiling it has two behavior. -\layout Itemize +\end_layout +\begin_layout Itemize --without-ipv4-default: the client tries an IPv6 connect first automatically and fall back to IPv4 if not working -\layout Itemize +\end_layout +\begin_layout Itemize --with-ipv4-default: default connection is IPv4, IPv6 connection must be force like following example shows -\layout Code +\end_layout +\begin_layout Code $ ssh -\series bold +\series bold -6 -\series default +\series default ::1 -\layout Code +\end_layout +\begin_layout Code user@::1's password: ****** -\layout Code +\end_layout +\begin_layout Code [user@ipv6host user]$ -\layout Standard +\end_layout +\begin_layout Standard If your ssh client doesn't understand the option \begin_inset Quotes sld -\end_inset +\end_inset -6 \begin_inset Quotes srd -\end_inset +\end_inset then it's not IPv6-enabled, like most ssh version 1 packages. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ssh.com -\layout Standard +\end_layout +\begin_layout Standard SSH.com's SSH client and server is also IPv6 aware now and is free for all Linux and FreeBSD machine regardless if used for personal or commercial use. -\layout Subsection +\end_layout +\begin_layout Subsection IPv6-ready web browsers -\layout Standard +\end_layout +\begin_layout Standard A current status of IPv6 enabled web browsers is available at \begin_inset LatexCommand \url[IPv6+Linux-status-apps.html#HTTP]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#HTTP} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard Most of them have unresolved problems at the moment -\layout Enumerate +\end_layout +\begin_layout Enumerate If using an IPv4 only proxy in the settings, IPv6 requests will be sent to the proxy, but the proxy will fail to understand the request and the request fails. Solution: update proxy software (see later). -\layout Enumerate +\end_layout +\begin_layout Enumerate Automatic proxy settings (*.pac) cannot be extended to handle IPv6 requests differently (e.g. don't use proxy) because of their nature (written in Java-script and well hard coded in source like to be seen in Maxilla source code). -\layout Standard +\end_layout +\begin_layout Standard Also older versions don't understand an URL with IPv6 encoded addresses like \begin_inset LatexCommand \url[http://[3ffe:400:100::1]/]{http://[3ffe:400:100::1]/} -\end_inset +\end_inset (this given URL only works with an IPv6-enabled browser!). -\layout Standard +\end_layout +\begin_layout Standard A short test is to try shown URL with a given browser and using no proxy. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection URLs for testing -\layout Standard +\end_layout +\begin_layout Standard A good starting point for browsing using IPv6 is \begin_inset LatexCommand \url[http://www.kame.net/]{http://www.kame.net/} -\end_inset +\end_inset . If the turtle on this page is animated, the connection is via IPv6, otherwise the turtle is static. -\layout Section +\end_layout +\begin_layout Section IPv6-ready server programs -\layout Standard +\end_layout +\begin_layout Standard 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 \begin_inset LatexCommand \ref[Hints for IPv6-enabled daemons]{chapter-hints-daemons} -\end_inset +\end_inset . -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{faq-ipv6-ready-system-check} -\end_inset +\end_inset FAQ (IPv6-ready system check) -\layout Subsection +\end_layout +\begin_layout Subsection Using tools -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Q: Cannot ping6 to link-local addresses -\layout Standard +\end_layout +\begin_layout Standard Error message: " -\emph on +\emph on connect: Invalid argument -\emph default +\emph default " -\layout Standard +\end_layout +\begin_layout Standard Kernel doesn't know, which physical or virtual link you want to use to send such ICMPv6 packets. Therefore it displays this error message. -\layout Standard +\end_layout +\begin_layout Standard Solution: Specify interface like: \begin_inset Quotes sld -\end_inset +\end_inset ping6 -\series bold +\series bold -I eth0 -\series default +\series default fe80::2e0:18ff:fe90:9205 \begin_inset Quotes srd -\end_inset +\end_inset , see also \begin_inset LatexCommand \ref[program ping6 usage]{program-ping6} -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Q: Cannot ping6 or traceroute6 as normal user -\layout Standard +\end_layout +\begin_layout Standard Error message: \begin_inset Quotes sld -\end_inset +\end_inset -\emph on +\emph on icmp socket: Operation not permitted -\emph default +\emph default \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard These 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 \begin_inset Quotes sld -\end_inset +\end_inset root \begin_inset Quotes srd -\end_inset +\end_inset user. Therefore normal users get such error message. -\layout Standard +\end_layout +\begin_layout Standard 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 +\end_inset suid \begin_inset Quotes srd -\end_inset +\end_inset bit using \begin_inset Quotes srd -\end_inset +\end_inset chmod u+s /path/to/program \begin_inset Quotes srd -\end_inset +\end_inset , see also \begin_inset LatexCommand \ref[program ping6 usage]{program-ping6} -\end_inset +\end_inset . If not all users should be able to, you can change the group of the program to e.g. \begin_inset Quotes sld -\end_inset +\end_inset wheel \begin_inset Quotes srd -\end_inset +\end_inset , add these power users to this group and remove the execution bit for other users using \begin_inset Quotes sld -\end_inset +\end_inset chmod o-rwx /path/to/program \begin_inset Quotes srd -\end_inset +\end_inset . Or configure \begin_inset Quotes sld -\end_inset +\end_inset sudo \begin_inset Quotes srd -\end_inset +\end_inset to enable your security policy. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-interface} -\end_inset +\end_inset Configuring interfaces -\layout Section +\end_layout +\begin_layout Section Different network devices -\layout Standard +\end_layout +\begin_layout Standard On a node, there exist different network devices. They can be collected in classes -\layout Itemize +\end_layout +\begin_layout Itemize Physically bounded, like eth0, tr0 -\layout Itemize +\end_layout +\begin_layout Itemize Virtually existing, like ppp0, tun0, tap0, sit0, isdn0, ippp0 -\layout Subsection +\end_layout +\begin_layout Subsection Physically bounded -\layout Standard +\end_layout +\begin_layout Standard Physically bounded interfaces like Ethernet or Token-Ring are normal ones and need no special treatment. -\layout Subsection +\end_layout +\begin_layout Subsection Virtually bounded -\layout Standard +\end_layout +\begin_layout Standard Virtually bounded interfaces always need special support -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6-in-IPv4 tunnel interfaces -\layout Standard +\end_layout +\begin_layout Standard These interfaces are normally named -\series bold +\series bold sit -\emph on +\emph on x -\series default -\emph default +\series default +\emph default . The name -\emph on +\emph on sit -\emph default +\emph default is a shortcut for -\series bold +\series bold S -\series default +\series default imple -\series bold +\series bold I -\series default +\series default nternet -\series bold +\series bold T -\series default +\series default ransition. This device has the capability to encapsulate IPv6 packets into IPv4 ones and tunnel them to a foreign endpoint. -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold sit0 -\series default +\series default has a special meaning and cannot be used for dedicated tunnels. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection PPP interfaces -\layout Standard +\end_layout +\begin_layout Standard PPP interfaces get their IPv6 capability from an IPv6 enabled PPP daemon. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ISDN HDLC interfaces -\layout Standard +\end_layout +\begin_layout Standard IPv6 capability for HDLC with encapsulation -\series bold +\series bold ip -\series default +\series default is already built-in in the kernel -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ISDN PPP interfaces -\layout Standard +\end_layout +\begin_layout Standard ISDN PPP interfaces (ippp) aren't IPv6 enabled by kernel. Also there are also no plans to do that because in kernel 2.5.+ they will be replaced by a more generic ppp interface layer. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection SLIP + PLIP -\layout Standard +\end_layout +\begin_layout Standard Like mentioned earlier, this interfaces don't support IPv6 transport (sending is OK, but dispatching on receiving don't work). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Ether-tap device -\layout Standard +\end_layout +\begin_layout Standard Ether-tap devices are IPv6-enabled and also stateless configured. For use, the module \begin_inset Quotes sld -\end_inset +\end_inset ethertap \begin_inset Quotes srd -\end_inset +\end_inset has to be loaded before. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection tun devices -\layout Standard +\end_layout +\begin_layout Standard Currently not tested by me. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ATM -\layout Standard +\end_layout +\begin_layout Standard 01/2002: Aren't currently supported by vanilla kernel, supported by USAGI extension -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Others -\layout Standard +\end_layout +\begin_layout Standard Did I forget an interface?... -\layout Section +\end_layout +\begin_layout Section Bringing interfaces up/down -\layout Standard +\end_layout +\begin_layout Standard Two methods can be used to bring interfaces up or down. -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # ip link set dev up -\layout Code +\end_layout +\begin_layout Code # ip link set dev down -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # ip link set dev eth0 up -\layout Code +\end_layout +\begin_layout Code # ip link set dev eth0 down -\layout Subsection +\end_layout +\begin_layout Subsection Using "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig up -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig down -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 down -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-address} -\end_inset +\end_inset Configuring IPv6 addresses -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left There are different ways to configure an IPv6 address on an interface. You can use use "ifconfig" or "ip". -\layout Section +\end_layout +\begin_layout Section Displaying existing IPv6 addresses -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left First you should check, whether and which IPv6 addresses are already configured (perhaps auto-magically during stateless auto-configuration). -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show dev -\layout Standard +\end_layout +\begin_layout Standard Example for a static configured host: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show dev eth0 -\layout Code +\end_layout +\begin_layout Code 2: eth0: -\layout Standard +\end_layout +\begin_layout Standard Example (output filtered with grep to display only IPv6 addresses). Here you see different IPv6 addresses with different scopes. -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 |grep "inet6 addr:" -\layout Code +\end_layout +\begin_layout Code inet6 addr: fe80::210:a4ff:fee3:9566/10 Scope:Link -\layout Code +\end_layout +\begin_layout Code inet6 addr: 3ffe:ffff:0:f101::1/64 Scope:Global -\layout Code +\end_layout +\begin_layout Code inet6 addr: fec0:0:0:f101::1/64 Scope:Site -\layout Section +\end_layout +\begin_layout Section Add an IPv6 address -\layout Standard +\end_layout +\begin_layout Standard Adding an IPv6 address is similar to the mechanism of "IP ALIAS" addresses in Linux IPv4 addressed interfaces. -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add / dev -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add 3ffe:ffff:0:f101::1/64 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Using "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig inet6 add / -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 inet6 add 3ffe:ffff:0:f101::1/64 -\layout Section +\end_layout +\begin_layout Section Removing an IPv6 address -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Not so often needed, be carefully with removing non existent IPv6 address, sometimes using older kernels it results in a crash. -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr del / dev -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr del 3ffe:ffff:0:f101::1/64 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Using "ifconfig" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig inet6 del / -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig eth0 inet6 del 3ffe:ffff:0:f101::1/64 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuration-route} -\end_inset +\end_inset Configuring normal IPv6 routes -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left If you want to leave your link and want to send packets in the world wide IPv6-Internet, you need routing. If there is already an IPv6 enabled router on your link, it's possible enough to add IPv6 routes. -\layout Section +\end_layout +\begin_layout Section Displaying existing IPv6 routes -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left First you should check, whether and which IPv6 addresses are already configured (perhaps auto-magically during auto-configuration). -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route show [dev ] -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route show dev eth0 -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0:f101::/64 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code fe80::/10 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code ff00::/8 proto kernel metric 256 mtu 1500 advmss 1440 -\layout Code +\end_layout +\begin_layout Code default proto kernel metric 256 mtu 1500 advmss 1440 -\layout Subsection +\end_layout +\begin_layout Subsection Using "route" -\layout Standard -\align left -Usage: -\layout Code +\end_layout +\begin_layout Standard +\align left +Usage: +\end_layout + +\begin_layout Code # /sbin/route -A inet6 -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Example (output is filtered for interface eth0). Here you see different IPv6 routes for different addresses on a single interface. -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 |grep -w "eth0" -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:0:f101 ::/64 :: UA 256 0 0 eth0 <- Interface route for global -\layout Code +\end_layout +\begin_layout Code ¬ address -\layout Code +\end_layout +\begin_layout Code fe80::/10 :: UA 256 0 0 eth0 <- Interface route for link-local -\layout Code +\end_layout +\begin_layout Code ¬ address -\layout Code +\end_layout +\begin_layout Code ff00::/8 :: UA 256 0 0 eth0 <- Interface route for all multicast -\layout Code +\end_layout +\begin_layout Code ¬ addresses -\layout Code +\end_layout +\begin_layout Code ::/0 :: UDA 256 0 0 eth0 <- Automatic default route -\layout Section +\end_layout +\begin_layout Section Add an IPv6 route through a gateway -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Mostly needed to reach the outside with IPv6 using an IPv6-enabled router on your link. -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add / via -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 via 3ffe:ffff:0:f101::1 -\layout Subsection +\end_layout +\begin_layout Subsection Using "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add / gw -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left A device can be needed, too, if the IPv6 address of the gateway is a link local one. -\layout Standard +\end_layout +\begin_layout Standard Following shown example adds a route for all currently global addresses (2000::/3) through gateway -\family typewriter +\family typewriter \lang afrikaans 3ffe:ffff:0:f101::1 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 gw 3ffe:ffff:0:f101::1 -\layout Section +\end_layout +\begin_layout Section Removing an IPv6 route through a gateway -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Not so often needed manually, mostly done by network configure scripts on shutdown (full or per interface) -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard -\align left -Usage: -\layout Code +\end_layout +\begin_layout Standard +\align left +Usage: +\end_layout + +\begin_layout Code # /sbin/ip -6 route del / via -\layout Code +\end_layout +\begin_layout Code ¬ [dev ] -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del 2000::/3 via 3ffe:ffff:0:f101::1 -\layout Subsection +\end_layout +\begin_layout Subsection Using "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del / [dev ] -\layout Standard +\end_layout +\begin_layout Standard Example for removing upper added route again: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 gw 3ffe:ffff:0:f101::1 -\layout Section +\end_layout +\begin_layout Section Add an IPv6 route through an interface -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Not often needed, sometimes in cases of dedicated point-to-point links. -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add / dev -\layout Code +\end_layout +\begin_layout Code ¬ metric 1 -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 dev eth0 metric 1 -\layout Standard +\end_layout +\begin_layout Standard Metric \begin_inset Quotes sld -\end_inset +\end_inset 1 \begin_inset Quotes srd -\end_inset +\end_inset is used here to be compatible with the metric used by route, because the default metric on using \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset is \begin_inset Quotes sld -\end_inset +\end_inset 1024 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Using "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add / dev -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 dev eth0 -\layout Section +\end_layout +\begin_layout Section Removing an IPv6 route through an interface -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Not so often needed to use by hand, configuration scripts will use such on shutdown. -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del / dev -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del 2000::/3 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Using "route" -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del / dev -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 dev eth0 -\layout Section +\end_layout +\begin_layout Section FAQ for IPv6 routes -\layout Subsection +\end_layout +\begin_layout Subsection Support of an IPv6 default route -\layout Standard +\end_layout +\begin_layout Standard One idea of IPv6 was a hierachical routing, therefore only less routing entries are needed in routers. -\layout Standard +\end_layout +\begin_layout Standard There are some issues in current Linux kernels: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Clients (not routing any packet!) -\layout Standard +\end_layout +\begin_layout Standard Client can setup a default route like prefix \begin_inset Quotes sld -\end_inset +\end_inset ::/0 \begin_inset Quotes srd -\end_inset +\end_inset , they also learn such route on autoconfiguration e.g. using radvd on the link like following example shows: -\layout Code +\end_layout +\begin_layout Code # ip -6 route show | grep ^default -\layout Code +\end_layout +\begin_layout Code default via fe80::212:34ff:fe12:3450 dev eth0 proto kernel metric 1024 expires -\layout Code +\end_layout +\begin_layout Code ¬ 29sec mtu 1500 advmss 1440 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Routers in case of packet forwarding -\layout Standard +\end_layout +\begin_layout Standard Current mainstream Linux kernel (at least <= 2.4.17) don't support default routes. You can set them up, but the route lookup fails when a packet should be forwarded (normal intention of a router). -\layout Standard +\end_layout +\begin_layout Standard Therefore at this time \begin_inset Quotes sld -\end_inset +\end_inset default routing \begin_inset Quotes srd -\end_inset +\end_inset can be setup using the currently only global address prefix \begin_inset Quotes sld -\end_inset +\end_inset 2000::/3 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard The USAGI project already supports this in their extension with a hack. -\layout Standard +\end_layout +\begin_layout Standard Note: take care about default routing without address filtering on edge routers. Otherwise unwanted multicast or site-local traffic leave the edge. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-Neighbor-Discovery} -\end_inset +\end_inset Neighbor Discovery -\layout Standard +\end_layout +\begin_layout Standard 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 @@ -4163,193 +5129,236 @@ Neighbor discovery was the IPv6 successor for the ARP (Address Resolution IPv4). You can dig into the learnt table using \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Section +\end_layout +\begin_layout Section Displaying neighbors using \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard With following command you can display the learnt or configured IPv6 neighbors -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh show [dev ] -\layout Standard +\end_layout +\begin_layout Standard The following example shows one neighbor, which is a reachable router -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh show -\layout Code +\end_layout +\begin_layout Code fe80::201:23ff:fe45:6789 dev eth0 lladdr 00:01:23:45:67:89 router nud reachable -\layout Section +\end_layout +\begin_layout Section Manipulating neighbors table using \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Manually add an entry -\layout Standard +\end_layout +\begin_layout Standard With following command you are able to manually add an entry -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh add lladdr dev -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh add fec0::1 lladdr 02:01:02:03:04:05 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Manually delete an entry -\layout Standard +\end_layout +\begin_layout Standard Like adding also an entry can be deleted: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh del lladdr dev -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh del fec0::1 lladdr 02:01:02:03:04:05 dev eth0 -\layout Subsection +\end_layout +\begin_layout Subsection More advanced settings -\layout Standard +\end_layout +\begin_layout Standard The tool \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset is less documentated, but very strong. See online \begin_inset Quotes sld -\end_inset +\end_inset help \begin_inset Quotes srd -\end_inset +\end_inset for more: -\layout Code +\end_layout +\begin_layout Code # ip -6 neigh help -\layout Code +\end_layout +\begin_layout Code Usage: ip neigh { add | del | change | replace } { ADDR [ lladdr LLADDR ] -\layout Code +\end_layout +\begin_layout Code [ nud { permanent | noarp | stale | reachable } ] -\layout Code +\end_layout +\begin_layout Code | proxy ADDR } [ dev DEV ] -\layout Code +\end_layout +\begin_layout Code ip neigh {show|flush} [ to PREFIX ] [ dev DEV ] [ nud STATE ] -\layout Standard +\end_layout +\begin_layout Standard Looks like some options are only for IPv4...if you can contribute information about flags and advanced usage, pls. send. -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuring-ipv6-in-ipv4-tunnels} -\end_inset +\end_inset Configuring IPv6-in-IPv4 tunnels -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left If you want to leave your link you have no IPv6 capable network around you, you need IPv6-in-IPv4 tunneling to reach the world wide IPv6-Internet. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left There are some kind of tunnel mechanism and also some possibilities to setup tunnels. -\layout Section +\end_layout +\begin_layout Section Types of tunnels -\layout Standard +\end_layout +\begin_layout Standard There are more than one possibility to tunnel IPv6 packets over IPv4-only links. -\layout Subsection +\end_layout +\begin_layout Subsection Static point-to-point tunneling: 6bone -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left A point-to-point tunnel is a dedicated tunnel to an endpoint, which knows about your IPv6 network (for backward routing) and the IPv4 address of your tunnel endpoint and defined in \begin_inset LatexCommand \url[RFC 2893 / Transition Mechanisms for IPv6 Hosts and Routers]{http://www.faqs.org/rfcs/rfc2893.html} -\end_inset +\end_inset . Requirements: -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left IPv4 address of your local tunnel endpoint must be static, global unique and reachable from the foreign tunnel endpoint -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left A global IPv6 prefix assigned to you (see 6bone registry) -\layout Itemize -\align left +\end_layout + +\begin_layout Itemize +\align left A foreign tunnel endpoint which is capable to route your IPv6 prefix to your local tunnel endpoint (mostly remote manual configuration required) -\layout Subsection +\end_layout +\begin_layout Subsection Automatically tunneling -\layout Standard +\end_layout +\begin_layout Standard Automatic tunneling occurs, when a node directly connects another node gotten the IPv4 address of the other node before. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{tunneling-6to4} -\end_inset +\end_inset 6to4-Tunneling -\layout Standard +\end_layout +\begin_layout Standard 6to4 tunneling ( \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset ) uses a simple mechanism to create automatic tunnels. Each node with a global unique IPv4 address is able to be a 6to4 tunnel @@ -4358,492 +5367,646 @@ Automatic tunneling occurs, when a node directly connects another node gotten This case of tunneling can be divided into upstream and downstream tunneling. Also, a special IPv6 address indicates that this node will use 6to4 tunneling for connecting the world-wide IPv6 network -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Generation of 6to4 prefix -\layout Standard +\end_layout +\begin_layout Standard The 6to4 address is defined like following (schema is taken from \begin_inset LatexCommand \url[RFC 3056 / Connection of IPv6 Domains via IPv4 Clouds]{http://www.faqs.org/rfcs/rfc3056.html} -\end_inset +\end_inset ): -\layout Code +\end_layout +\begin_layout Code | 3+13 | 32 | 16 | 64 bits | -\layout Code +\end_layout +\begin_layout Code +---+------+-----------+--------+--------------------------------+ -\layout Code +\end_layout +\begin_layout Code | FP+TLA | V4ADDR | SLA ID | Interface ID | -\layout Code +\end_layout +\begin_layout Code | 0x2002 | | | | -\layout Code +\end_layout +\begin_layout Code +---+------+-----------+--------+--------------------------------+ -\layout Standard +\end_layout +\begin_layout Standard FP and TLA together (16 bits) have the value 0x2002. V4ADDR is the node's global unique IPv4 address (in hexadecimal notation). SLA is the subnet identifier (65536 local subnets possible) and are usable to represent your local network structure. -\layout Standard +\end_layout +\begin_layout Standard For gateways, such prefix is generated by normally using SLA \begin_inset Quotes sld -\end_inset +\end_inset 0000 \begin_inset Quotes srd -\end_inset +\end_inset and suffix \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset (not a must, can be an arbitrary one with local-scope) and assigned to the 6to4 tunnel interface. Note that Microsoft Windows uses V4ADDR also for suffix. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection 6to4 upstream tunneling -\layout Standard +\end_layout +\begin_layout Standard The node has to know to which foreign tunnel endpoint its in IPv4 packed IPv6 packets should be send to. In \begin_inset Quotes sld -\end_inset +\end_inset early \begin_inset Quotes srd -\end_inset +\end_inset days of 6to4 tunneling, dedicated upstream accepting routers were defined. See \begin_inset LatexCommand \url[NSayer's 6to4 information]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset for a list of routers. -\layout Standard +\end_layout +\begin_layout Standard 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 \begin_inset LatexCommand \url[RFC 3068 / An Anycast Prefix for 6to4 Relay Routers]{http://www.faqs.org/rfcs/rfc3068.html} -\end_inset +\end_inset for details. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection 6to4 downstream tunneling -\layout Standard +\end_layout +\begin_layout Standard The downstream (6bone -> your 6to4 enabled node) is not really fix and can vary from foreign host which originated packets were send to. There exist two possibilities: -\layout Itemize +\end_layout +\begin_layout Itemize Foreign host uses 6to4 and sends packet direct back to your node (see below) -\layout Itemize +\end_layout +\begin_layout Itemize Foreign host sends packets back to the world-wide IPv6 network and depending on the dynamic routing a relay router create a automatic tunnel back to your node. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Possible 6to4 traffic -\layout Itemize +\end_layout +\begin_layout Itemize from 6to4 to 6to4: is normally directly tunneled between the both 6to4 enabled hosts -\layout Itemize +\end_layout +\begin_layout Itemize from 6to4 to non-6to4: is sent via upstream tunneling -\layout Itemize +\end_layout +\begin_layout Itemize non-6to4 to 6to4: is sent via downstream tunneling -\layout Section +\end_layout +\begin_layout Section Displaying existing tunnels -\layout Subsection +\end_layout +\begin_layout Subsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 tunnel show [] -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 tunnel show -\layout Code +\end_layout +\begin_layout Code sit0: ipv6/ip remote any local any ttl 64 nopmtudisc -\layout Code +\end_layout +\begin_layout Code sit1: ipv6/ip remote 195.226.187.50 local any ttl 64 -\layout Subsection +\end_layout +\begin_layout Subsection Using "route" -\layout Standard +\end_layout +\begin_layout Standard Usage: -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 -\layout Standard +\end_layout +\begin_layout Standard Example (output is filtered to display only tunnels through virtual interface sit0): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 | grep " -\backslash +\backslash Wsit0 -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code ::/96 :: U 256 2 0 sit0 -\layout Code +\end_layout +\begin_layout Code 2002::/16 :: UA 256 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code 2000::/3 ::193.113.58.75 UG 1 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code fe80::/10 :: UA 256 0 0 sit0 -\layout Code +\end_layout +\begin_layout Code ff00::/8 :: UA 256 0 0 sit0 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{conf-ipv6-in-ipv4-point-to-point-tunnels} -\end_inset +\end_inset Setup of point-to-point tunnel -\layout Standard -\align left -There are 3 possibilities to add or remove point-to-point tunnels. -\layout Standard +\end_layout +\begin_layout Standard +\align left +There are 3 possibilities to add or remove point-to-point tunnels. +\end_layout + +\begin_layout Standard A good additional information about tunnel setup using \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset is \begin_inset LatexCommand \url[Configuring tunnels with iproute2 (article)]{http://www.deepspace6.net/docs/iproute2tunnel-en.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/docs/iproute2tunnel-en.html} -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection Add point-to-point tunnels -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using "ip" -\layout Standard -\align left -Common method at the moment for a small amount of tunnels. -\layout Standard +\end_layout +\begin_layout Standard +\align left +Common method at the moment for a small amount of tunnels. +\end_layout + +\begin_layout Standard Usage for creating a tunnel device (but it's not up afterward, also a TTL must be specified because the default value is 0). -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add mode sit ttl remote -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Standard +\end_layout +\begin_layout Standard Usage (generic example for three tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add sit1 mode sit ttl remote -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit1 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit1 metric 1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip tunnel add sit2 mode sit ttl -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit2 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit2 metric 1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip tunnel add sit3 mode sit ttl -\layout Code +\end_layout +\begin_layout Code ¬ local -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev sit3 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add dev sit3 metric 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using "ifconfig" and "route" (deprecated) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left This not very recommended way to add a tunnel because it's a little bit strange. No problem if adding only one, but if you setup more than one, you cannot easy shutdown the first ones and leave the others running. -\layout Standard +\end_layout +\begin_layout Standard Usage (generic example for three tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit1 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit2 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit2 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 tunnel -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit3 up -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add dev sit3 -\layout Standard +\end_layout +\begin_layout Standard Important: DON'T USE THIS, because this setup implicit enable "automatic tunneling" from anywhere in the Internet, this is a risk, and it should not be advocated. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using "route" only -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left It's also possible to setup tunnels in Non Broadcast Multiple Access (NBMA) style, it's a easy way to add many tunnels at once. But none of the tunnel can be numbered (which is a not required feature). -\layout Standard +\end_layout +\begin_layout Standard Usage (generic example for three tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Standard +\end_layout +\begin_layout Standard Important: DON'T USE THIS, because this setup implicit enable "automatic tunneling" from anywhere in the Internet, this is a risk, and it should not be advocated. -\layout Subsection +\end_layout +\begin_layout Subsection Removing point-to-point tunnels -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Manually not so often needed, but used by scripts for clean shutdown or restart of IPv6 configuration. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using "ip" -\layout Standard +\end_layout +\begin_layout Standard Usage for removing a tunnel device: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del -\layout Standard +\end_layout +\begin_layout Standard Usage (generic example for three tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route del dev sit1 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit1 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit1 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip -6 route del dev sit2 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit2 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit2 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ip -6 route del dev sit3 -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set sit3 down -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del sit3 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using "ifconfig" and "route" (deprecated because not very funny) -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Not only the creation is strange, the shutdown also...you have to remove the tunnels in backorder, means the latest created must be removed first. -\layout Standard +\end_layout +\begin_layout Standard Usage (generic example for three tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del dev sit3 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit3 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 del dev sit2 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit2 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/route -A inet6 add dev sit1 -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit1 down -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Code +\end_layout -\layout Subsubsection +\begin_layout Code +\end_layout + +\begin_layout Subsubsection Using "route" -\layout Standard +\end_layout +\begin_layout Standard This is like removing normal IPv6 routes. -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left Usage (generic example for three tunnels): -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del gw -\layout Code +\end_layout +\begin_layout Code ¬ :: dev sit0 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Subsection +\end_layout +\begin_layout Subsection Numbered point-to-point tunnels -\layout Standard +\end_layout +\begin_layout Standard Sometimes it's needed to configure a point-to-point tunnel with IPv6 addresses like in IPv4 today. This is only possible with the first (ifconfig+route - deprecated) and @@ -4851,2014 +6014,2465 @@ Sometimes it's needed to configure a point-to-point tunnel with IPv6 addresses In such cases, you can add the IPv6 address to the tunnel interface like shown on interface configuration. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{configuring-ipv6to4-tunnels} -\end_inset +\end_inset Setup of 6to4 tunnels -\layout Standard +\end_layout +\begin_layout Standard Pay attention that the support of 6to4 tunnels currently lacks on vanilla kernel series 2.2.x (see \begin_inset LatexCommand \ref[systemcheck/kernel]{systemcheck-kernel} -\end_inset +\end_inset for more information). Also note that that the prefix length for a 6to4 address is 16 because of from network point of view, all other 6to4 enabled hosts are on the same layer 2. -\layout Subsection +\end_layout +\begin_layout Subsection Add a 6to4 tunnel -\layout Standard +\end_layout +\begin_layout Standard First, you have to calculate your 6to4 prefix using your local assigned global routable IPv4 address (if your host has no global routable IPv4 address, in special cases NAT on border gateways is possible): -\layout Standard +\end_layout +\begin_layout Standard Assuming your IPv4 address is -\layout Code +\end_layout +\begin_layout Code 1.2.3.4 -\layout Standard +\end_layout +\begin_layout Standard the generated 6to4 prefix will be -\layout Code +\end_layout +\begin_layout Code 2002:0102:0304:: -\layout Standard +\end_layout +\begin_layout Standard Local 6to4 gateways should (but it's not a must, you can choose an arbitrary suffix with local-scope, if you feel better) always assigned the suffix \begin_inset Quotes sld -\end_inset +\end_inset ::1 \begin_inset Quotes srd -\end_inset +\end_inset , therefore your local 6to4 address will be -\layout Code +\end_layout +\begin_layout Code 2002:0102:0304::1 -\layout Standard +\end_layout +\begin_layout Standard Use e.g. following for automatic generation: -\layout Code +\end_layout +\begin_layout Code ipv4="1.2.3.4"; printf "2002:%02x%02x:%02x%02x::1" `echo $ipv4 | tr "." " "` -\layout Standard +\end_layout +\begin_layout Standard There are two ways possible to setup 6to4 tunneling now. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using "ip" and a dedicated tunnel device -\layout Standard +\end_layout +\begin_layout Standard This is now the recommended way (a TTL must be specified because the default value is 0). -\layout Standard +\end_layout +\begin_layout Standard Create a new tunnel device -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel add tun6to4 mode sit ttl remote any local -\layout Standard +\end_layout +\begin_layout Standard Bring interface up -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev tun6to4 up -\layout Standard +\end_layout +\begin_layout Standard Add local 6to4 address to interface (note: prefix length 16 is important!) -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr add /16 dev tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Add (default) route to the global IPv6 network using the all-6to4-routers IPv4 anycast address -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 via ::192.88.99.1 dev tun6to4 metric 1 -\layout Standard +\end_layout +\begin_layout Standard It was reported that some versions of \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset (e.g. SuSE Linux 9.0) don't support IPv4-compatible IPv6 addresses for gateways, in this case the related IPv6 address has to be used: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2000::/3 via -\series bold +\series bold 2002:c058:6301::1 -\series default +\series default dev tun6to4 metric 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using "ifconfig" and "route" and generic tunnel device \begin_inset Quotes sld -\end_inset +\end_inset sit0 \begin_inset Quotes srd -\end_inset +\end_inset (deprecated) -\layout Standard +\end_layout +\begin_layout Standard This is now deprecated because using the generic tunnel device sit0 doesn't let specify filtering per device. -\layout Standard +\end_layout +\begin_layout Standard Bring generic tunnel interface sit0 up -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 up -\layout Standard +\end_layout +\begin_layout Standard Add local 6to4 address to interface -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 add /16 -\layout Standard +\end_layout +\begin_layout Standard Add (default) route to the global IPv6 network using the all-6to4-relays IPv4 anycast address -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 add 2000::/3 gw ::192.88.99.1 dev sit0 -\layout Subsection +\end_layout +\begin_layout Subsection Remove a 6to4 tunnel -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using "ip" and a dedicated tunnel device -\layout Standard +\end_layout +\begin_layout Standard Remove all routes through this dedicated tunnel device -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route flush dev tun6to4 -\layout Standard +\end_layout +\begin_layout Standard Shut down interface -\layout Code +\end_layout +\begin_layout Code # /sbin/ip link set dev tun6to4 down -\layout Standard +\end_layout +\begin_layout Standard Remove created tunnel device -\layout Code +\end_layout +\begin_layout Code # /sbin/ip tunnel del tun6to4 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Using \begin_inset Quotes sld -\end_inset +\end_inset ifconfig \begin_inset Quotes srd -\end_inset +\end_inset and \begin_inset Quotes sld -\end_inset +\end_inset route \begin_inset Quotes srd -\end_inset +\end_inset and generic tunnel device \begin_inset Quotes sld -\end_inset +\end_inset sit0 \begin_inset Quotes srd -\end_inset +\end_inset (deprecated) -\layout Standard +\end_layout +\begin_layout Standard Remove (default) route through the 6to4 tunnel interface -\layout Code +\end_layout +\begin_layout Code # /sbin/route -A inet6 del 2000::/3 gw ::192.88.99.1 dev sit0 -\layout Standard +\end_layout +\begin_layout Standard Remove local 6to4 address to interface -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 del /16 -\layout Standard +\end_layout +\begin_layout Standard Shut down generic tunnel device (take care about this, perhaps it's still in use...) -\layout Code +\end_layout +\begin_layout Code # /sbin/ifconfig sit0 down -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-configuring-ipv4-in-ipv6-tunnels} -\end_inset +\end_inset Configuring IPv4-in-IPv6 tunnels -\layout Standard -\align left +\end_layout + +\begin_layout Standard +\align left This will be filled in the future. At the moment, such tunnels are more used in test environments but it looks like that support is missing currently for Linux (03/2004). -\layout Standard +\end_layout +\begin_layout Standard More information in the meantime: \begin_inset LatexCommand \url[RFC 2473 / Generic Packet Tunneling in IPv6 Specification]{http://www.faqs.org/rfcs/rfc2473.html} -\end_inset +\end_inset -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-kernel-settings} -\end_inset +\end_inset Kernel settings in /proc-filesystem -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \label{proc-filesystem} -\end_inset +\end_inset Note: the source of this section is mostly the file \begin_inset Quotes sld -\end_inset +\end_inset ip-sysctl.txt \begin_inset Quotes srd -\end_inset +\end_inset which is included in current kernel sources in directory \begin_inset Quotes sld -\end_inset +\end_inset Documentation/networking \begin_inset Quotes srd -\end_inset +\end_inset . Credits to Pekka Savola for maintaining the IPv6-related part in this file. Also some text is more or less copied & pasted into this document. -\layout Section +\end_layout +\begin_layout Section How to access the /proc-filesystem -\layout Subsection +\end_layout +\begin_layout Subsection Using \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset and \begin_inset Quotes sld -\end_inset +\end_inset echo \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Using \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset and \begin_inset Quotes sld -\end_inset +\end_inset echo \begin_inset Quotes srd -\end_inset +\end_inset is the simplest way to access the /proc filesystem, but some requirements are needed for that -\layout Itemize +\end_layout +\begin_layout Itemize The /proc-filesystem had to be enabled in kernel, means on compiling following switch has to be set -\layout Code +\end_layout +\begin_layout Code CONFIG_PROC_FS=y -\layout Itemize +\end_layout +\begin_layout Itemize The /proc-filesystem was mounted before, which can be tested using -\layout Code +\end_layout +\begin_layout Code # mount | grep "type proc" -\layout Code +\end_layout +\begin_layout Code none on /proc type proc (rw) -\layout Itemize +\end_layout +\begin_layout Itemize You need read and sometimes also write access (normally root only) to the /proc-filesystem -\layout Standard +\end_layout +\begin_layout Standard Normally, only entries in /proc/sys/* are writable, the others are readonly and for information retrieving only. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Retrieving a value -\layout Standard +\end_layout +\begin_layout Standard The value of an entry can be retrieved using \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset : -\layout Code +\end_layout +\begin_layout Code # cat /proc/sys/net/ipv6/conf/all/forwarding -\layout Code +\end_layout +\begin_layout Code 0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Setting a value -\layout Standard +\end_layout +\begin_layout Standard A new value can be set (if entry is writable) using \begin_inset Quotes sld -\end_inset +\end_inset echo \begin_inset Quotes srd -\end_inset +\end_inset : -\layout Code +\end_layout +\begin_layout Code # echo "1" >/proc/sys/net/ipv6/conf/all/forwarding -\layout Subsection +\end_layout +\begin_layout Subsection Using \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Using the \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset program to access the kernel switches is a modern method today. You can use it also, if the /proc-filesystem isn't mounted. But you have only access to /proc/sys/*! -\layout Standard +\end_layout +\begin_layout Standard The program \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset is included in package \begin_inset Quotes sld -\end_inset +\end_inset procps \begin_inset Quotes srd -\end_inset +\end_inset (on Red Hat Linux systems). -\layout Itemize +\end_layout +\begin_layout Itemize The sysctl-interface had to be enabled in kernel, means on compiling following switch has to be set -\layout Code +\end_layout +\begin_layout Code CONFIG_SYSCTL=y -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Retrieving a value -\layout Standard +\end_layout +\begin_layout Standard The value of an entry can be retrieved now: -\layout Code +\end_layout +\begin_layout Code # sysctl net.ipv6.conf.all.forwarding -\layout Code +\end_layout +\begin_layout Code net.ipv6.conf.all.forwarding = 0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Setting a value -\layout Standard +\end_layout +\begin_layout Standard A new value can be set (if entry is writable): -\layout Code +\end_layout +\begin_layout Code # sysctl -w net.ipv6.conf.all.forwarding=1 -\layout Code +\end_layout +\begin_layout Code net.ipv6.conf.all.forwarding = 1 -\layout Standard +\end_layout +\begin_layout Standard Note: Don't use spaces around the \begin_inset Quotes sld -\end_inset +\end_inset = \begin_inset Quotes srd -\end_inset +\end_inset on setting values. Also on multiple values per line, quote them like e.g. -\layout Code +\end_layout +\begin_layout Code # sysctl -w net.ipv4.ip_local_port_range= -\series bold +\series bold " -\series default +\series default 32768 61000 -\series bold +\series bold " -\layout Code +\end_layout +\begin_layout Code net.ipv4.ip_local_port_range = 32768 61000 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Additionals -\layout Standard +\end_layout +\begin_layout Standard Note: There are sysctl versions in the wild which displaying \begin_inset Quotes sld -\end_inset +\end_inset / \begin_inset Quotes srd -\end_inset +\end_inset instead of the \begin_inset Quotes sld -\end_inset +\end_inset . \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard For more details take a look into sysctl's manpage. -\layout Standard +\end_layout +\begin_layout Standard Hint: for digging fast into the settings, use the option \begin_inset Quotes sld -\end_inset +\end_inset -a \begin_inset Quotes srd -\end_inset +\end_inset (display all entries) in conjunction with \begin_inset Quotes sld -\end_inset +\end_inset grep \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Values found in /proc-filesystems -\layout Standard +\end_layout +\begin_layout Standard There are several formats seen in /proc-filesystem: -\layout Itemize +\end_layout +\begin_layout Itemize BOOLEAN: simple a \begin_inset Quotes sld -\end_inset +\end_inset 0 \begin_inset Quotes srd -\end_inset +\end_inset (false) or a \begin_inset Quotes sld -\end_inset +\end_inset 1 \begin_inset Quotes srd -\end_inset +\end_inset (true) -\layout Itemize +\end_layout +\begin_layout Itemize INTEGER: an integer value, can be unsigned, too -\layout Itemize +\end_layout +\begin_layout Itemize more sophisticated lines with several values: sometimes a header line is displayed also, if not, have a look into the kernel source to retrieve information about the meaning of each value... -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-sys-net-ipv6} -\end_inset +\end_inset Entries in /proc/sys/net/ipv6/ -\layout Subsection +\end_layout +\begin_layout Subsection conf/default/* -\layout Standard +\end_layout +\begin_layout Standard Change the interface-specific default settings. -\layout Subsection +\end_layout +\begin_layout Subsection conf/all/* -\layout Standard +\end_layout +\begin_layout Standard Change all the interface-specific settings. -\layout Standard +\end_layout +\begin_layout Standard Exception: \begin_inset Quotes sld -\end_inset +\end_inset conf/all/forwarding \begin_inset Quotes srd -\end_inset +\end_inset has a different meaning here -\layout Subsubsection +\end_layout +\begin_layout Subsubsection conf/all/forwarding -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Standard +\end_layout +\begin_layout Standard This enables global IPv6 forwarding between all interfaces. -\layout Standard +\end_layout +\begin_layout Standard In IPv6 you can't control forwarding per device, forwarding control has to be done using IPv6-netfilter (controlled with ip6tables) rulesets and specify input and output devices (see \begin_inset LatexCommand \ref[Firewalling/Netfilter6]{firewalling-netfilter6} -\end_inset +\end_inset for more). This is different to IPv4, where you are able to control forwarding per device (decision is made on interface where packet came in). -\layout Standard +\end_layout +\begin_layout Standard This also sets all interfaces' Host/Router setting 'forwarding' to the specified value. See below for details. This referred to as global forwarding. -\layout Standard +\end_layout +\begin_layout Standard If this value is 0, no IPv6 forwarding is enabled, packets never leave another interface, neither physical nor logical like e.g. tunnels. -\layout Subsection +\end_layout +\begin_layout Subsection conf/interface/* -\layout Standard +\end_layout +\begin_layout Standard Change special settings per interface. -\layout Standard +\end_layout +\begin_layout Standard The functional behaviour for certain settings is different depending on whether local forwarding is enabled or not. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection accept_ra -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Itemize +\end_layout +\begin_layout Itemize Functional default: enabled if local forwarding is disabled. disabled if local forwarding is enabled. -\layout Standard +\end_layout +\begin_layout Standard Accept Router Advertisements, and autoconfigure this interface with received data. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection accept_redirects -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Itemize +\end_layout +\begin_layout Itemize Functional default: enabled if local forwarding is disabled. disabled if local forwarding is enabled. -\layout Standard +\end_layout +\begin_layout Standard Accept Redirects sent by an IPv6 router. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection autoconf -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Itemize +\end_layout +\begin_layout Itemize Default: TRUE -\layout Standard +\end_layout +\begin_layout Standard Configure link-local addresses (see also \begin_inset LatexCommand \ref[Addresstypes]{chapter-addresstypes} -\end_inset +\end_inset ) using L2 hardware addresses. E.g. this generates automagically an address like \begin_inset Quotes sld -\end_inset +\end_inset fe80::201:23ff:fe45:6789 \begin_inset Quotes srd -\end_inset +\end_inset on an interface with a L2-MAC address. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dad_transmits -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 1 -\layout Standard +\end_layout +\begin_layout Standard The amount of Duplicate Address Detection probes to send. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection forwarding -\layout Itemize +\end_layout +\begin_layout Itemize Type: BOOLEAN -\layout Itemize +\end_layout +\begin_layout Itemize Default: FALSE if global forwarding is disabled (default), otherwise TRUE -\layout Standard +\end_layout +\begin_layout Standard Configure interface-specific Host/Router behaviour. -\layout Standard +\end_layout +\begin_layout Standard Note: It is recommended to have the same setting on all interfaces; mixed router/host scenarios are rather uncommon. -\layout Itemize +\end_layout +\begin_layout Itemize Value FALSE: By default, Host behaviour is assumed. This means: -\layout Enumerate +\end_layout +\begin_layout Enumerate IsRouter flag is not set in Neighbour Advertisements. -\layout Enumerate +\end_layout +\begin_layout Enumerate Router Solicitations are being sent when necessary. -\layout Enumerate +\end_layout +\begin_layout Enumerate If accept_ra is TRUE (default), accept Router Advertisements (and do autoconfigu ration). -\layout Enumerate +\end_layout +\begin_layout Enumerate If accept_redirects is TRUE (default), accept Redirects. -\layout Itemize +\end_layout +\begin_layout Itemize Value TRUE: If local forwarding is enabled, Router behaviour is assumed. This means exactly the reverse from the above: -\layout Enumerate +\end_layout +\begin_layout Enumerate IsRouter flag is set in Neighbour Advertisements. -\layout Enumerate +\end_layout +\begin_layout Enumerate Router Solicitations are not sent. -\layout Enumerate +\end_layout +\begin_layout Enumerate Router Advertisements are ignored. -\layout Enumerate +\end_layout +\begin_layout Enumerate Redirects are ignored. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection hop_limit -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 64 -\layout Standard +\end_layout +\begin_layout Standard Default Hop Limit to set. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mtu -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 1280 (IPv6 required minimum) -\layout Standard +\end_layout +\begin_layout Standard Default Maximum Transfer Unit -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitation_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 1 -\layout Standard +\end_layout +\begin_layout Standard Number of seconds to wait after interface is brought up before sending Router Solicitations. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitation_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 4 -\layout Standard +\end_layout +\begin_layout Standard Number of seconds to wait between Router Solicitations. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection router_solicitations -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 3 -\layout Standard +\end_layout +\begin_layout Standard Number of Router Solicitations to send until assuming no routers are present. -\layout Subsection +\end_layout +\begin_layout Subsection neigh/default/* -\layout Standard +\end_layout +\begin_layout Standard Change default settings for neighbor detection and some special global interval and threshold values: -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh1 -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 128 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh2 -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 512 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh3 -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 1024 -\layout Standard +\end_layout +\begin_layout Standard Tuning parameter for neighbour table size. -\layout Standard +\end_layout +\begin_layout Standard Increase this value if you have a lot of interfaces and problem with routes start to act mysteriously and fail. Or if a running \begin_inset LatexCommand \url[Zebra (routing daemon)]{http://www.zebra.org/} -\end_inset +\end_inset reports: -\layout Code +\end_layout +\begin_layout Code ZEBRA: netlink-listen error: No buffer space available, type=RTM_NEWROUTE(24), seq=426, pid=0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 30 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsection +\end_layout +\begin_layout Subsection neigh/interface/* -\layout Standard +\end_layout +\begin_layout Standard Change special settings per interface for neighbor detection. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection anycast_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 100 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_stale_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 60 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection proxy_qlen -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 64 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection unres_qlen -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 3 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection app_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 0 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection locktime -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 0 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection retrans_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 100 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection base_reachable_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 30 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mcast_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 3 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ucast_solicit -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 3 -\layout Standard +\end_layout +\begin_layout Standard More to be filled -\layout Subsubsection +\end_layout +\begin_layout Subsubsection delay_first_probe_time -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 5 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection proxy_delay -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 80 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsection +\end_layout +\begin_layout Subsection route/* -\layout Standard +\end_layout +\begin_layout Standard Change global settings for routing. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection flush -\layout Standard +\end_layout +\begin_layout Standard Removed in newer kernel releases - more to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 30 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_thresh -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 1024 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection mtu_expires -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 600 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_elasticity -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 0 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_min_interval -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 5 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection gc_timeout -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 60 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection min_adv_mss -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 12 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection max_size -\layout Itemize +\end_layout +\begin_layout Itemize Type: INTEGER -\layout Itemize +\end_layout +\begin_layout Itemize Default: 4096 -\layout Standard +\end_layout +\begin_layout Standard More to be filled. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-sys-net-ipv4} -\end_inset +\end_inset IPv6-related entries in /proc/sys/net/ipv4/ -\layout Standard +\end_layout +\begin_layout Standard At the moment (and this will be until IPv4 is completly converted to an independend kernel module) some switches are also used here for IPv6. -\layout Subsection +\end_layout +\begin_layout Subsection ip_* -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ip_local_port_range -\layout Standard +\end_layout +\begin_layout Standard This control setting is used by IPv6 also. -\layout Subsection +\end_layout +\begin_layout Subsection tcp_* -\layout Standard +\end_layout +\begin_layout Standard This control settings are used by IPv6 also. -\layout Subsection +\end_layout +\begin_layout Subsection icmp_* -\layout Standard +\end_layout +\begin_layout Standard This control settings are not used by IPv6. To enable ICMPv6 rate limiting (which is very recommended because of the capability of ICMPv6 storms) netfilter-v6 rules must be used. -\layout Subsection +\end_layout +\begin_layout Subsection others -\layout Standard +\end_layout +\begin_layout Standard Unknown, but probably not used by IPv6. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{proc-net} -\end_inset +\end_inset IPv6-related entries in /proc/net/ -\layout Standard +\end_layout +\begin_layout Standard In /proc/net there are several read-only entries available. You cannot retrieve information using \begin_inset Quotes sld -\end_inset +\end_inset sysctl \begin_inset Quotes srd -\end_inset +\end_inset here, so use e.g. \begin_inset Quotes sld -\end_inset +\end_inset cat \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection if_inet6 -\layout Itemize +\end_layout +\begin_layout Itemize Type: One line per addresss containing multiple values -\layout Standard +\end_layout +\begin_layout Standard Here all configured IPv6 addresses are shown in a special format. The example displays for loopback interface only. The meaning is shown below (see \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/addrconf.c \begin_inset Quotes srd -\end_inset +\end_inset for more). -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/if_inet6 -\layout Code +\end_layout +\begin_layout Code 00000000000000000000000000000001 01 80 10 80 lo -\layout Code +\end_layout +\begin_layout Code +------------------------------+ ++ ++ ++ ++ ++ -\layout Code +\end_layout +\begin_layout Code | | | | | | -\layout Code +\end_layout +\begin_layout Code 1 2 3 4 5 6 -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 address displayed in 32 hexadecimal chars without colons as separator -\layout Enumerate +\end_layout +\begin_layout Enumerate Netlink device number (interface index) in hexadecimal (see \begin_inset Quotes sld -\end_inset +\end_inset ip addr \begin_inset Quotes srd -\end_inset +\end_inset , too) -\layout Enumerate +\end_layout +\begin_layout Enumerate Prefix length in hexadecimal -\layout Enumerate +\end_layout +\begin_layout Enumerate Scope value (see kernel source \begin_inset Quotes sld -\end_inset +\end_inset include/net/ipv6.h \begin_inset Quotes srd -\end_inset +\end_inset and \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/addrconf.c \begin_inset Quotes srd -\end_inset +\end_inset for more) -\layout Enumerate +\end_layout +\begin_layout Enumerate Interface flags (see \begin_inset Quotes sld -\end_inset +\end_inset include/linux/rtnetlink.h \begin_inset Quotes srd -\end_inset +\end_inset and \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/addrconf.c \begin_inset Quotes srd -\end_inset +\end_inset for more) -\layout Enumerate +\end_layout +\begin_layout Enumerate Device name -\layout Subsection +\end_layout +\begin_layout Subsection ipv6_route -\layout Itemize +\end_layout +\begin_layout Itemize Type: One line per route containing multiple values -\layout Standard +\end_layout +\begin_layout Standard Here all configured IPv6 routes are shown in a special format. The example displays for loopback interface only. The meaning is shown below (see \begin_inset Quotes sld -\end_inset +\end_inset net/ipv6/route.c \begin_inset Quotes srd -\end_inset +\end_inset for more). -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/ipv6_route -\layout Code +\end_layout +\begin_layout Code 00000000000000000000000000000000 00 00000000000000000000000000000000 00 -\layout Code +\end_layout +\begin_layout Code +------------------------------+ ++ +------------------------------+ ++ -\layout Code +\end_layout +\begin_layout Code | | | | -\layout Code +\end_layout +\begin_layout Code 1 2 3 4 -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code ¬ 00000000000000000000000000000000 ffffffff 00000001 00000001 00200200 lo -\layout Code +\end_layout +\begin_layout Code ¬ +------------------------------+ +------+ +------+ +------+ +------+ ++ -\layout Code +\end_layout +\begin_layout Code ¬ | | | | | | -\layout Code +\end_layout +\begin_layout Code ¬ 5 6 7 8 9 10 -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 destination network displayed in 32 hexadecimal chars without colons as separator -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 destination prefix length in hexadecimal -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 source network displayed in 32 hexadecimal chars without colons as separator -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 source prefix length in hexadecimal -\layout Enumerate +\end_layout +\begin_layout Enumerate IPv6 next hop displayed in 32 hexadecimal chars without colons as separator -\layout Enumerate +\end_layout +\begin_layout Enumerate Metric in hexadecimal -\layout Enumerate +\end_layout +\begin_layout Enumerate Reference counter -\layout Enumerate +\end_layout +\begin_layout Enumerate Use counter -\layout Enumerate +\end_layout +\begin_layout Enumerate Flags -\layout Enumerate +\end_layout +\begin_layout Enumerate Device name -\layout Subsection +\end_layout +\begin_layout Subsection sockstat6 -\layout Itemize +\end_layout +\begin_layout Itemize Type: One line per protocol with description and value -\layout Standard +\end_layout +\begin_layout Standard Statistics about used IPv6 sockets. Example: -\layout Code +\end_layout +\begin_layout Code # cat /proc/net/sockstat6 -\layout Code +\end_layout +\begin_layout Code TCP6: inuse 7 -\layout Code +\end_layout +\begin_layout Code UDP6: inuse 2 -\layout Code +\end_layout +\begin_layout Code RAW6: inuse 1 -\layout Code +\end_layout +\begin_layout Code FRAG6: inuse 0 memory 0 -\layout Subsection +\end_layout +\begin_layout Subsection tcp6 -\layout Standard +\end_layout +\begin_layout Standard To be filled. -\layout Subsection +\end_layout +\begin_layout Subsection udp6 -\layout Standard +\end_layout +\begin_layout Standard To be filled. -\layout Subsection +\end_layout +\begin_layout Subsection igmp6 -\layout Standard +\end_layout +\begin_layout Standard To be filled. -\layout Subsection +\end_layout +\begin_layout Subsection raw6 -\layout Standard +\end_layout +\begin_layout Standard To be filled. -\layout Subsection +\end_layout +\begin_layout Subsection ip6_flowlabel -\layout Standard +\end_layout +\begin_layout Standard To be filled. -\layout Subsection +\end_layout +\begin_layout Subsection rt6_stats -\layout Standard +\end_layout +\begin_layout Standard To be filled. -\layout Subsection +\end_layout +\begin_layout Subsection snmp6 -\layout Itemize +\end_layout +\begin_layout Itemize Type: One line per SNMP description and value -\layout Standard +\end_layout +\begin_layout Standard SNMP statistics, can be retrieved via SNMP server and related MIB table by network management software. -\layout Subsection +\end_layout +\begin_layout Subsection ip6_tables_names -\layout Standard +\end_layout +\begin_layout Standard Available netfilter6 tables -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{netlink} -\end_inset +\end_inset Netlink-Interface to kernel -\layout Standard +\end_layout +\begin_layout Standard To be filled...I have no experience with that... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{network-debugging} -\end_inset +\end_inset Network debugging -\layout Section +\end_layout +\begin_layout Section Server socket binding -\layout Subsection +\end_layout +\begin_layout Subsection Using \begin_inset Quotes sld -\end_inset +\end_inset netstat \begin_inset Quotes srd -\end_inset +\end_inset for server socket binding check -\layout Standard +\end_layout +\begin_layout Standard It's always interesting which server sockets are currently active on a node. Using \begin_inset Quotes sld -\end_inset +\end_inset netstat \begin_inset Quotes srd -\end_inset +\end_inset is a short way to get such information: -\layout Standard +\end_layout +\begin_layout Standard Used options: -nlptu -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # netstat -nlptu -\layout Code +\end_layout +\begin_layout Code Active Internet connections (only servers) -\layout Code +\end_layout +\begin_layout Code Proto Recv-Q Send-Q Local Address Foreign Address State -\layout Code +\end_layout +\begin_layout Code ¬ PID/Program name -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:32768 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1258/rpc.statd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:32769 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1502/rpc.mountd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:515 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 22433/lpd Waiting -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:139 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1746/smbd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1230/portmap -\layout Code +\end_layout +\begin_layout Code tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 3551/X -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:8081 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 18735/junkbuster -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.1:3128 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:1.2.3.1:993 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::13 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:1.2.3.1:143 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 6742/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::53 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::22 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 1410/sshd -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::6010 :::* LISTEN -\layout Code +\end_layout +\begin_layout Code ¬ 13237/sshd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32768 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1258/rpc.statd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:2049 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ - -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32770 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1502/rpc.mountd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32771 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ - -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:137 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:137 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:138 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:138 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1751/nmbd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:33044 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.1:53 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 127.0.0.1:53 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:67 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1530/dhcpd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:67 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1530/dhcpd -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32858 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:4827 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 18822/(squid) -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:111 0.0.0.0:* -\layout Code +\end_layout +\begin_layout Code ¬ 1230/portmap -\layout Code +\end_layout +\begin_layout Code udp 0 0 :::53 :::* -\layout Code +\end_layout +\begin_layout Code ¬ 30734/named -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{examples-tcpdump} -\end_inset +\end_inset Examples for tcpdump packet dumps -\layout Standard +\end_layout +\begin_layout Standard Here some examples of captured packets are shown, perhaps useful for your own debugging... -\layout Standard +\end_layout +\begin_layout Standard ...more coming next... -\layout Subsection +\end_layout +\begin_layout Subsection Router discovery -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Router advertisement -\layout Code +\end_layout +\begin_layout Code 15:43:49.484751 fe80::212:34ff:fe12:3450 > ff02::1: icmp6: router -\layout Code +\end_layout +\begin_layout Code ¬ advertisement(chlim=64, router_ltime=30, reachable_time=0, -\layout Code +\end_layout +\begin_layout Code ¬ retrans_time=0)(prefix info: AR valid_ltime=30, preffered_ltime=20, -\layout Code +\end_layout +\begin_layout Code ¬ prefix=2002:0102:0304:1::/64)(prefix info: LAR valid_ltime=2592000, -\layout Code +\end_layout +\begin_layout Code ¬ preffered_ltime=604800, prefix=3ffe:ffff:0:1::/64)(src lladdr: -\layout Code +\end_layout +\begin_layout Code ¬ 0:12:34:12:34:50) (len 88, hlim 255) -\layout Standard +\end_layout +\begin_layout Standard Router with link-local address \begin_inset Quotes sld -\end_inset +\end_inset fe80::212:34ff:fe12:3450 \begin_inset Quotes srd -\end_inset +\end_inset send an advertisement to the all-node-on-link multicast address \begin_inset Quotes sld -\end_inset +\end_inset ff02::1 \begin_inset Quotes srd -\end_inset +\end_inset containing two prefixes \begin_inset Quotes sld -\end_inset +\end_inset 2002:0102:0304:1::/64 \begin_inset Quotes srd -\end_inset +\end_inset (lifetime 30 s) and \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1::/64 \begin_inset Quotes srd -\end_inset +\end_inset (lifetime 2592000 s) including its own layer 2 MAC address \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:50 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Router solicitation -\layout Code +\end_layout +\begin_layout Code 15:44:21.152646 fe80::212:34ff:fe12:3456 > ff02::2: icmp6: router solicitation -\layout Code +\end_layout +\begin_layout Code ¬ (src lladdr: 0:12:34:12:34:56) (len 16, hlim 255) -\layout Standard +\end_layout +\begin_layout Standard Node with link-local address \begin_inset Quotes sld -\end_inset +\end_inset fe80::212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset and layer 2 MAC address \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:56 \begin_inset Quotes srd -\end_inset +\end_inset is looking for a router on-link, therefore sending this solicitation to the all-router-on-link multicast address \begin_inset Quotes sld -\end_inset +\end_inset ff02::2 \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Neighbor discovery -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Neighbor discovery solicitation for duplicate address detection -\layout Standard +\end_layout +\begin_layout Standard Following packets are sent by a node with layer 2 MAC address \begin_inset Quotes sld -\end_inset +\end_inset 0:12:34:12:34:56 \begin_inset Quotes srd -\end_inset +\end_inset 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. -\layout Itemize +\end_layout +\begin_layout Itemize Node wants to configure its link-local address \begin_inset Quotes sld -\end_inset +\end_inset fe80::212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset , checks for duplicate now -\layout Code +\end_layout +\begin_layout Code 15:44:17.712338 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ fe80::212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Node wants to configure its global address \begin_inset Quotes sld -\end_inset +\end_inset 2002:0102:0304:1:212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset (after receiving advertisement shown above), checks for duplicate now -\layout Code +\end_layout +\begin_layout Code 15:44:21.905596 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ 2002:0102:0304:1:212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, -\layout Code +\end_layout +\begin_layout Code ¬ hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Node wants to configure its global address \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1:212:34ff:fe12:3456 \begin_inset Quotes srd -\end_inset +\end_inset (after receiving advertisement shown above), checks for duplicate now -\layout Code +\end_layout +\begin_layout Code 15:44:22.304028 :: > ff02::1:ff12:3456: icmp6: neighbor sol: who has -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:0:1:212:34ff:fe12:3456(src lladdr: 0:12:34:12:34:56) (len 32, hlim -\layout Code +\end_layout +\begin_layout Code ¬ 255) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Neighbor discovery solicitation for looking for host or gateway -\layout Itemize +\end_layout +\begin_layout Itemize Node wants to send packages to \begin_inset Quotes sld -\end_inset +\end_inset 3ffe:ffff:0:1::10 \begin_inset Quotes srd -\end_inset +\end_inset but has no layer 2 MAC address to send packet, so send solicitation now -\layout Code +\end_layout +\begin_layout Code 13:07:47.664538 2002:0102:0304:1:2e0:18ff:fe90:9205 > ff02::1:ff00:10: icmp6: -\layout Code +\end_layout +\begin_layout Code ¬ neighbor sol: who has 3ffe:ffff:0:1::10(src lladdr: 0:e0:18:90:92:5) (len 32, -\layout Code +\end_layout +\begin_layout Code ¬ hlim 255) -\layout Itemize +\end_layout +\begin_layout Itemize Node looks for \begin_inset Quotes sld -\end_inset +\end_inset fe80::10 \begin_inset Quotes srd -\end_inset +\end_inset now -\layout Code +\end_layout +\begin_layout Code 13:11:20.870070 fe80::2e0:18ff:fe90:9205 > ff02::1:ff00:10: icmp6: neighbor -\layout Code +\end_layout +\begin_layout Code ¬ sol: who has fe80::10(src lladdr: 0:e0:18:90:92:5) (len 32, hlim 255) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-support-persistent-configuration} -\end_inset +\end_inset Support for persistent IPv6 configuration in Linux distributions -\layout Standard +\end_layout +\begin_layout Standard Some Linux distribution contain already support of a persistent IPv6 configurati on using existing or new configuration and script files and some hook in the IPv4 script files. -\layout Section +\end_layout +\begin_layout Section Red Hat Linux and \begin_inset Quotes sld -\end_inset +\end_inset clones \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Since starting writing the \begin_inset LatexCommand \url[IPv6 & Linux - HowTo]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset 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, @@ -6870,2378 +8484,2806 @@ Since starting writing the they got their own homepage: \begin_inset LatexCommand \url[initscripts-ipv6 homepage]{http://www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ). 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 -\emph on +\emph on historic issue -\emph default +\emph default ). 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. -\layout Standard +\end_layout +\begin_layout Standard 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. -\layout Standard +\end_layout +\begin_layout Standard Mandrake since version 8.0 also includes an IPv6-enabled initscript package, but a minor bug still prevents usage ( \begin_inset Quotes sld -\end_inset +\end_inset ifconfig \begin_inset Quotes srd -\end_inset +\end_inset misses \begin_inset Quotes sld -\end_inset +\end_inset inet6 \begin_inset Quotes srd -\end_inset +\end_inset before \begin_inset Quotes sld -\end_inset +\end_inset add \begin_inset Quotes srd -\end_inset +\end_inset ). -\layout Subsection +\end_layout +\begin_layout Subsection Test for IPv6 support of network configuration scripts -\layout Standard +\end_layout +\begin_layout Standard You can test, whether your Linux distribution contain support for persistent IPv6 configuration using my set. Following script library should exist: -\layout Code +\end_layout +\begin_layout Code /etc/sysconfig/network-scripts/network-functions-ipv6 -\layout Standard +\end_layout +\begin_layout Standard Auto-magically test: -\layout Code +\end_layout +\begin_layout Code # test -f /etc/sysconfig/network-scripts/network-functions-ipv6 && echo "Main -\layout Code +\end_layout +\begin_layout Code ¬ IPv6 script library exists" -\layout Standard +\end_layout +\begin_layout Standard The version of the library is important if you miss some features. You can get it executing following (or easier look at the top of the file): -\layout Code +\end_layout +\begin_layout Code # source /etc/sysconfig/network-scripts/network-functions-ipv6 && -\layout Code +\end_layout +\begin_layout Code ¬ getversion_ipv6_functions -\layout Code +\end_layout +\begin_layout Code 20011124 -\layout Standard +\end_layout +\begin_layout Standard In shown example, the used version is -\series bold +\series bold 20011124 -\series default +\series default . Check this against latest information on \begin_inset LatexCommand \url[initscripts-ipv6 homepage]{http://www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/projects/initscripts-ipv6.html} -\end_inset +\end_inset ) to see what has been changed. You will find there also a change-log. -\layout Subsection +\end_layout +\begin_layout Subsection Short hint for enabling IPv6 on current RHL 7.1, 7.2, 7.3, ... -\layout Itemize +\end_layout +\begin_layout Itemize Check whether running system has already IPv6 module loaded -\layout Code +\end_layout +\begin_layout Code # modprobe -c | grep net-pf-10 -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 off -\layout Itemize +\end_layout +\begin_layout Itemize If result is \begin_inset Quotes sld -\end_inset +\end_inset off \begin_inset Quotes srd -\end_inset +\end_inset , then enable IPv6 networking by editing /etc/sysconfig/network, add following new line -\layout Code +\end_layout +\begin_layout Code NETWORKING_IPV6=yes -\layout Itemize +\end_layout +\begin_layout Itemize Reboot or restart networking using -\layout Code +\end_layout +\begin_layout Code # service network restart -\layout Itemize +\end_layout +\begin_layout Itemize Now IPv6 module should be loaded -\layout Code +\end_layout +\begin_layout Code # modprobe -c | grep ipv6 -\layout Code +\end_layout +\begin_layout Code alias net-pf-10 ipv6 -\layout Standard +\end_layout +\begin_layout Standard If your system is on a link which provides router advertisement, autoconfigurati on will be done automatically. For more information which settings are supported see /usr/share/doc/initscript s-$version/sysconfig.txt. -\layout Section +\end_layout +\begin_layout Section SuSE Linux -\layout Standard +\end_layout +\begin_layout Standard In newer 7.x versions there is a really rudimentary support available, see /etc/rc.config for details. -\layout Standard +\end_layout +\begin_layout Standard Because of the really different configuration and script file structure it is hard (or impossible) to use the set for Red Hat Linux and clones with this distribution. -\newline -In versions 8.x they completly change their configuration setup. +\newline +In versions 8.x they completly change their configuration + setup. -\layout Subsection +\end_layout +\begin_layout Subsection SuSE Linux 7.3 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[How to setup 6to4 IPv6 with SuSE 7.3]{http://www.feyrer.de/IPv6/SuSE73-IPv6+6to4-setup.html} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection SuSE Linux 8.0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 address configuration -\layout Standard +\end_layout +\begin_layout Standard Edit file /etc/sysconfig/network/ifcfg- and setup following value -\layout Code +\end_layout +\begin_layout Code IP6ADDR="/" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Additional information -\layout Standard +\end_layout +\begin_layout Standard See file /usr/share/doc/packages/sysconfig/README -\layout Subsection +\end_layout +\begin_layout Subsection SuSE Linux 8.1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 address configuration -\layout Standard +\end_layout +\begin_layout Standard Edit file /etc/sysconfig/network/ifcfg- and setup following value -\layout Code +\end_layout +\begin_layout Code IPADDR="/" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Additional information -\layout Standard +\end_layout +\begin_layout Standard See file /usr/share/doc/packages/sysconfig/Network -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{Configuration-Debian-Linux} -\end_inset +\end_inset Debian Linux -\layout Standard +\end_layout +\begin_layout Standard Following information was contributed by Stephane Bortzmeyer -\layout Enumerate +\end_layout +\begin_layout Enumerate Be sure that IPv6 is loaded, either because it is compiled into the kernel or because the module is loaded. For the latest, three solutions, adding it to /etc/modules, using the pre-up trick shown later or using kmod (not detailed here). -\layout Enumerate +\end_layout +\begin_layout Enumerate Configure your interface. Here we assume eth0 and address (3ffe:ffff:1234:5::1:1). Edit /etc/network/interfaces: -\layout Code +\end_layout +\begin_layout Code iface eth0 inet6 static -\layout Code +\end_layout +\begin_layout Code pre-up modprobe ipv6 -\layout Code +\end_layout +\begin_layout Code address 3ffe:ffff:1234:5::1:1 -\layout Code +\end_layout +\begin_layout Code # To suppress completely autoconfiguration: -\layout Code +\end_layout +\begin_layout Code # up echo 0 > /proc/sys/net/ipv6/conf/all/autoconf -\layout Code +\end_layout +\begin_layout Code netmask 64 -\layout Code +\end_layout +\begin_layout Code # The router is autoconfigured and has no fixed address. -\layout Code +\end_layout +\begin_layout Code # It is magically -\layout Code +\end_layout +\begin_layout Code # found. (/proc/sys/net/ipv6/conf/all/accept_ra). Otherwise: -\layout Code +\end_layout +\begin_layout Code #gateway 3ffe:ffff:1234:5::1 -\layout Standard +\end_layout +\begin_layout Standard And you reboot or you just -\layout Code +\end_layout +\begin_layout Code # ifup --force eth0 -\layout Standard +\end_layout +\begin_layout Standard and you have your static address. -\layout Subsection +\end_layout +\begin_layout Subsection Further information -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 on Debian Linux]{http://people.debian.org/~csmall/ipv6/} -\end_inset +\end_inset by Craig Small -\layout Itemize +\end_layout +\begin_layout Itemize Jean-Marc V. Liotier's \begin_inset LatexCommand \url[HOWTO for Freenet6 & Debian Users]{http://www.ruwenzori.net/ipv6/Jims_LAN_IPv6_global_connectivity_howto.html} -\end_inset +\end_inset (announced 24.12.2002 on \begin_inset LatexCommand \ref[mailinglist]{information-maillists} -\end_inset +\end_inset users@ipv6.org ) -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-autoconfiguration} -\end_inset +\end_inset Auto-configuration and mobility -\layout Section +\end_layout +\begin_layout Section Stateless auto-configuration -\layout Standard +\end_layout +\begin_layout Standard Is supported and seen on the assigned link-local address after an IPv6-enabled interface is up. -\layout Standard +\end_layout +\begin_layout Standard Example: -\layout Code +\end_layout +\begin_layout Code # ip -6 addr show dev eth0 scope link -\layout Code +\end_layout +\begin_layout Code 2: eth0: mtu 1500 qlen1000 -\layout Code +\end_layout +\begin_layout Code inet6 fe80::211:d8ff:fe6b:f0f5/64 scope link -\layout Code +\end_layout +\begin_layout Code valid_lft forever preferred_lft forever -\layout Section +\end_layout +\begin_layout Section Stateful auto-configuration using Router Advertisement Daemon (radvd) -\layout Standard +\end_layout +\begin_layout Standard to be filled. See \begin_inset LatexCommand \ref[radvd daemon autoconfiguration]{hints-daemons-radvd} -\end_inset +\end_inset below. -\layout Section +\end_layout +\begin_layout Section Dynamic Host Configuration Protocol v6 (DHCPv6) -\layout Standard +\end_layout +\begin_layout Standard After a long time discussing issues, finally \begin_inset LatexCommand \url[RFC 3315 / Dynamic Host Configuration Protocol for IPv6 (DHCPv6)]{http://www.faqs.org/rfcs/rfc3315.html} -\end_inset +\end_inset was finished. At time updating this part (10/2005) currently two implementations are available: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Dibbler]{http://klub.com.pl/dhcpv6/} -\end_inset +\end_inset by Tomasz Mrugalski -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DHCPv6 on Sourceforge]{http://dhcpv6.sourceforge.net/} -\end_inset +\end_inset + ( +\begin_inset LatexCommand \ref[Hints for configuration]{hints-daemons-dhcpv6} -\layout Section +\end_inset +) +\end_layout + +\begin_layout Section Mobility -\layout Standard +\end_layout -to be filled. - -\layout Standard +\begin_layout Subsection +Node Mobility +\end_layout -For the moment, see -\begin_inset LatexCommand \url[Mobile IPv6 for Linux(MIPL) homepage]{http://www.mipl.mediapoli.com/} +\begin_layout Standard +Support for IPv6 mobility can be enabled in Linux by installing the MIPL2 + implementation found at: +\begin_inset LatexCommand \url[http://www.mobile-ipv6.org]{http://www.mobile-ipv6.org} -\end_inset +\end_inset - for more details. - Further infos can be found here (please report broken links): -\layout Itemize +\end_layout -\begin_inset LatexCommand \url[draft-oneill-mipv6-cao-??.txt / MIPv6 Care of Address Option]{http://www.ietf.org/internet-drafts/} +\begin_layout Standard +This implementation is compliant with RFC 3775. + It is composed of a kernel patch and a mobility daemon called mip6d. + Version 2.0.1 applies on Linux kernel 2.6.15. +\end_layout -\end_inset +\begin_layout Standard +Installation and setup are described in the Linux Mobile IPv6 HOWTO: +\begin_inset LatexCommand \url[http://gnist.org/~lars/doc/Mobile-IPv6-HOWTO/Mobile-IPv6-HOWTO.html]{http://gnist.org/~lars/doc/Mobile-IPv6-HOWTO/Mobile-IPv6-HOWTO.html} +\end_inset -\layout Itemize + (temporary link) +\end_layout +\begin_layout Subsection +Network Mobility +\end_layout -\begin_inset LatexCommand \url[draft-mccann-mobileip-80211fh-??.txt / Mobile IPv6 Fast Handovers for 802.11 Networks]{http://www.ietf.org/internet-drafts/} +\begin_layout Standard +There also exists an implementation of network mobility for Linux, it is + called NEPL and is based on MIPL. + It can also be downloaded from: +\begin_inset LatexCommand \url[http://www.mobile-ipv6.org]{http://www.mobile-ipv6.org} -\end_inset +\end_inset +. +\end_layout -\layout Itemize +\begin_layout Standard +The HOWTO document describing setup and configuration is available at: +\begin_inset LatexCommand \url[http://www.nautilus6.org/doc/nepl-howto/]{http://www.nautilus6.org/doc/nepl-howto/} +\end_inset -\begin_inset LatexCommand \url[draft-haberman-ipv6-anycast-rr-??.txt / IPv6 Anycast Binding using Return Routability]{http://www.ietf.org/internet-drafts/} +. +\end_layout -\end_inset +\begin_layout Subsection +Links +\end_layout +\begin_layout Itemize +Mobile IPv6 for Linux (MIPL) project: +\begin_inset LatexCommand \url[http://www.mobile-ipv6.org]{http://www.mobile-ipv6.org} -\layout Itemize +\end_inset -\begin_inset LatexCommand \url[draft-mun-aaa-localkm-mobileipv6-??.txt / Localized Key Management for AAA in MobileIPv6]{http://www.ietf.org/internet-drafts/} +\end_layout -\end_inset +\begin_layout Itemize +Nautilus6 working group: +\begin_inset LatexCommand \url[http://nautilus6.org/]{http://nautilus6.org/} +\end_inset -\layout Itemize +\end_layout -\begin_inset LatexCommand \url[draft-thubert-nemo-ro-taxonomy-??.txt / Taxonomy of Route Optimization Models in the NEMO Context]{http://www.ietf.org/internet-drafts/} +\begin_layout Itemize +Fast Handovers for Mobile IPv6 for Linux project: +\begin_inset LatexCommand \url[http://www.fmipv6.org/]{http://www.fmipv6.org/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize +RFC 3775, Mobility Support in IPv6: +\begin_inset LatexCommand \url[http://www.ietf.org/rfc/rfc3775.txt]{http://www.ietf.org/rfc/rfc3775.txt} -\begin_inset LatexCommand \url[draft-le-aaa-diameter-mobileipv6-??.txt / Diameter Mobile IPv6 Application]{http://www.ietf.org/internet-drafts/} +\end_inset -\end_inset +\end_layout -\layout Itemize +\begin_layout Itemize +RFC 3776, Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes + and Home Agents: +\begin_inset LatexCommand \url[http://www.ietf.org/rfc/rfc3776.txt]{http://www.ietf.org/rfc/rfc3776.txt} +\end_inset -\begin_inset LatexCommand \url[draft-wakikawa-manet-globalv6-??.txt / Global Connectivity for IPv6 Mobile Ad Hoc Networks]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_layout +\begin_layout Itemize +RFC 3963, Network Mobility (NEMO): +\begin_inset LatexCommand \url[http://www.ietf.org/rfc/rfc3963.txt]{http://www.ietf.org/rfc/rfc3963.txt} -\layout Itemize +\end_inset -\begin_inset LatexCommand \url[draft-ietf-mobileip-fast-mipv6-??.txt / Fast Handovers for Mobile IPv6]{http://www.ietf.org/internet-drafts/} +\end_layout -\end_inset +\begin_layout Itemize +RFC 4068, Fast Handovers for Mobile IPv6: +\begin_inset LatexCommand \url[http://www.ietf.org/rfc/rfc4068.txt]{http://www.ietf.org/rfc/rfc4068.txt} +\end_inset -\layout Itemize - - -\begin_inset LatexCommand \url[draft-ietf-mobileip-ipv6-??.txt / Mobility Support in IPv6]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-ohnishi-mobileip-v6vpngateway-??.txt / Mobile IPv6 VPN using Gateway Home Agent]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-ietf-mobileip-hmipv6-??.txt / Hierarchical MIPv6 mobility management (HMIPv6)]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-mkhalil-ipv6-fastra-??.txt / IPv6 Fast Router Advertisement]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-okazaki-mobileip-abk-??.txt / Securing MIPv6 Binding Updates Using Address Based Keys (ABKs)]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-vriz-mobileip-hbhlmap-??.txt / Hop-by-Hop Local Mobility Agents Probing for Mobile IPv6]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-thubert-nemo-reverse-routing-header-??.txt / IPv6 Reverse Routing Header and its application to Mobile Networks]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-ietf-mobileip-mipv6-ha-ipsec-??.txt / Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-suh-rmm-??.txt / Regional Mobile IPv6 mobility management]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-mccann-mobileip-ipv6mipv4-??.txt / IPv6 over Mobile IPv4]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-kempf-mobileip-fmipv6-sem-??.txt / Improving the Architectural Alignment for FMIPv6]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-le-aaa-mipv6-requirements-??.txt / Mobile IPv6 Authentication, Authorization, and Accounting Requirements]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[draft-hwang-rohc-mipv6-??.txt / RObust Header Compression (ROHC): A Compression Profile for Mobile IPv6]{http://www.ietf.org/internet-drafts/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[LANCASTER MOBILE IPv6 PACKAGE]{http://www.cs-ipv6.lancs.ac.uk/ipv6/MobileIP/} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[Testbed for MIND project on IPv6]{http://gsyc.escet.urjc.es/Mobiquo/Mind/documentacion/MontajeMaquetaIPv6_en/MontajeMaquetaIPv6_en.html} - -\end_inset - - -\layout Itemize - - -\begin_inset LatexCommand \url[Mobile IPv6 Issue List]{http://www.piuha.net/~jarkko/publications/mipv6/MIPv6-Issues.html} - -\end_inset - - -\layout Chapter +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-firewalling-security} -\end_inset +\end_inset Firewalling -\layout Standard +\end_layout +\begin_layout Standard IPv6 firewalling is important, especially if using IPv6 on internal networks with global IPv6 addresses. Because unlike at IPv4 networks where in common internal hosts are protected automatically using private IPv4 addresses like \begin_inset LatexCommand \url[RFC 1918 / Address Allocation for Private Internets]{http://www.faqs.org/rfcs/rfc1918.html} -\end_inset +\end_inset or Automatic Private IP Addressing (APIPA) \begin_inset LatexCommand \url[Google search for Microsoft + APIPA]{http://www.google.com/search?q=apipa+microsoft} -\end_inset +\end_inset , in IPv6 normally global addresses are used and someone with IPv6 connectivity can reach all internal IPv6 enabled nodes. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{firewalling-netfilter6} -\end_inset +\end_inset Firewalling using netfilter6 -\layout Standard +\end_layout +\begin_layout Standard Native IPv6 firewalling is only supported in kernel versions 2.4+. In older 2.2- you can only filter IPv6-in-IPv4 by protocol 41. -\layout Standard +\end_layout +\begin_layout Standard Attention: no warranty that described rules or examples can really protect your system! -\layout Standard +\end_layout +\begin_layout Standard Audit your ruleset after installation, see \begin_inset LatexCommand \ref{IPv6-security-auditing} -\end_inset +\end_inset for more. -\layout Standard +\end_layout +\begin_layout Standard Note also that the USAGI project is currently working on finishing the connectio n tracking for IPv6! This will make ruleset easier and more secure in the future! -\layout Subsection +\end_layout +\begin_layout Subsection More information -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Netfilter project]{http://www.netfilter.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[maillist archive of netfilter users]{https://lists.netfilter.org/mailman/listinfo/netfilter} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[maillist archive of netfilter developers]{https://lists.netfilter.org/mailman/listinfo/netfilter-devel} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Unofficial status informations]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-kernel.html#netfilter6 } -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section Preparation -\layout Subsection +\end_layout +\begin_layout Subsection Get sources -\layout Standard +\end_layout +\begin_layout Standard Get the latest kernel source: \begin_inset LatexCommand \url[http://www.kernel.org/]{http://www.kernel.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Get the latest iptables package: -\layout Itemize +\end_layout +\begin_layout Itemize Source tarball (for kernel patches): \begin_inset LatexCommand \url[http://www.netfilter.org/]{http://www.netfilter.org/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Source RPM for rebuild of binary (for RedHat systems): \begin_inset LatexCommand \url[ftp://ftp.redhat.com/redhat/linux/rawhide/SRPMS/SRPMS/]{ftp://ftp.redhat.com/redhat/linux/rawhide/SRPMS/SRPMS/} -\end_inset +\end_inset or perhaps also at \begin_inset LatexCommand \url[http://www.netcore.fi/pekkas/linux/ipv6/]{http://www.netcore.fi/pekkas/linux/ipv6/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Extract sources -\layout Standard +\end_layout +\begin_layout Standard Change to source directory: -\layout Code +\end_layout +\begin_layout Code # cd /path/to/src -\layout Standard +\end_layout +\begin_layout Standard Unpack and rename kernel sources -\layout Code +\end_layout +\begin_layout Code # tar z|jxf kernel-version.tar.gz|bz2 -\layout Code +\end_layout +\begin_layout Code # mv linux linux-version-iptables-version+IPv6 -\layout Standard +\end_layout +\begin_layout Standard Unpack iptables sources -\layout Code +\end_layout +\begin_layout Code # tar z|jxf iptables-version.tar.gz|bz2 -\layout Subsection +\end_layout +\begin_layout Subsection Apply latest iptables/IPv6-related patches to kernel source -\layout Standard +\end_layout +\begin_layout Standard Change to iptables directory -\layout Code +\end_layout +\begin_layout Code # cd iptables-version -\layout Standard +\end_layout +\begin_layout Standard Apply pending patches -\layout Code +\end_layout +\begin_layout Code # make pending-patches KERNEL_DIR=/path/to/src/linux-version-iptables-version/ -\layout Standard +\end_layout +\begin_layout Standard Apply additional IPv6 related patches (still not in the vanilla kernel included) -\layout Code +\end_layout +\begin_layout Code # make patch-o-matic KERNEL_DIR=/path/to/src/linux-version-iptables-version/ -\layout Standard +\end_layout +\begin_layout Standard Say yes at following options (iptables-1.2.2) -\layout Itemize +\end_layout +\begin_layout Itemize ah-esp.patch -\layout Itemize +\end_layout +\begin_layout Itemize masq-dynaddr.patch (only needed for systems with dynamic IP assigned WAN connections like PPP or PPPoE) -\layout Itemize +\end_layout +\begin_layout Itemize ipv6-agr.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize ipv6-ports.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize LOG.patch.ipv6 -\layout Itemize +\end_layout +\begin_layout Itemize REJECT.patch.ipv6 -\layout Standard +\end_layout +\begin_layout Standard Check IPv6 extensions -\layout Code +\end_layout +\begin_layout Code # make print-extensions -\layout Code +\end_layout +\begin_layout Code Extensions found: IPv6:owner IPv6:limit IPv6:mac IPv6:multiport -\layout Subsection +\end_layout +\begin_layout Subsection Configure, build and install new kernel -\layout Standard +\end_layout +\begin_layout Standard Change to kernel sources -\layout Code +\end_layout +\begin_layout Code # cd /path/to/src/linux-version-iptables-version/ -\layout Standard +\end_layout +\begin_layout Standard Edit Makefile -\layout Code +\end_layout +\begin_layout Code - EXTRAVERSION = -\layout Code +\end_layout +\begin_layout Code + EXTRAVERSION = -iptables-version+IPv6-try -\layout Standard +\end_layout +\begin_layout Standard Run configure, enable IPv6 related -\layout Code +\end_layout +\begin_layout Code Code maturity level options -\layout Code +\end_layout +\begin_layout Code Prompt for development and/or incomplete code/drivers : yes -\layout Code +\end_layout +\begin_layout Code Networking options -\layout Code +\end_layout +\begin_layout Code Network packet filtering: yes -\layout Code +\end_layout +\begin_layout Code The IPv6 protocol: module -\layout Code +\end_layout +\begin_layout Code IPv6: Netfilter Configuration -\layout Code +\end_layout +\begin_layout Code IP6 tables support: module -\layout Code +\end_layout +\begin_layout Code All new options like following: -\layout Code +\end_layout +\begin_layout Code limit match support: module -\layout Code +\end_layout +\begin_layout Code MAC address match support: module -\layout Code +\end_layout +\begin_layout Code Multiple port match support: module -\layout Code +\end_layout +\begin_layout Code Owner match support: module -\layout Code +\end_layout +\begin_layout Code netfilter MARK match support: module -\layout Code +\end_layout +\begin_layout Code Aggregated address check: module -\layout Code +\end_layout +\begin_layout Code Packet filtering: module -\layout Code +\end_layout +\begin_layout Code REJECT target support: module -\layout Code +\end_layout +\begin_layout Code LOG target support: module -\layout Code +\end_layout +\begin_layout Code Packet mangling: module -\layout Code +\end_layout +\begin_layout Code MARK target support: module -\layout Standard +\end_layout +\begin_layout Standard Configure other related to your system, too -\layout Standard +\end_layout +\begin_layout Standard Compilation and installing: see the kernel section here and other HOWTOs -\layout Subsection +\end_layout +\begin_layout Subsection Rebuild and install binaries of iptables -\layout Standard +\end_layout +\begin_layout Standard Make sure, that upper kernel source tree is also available at /usr/src/linux/ -\layout Standard +\end_layout +\begin_layout Standard Rename older directory -\layout Code +\end_layout +\begin_layout Code # mv /usr/src/linux /usr/src/linux.old -\layout Standard +\end_layout +\begin_layout Standard Create a new softlink -\layout Code +\end_layout +\begin_layout Code # ln -s /path/to/src/linux-version-iptables-version /usr/src/linux -\layout Standard +\end_layout +\begin_layout Standard Rebuild SRPMS -\layout Code +\end_layout +\begin_layout Code # rpm --rebuild /path/to/SRPMS/iptables-version-release.src.rpm -\layout Standard +\end_layout +\begin_layout Standard Install new iptables packages (iptables + iptables-ipv6) -\layout Itemize +\end_layout +\begin_layout Itemize On RH 7.1 systems, normally, already an older version is installed, therefore use "freshen" -\layout Code +\end_layout +\begin_layout Code # rpm -Fhv /path/to/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Itemize +\end_layout +\begin_layout Itemize If not already installed, use "install" -\layout Code +\end_layout +\begin_layout Code # rpm -ihv /path/to/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Itemize +\end_layout +\begin_layout Itemize On RH 6.2 systems, normally, no kernel 2.4.x is installed, therefore the requiremen ts don't fit. Use "--nodeps" to install it -\layout Code +\end_layout +\begin_layout Code # rpm -ihv --nodeps /path/to/RPMS/cpu/iptables*-version-release.cpu.rpm -\layout Standard +\end_layout +\begin_layout Standard Perhaps it's necessary to create a softlink for iptables libraries where iptables looks for them -\layout Code +\end_layout +\begin_layout Code # ln -s /lib/iptables/ /usr/lib/iptables -\layout Section +\end_layout +\begin_layout Section Usage -\layout Subsection +\end_layout +\begin_layout Subsection Check for support -\layout Standard +\end_layout +\begin_layout Standard Load module, if so compiled -\layout Code +\end_layout +\begin_layout Code # modprobe ip6_tables -\layout Standard +\end_layout +\begin_layout Standard Check for capability -\layout Code +\end_layout +\begin_layout Code # [ ! -f /proc/net/ip6_tables_names ] && echo "Current kernel doesn't support -\layout Code +\end_layout +\begin_layout Code ¬ 'ip6tables' firewalling (IPv6)!" -\layout Subsection +\end_layout +\begin_layout Subsection Learn how to use ip6tables -\layout Subsubsection +\end_layout +\begin_layout Subsubsection List all IPv6 netfilter entries -\layout Itemize +\end_layout +\begin_layout Itemize Short -\layout Code +\end_layout +\begin_layout Code # ip6tables -L -\layout Itemize +\end_layout +\begin_layout Itemize Extended -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v --line-numbers -L -\layout Subsubsection +\end_layout +\begin_layout Subsubsection List specified filter -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v --line-numbers -L INPUT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Insert a log rule at the input filter with options -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --append INPUT -j LOG --log-prefix "INPUT:" -\layout Code +\end_layout +\begin_layout Code ¬ --log-level 7 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Insert a drop rule at the input filter -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --append INPUT -j DROP -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Delete a rule by number -\layout Code +\end_layout +\begin_layout Code # ip6tables --table filter --delete INPUT 1 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Allow ICMPv6 -\layout Standard +\end_layout +\begin_layout Standard Using older kernels (unpatched kernel 2.4.5 and iptables-1.2.2) no type can be specified -\layout Itemize +\end_layout +\begin_layout Itemize Accept incoming ICMPv6 through tunnels -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -i sit+ -p icmpv6 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Allow outgoing ICMPv6 through tunnels -\layout Code +\end_layout +\begin_layout Code # ip6tables -A OUTPUT -o sit+ -p icmpv6 -j ACCEPT -\layout Standard +\end_layout +\begin_layout Standard Newer kernels allow specifying of ICMPv6 types: -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -p icmpv6 --icmpv6-type echo-request -j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Rate-limiting -\layout Standard +\end_layout +\begin_layout Standard Because it can happen (author already saw it to times) that an ICMPv6 storm will raise up, you should use available rate limiting for at least ICMPv6 ruleset. In addition logging rules should also get rate limiting to prevent DoS attacks against syslog and storage of log file partition. An example for a rate limited ICMPv6 looks like: -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT --protocol icmpv6 --icmpv6-type echo-request -\layout Code +\end_layout +\begin_layout Code ¬ -j ACCEPT --match limit --limit 30/minute -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Allow incoming SSH -\layout Standard +\end_layout +\begin_layout Standard Here an example is shown for a ruleset which allows incoming SSH connection from a specified IPv6 address -\layout Itemize +\end_layout +\begin_layout Itemize Allow incoming SSH from 3ffe:ffff:100::1/128 -\layout Code +\end_layout +\begin_layout Code # ip6tables -A INPUT -i sit+ -p tcp -s 3ffe:ffff:100::1/128 --sport 512:65535 -\layout Code +\end_layout +\begin_layout Code ¬ --dport 22 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Allow response packets (at the moment IPv6 connection tracking isn't in mainstream netfilter6 implemented) -\layout Code +\end_layout +\begin_layout Code # ip6tables -A OUTPUT -o sit+ -p tcp -d 3ffe:ffff:100::1/128 --dport 512:65535 -\layout Code +\end_layout +\begin_layout Code ¬ --sport 22 ! --syn j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Enable tunneled IPv6-in-IPv4 -\layout Standard +\end_layout +\begin_layout Standard To accept tunneled IPv6-in-IPv4 packets, you have to insert rules in your -\series bold +\series bold IPv4 firewall setup -\series default +\series default relating to such packets, for example -\layout Itemize +\end_layout +\begin_layout Itemize Accept incoming IPv6-in-IPv4 on interface ppp0 -\layout Code +\end_layout +\begin_layout Code # iptables -A INPUT -i ppp0 -p ipv6 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Allow outgoing IPv6-in-IPv4 to interface ppp0 -\layout Code +\end_layout +\begin_layout Code # iptables -A OUTPUT -o ppp0 -p ipv6 -j ACCEPT -\layout Standard +\end_layout +\begin_layout Standard If you have only a static tunnel, you can specify the IPv4 addresses, too, like -\layout Itemize +\end_layout +\begin_layout Itemize Accept incoming IPv6-in-IPv4 on interface ppp0 from tunnel endpoint 1.2.3.4 -\layout Code +\end_layout +\begin_layout Code # iptables -A INPUT -i ppp0 -p ipv6 -s 1.2.3.4 -j ACCEPT -\layout Itemize +\end_layout +\begin_layout Itemize Allow outgoing IPv6-in-IPv4 to interface ppp0 to tunnel endpoint 1.2.3.4 -\layout Code +\end_layout +\begin_layout Code # iptables -A OUTPUT -o ppp0 -p ipv6 -d 1.2.3.4 -j ACCEPT -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Protection against incoming TCP connection requests -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold VERY RECOMMENDED! -\series default +\series default For security issues you should really insert a rule which blocks incoming TCP connection requests. Adapt "-i" option, if other interface names are in use! -\layout Itemize +\end_layout +\begin_layout Itemize Block incoming TCP connection requests to this host -\layout Code +\end_layout +\begin_layout Code # ip6tables -I INPUT -i sit+ -p tcp --syn -j DROP -\layout Itemize +\end_layout +\begin_layout Itemize Block incoming TCP connection requests to hosts behind this router -\layout Code +\end_layout +\begin_layout Code # ip6tables -I FORWARD -i sit+ -p tcp --syn -j DROP -\layout Standard +\end_layout +\begin_layout Standard Perhaps the rules have to be placed below others, but that is work you have to think about it. Best way is to create a script and execute rules in a specified way. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Protection against incoming UDP connection requests -\layout Standard +\end_layout +\begin_layout Standard -\series bold +\series bold ALSO RECOMMENDED! -\series default +\series default Like mentioned on my firewall information it's possible to control the ports on outgoing UDP/TCP sessions. So if all of your local IPv6 systems are using local ports e.g. from 32768 to 60999 you are able to filter UDP connections also (until connection tracking works) like: -\layout Itemize +\end_layout +\begin_layout Itemize Block incoming UDP packets which cannot be responses of outgoing requests of this host -\layout Code +\end_layout +\begin_layout Code # ip6tables -I INPUT -i sit+ -p udp ! --dport 32768:60999 -j DROP -\layout Itemize +\end_layout +\begin_layout Itemize Block incoming UDP packets which cannot be responses of forwarded requests of hosts behind this router -\layout Code +\end_layout +\begin_layout Code # ip6tables -I FORWARD -i sit+ -p udp ! --dport 32768:60999 -j DROP -\layout Subsection +\end_layout +\begin_layout Subsection Demonstration example -\layout Standard +\end_layout +\begin_layout Standard Following lines show a more sophisticated setup as an example. Happy netfilter6 ruleset creation.... -\layout Code +\end_layout +\begin_layout Code # ip6tables -n -v -L -\layout Code +\end_layout +\begin_layout Code Chain INPUT (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code 0 0 extIN all sit+ * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 4 384 intIN all eth0 * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::1/128 ::1/128 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all lo * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `INPUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain FORWARD (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 int2ext all eth0 sit+ ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ext2int all sit+ eth0 ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `FORWARD-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain OUTPUT (policy DROP 0 packets, 0 bytes) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 extOUT all * sit+ ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 4 384 intOUT all * eth0 ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::1/128 ::1/128 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * lo ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `OUTPUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain ext2int (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1:65535 dpts:1024:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `ext2int-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain extIN (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * 3ffe:400:100::1/128 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:512:65535 dpt:22 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * 3ffe:400:100::2/128 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:512:65535 dpt:22 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1:65535 dpts:1024:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ udp spts:1:65535 dpts:1024:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ limit: avg 5/min burst 5 LOG flags 0 level 7 prefix `extIN-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain extOUT (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100::1/128tcp spt:22 dpts:512:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:100::2/128tcp spt:22 dpts:512:65535 flags:!0x16/0x02 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ udp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `extOUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain int2ext (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT icmpv6 * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ tcp spts:1024:65535 dpts:1:65535 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `int2ext:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `int2ext-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP tcp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP udp * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain intIN (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ fe80::/ffc0:: -\layout Code +\end_layout +\begin_layout Code 4 384 ACCEPT all * * ::/0 ff02::/16 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code Chain intOUT (1 references) -\layout Code +\end_layout +\begin_layout Code pkts bytes target prot opt in out source destination -\layout Code +\end_layout +\begin_layout Code ¬ -\layout Code +\end_layout +\begin_layout Code 0 0 ACCEPT all * * ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ fe80::/ffc0:: -\layout Code +\end_layout +\begin_layout Code 4 384 ACCEPT all * * ::/0 ff02::/16 -\layout Code +\end_layout +\begin_layout Code 0 0 LOG all * * ::/0 ::/0 -\layout Code +\end_layout +\begin_layout Code ¬ LOG flags 0 level 7 prefix `intOUT-default:' -\layout Code +\end_layout +\begin_layout Code 0 0 DROP all * * ::/0 ::/0 -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-security} -\end_inset +\end_inset Security -\layout Section +\end_layout +\begin_layout Section Node security -\layout Standard +\end_layout +\begin_layout Standard It's very recommended to apply all available patches and disable all not necessary services. Also bind services to the needed IPv4/IPv6 addresses only and install local firewalling. -\layout Standard +\end_layout +\begin_layout Standard More to be filled... -\layout Section +\end_layout +\begin_layout Section Access limitations -\layout Standard +\end_layout +\begin_layout Standard Many services uses the tcp_wrapper library for access control. Below is described the \begin_inset LatexCommand \ref[use of tcp_wrapper]{hints-daemons-tcpwrapper} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard More to be filled... -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{IPv6-security-auditing} -\end_inset +\end_inset IPv6 security auditing -\layout Standard +\end_layout +\begin_layout Standard Currently there are no comfortable tools out which are able to check a system over network for IPv6 security issues. Neither \begin_inset LatexCommand \url[Nessus]{http://www.nessus.org/} -\end_inset +\end_inset nor any commercial security scanner is as far as I know able to scan IPv6 addresses. -\layout Subsection +\end_layout +\begin_layout Subsection Legal issues -\layout Standard +\end_layout +\begin_layout Standard ATTENTION: always take care that you only scan your own systems or after receiving a written order, otherwise legal issues are able to come up to you. -\newline +\newline CHECK destination IPv6 addresses TWICE before starting a scan. -\layout Subsection +\end_layout +\begin_layout Subsection Security auditing using IPv6-enabled netcat -\layout Standard +\end_layout +\begin_layout Standard With the IPv6-enabled netcat (see \begin_inset LatexCommand \url[IPv6+Linux-status-apps/security-auditing]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#security-auditing} -\end_inset +\end_inset for more) you can run a portscan by wrapping a script around which run through a port range, grab banners and so on. Usage example: -\layout Code +\end_layout +\begin_layout Code # nc6 ::1 daytime -\layout Code +\end_layout +\begin_layout Code 13 JUL 2002 11:22:22 CEST -\layout Subsection +\end_layout +\begin_layout Subsection Security auditing using IPv6-enabled nmap -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[NMap]{http://www.insecure.org/nmap/} -\end_inset +\end_inset , one of the best portscaner around the world, supports IPv6 since version 3.10ALPHA1. Usage example: -\layout Code +\end_layout +\begin_layout Code # nmap -6 -sT ::1 -\layout Code +\end_layout +\begin_layout Code Starting nmap V. 3.10ALPHA3 ( www.insecure.org/nmap/ ) -\layout Code +\end_layout +\begin_layout Code Interesting ports on localhost6 (::1): -\layout Code +\end_layout +\begin_layout Code (The 1600 ports scanned but not shown below are in state: closed) -\layout Code +\end_layout +\begin_layout Code Port State Service -\layout Code +\end_layout +\begin_layout Code 22/tcp open ssh -\layout Code +\end_layout +\begin_layout Code 53/tcp open domain -\layout Code +\end_layout +\begin_layout Code 515/tcp open printer -\layout Code +\end_layout +\begin_layout Code 2401/tcp open cvspserver -\layout Code +\end_layout +\begin_layout Code Nmap run completed -- 1 IP address (1 host up) scanned in 0.525 seconds -\layout Subsection +\end_layout +\begin_layout Subsection Security auditing using IPv6-enabled strobe -\layout Standard +\end_layout +\begin_layout Standard Strobe is a (compared to NMap) more a low budget portscanner, but there is an IPv6-enabling patch available (see \begin_inset LatexCommand \url[IPv6+Linux-status-apps/security-auditing]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-apps.html#security-auditing} -\end_inset +\end_inset for more). Usage example: -\layout Code +\end_layout +\begin_layout Code # ./strobe ::1 strobe 1.05 (c) 1995-1999 Julian Assange . -\layout Code +\end_layout +\begin_layout Code ::1 2401 unassigned unknown -\layout Code +\end_layout +\begin_layout Code ::1 22 ssh Secure Shell - RSA encrypted rsh -\layout Code +\end_layout +\begin_layout Code ::1 515 printer spooler (lpd) -\layout Code +\end_layout +\begin_layout Code ::1 6010 unassigned unknown -\layout Code +\end_layout +\begin_layout Code ::1 53 domain Domain Name Server -\layout Standard +\end_layout +\begin_layout Standard Note: strobe isn't really developed further on, the shown version number isn't the right one. -\layout Subsection +\end_layout +\begin_layout Subsection Audit results -\layout Standard +\end_layout +\begin_layout Standard If the result of an audit mismatch your IPv6 security policy, use IPv6 firewalli ng to close the holes, e.g. using netfilter6 (see \begin_inset LatexCommand \ref[Firewalling/Netfilter6]{firewalling-netfilter6} -\end_inset +\end_inset for more). -\layout Standard +\end_layout +\begin_layout Standard Info: More detailed information concerning IPv6 Security can be found here: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Firewalling Considerations for IPv6 / draft-savola-v6ops-firewalling-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Neighbour Discovery trust models and threats / draft-ietf-send-psreq-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Security Considerations for 6to4 / draft-savola-v6ops-6to4-security-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Access Control Prefix Router Advertisement Option for IPv6 / draft-bellovin-ipv6-accessprefix-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Requirements for Plug and Play IPsec for IPv6 applications /draft-kobayakawa-ipsec-ipv6-pnpipsec-reqts-??.txt ]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Security of IPv6 Routing Header and Home Address Options / draft-savola-ipv6-rh-ha-security-??.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-encryption-authentication} -\end_inset +\end_inset Encryption and Authentication -\layout Standard +\end_layout +\begin_layout Standard Unlike in IPv4, encryption and authentication is a mandatory feature of IPv6. Those features are normally implemented using IPsec (which can be also used by IPv4). -\layout Section +\end_layout +\begin_layout Section Modes of using encryption and authentication -\layout Standard +\end_layout +\begin_layout Standard Two modes of encryption and authentication of a connection are possible: -\layout Subsection +\end_layout +\begin_layout Subsection Transport mode -\layout Standard +\end_layout +\begin_layout Standard Transport mode is a real end-to-end connection mode. Here, only the payload (usually ICMP, TCP or UDP) is encrypted with their particular header, while the IP header is not encrypted (but usually included in authentication). -\layout Standard +\end_layout +\begin_layout Standard Using AES-128 for encryption and SHA1 for authentication, this mode decreases the MTU by 42 octets. -\layout Subsection +\end_layout +\begin_layout Subsection Tunnel mode -\layout Standard +\end_layout +\begin_layout Standard Tunnel mode can be used either for end-to-end or for gateway-to-gateway connection modes. Here, the complete IP packet is being encrypted and gets a new IP header prepended, all together constituing a new IP packet (this mechanism is also known as "encapsulation") -\layout Standard +\end_layout +\begin_layout Standard This mode usually decreases the MTU by 40 octets from the MTU of transport mode. I.e. using AES-128 for encryption and SHA1 for authentication 82 octets less than the normal MTU. -\layout Section +\end_layout +\begin_layout Section Support in kernel (ESP and AH) -\layout Subsection +\end_layout +\begin_layout Subsection Support in vanilla Linux kernel 2.4.x -\layout Standard +\end_layout +\begin_layout Standard At the time of writing missing in vanilla up to 2.4.28. There was an issue about keeping the Linux kernel source free of export/import- control-laws regarding encryption code. This is also one case why \begin_inset LatexCommand \url[FreeS/WAN project]{http://www.freeswan.org/} -\end_inset +\end_inset wasn't included in vanilla source. Perhaps a backport from 2.6.x will be done in the future. -\layout Subsection +\end_layout +\begin_layout Subsection Support in vanilla Linux kernel 2.6.x -\layout Standard +\end_layout +\begin_layout Standard Current versions (as time of writing 2.6.9 and upper) support native IPsec for IPv4 and IPv6. -\layout Standard +\end_layout +\begin_layout Standard Implementation was helped by the USAGI project. -\layout Section +\end_layout +\begin_layout Section Automatic key exchange (IKE) -\layout Standard +\end_layout +\begin_layout Standard IPsec requires a key exchange of a secret. This is mostly done automatically by so called IKE daemons. They also handle the authentication of the peers, either by a common known secret (so called \begin_inset Quotes sld -\end_inset +\end_inset pre-shared secret \begin_inset Quotes srd -\end_inset +\end_inset ) or by RSA keys (which can also be used from X.509 certificates). -\layout Standard +\end_layout +\begin_layout Standard Currently, two different IKE daemons are available for Linux, which totally differ in configuration and usage. -\layout Standard +\end_layout +\begin_layout Standard I prefer \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset from the *S/WAN implementation because of the easier and one-config-only setup. -\layout Subsection +\end_layout +\begin_layout Subsection IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard The IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset is taken from the KAME project and ported to Linux. Modern Linux distributions contain this daemon in the package \begin_inset Quotes sld -\end_inset +\end_inset ipsec-tools \begin_inset Quotes srd -\end_inset +\end_inset . Two executables are required for a proper IPsec setup. Take a look on \begin_inset LatexCommand \url[Linux Advanced Routing & Traffic Control HOWTO / IPSEC]{http://lartc.org/howto/lartc.ipsec.html} -\end_inset +\end_inset , too. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Manipulation of the IPsec SA/SP database with the tool \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset is important to define the security policy (SP) for the kernel. -\layout Standard +\end_layout +\begin_layout Standard File: /etc/racoon/setkey.sh -\layout Itemize +\end_layout +\begin_layout Itemize Example for an end-to-end encrypted connection in transport mode -\layout Code +\end_layout +\begin_layout Code #!/sbin/setkey -f -\layout Code +\end_layout +\begin_layout Code flush; -\layout Code +\end_layout +\begin_layout Code spdflush; -\layout Code +\end_layout +\begin_layout Code spdadd 2001:db8:1:1::1 2001:db8:2:2::2 any -P out ipsec esp/transport//require; -\layout Code +\end_layout +\begin_layout Code spdadd 2001:db8:2:2::2 2001:db8:1:1::1 any -P in ipsec esp/transport//require; -\layout Code +\end_layout -\layout Itemize +\begin_layout Code +\end_layout + +\begin_layout Itemize Example for a end-to-end encrypted connection in tunnel mode -\layout Code +\end_layout +\begin_layout Code #!/sbin/setkey -f -\layout Code +\end_layout +\begin_layout Code flush; -\layout Code +\end_layout +\begin_layout Code spdflush; -\layout Code +\end_layout +\begin_layout Code spdadd 2001:db8:1:1::1 2001:db8:2:2::2 any -P out ipsec -\layout Code +\end_layout +\begin_layout Code ¬ esp/tunnel/2001:db8:1:1::1-2001:db8:2:2::2/require; -\layout Code +\end_layout +\begin_layout Code spdadd 2001:db8:2:2::2 2001:db8:1:1::1 any -P in ipsec -\layout Code +\end_layout +\begin_layout Code ¬ esp/tunnel/2001:db8:2:2::2-2001:db8:1:1::1/require; -\layout Standard +\end_layout +\begin_layout Standard For the other peer, you have to replace \begin_inset Quotes sld -\end_inset +\end_inset in \begin_inset Quotes srd -\end_inset +\end_inset with \begin_inset Quotes sld -\end_inset +\end_inset out \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Configuration of the IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset requires a configuration file for proper execution. It includes the related settings to the security policy, which should be set up previously using \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard File: /etc/racoon/racoon.conf -\layout Code +\end_layout +\begin_layout Code # Racoon IKE daemon configuration file. -\layout Code +\end_layout +\begin_layout Code # See 'man racoon.conf' for a description of the format and entries. -\layout Code +\end_layout +\begin_layout Code path include "/etc/racoon"; -\layout Code +\end_layout +\begin_layout Code path pre_shared_key "/etc/racoon/psk.txt"; -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code listen -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code isakmp 2001:db8:1:1::1; -\layout Code +\end_layout +\begin_layout Code } -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code remote 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code exchange_mode main; -\layout Code +\end_layout +\begin_layout Code lifetime time 24 hour; -\layout Code +\end_layout +\begin_layout Code proposal -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code hash_algorithm md5; -\layout Code +\end_layout +\begin_layout Code authentication_method pre_shared_key; -\layout Code +\end_layout +\begin_layout Code dh_group 2; -\layout Code +\end_layout +\begin_layout Code } -\layout Code +\end_layout +\begin_layout Code } -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # gateway-to-gateway -\layout Code +\end_layout +\begin_layout Code sainfo address 2001:db8:1:1::1 any address 2001:db8:2:2::2 any -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code lifetime time 1 hour; -\layout Code +\end_layout +\begin_layout Code encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code authentication_algorithm hmac_md5; -\layout Code +\end_layout +\begin_layout Code compression_algorithm deflate; -\layout Code +\end_layout +\begin_layout Code } -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code sainfo address 2001:db8:2:2::2 any address 2001:db8:1:1::1 any -\layout Code +\end_layout +\begin_layout Code { -\layout Code +\end_layout +\begin_layout Code lifetime time 1 hour; -\layout Code +\end_layout +\begin_layout Code encryption_algorithm 3des; -\layout Code +\end_layout +\begin_layout Code authentication_algorithm hmac_md5; -\layout Code +\end_layout +\begin_layout Code compression_algorithm deflate; -\layout Code +\end_layout +\begin_layout Code } -\layout Standard +\end_layout +\begin_layout Standard Also set up the pre-shared secret: -\layout Standard +\end_layout +\begin_layout Standard File: /etc/racoon/psk.txt -\layout Code +\end_layout +\begin_layout Code # file for pre-shared keys used for IKE authentication -\layout Code +\end_layout +\begin_layout Code # format is: 'identifier' 'key' -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code 2001:db8:2:2::2 verysecret -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Running IPsec with IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard At least the daemon needs to be started. For the first time, use debug and foreground mode. The following example shows a successful IKE phase 1 (ISAKMP-SA) and 2 (IPsec-SA) negotiation: -\layout Code +\end_layout +\begin_layout Code # racoon -F -v -f /etc/racoon/racoon.conf -\layout Code +\end_layout +\begin_layout Code Foreground mode. -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:30:15: INFO: @(#)ipsec-tools 0.3.3 (http://ipsec-tools.sourceforge.net ) -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:30:15: INFO: @(#)This product linked -\layout Code +\end_layout +\begin_layout Code ¬ OpenSSL 0.9.7a Feb 19 2003 (http://www.openssl.org/) -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:30:15: INFO: 2001:db8:1:1::1[500] used as isakmp port (fd=7) -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:06: INFO: IPsec-SA request for 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code ¬ queued due to no phase1 found. -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:06: INFO: initiate new phase 1 negotiation: -\layout Code +\end_layout +\begin_layout Code ¬ 2001:db8:1:1::1[500]<=>2001:db8:2:2::2[500] -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:06: INFO: begin Identity Protection mode. -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:09: INFO: ISAKMP-SA established -\layout Code +\end_layout +\begin_layout Code ¬ 2001:db8:1:1::1[500]-2001:db8:2:2::2[500] spi:da3d3693289c9698:ac039a402b2db40 1 -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:09: INFO: initiate new phase 2 negotiation: -\layout Code +\end_layout +\begin_layout Code ¬ 2001:6f8:900:94::2[0]<=>2001:db8:2:2::2[0] -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:10: INFO: IPsec-SA established: -\layout Code +\end_layout +\begin_layout Code ¬ ESP/Tunnel 2001:db8:2:2::2->2001:db8:1:1::1 spi=253935531(0xf22bfab) -\layout Code +\end_layout +\begin_layout Code 2005-01-01 20:31:10: INFO: IPsec-SA established: -\layout Code +\end_layout +\begin_layout Code ¬ ESP/Tunnel 2001:db8:1:1::1->2001:db8:2:2::2 spi=175002564(0xa6e53c4) -\layout Standard +\end_layout +\begin_layout Standard Each direction got its own IPsec-SA (like defined in the IPsec standard). With \begin_inset Quotes sld -\end_inset +\end_inset tcpdump \begin_inset Quotes srd -\end_inset +\end_inset on the related interface, you will see as result of an IPv6 ping: -\layout Code +\end_layout +\begin_layout Code 20:35:55.305707 2001:db8:1:1::1 > 2001:db8:2:2::2: ESP(spi=0x0a6e53c4,seq=0x3) -\layout Code +\end_layout +\begin_layout Code 20:35:55.537522 2001:db8:2:2::2 > 2001:db8:1:1::1: ESP(spi=0x0f22bfab,seq=0x3) -\layout Standard +\end_layout +\begin_layout Standard As expected, the negotiated SPIs are being used here. -\layout Standard +\end_layout +\begin_layout Standard And using \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset , current active parameters are shown: -\layout Code +\end_layout +\begin_layout Code # setkey -D -\layout Code +\end_layout +\begin_layout Code 2001:db8:1:1::1 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code esp mode=tunnel spi=175002564(0x0a6e53c4) reqid=0(0x00000000) -\layout Code +\end_layout +\begin_layout Code E: 3des-cbc bd26bc45 aea0d249 ef9c6b89 7056080f 5d9fa49c 924e2edd -\layout Code +\end_layout +\begin_layout Code A: hmac-md5 60c2c505 517dd8b7 c9609128 a5efc2db -\layout Code +\end_layout +\begin_layout Code seq=0x00000000 replay=4 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code created: Jan 1 20:31:10 2005 current: Jan 1 20:40:47 2005 -\layout Code +\end_layout +\begin_layout Code diff: 577(s) hard: 3600(s) soft: 2880(s) -\layout Code +\end_layout +\begin_layout Code last: Jan 1 20:35:05 2005 hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code current: 540(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code allocated: 3 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code sadb_seq=1 pid=22358 refcnt=0 -\layout Code +\end_layout +\begin_layout Code 2001:db8:2:2::2 2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code esp mode=tunnel spi=253935531(0x0f22bfab) reqid=0(0x00000000) -\layout Code +\end_layout +\begin_layout Code E: 3des-cbc c1ddba65 83debd62 3f6683c1 20e747ac 933d203f 4777a7ce -\layout Code +\end_layout +\begin_layout Code A: hmac-md5 3f957db9 9adddc8c 44e5739d 3f53ca0e -\layout Code +\end_layout +\begin_layout Code seq=0x00000000 replay=4 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code created: Jan 1 20:31:10 2005 current: Jan 1 20:40:47 2005 -\layout Code +\end_layout +\begin_layout Code diff: 577(s) hard: 3600(s) soft: 2880(s) -\layout Code +\end_layout +\begin_layout Code last: Jan 1 20:35:05 2005 hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code current: 312(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code allocated: 3 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code sadb_seq=0 pid=22358 refcnt=0 -\layout Subsection +\end_layout +\begin_layout Subsection IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard The IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset is included in distributions of the *S/WAN projects. *S/WAN project starts at the beginning as \begin_inset LatexCommand \url[FreeS/WAN]{http://www.freeswan.org/} -\end_inset +\end_inset . Unfortunately, the FreeS/WAN project stopped further development in 2004. @@ -9249,1065 +11291,1334 @@ pluto \begin_inset LatexCommand \url[strongSwan]{http://www.strongswan.org/} -\end_inset +\end_inset and \begin_inset LatexCommand \url[Openswan]{http://www.openswan.org/} -\end_inset +\end_inset . Today, readily installable packages are available for at least Openswan (included in Fedora Core 3). -\layout Standard +\end_layout +\begin_layout Standard A major difference to \begin_inset Quotes sld -\end_inset +\end_inset racoon \begin_inset Quotes srd -\end_inset +\end_inset , only one configuration file is required. Also, an initscript exists for automatic setup after booting. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Configuration of the IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard The configuration is very similar to the IPv4 one, only one important option is necessary. -\layout Standard +\end_layout +\begin_layout Standard File: /etc/ipsec.conf -\layout Code +\end_layout +\begin_layout Code # /etc/ipsec.conf - Openswan IPsec configuration file -\layout Code +\end_layout +\begin_layout Code # -\layout Code +\end_layout +\begin_layout Code # Manual: ipsec.conf.5 -\layout Code +\end_layout +\begin_layout Code version 2.0 # conforms to second version of ipsec.conf specification -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # basic configuration -\layout Code +\end_layout +\begin_layout Code config setup -\layout Code +\end_layout +\begin_layout Code # Debug-logging controls: "none" for (almost) none, "all" for lots. -\layout Code +\end_layout +\begin_layout Code # klipsdebug=none -\layout Code +\end_layout +\begin_layout Code # plutodebug="control parsing" -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code #Disable Opportunistic Encryption -\layout Code +\end_layout +\begin_layout Code include /etc/ipsec.d/examples/no_oe.conf -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code conn ipv6-p1-p2 -\layout Code +\end_layout +\begin_layout Code connaddrfamily=ipv6 # Important for IPv6! -\layout Code +\end_layout +\begin_layout Code left=2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code right=2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code authby=secret -\layout Code +\end_layout +\begin_layout Code esp=aes128-sha1 -\layout Code +\end_layout +\begin_layout Code ike=aes128-sha-modp1024 -\layout Code +\end_layout +\begin_layout Code type=transport -\layout Code +\end_layout +\begin_layout Code #type=tunnel -\layout Code +\end_layout +\begin_layout Code compress=no -\layout Code +\end_layout +\begin_layout Code #compress=yes -\layout Code +\end_layout +\begin_layout Code auto=add -\layout Code +\end_layout +\begin_layout Code #auto=start -\layout Code +\end_layout -\layout Standard +\begin_layout Code +\end_layout + +\begin_layout Standard Don't forget to define the pre-shared secret here also. -\layout Standard +\end_layout +\begin_layout Standard File: /etc/ipsec.secrets -\layout Code +\end_layout +\begin_layout Code 2001:db8:1:1::1 2001:db8:2:2::2 : PSK "verysecret" -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Running IPsec with IKE daemon \begin_inset Quotes sld -\end_inset +\end_inset pluto \begin_inset Quotes srd -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard If installation of Openswan was successfully, an initscript should exist for starting IPsec, simply run (on each peer): -\layout Code +\end_layout +\begin_layout Code # /etc/rc.d/init.d/ipsec start -\layout Standard +\end_layout +\begin_layout Standard Afterwards, start this connection on one peer. If you saw the line \begin_inset Quotes sld -\end_inset +\end_inset IPsec SA established \begin_inset Quotes srd -\end_inset +\end_inset , all worked fine. -\layout Code +\end_layout +\begin_layout Code # ipsec auto --up ipv6-peer1-peer2 -\layout Code +\end_layout +\begin_layout Code 104 "ipv6-p1-p2" #1: STATE_MAIN_I1: initiate -\layout Code +\end_layout +\begin_layout Code 106 "ipv6-p1-p2" #1: STATE_MAIN_I2: sent MI2, expecting MR2 -\layout Code +\end_layout +\begin_layout Code 108 "ipv6-p1-p2" #1: STATE_MAIN_I3: sent MI3, expecting MR3 -\layout Code +\end_layout +\begin_layout Code 004 "ipv6-p1-p2" #1: STATE_MAIN_I4: ISAKMP SA established -\layout Code +\end_layout +\begin_layout Code 112 "ipv6-p1-p2" #2: STATE_QUICK_I1: initiate -\layout Code +\end_layout +\begin_layout Code 004 "ipv6-p1-p2" #2: STATE_QUICK_I2: sent QI2, -\layout Code +\end_layout +\begin_layout Code ¬ IPsec SA established {ESP=>0xa98b7710 <0xa51e1f22} -\layout Standard +\end_layout +\begin_layout Standard Because *S/WAN and setkey/racoon do use the same IPsec implementation in Linux 2.6.x kernel, \begin_inset Quotes sld -\end_inset +\end_inset setkey \begin_inset Quotes srd -\end_inset +\end_inset can be used here too to show current active parameters: -\layout Code +\end_layout +\begin_layout Code # setkey -D -\layout Code +\end_layout +\begin_layout Code 2001:db8:1:1::1 2001:db8:2:2::2 -\layout Code +\end_layout +\begin_layout Code esp mode=transport spi=2844489488(0xa98b7710) reqid=16385(0x00004001) -\layout Code +\end_layout +\begin_layout Code E: aes-cbc 082ee274 2744bae5 7451da37 1162b483 -\layout Code +\end_layout +\begin_layout Code A: hmac-sha1 b7803753 757417da 477b1c1a 64070455 ab79082c -\layout Code +\end_layout +\begin_layout Code seq=0x00000000 replay=64 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code created: Jan 1 21:16:32 2005 current: Jan 1 21:22:20 2005 -\layout Code +\end_layout +\begin_layout Code diff: 348(s) hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code last: hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code current: 0(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code allocated: 0 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code sadb_seq=1 pid=23825 refcnt=0 -\layout Code +\end_layout +\begin_layout Code 2001:db8:2:2::2 2001:db8:1:1::1 -\layout Code +\end_layout +\begin_layout Code esp mode=transport spi=2770214690(0xa51e1f22) reqid=16385(0x00004001) -\layout Code +\end_layout +\begin_layout Code E: aes-cbc 6f59cc30 8d856056 65e07b76 552cac18 -\layout Code +\end_layout +\begin_layout Code A: hmac-sha1 c7c7d82b abfca8b1 5440021f e0c3b335 975b508b -\layout Code +\end_layout +\begin_layout Code seq=0x00000000 replay=64 flags=0x00000000 state=mature -\layout Code +\end_layout +\begin_layout Code created: Jan 1 21:16:31 2005 current: Jan 1 21:22:20 2005 -\layout Code +\end_layout +\begin_layout Code diff: 349(s) hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code last: hard: 0(s) soft: 0(s) -\layout Code +\end_layout +\begin_layout Code current: 0(bytes) hard: 0(bytes) soft: 0(bytes) -\layout Code +\end_layout +\begin_layout Code allocated: 0 hard: 0 soft: 0 -\layout Code +\end_layout +\begin_layout Code sadb_seq=0 pid=23825 refcnt=0 -\layout Section +\end_layout +\begin_layout Section Additional informations: -\layout Standard +\end_layout +\begin_layout Standard On Linux Kernel 2.6.x you can get the policy and status of IPsec also using \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset : -\layout Code +\end_layout +\begin_layout Code # ip xfrm policy -\layout Code +\end_layout +\begin_layout Code ... -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code # ip xfrm state -\layout Code +\end_layout +\begin_layout Code ... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-qos} -\end_inset +\end_inset Quality of Service (QoS) -\layout Standard +\end_layout +\begin_layout Standard IPv6 supports QoS with use of Flow Labels and Traffic Classes. This can be controlled using \begin_inset Quotes sld -\end_inset +\end_inset tc \begin_inset Quotes srd -\end_inset +\end_inset (contained in package \begin_inset Quotes sld -\end_inset +\end_inset iproute \begin_inset Quotes srd -\end_inset +\end_inset ). -\layout Standard +\end_layout +\begin_layout Standard Additional infos: -\layout Itemize +\end_layout +\begin_layout Itemize \lang ngerman - \begin_inset LatexCommand \url[RFC 3697 / IPv6 Flow Label Specification]{http://www.faqs.org/rfcs/rfc3697.html} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard more to be filled... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-hints-daemons} -\end_inset +\end_inset Hints for IPv6-enabled daemons -\layout Standard +\end_layout +\begin_layout Standard Here some hints are shown for IPv6-enabled daemons. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-bind} -\end_inset +\end_inset Berkeley Internet Name Daemon BIND (named) -\layout Standard +\end_layout +\begin_layout Standard IPv6 is supported since version 9. Always use newest available version. At least version 9.1.3 must be used, older versions can contain remote exploitabl e security holes. -\layout Subsection +\end_layout +\begin_layout Subsection Listening on IPv6 addresses -\layout Standard +\end_layout +\begin_layout Standard Note: unlike in IPv4 current versions doesn't allow to bind a server socket to dedicated IPv6 addresses, so only -\emph on +\emph on any -\emph default +\emph default or -\emph on +\emph on none -\emph default +\emph default are valid. Because this can be a security issue, check the Access Control List (ACL) section below, too! -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Enable BIND named for listening on IPv6 address -\layout Standard +\end_layout +\begin_layout Standard To enable IPv6 for listening, following options are requested to change -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # sure other options here, too -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { any; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard This should result after restart in e.g. -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu |grep "named -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::53 :::* LISTEN 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming TCP requests -\layout Code +\end_layout +\begin_layout Code udp 0 0 1.2.3.4:53 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP requests to IPv4 1.2.3.4 -\layout Code +\end_layout +\begin_layout Code udp 0 0 127.0.0.1:53 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP requests to IPv4 localhost -\layout Code +\end_layout +\begin_layout Code udp 0 0 0.0.0.0:32868 0.0.0.0:* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # dynamic chosen port for outgoing queries -\layout Code +\end_layout +\begin_layout Code udp 0 0 :::53 :::* 1234/named -\layout Code +\end_layout +\begin_layout Code ¬ # incoming UDP request to any IPv6 -\layout Standard +\end_layout +\begin_layout Standard And a simple test looks like -\layout Code +\end_layout +\begin_layout Code # dig localhost @::1 -\layout Standard +\end_layout +\begin_layout Standard and should show you a result. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Disable BIND named for listening on IPv6 address -\layout Standard +\end_layout +\begin_layout Standard To disable IPv6 for listening, following options are requested to change -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # sure other options here, too -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { none; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 enabled Access Control Lists (ACL) -\layout Standard +\end_layout +\begin_layout Standard IPv6 enabled ACLs are possible and should be used whenever it's possible. An example looks like following: -\layout Code +\end_layout +\begin_layout Code acl internal-net { -\layout Code +\end_layout +\begin_layout Code 127.0.0.1; -\layout Code +\end_layout +\begin_layout Code 1.2.3.0/24; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::/56; -\layout Code +\end_layout +\begin_layout Code ::1/128; -\layout Code +\end_layout +\begin_layout Code ::ffff:1.2.3.4/128; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code acl ns-internal-net { -\layout Code +\end_layout +\begin_layout Code 1.2.3.4; -\layout Code +\end_layout +\begin_layout Code 1.2.3.5; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::4/128; -\layout Code +\end_layout +\begin_layout Code 3ffe:ffff:100::5/128; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard This ACLs can be used e.g. for queries of clients and transfer zones to secondary name-servers. This prevents also your caching name-server to be used from outside using IPv6. -\layout Code +\end_layout +\begin_layout Code options { -\layout Code +\end_layout +\begin_layout Code # sure other options here, too -\layout Code +\end_layout +\begin_layout Code listen-on-v6 { none; }; -\layout Code +\end_layout +\begin_layout Code allow-query { internal-net; }; -\layout Code +\end_layout +\begin_layout Code allow-transfer { ns-internal-net; }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard It's also possible to set the -\emph on +\emph on allow-query -\emph default +\emph default and -\emph on +\emph on allow-transfer -\emph default +\emph default option for most of single zone definitions, too. -\layout Subsection +\end_layout +\begin_layout Subsection Sending queries with dedicated IPv6 address -\layout Standard +\end_layout +\begin_layout Standard This option is not required, but perhaps needed: -\layout Code +\end_layout +\begin_layout Code query-source-v6 address port ; -\layout Subsection +\end_layout +\begin_layout Subsection Per zone defined dedicated IPv6 addresses -\layout Standard +\end_layout +\begin_layout Standard It's also possible to define per zone some IPv6 addresses. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Transfer source address -\layout Standard +\end_layout +\begin_layout Standard Transfer source address is used for outgoing zone transfers: -\layout Code +\end_layout +\begin_layout Code transfer-source-v6 [port port]; -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Notify source address -\layout Standard +\end_layout +\begin_layout Standard Notify source address is used for outgoing notify messages: -\layout Code +\end_layout +\begin_layout Code notify-source-v6 [port port]; -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 DNS zone files examples -\layout Standard +\end_layout +\begin_layout Standard Some information can be also found at \begin_inset LatexCommand \url[IPv6 DNS Setup Information (article)]{http://www.isi.edu/~bmanning/v6DNS.html} -\end_inset +\end_inset . Perhaps also helpful is the \begin_inset LatexCommand \url[IPv6 Reverse DNS zone builder for BIND 8/9 (webtool)]{http://tools.fpsn.net/ipv6-inaddr/} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Serving IPv6 related DNS data -\layout Standard +\end_layout +\begin_layout Standard For IPv6 new types and root zones for reverse lookups are defined: -\layout Itemize +\end_layout +\begin_layout Itemize AAAA and reverse IP6.INT: specified in \begin_inset LatexCommand \url[RFC 1886 / DNS Extensions to support IP version 6]{http://www.faqs.org/rfcs/rfc1886.html} -\end_inset +\end_inset , usable since BIND version 4.9.6 -\layout Itemize +\end_layout +\begin_layout Itemize A6, DNAME (DEPRECATED NOW!) and reverse IP6.ARPA: specified in \begin_inset LatexCommand \url[RFC 2874 / DNS Extensions to Support IPv6 Address Aggregation and Renumbering]{http://www.faqs.org/rfcs/rfc2874.html} -\end_inset +\end_inset , usable since BIND 9, but see also an information about the current state at \begin_inset LatexCommand \url[draft-ietf-dnsext-ipv6-addresses-00.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Perhaps filled later more content, for the meantime take a look at given RFCs and -\layout Itemize +\end_layout +\begin_layout Itemize AAAA and reverse IP6.INT: \begin_inset LatexCommand \url[IPv6 DNS Setup Information]{http://www.isi.edu/~bmanning/v6DNS.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize A6, DNAME (DEPRECATED NOW!) and reverse IP6.ARPA: take a look into chapter 4 and 6 of the BIND 9 Administrator Reference Manual (ARM) distributed which the bind-package or get this here: \begin_inset LatexCommand \url[BIND version 9 ARM (PDF)]{http://www.nominum.com/content/documents/bind9arm.pdf} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Because IP6.INT is deprecated (but still in use), a DNS server which will support IPv6 information has to serve both reverse zones. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Current best practice -\layout Standard +\end_layout +\begin_layout Standard Because there are some troubles around using the new formats, current best practice is: -\layout Standard +\end_layout +\begin_layout Standard Forward lookup support: -\layout Itemize +\end_layout +\begin_layout Itemize AAAA -\layout Standard +\end_layout +\begin_layout Standard Reverse lookup support: -\layout Itemize +\end_layout +\begin_layout Itemize Reverse nibble format for zone ip6.int (FOR BACKWARD COMPATIBILITY) -\layout Itemize +\end_layout +\begin_layout Itemize Reverse nibble format for zone ip6.arpa (RECOMMENDED) -\layout Subsection +\end_layout +\begin_layout Subsection Checking IPv6-enabled connect -\layout Standard +\end_layout +\begin_layout Standard To check, whether BIND is listening on an IPv6 socket and serving data see following examples. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 connect, but denied by ACL -\layout Standard +\end_layout +\begin_layout Standard Specifying a dedicated server for the query, an IPv6 connect can be forced: -\layout Code +\end_layout +\begin_layout Code $ host -t aaaa www.6bone.net 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Using domain server: -\layout Code +\end_layout +\begin_layout Code Name: 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Address: 3ffe:ffff:200:f101::1#53 -\layout Code +\end_layout +\begin_layout Code Aliases: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code Host www.6bone.net. not found: 5(REFUSED) -\layout Standard +\end_layout +\begin_layout Standard Related log entry looks like following: -\layout Code +\end_layout +\begin_layout Code Jan 3 12:43:32 gate named[12347]: client -\layout Code +\end_layout +\begin_layout Code ¬ 3ffe:ffff:200:f101:212:34ff:fe12:3456#32770: -\layout Code +\end_layout +\begin_layout Code query denied -\layout Standard +\end_layout +\begin_layout Standard If you see such entries in the log, check whether requests from this client should be allowed and perhaps review your ACL configuration. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Successful IPv6 connect -\layout Standard +\end_layout +\begin_layout Standard A successful IPv6 connect looks like following: -\layout Code +\end_layout +\begin_layout Code $ host -t aaaa www.6bone.net 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Using domain server: -\layout Code +\end_layout +\begin_layout Code Name: 3ffe:ffff:200:f101::1 -\layout Code +\end_layout +\begin_layout Code Address: 3ffe:ffff:200:f101::1#53 -\layout Code +\end_layout +\begin_layout Code Aliases: -\layout Code +\end_layout -\layout Code +\begin_layout Code +\end_layout + +\begin_layout Code www.6bone.net. is an alias for 6bone.net. -\layout Code +\end_layout +\begin_layout Code 6bone.net. has AAAA address 3ffe:b00:c18:1::10 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-xinetd} -\end_inset +\end_inset Internet super daemon (xinetd) -\layout Standard +\end_layout +\begin_layout Standard IPv6 is supported since \begin_inset LatexCommand \url[xinetd]{http://www.xinetd.org/} -\end_inset +\end_inset version around 1.8.9. Always use newest available version. At least version 2.3.3 must be used, older versions can contain remote exploitabl e security holes. -\layout Standard +\end_layout +\begin_layout Standard Some Linux distribution contain an extra package for the IPv6 enabled xinetd, some others start the IPv6-enabled xinetd if following variable is set: NETWORKING_IPV6="yes", mostly done by /etc/sysconfig/network (only valid for Red Hat like distributions). In newer releases, one binary supports IPv4 and IPv6. -\layout Standard +\end_layout +\begin_layout Standard If you enable a built-in service like e.g. daytime by modifying the configuration file in /etc/xinetd.d/daytime like -\layout Code +\end_layout +\begin_layout Code # diff -u /etc/xinetd.d/daytime.orig /etc/xinetd.d/daytime -\layout Code +\end_layout +\begin_layout Code --- /etc/xinetd.d/daytime.orig Sun Dec 16 19:00:14 2001 -\layout Code +\end_layout +\begin_layout Code +++ /etc/xinetd.d/daytime Sun Dec 16 19:00:22 2001 -\layout Code +\end_layout +\begin_layout Code @@ -10,5 +10,5 @@ -\layout Code +\end_layout +\begin_layout Code protocol = tcp -\layout Code +\end_layout +\begin_layout Code user = root -\layout Code +\end_layout +\begin_layout Code wait = no -\layout Code +\end_layout +\begin_layout Code - disable = yes -\layout Code +\end_layout +\begin_layout Code + disable = no -\layout Code +\end_layout +\begin_layout Code } -\layout Standard +\end_layout +\begin_layout Standard After restarting the xinetd you should get a positive result like: -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu -A inet6 |grep "xinetd*" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:192.168.1.1:993 :::* LISTEN 12345/xinetd-ipv6 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 :::13 :::* LISTEN 12345/xinetd-ipv6 <- service -\layout Code +\end_layout +\begin_layout Code ¬ daytime/tcp -\layout Code +\end_layout +\begin_layout Code tcp 0 0 ::ffff:192.168.1.1:143 :::* LISTEN 12345/xinetd-ipv6 -\layout Standard +\end_layout +\begin_layout Standard Shown example also displays an IMAP and IMAP-SSL IPv4-only listening xinetd. -\layout Standard +\end_layout +\begin_layout Standard Note: earlier versions had a problem that an IPv4-only xinetd won't start on an IPv6-enabled node and also the IPv6-enabled xinetd won't start on an IPv4-only node. This is known to be fixed in later versions, at least version 2.3.11. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-apache2} -\end_inset +\end_inset Webserver Apache2 (httpd2) -\layout Standard +\end_layout +\begin_layout Standard Apache web server supports IPv6 native by maintainers since 2.0.14. Available patches for the older 1.3.x series are not current and shouldn't be used in public environment, but available at \begin_inset LatexCommand \url[KAME / Misc]{ftp://ftp.kame.net/pub/kame/misc/} -\end_inset +\end_inset . -\layout Subsection +\end_layout +\begin_layout Subsection Listening on IPv6 addresses -\layout Standard +\end_layout +\begin_layout Standard Note: virtual hosts on IPv6 addresses are broken in versions until 2.0.28 (a patch is available for 2.0.28). But always try latest available version first because earlier versions had some security issues. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Virtual host listen on an IPv6 address only -\layout Code +\end_layout +\begin_layout Code Listen [3ffe:ffff:100::1]:80 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code ServerName ipv6only.yourdomain.yourtopleveldomain -\layout Code +\end_layout +\begin_layout Code # ...sure more config lines -\layout Code +\end_layout +\begin_layout Code -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Virtual host listen on an IPv6 and on an IPv4 address -\layout Code +\end_layout +\begin_layout Code Listen [3ffe:ffff:100::2]:80 -\layout Code +\end_layout +\begin_layout Code Listen 1.2.3.4:80 -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code ServerName ipv6andipv4.yourdomain.yourtopleveldomain -\layout Code +\end_layout +\begin_layout Code # ...sure more config lines -\layout Code +\end_layout +\begin_layout Code -\layout Standard +\end_layout +\begin_layout Standard This should result after restart in e.g. -\layout Code +\end_layout +\begin_layout Code # netstat -lnptu |grep "httpd2 -\backslash +\backslash W*$" -\layout Code +\end_layout +\begin_layout Code tcp 0 0 1.2.3.4:80 0.0.0.0:* LISTEN 12345/httpd2 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 3ffe:ffff:100::1:80 :::* LISTEN 12345/httpd2 -\layout Code +\end_layout +\begin_layout Code tcp 0 0 3ffe:ffff:100::2:80 :::* LISTEN 12345/httpd2 -\layout Standard +\end_layout +\begin_layout Standard For simple tests use the telnet example already shown. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Additional notes -\layout Itemize +\end_layout +\begin_layout Itemize Apache2 supports a method called \begin_inset Quotes sld -\end_inset +\end_inset sendfile \begin_inset Quotes srd -\end_inset +\end_inset to speedup serving data. Some NIC drivers also support offline checksumming. In some cases, this can lead to connection problems and invalid TCP checksums. In this cases, disable \begin_inset Quotes sld -\end_inset +\end_inset sendfile \begin_inset Quotes srd -\end_inset +\end_inset either by recompiling using configure option \begin_inset Quotes sld -\end_inset +\end_inset --without-sendfile \begin_inset Quotes srd -\end_inset +\end_inset or by using the "EnableSendfile off" directive in configuration file. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-radvd} -\end_inset +\end_inset Router Advertisement Daemon (radvd) -\layout Standard +\end_layout +\begin_layout Standard The router advertisement daemon is very useful on a LAN, if clients should be auto-configured. The daemon itself should run on the Linux default IPv6 gateway router (it's not required that this is also the default IPv4 gateway, so pay attention who on your LAN is sending router advertisements). -\layout Standard +\end_layout +\begin_layout Standard You can specify some information and flags which should be contained in the advertisement. Common used are -\layout Itemize +\end_layout +\begin_layout Itemize Prefix (needed) -\layout Itemize +\end_layout +\begin_layout Itemize Lifetime of the prefix -\layout Itemize +\end_layout +\begin_layout Itemize Frequency of sending advertisements (optional) -\layout Standard +\end_layout +\begin_layout Standard After a proper configuration, the daemon sends advertisements through specified interfaces and clients are hopefully receive them and auto-magically configure addresses with received prefix and the default route. -\layout Subsection +\end_layout +\begin_layout Subsection Configuring radvd -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Simple configuration -\layout Standard +\end_layout +\begin_layout Standard Radvd's config file is normally /etc/radvd.conf. An simple example looks like following: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code AdvSendAdvert on; -\layout Code +\end_layout +\begin_layout Code MinRtrAdvInterval 3; -\layout Code +\end_layout +\begin_layout Code MaxRtrAdvInterval 10; -\layout Code +\end_layout +\begin_layout Code prefix 3ffe:ffff:0100:f101::/64 { -\layout Code +\end_layout +\begin_layout Code AdvOnLink on; -\layout Code +\end_layout +\begin_layout Code AdvAutonomous on; -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr on; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard This results on client side in -\layout Code +\end_layout +\begin_layout Code # ip -6 addr show eth0 -\layout Code +\end_layout +\begin_layout Code 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 -\layout Code +\end_layout +\begin_layout Code inet6 3ffe:ffff:100:f101:2e0:12ff:fe34:1234/64 scope global dynamic -\layout Code +\end_layout +\begin_layout Code valid_lft 2591992sec preferred_lft 604792sec -\layout Code +\end_layout +\begin_layout Code inet6 fe80::2e0:12ff:fe34:1234/10 scope link -\layout Standard +\end_layout +\begin_layout Standard Because no lifetime was defined, a very high value was used. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Special 6to4 configuration -\layout Standard +\end_layout +\begin_layout Standard Version since 0.6.2pl3 support the automatic (re)-generation of the prefix depending on an IPv4 address of a specified interface. This can be used to distribute advertisements in a LAN after the 6to4 tunneling @@ -10315,1053 +12626,1231 @@ Version since 0.6.2pl3 support the automatic (re)-generation of the prefix Mostly used behind a dynamic dial-on-demand Linux router. Because of the sure shorter lifetime of such prefix (after each dial-up, another prefix is valid), the lifetime configured to minimal values: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code AdvSendAdvert on; -\layout Code +\end_layout +\begin_layout Code MinRtrAdvInterval 3; -\layout Code +\end_layout +\begin_layout Code MaxRtrAdvInterval 10; -\layout Code +\end_layout +\begin_layout Code prefix 0:0:0:f101::/64 { -\layout Code +\end_layout +\begin_layout Code AdvOnLink off; -\layout Code +\end_layout +\begin_layout Code AdvAutonomous on; -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr on; -\layout Code +\end_layout +\begin_layout Code Base6to4Interface ppp0; -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime 20; -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime 30; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Standard +\end_layout +\begin_layout Standard This results on client side in (assuming, ppp0 has currently 1.2.3.4 as local IPv4 address): -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 addr show eth0 -\layout Code +\end_layout +\begin_layout Code 3: eth0: mtu 1500 qdisc pfifo_fast qlen 100 -\layout Code +\end_layout +\begin_layout Code inet6 2002:0102:0304 -\series bold +\series bold : -\series default +\series default f101:2e0:12ff:fe34:1234/64 scope global dynamic -\layout Code +\end_layout +\begin_layout Code valid_lft 22sec preferred_lft 12sec -\layout Code +\end_layout +\begin_layout Code inet6 fe80::2e0:12ff:fe34:1234/10 scope link -\layout Standard +\end_layout +\begin_layout Standard Because a small lifetime was defined, such prefix will be thrown away quickly, if no related advertisement was received. -\layout Standard +\end_layout +\begin_layout Standard Additional note: if you do not used special 6to4 support in initscripts, you have to setup a special route on the internal interface on the router, otherwise you will get some backrouting problems. for the example showh here: -\layout Code +\end_layout +\begin_layout Code # /sbin/ip -6 route add 2002:0102:0304 -\series bold +\series bold : -\series default +\series default f101::/64 dev eth0 metric 1 -\layout Standard +\end_layout +\begin_layout Standard This route needs to be replaced every time the prefix changes, which is the case after a new IPv4 address was assigned to the dial-up interface. -\layout Subsection +\end_layout +\begin_layout Subsection Debugging -\layout Standard +\end_layout +\begin_layout Standard A program called \begin_inset Quotes sld -\end_inset +\end_inset radvdump \begin_inset Quotes srd -\end_inset +\end_inset can help you looking into sent or received advertisements. Simple to use: -\layout Code +\end_layout +\begin_layout Code # radvdump -\layout Code +\end_layout +\begin_layout Code Router advertisement from fe80::280:c8ff:feb9:cef9 (hoplimit 255) -\layout Code +\end_layout +\begin_layout Code AdvCurHopLimit: 64 -\layout Code +\end_layout +\begin_layout Code AdvManagedFlag: off -\layout Code +\end_layout +\begin_layout Code AdvOtherConfigFlag: off -\layout Code +\end_layout +\begin_layout Code AdvHomeAgentFlag: off -\layout Code +\end_layout +\begin_layout Code AdvReachableTime: 0 -\layout Code +\end_layout +\begin_layout Code AdvRetransTimer: 0 -\layout Code +\end_layout +\begin_layout Code Prefix 2002:0102:0304:f101::/64 -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime: 30 -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime: 20 -\layout Code +\end_layout +\begin_layout Code AdvOnLink: off -\layout Code +\end_layout +\begin_layout Code AdvAutonomous: on -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr: on -\layout Code +\end_layout +\begin_layout Code Prefix 3ffe:ffff:100:f101::/64 -\layout Code +\end_layout +\begin_layout Code AdvValidLifetime: 2592000 -\layout Code +\end_layout +\begin_layout Code AdvPreferredLifetime: 604800 -\layout Code +\end_layout +\begin_layout Code AdvOnLink: on -\layout Code +\end_layout +\begin_layout Code AdvAutonomous: on -\layout Code +\end_layout +\begin_layout Code AdvRouterAddr: on -\layout Code +\end_layout +\begin_layout Code AdvSourceLLAddress: 00 80 12 34 56 78 -\layout Standard +\end_layout +\begin_layout Standard Output shows you each advertisement package in readable format. You should see your configured values here again, if not, perhaps it's not your radvd which sends the advertisement...look for another router on the link (and take the LLAddress, which is the MAC address for tracing). -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-dhcpv6} -\end_inset +\end_inset Dynamic Host Configuration v6 Server (dhcp6s) -\layout Standard +\end_layout +\begin_layout Standard DHCPv6 can be used for stateful configurations. The daemon itself need not necessary run on the Linux default IPv6 gateway router. -\layout Standard +\end_layout +\begin_layout Standard You can specify more information than by using radvd. The are most similar to IPv4 DHCP server. -\layout Standard +\end_layout +\begin_layout Standard After a proper configuration, the daemon reacts on received ICMPv6 multicast packets sent by a client to address ff02::16 -\layout Subsection +\end_layout +\begin_layout Subsection Configuration of the DHCPv6 server (dhcp6s) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Simple configuration -\layout Standard +\end_layout +\begin_layout Standard dhcp6s's config file is normally /etc/dhcp6s.conf. An simple example looks like following: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code server-preference 255; -\layout Code +\end_layout +\begin_layout Code renew-time 60; -\layout Code +\end_layout +\begin_layout Code rebind-time 90; -\layout Code +\end_layout +\begin_layout Code prefer-life-time 130; -\layout Code +\end_layout +\begin_layout Code valid-life-time 200; -\layout Code +\end_layout +\begin_layout Code allow rapid-commit; -\layout Code +\end_layout +\begin_layout Code option dns_servers 2001:db8:0:f101::1 sub.domain.example; -\layout Code +\end_layout +\begin_layout Code link AAA { -\layout Code +\end_layout +\begin_layout Code range 2001:db8:0:f101::1000 to 2001:db8:0:f101::ffff/64; -\layout Code +\end_layout +\begin_layout Code prefix 2001:db8:0:f101::/64; -\layout Code +\end_layout +\begin_layout Code }; -\layout Code +\end_layout +\begin_layout Code }; -\layout Subsection +\end_layout +\begin_layout Subsection Configuration of the DHCPv6 client (dhcp6c) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Simple configuration -\layout Standard +\end_layout +\begin_layout Standard dhcp6c's config file is normally /etc/dhcp6c.conf. An simple example looks like following: -\layout Code +\end_layout +\begin_layout Code interface eth0 { -\layout Code +\end_layout +\begin_layout Code send rapid-commit; -\layout Code +\end_layout +\begin_layout Code request domain-name-servers; -\layout Code +\end_layout +\begin_layout Code }; -\layout Subsection +\end_layout +\begin_layout Subsection Usage -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dhcpv6_server -\layout Standard +\end_layout +\begin_layout Standard Start server, e.g. -\layout Code +\end_layout +\begin_layout Code # service dhcp6s start -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dhcpv6_client -\layout Standard +\end_layout +\begin_layout Standard Start client in foreground, e.g. -\layout Code +\end_layout +\begin_layout Code # # dhcp6c -f eth0 -\layout Subsection +\end_layout +\begin_layout Subsection Debugging -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dhcpv6_server -\layout Standard +\end_layout +\begin_layout Standard The server has one foreground and two debug toggles (both should be used for debugging), here is an example: -\layout Code +\end_layout +\begin_layout Code # dhcp6c -d -D -f eth0 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection dhcpv6_client -\layout Standard +\end_layout +\begin_layout Standard The client has one foreground and two debug toggles, here is an example: -\layout Code +\end_layout +\begin_layout Code # dhcp6c -d -f eth0 -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:16 dhcpv6 doesn't support hardware type 776 -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:16 doesn't support sit0 address family 0 -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:16 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:16 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 status code for this address is: success -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 status code: success -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 netlink_recv_rtgenmsg error -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 assigned address 2001:db8:0:f101::1002 prefix len is not in any RAs prefix length using 64 bit instead -\layout Code +\end_layout +\begin_layout Code Oct/03/2005 17:18:17 renew time 60, rebind time 9 -\layout Standard +\end_layout +\begin_layout Standard Note that the netlink error messages have no impact. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-tcpwrapper} -\end_inset +\end_inset tcp_wrapper -\layout Standard +\end_layout +\begin_layout Standard tcp_wrapper is a library which can help you to protect service against misuse. -\layout Subsection +\end_layout +\begin_layout Subsection Filtering capabilities -\layout Standard +\end_layout +\begin_layout Standard You can use tcp_wrapper for -\layout Itemize +\end_layout +\begin_layout Itemize Filtering against source addresses (IPv4 or IPv6) -\layout Itemize +\end_layout +\begin_layout Itemize Filtering against users (requires a running ident daemon on the client) -\layout Subsection +\end_layout +\begin_layout Subsection Which program uses tcp_wrapper -\layout Standard +\end_layout +\begin_layout Standard Following are known: -\layout Itemize +\end_layout +\begin_layout Itemize Each service which is called by xinetd (if xinetd is compiled using tcp_wrapper library) -\layout Itemize +\end_layout +\begin_layout Itemize sshd (if compiled using tcp_wrapper) -\layout Subsection +\end_layout +\begin_layout Subsection Usage -\layout Standard +\end_layout +\begin_layout Standard tcp_wrapper is controlled by two files name /etc/hosts.allow and /etc/hosts.deny. For more information see -\layout Code +\end_layout +\begin_layout Code $ man hosts.allow -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Example for /etc/hosts.allow -\layout Standard +\end_layout +\begin_layout Standard In this file, each service which should be positive filtered (means connects are accepted) need a line. -\layout Code +\end_layout +\begin_layout Code sshd: 1.2.3. [3ffe:ffff:100:200::]/64 -\layout Code +\end_layout +\begin_layout Code daytime-stream: 1.2.3. [3ffe:ffff:100:200::]/64 -\layout Standard +\end_layout +\begin_layout Standard Note: there are broken implementations around, which uses following broken IPv6 network description: [3ffe:ffff:100:200::/64]. Hopefully, such versions will be fixed soon. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Example for /etc/hosts.deny -\layout Standard +\end_layout +\begin_layout Standard This file contains all negative filter entries and should normally deny the rest using -\layout Code +\end_layout +\begin_layout Code ALL: ALL -\layout Standard +\end_layout +\begin_layout Standard If this node is a more sensible one you can replace the standard line above with this one, but this can cause a DoS attack (load of mailer and spool directory), if too many connects were made in short time. Perhaps a logwatch is better for such issues. -\layout Code +\end_layout +\begin_layout Code ALL: ALL: spawn (echo "Attempt from %h %a to %d at `date`" -\layout Code +\end_layout +\begin_layout Code | tee -a /var/log/tcp.deny.log | mail root@localhost) -\layout Subsection +\end_layout +\begin_layout Subsection Logging -\layout Standard +\end_layout +\begin_layout Standard Depending on the entry in the syslog daemon configuration file /etc/syslog.conf the tcp_wrapper logs normally into /var/log/secure. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Refused connection -\layout Standard +\end_layout +\begin_layout Standard A refused connection via IPv4 to an xinetd covered daytime service produces a line like following example -\layout Code +\end_layout +\begin_layout Code Jan 2 20:40:44 gate xinetd-ipv6[12346]: FAIL: daytime-stream libwrap -\layout Code +\end_layout +\begin_layout Code ¬ from=::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:32:06 gate xinetd-ipv6[12346]: FAIL: daytime-stream libwrap -\layout Code +\end_layout +\begin_layout Code from=3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Standard +\end_layout +\begin_layout Standard A refused connection via IPv4 to an dual-listen sshd produces a line like following example -\layout Code +\end_layout +\begin_layout Code Jan 2 20:24:17 gate sshd[12345]: refused connect from ::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code ¬ (::ffff:1.2.3.4) -\layout Code +\end_layout +\begin_layout Code Jan 2 20:39:33 gate sshd[12345]: refused connect -\layout Code +\end_layout +\begin_layout Code from 3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Code +\end_layout +\begin_layout Code ¬ (3ffe:ffff:100:200::212:34ff:fe12:3456) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Permitted connection -\layout Standard +\end_layout +\begin_layout Standard A permitted connection via IPv4 to an xinetd covered daytime service produces a line like following example -\layout Code +\end_layout +\begin_layout Code Jan 2 20:37:50 gate xinetd-ipv6[12346]: START: daytime-stream pid=0 -\layout Code +\end_layout +\begin_layout Code ¬ from=::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:37:56 gate xinetd-ipv6[12346]: START: daytime-stream pid=0 -\layout Code +\end_layout +\begin_layout Code from=3ffe:ffff:100:200::212:34ff:fe12:3456 -\layout Standard +\end_layout +\begin_layout Standard A permitted connection via IPv4 to an dual-listen sshd produces a line like following example -\layout Code +\end_layout +\begin_layout Code Jan 2 20:43:10 gate sshd[21975]: Accepted password for user from ::ffff:1.2.3.4 -\layout Code +\end_layout +\begin_layout Code ¬ port 33381 ssh2 -\layout Code +\end_layout +\begin_layout Code Jan 2 20:42:19 gate sshd[12345]: Accepted password for user -\layout Code +\end_layout +\begin_layout Code from 3ffe:ffff:100:200::212:34ff:fe12:3456 port 33380 ssh2 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-vsftpd} -\end_inset +\end_inset vsftpd -\layout Subsection +\end_layout +\begin_layout Subsection Listening on IPv6 addresses -\layout Standard +\end_layout +\begin_layout Standard Edit the configuration file, ususally /etc/vsftpd/vsftpd.conf, and adjust the listen option like -\layout Code +\end_layout +\begin_layout Code listen_ipv6=yes -\layout Standard +\end_layout +\begin_layout Standard That's all. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-proftpd} -\end_inset +\end_inset proftpd -\layout Subsection +\end_layout +\begin_layout Subsection Listening on IPv6 addresses -\layout Standard +\end_layout +\begin_layout Standard Edit the configuration file, ususally /etc/proftpd.conf, but take care, not 100% logical in virtual host setup -\layout Code +\end_layout +\begin_layout Code -\layout Code +\end_layout +\begin_layout Code ... -\layout Code +\end_layout +\begin_layout Code Bind 2001:0DB8::1 -\layout Code +\end_layout +\begin_layout Code ... -\layout Code +\end_layout +\begin_layout Code -\layout Standard +\end_layout +\begin_layout Standard That's all. -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{hints-daemons-others} -\end_inset +\end_inset Other daemons -\layout Standard +\end_layout +\begin_layout Standard Nowadays it's mostly simple, look for either a command line option or a configuration value to enable IPv6 listening. See manual page of the daemon or check related FAQs. It can happen that you can bind a daemon only to the IPv6- \begin_inset Quotes sld -\end_inset +\end_inset any \begin_inset Quotes srd -\end_inset +\end_inset -address (::) and not to bind to a dedicated IPv6 address, because the lack of support (depends on that what the programmer has implemented so far...). -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-programming-using-API} -\end_inset +\end_inset Programming (using API) -\layout Standard +\end_layout +\begin_layout Standard I have no experience in IPv6 programming, perhaps this chapter will be filled by others or moved away to another HOWTO. -\layout Standard +\end_layout +\begin_layout Standard More Information can be found here: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[RFC 2553 / Basic Socket Interface Extensions for IPv6]{http://www.faqs.org/rfcs/rfc2553.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Draft / Advanced Sockets API for IPv6 / draft-ietf-ipngwg-rfc2292bis-XY.txt]{http://www.ietf.org/internet-drafts/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize \lang ngerman - \begin_inset LatexCommand \url[Porting applications to IPv6 HowTo]{http://jungla.dit.upm.es/~ecastro/IPv6-web/ipv6.html} -\end_inset +\end_inset by Eva M. Castro -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-interoperability} -\end_inset +\end_inset Interoperability -\layout Standard +\end_layout +\begin_layout Standard There are some projects around the world which checks the interoperability of different operating systems regarding the implementation of IPv6 features. Here some URLs: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TAHI Project]{http://www.tahi.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard More coming next... -\layout Chapter - +\end_layout +\begin_layout Chapter \begin_inset LatexCommand \label{chapter-information} -\end_inset +\end_inset Further information and URLs -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-books} -\end_inset +\end_inset Paper printed books, articles, online reviews (mixed) -\layout Subsection +\end_layout +\begin_layout Subsection Printed Books (English) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Cisco -\layout Itemize +\end_layout +\begin_layout Itemize Cisco Self-Study: \begin_inset LatexCommand \url[Implementing IPv6 Networks (IPV6)]{http://www.amazon.com/exec/obidos/tg/detail/-/1587050862/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset , by Regis Desmeules. Cisco Press; ISBN 1587050862; 500 pages; 1st edition (April 11, 2003). -\newline -Note: This item will be published on April 11, 2003. -\layout Itemize - +\newline +Note: + This item will be published on April 11, 2003. +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Configuring IPv6 with Cisco IOS]{http://www.amazon.com/exec/obidos/tg/detail/-/1928994849/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset , by Sam Brown, Sam Browne, Neal Chen, Robbie Harrell, Edgar, Jr. Parenti (Editor), Eric Knipp (Editor), Paul Fong (Editor)362 pages; Syngress Media Inc; ISBN 1928994849; (July 12, 2002). -\layout Subsubsection +\end_layout +\begin_layout Subsubsection General -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Essentials]{http://www.sunny.ch/publications/f_ipv6.htm} -\end_inset +\end_inset by Silvia Hagen, July 2002, O'Reilly \begin_inset LatexCommand \url[Order Number: 1258]{http://www.oreilly.com/catalog/ipv6ess/} -\end_inset +\end_inset , ISBN 0-5960-0125-8, 352 pages. -\newline +\newline \begin_inset LatexCommand \url[ToC, Index, Sample Chapter etc.]{http://www.oreilly.com/catalog/ipv6ess/} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[O'Reilly Pressrelease]{http://press.oreilly.com/ipv6ess.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize IPv6: The New Internet Protocol. By Christian Huitema; Published by Prentice-Hall; ISBN 0138505055. -\newline -Description: This book, written by Christian Huitema - a member of the InternetA -rchitecture Board, gives an excellent description of IPv6, how it differs - from IPv4, and the hows and whys of it's development. +\newline +Description: This book, written by Christian Huitema - a member of the + InternetArchitecture Board, gives an excellent description of IPv6, how + it differs from IPv4, and the hows and whys of it's development. -\newline +\newline Source: \begin_inset LatexCommand \url[http://www.cs.uu.nl/wais/html/na-dir/internet/tcp-ip/resource-list.html]{http://www.cs.uu.nl/wais/html/na-dir/internet/tcp-ip/resource-list.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Networks]{http://www.epinions.com/book_mu-3402412/display_~full_specs} -\end_inset +\end_inset by Niles, Kitty; (ISBN 0070248079); 550 pages; Date Published 05/01/1998. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Implementing IPV6. Supporting the Next Generation Internet Protocols]{http://www.amazon.com/exec/obidos/tg/detail/-/0764545892/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset by P. E. Miller, Mark A. Miller; Publisher: John Wiley & Sons; ISBN 0764545892; 2nd edition (March 15, 2000); 402 pages. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Big Book of Ipv6 Addressing Rfcs]{http://www.amazon.com/exec/obidos/tg/detail/-/0126167702/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset by Peter H. Salus (Compiler), Morgan Kaufmann Publishers, April 2000, 450 pages ISBN 0126167702. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Understanding IPV6]{http://www.epinions.com/book_mu-3922588/display_~full_specs} -\end_inset +\end_inset by Davies, Joseph; ISBN 0735612455; Date Published 05/01/2001; Number of Pages: 350. -\newline +\newline \begin_inset LatexCommand \url[Understanding IPV6]{http://www.microsoft.com/MSPress/books/4883.asp} -\end_inset +\end_inset by Davies, Joseph; ISBN 0735612455; Date Published 13/11/2002; Number of Pages 544. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migrating to IPv6 - IPv6 in Practice]{http://www.amazon.com/exec/obidos/tg/detail/-/0471498920/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset . By Marc Blanchet Publisher: John Wiley & Sons; ISBN 0471498920; 1st edition (November 2002); 368 pages. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Ipv6 Network Programming]{http://www.amazon.com/exec/obidos/ASIN/1555583180/} -\end_inset +\end_inset by Jun-ichiro Hagino; ISBN 1555583180 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Wireless boosting IPv6]{http://www.nwfusion.com/news/2000/1023ipv6.html} -\end_inset +\end_inset by Carolyn Duffy Marsan, 10/23/2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[O'reilly Network search for keyword IPv6]{http://www.oreillynet.com/search/index.ncsp?sp-q=IPv6} -\end_inset +\end_inset results in 29 hits (28. January 2002). -\layout Subsection +\end_layout +\begin_layout Subsection Printed Books (German) -\layout Itemize +\end_layout +\begin_layout Itemize Technik der IP-Netze (TCP/IP incl. IPv6) \begin_inset LatexCommand \url[bei Amazon.de]{http://www.amazon.de/exec/obidos/ASIN/3446215018/} -\end_inset +\end_inset -\newline +\newline Anatol Badach, Erwin Hoffmann -\newline -Carl Hanser Verlag München, Wien, 2001 ISBN 3-446-21501-8 -\newline +\newline +Carl Hanser Verlag München, Wien, 2001 ISBN + 3-446-21501-8 +\newline Kap. 6: Protokoll IPv6 S.205-242 -\newline +\newline Kap. 7: Plug&Play-Unterstützung bei IPv6 S.243-276 -\newline +\newline Kap. 8: Migration zum IPv6-Einsatz S.277-294 -\newline +\newline Kap. 9.3.4: RIP für das Protokoll IPv6 (RIPng) S.349-351 -\newline +\newline Kap. 9.4.6: OSPF für IPv6 S.384-385 -\newline +\newline Kommentar: tw. nicht ganz up-to-date bzw. nicht ganz fehlerfreie Abbildungen -\newline +\newline \begin_inset LatexCommand \url[Homepage des Buches und Tabelle mit Fixes]{http://www.fehcom.de/tipn/tipn.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Internet-Sicherheit (Browser, Firewalls und Verschlüsselung) \begin_inset LatexCommand \url[bei Amazon.de]{http://www.amazon.de/exec/obidos/ASIN/3446217258/} -\end_inset +\end_inset -\newline +\newline Kai Fuhrberg -\newline +\newline 2. akt. Auflage 2000 Carl Hanser Verlag München, Wien, ISBN 3-446-21333-3 -\newline +\newline Kap.2.3.1.4. IPv6 S.18-22 -\newline -Kurz angerissen werden: RFC1825 - Security Association Konzept RFC1826 - - IP authentication Header RFC1827 - IP Encapsulation Security Payload -\layout Itemize +\newline +Kurz angerissen werden: RFC1825 - Security Association Konzept + RFC1826 - IP authentication Header RFC1827 - IP Encapsulation Security + Payload +\end_layout +\begin_layout Itemize IPv6. Das neue Internet- Protokoll. Technik, Anwendung, Migration \begin_inset LatexCommand \url[bei Amazon]{http://www.amazon.de/exec/obidos/ASIN/389864149X} -\end_inset +\end_inset -\newline +\newline Hans Peter Dittler -\newline +\newline 2. akt. und erweiterte Auflage 2002 dpunkt.verlag, ISBN 3-89864-149-X -\layout Itemize +\end_layout +\begin_layout Itemize Das neue Internetprotokoll IPv6 \begin_inset LatexCommand \url[bei Amazon]{http://www.amazon.de/exec/obidos/ASIN/3446216855} -\end_inset +\end_inset -\newline +\newline Herbert Wiese -\newline +\newline 2002 Carl Hanser Verlag, ISBN 3446216855 -\layout Subsection +\end_layout +\begin_layout Subsection Articles, eBooks, Online Reviews (mixed) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Getting Connected with 6to4]{http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html} -\end_inset +\end_inset by Huber Feyrer, 06/01/2001 -\layout Itemize +\end_layout +\begin_layout Itemize Transient Addressing for Related Processes: Improved Firewalling by Using IPv6 and Multiple Addresses per Host; written by Peter M. Gleiz, Steven M. Bellovin ( \begin_inset LatexCommand \url[PC-PDF-Version]{http://www.securiteinfo.com/ebooks/pdf/tarp.pdf} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[Palm-PDF-Version]{http://www.securiteinfo.com/ebooks/palm/tarp.pdf} -\end_inset +\end_inset ; \begin_inset LatexCommand \url[PDB-Version]{http://www.securiteinfo.com/ebooks/pdb/tarp.pdb} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6, théorie et pratique]{http://www.oreilly.fr/catalogue/ipv6-3ed.html} -\end_inset +\end_inset (french) 3e édition, mars 2002, O'Reilly, ISBN 2-84177-139-3 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPSec]{http://www.securiteinfo.com/crypto/IPSec.shtml} -\end_inset +\end_inset (language: french) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internetworking IPv6 with Cisco Routers]{http://www.ip6.com/index.html} -\end_inset +\end_inset by Silvano Gai, McGrawHill Italia, 1997. The 13 chapters and appendix A-D are downloadable as PDF-documents. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Secure and Dynamic Tunnel Broker]{http://www.vermicelli.pasta.cs.uit.no/ipv6/students/vegars/} -\end_inset +\end_inset by Vegar Skaerven Wang, Master of Engineering Thesis in Computer Science, 2.June 2000, Faculty of Science, Dep.of Computer Science, University of Tromso, Norway. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Aufbruch in die neue Welt - IPv6 in IPv4 Netzen]{http://www.old.netobjectdays.org/pdf/99/stja/doering.pdf} -\end_inset +\end_inset by Dipl.Ing. Ralf Döring, TU Illmenau, 1999 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migration and Co-existence of IPv4 and IPv6 in Residential Networks]{http://www.csc.fi/~psavola/residential.html} -\end_inset +\end_inset by Pekka Savola, CSC/FUNET, 2002 -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-sciencepublication} -\end_inset +\end_inset Science Publications (abstracts, bibliographies, online resources) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[GEANT IPv6 Workplan]{http://www.ipv6.ac.uk/gtpv6/workplan.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A simulation study on the performance of Mobile IPv6 in a WLAN-based cellular network]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=1} -\end_inset +\end_inset , by Perez Costa X.; Hartenstein H. -- Computer Networks, September 2002, vol. 40, no. 1, pp. 191-204(14) -- Elsevier Science. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Trials on UK Academic Networks: Bermuda Project Aug.2002]{http://www.ipv6.ac.uk/bermuda2/} -\end_inset +\end_inset : Participants - Getting connected - Project deliverables - Network topology - Address assignments - Wireless IPv6 access - IPv6 migration - Project presentations - Internet 2 - Other IPv6 projects - IPv6 fora and standards Bermuda 2... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[http://www.ipv6.ac.uk/]{http://www.ipv6.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A scalable parallel internet router that enables the QoS through merging ATM with IPv6]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=2} -\end_inset +\end_inset . By Song S. @@ -11369,12 +13858,12 @@ Science Publications (abstracts, bibliographies, online resources) 25, no. 7, pp. 647-651(5) -- Elsevier Science. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Linux IPv6: Which One to Deploy?]{http://liinwww.ira.uka.de/mpsbib?query=ti%3D(Linux+IPv6+Which+One+Deploy)} -\end_inset +\end_inset Linux Journal, Vol. 96, p. @@ -11382,15 +13871,15 @@ Science Publications (abstracts, bibliographies, online resources) (see also for more \begin_inset LatexCommand \url[liinwww.ira.uka.de/ipv6]{http://liinwww.ira.uka.de/mpsbib?query=ipv6&maxnum=200} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[An overview and analysis of mobile Internet protocols in cellular environments]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=3} -\end_inset +\end_inset . Chao H-C. @@ -11399,55 +13888,55 @@ Science Publications (abstracts, bibliographies, online resources) 11, no. 5, pp. 435-450(16) -- MCB University Press -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 for Future Wireless Networks]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=5} -\end_inset +\end_inset Toftegaard Nielsen T. -- Wireless Personal Communications, June 2001, vol. 17, no. 2/3, pp. 237-247(11) -- Kluwer Academic Publishers, Dordrecht, The Netherlands -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 at the University of Southampton]{http://www.ipv6.ecs.soton.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Seamless Support for Mobile Internet Protocol Based Cellular Environments]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=4} -\end_inset +\end_inset Chao H-C.; Chu Y-M. -- International Journal of Wireless Information Networks, July 2001, vol. 8, no. 3, pp. 133-153(21) -- Kluwer Academic/Plenum Publishers, New York, U.S.A. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: The Solution for Future Universal Networks]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1818, p. 82-??, 2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Modeling and performance analysis for IPv6 traffic with multiple QoS classes]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=8} -\end_inset +\end_inset . Zhang L.; Zheng L. @@ -11455,42 +13944,43 @@ Chao H-C.; Chu Y-M. 24, no. 15, pp. 1626-1636(11) -- Elsevier Science. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Threshold-Based Registration (TBR) in Mobile IPv6]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1818, p. 150-??, 2000. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Performance Analysis on FreeBSD Workstation Using Simple Applications]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3111/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 1961, p. 33-??, 2000. -\layout Itemize +\end_layout +\begin_layout Itemize Microsoft Research IPv6 Implementation (MSRIPv6): \begin_inset LatexCommand \url[MSRIPv6 Configuring 6to4 - Connectivity with MSR IPv6 - Our 6Bone Node... ]{http://www.research.microsoft.com/msripv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[New frontiers in cybersegmentation: marketing success in cyberspace depends on IP address]{http://www.ingenta.com/isis/searching/ExpandSearch/ingenta?year_to=2002&year_from=1997&date_type=range&title=IPv6&title_type=tka&database=1&newMatches=false&pageStart=1&index=9} -\end_inset +\end_inset . Louvieris P.; Driver J. @@ -11499,885 +13989,929 @@ Microsoft Research IPv6 Implementation (MSRIPv6): 4, no. 3, pp. 169-181(13) -- MCB University Press. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[QoS-Conditionalized Handoff for Mobile IPv6]{http://liinwww.ira.uka.de/cgi-bin/bibshow?e=Njtd0MODT0modt3113c/vojrvf} -\end_inset +\end_inset . Lecture Notes in Computer Science, Vol. 2345, p. 721-??, 2002. -\layout Subsection +\end_layout +\begin_layout Subsection Others -\layout Standard +\end_layout +\begin_layout Standard See following URL for more: \begin_inset LatexCommand \url[SWITCH IPv6 Pilot / References]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-conferences} -\end_inset +\end_inset Conferences, Meetings, Summits -\layout Subsection +\end_layout +\begin_layout Subsection 2002 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Renater - Conférence IPv6 2002]{http://www.renater.fr/IPv6-2002/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Deployment Summit at INET 2002]{http://www.ipv6summit.com/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Something missing? Suggestions are welcome! -\layout Subsection +\end_layout +\begin_layout Subsection 2003 -\layout Standard +\end_layout +\begin_layout Standard Suggestions are welcome! -\layout Subsection +\end_layout +\begin_layout Subsection 2004 -\layout Itemize +\end_layout +\begin_layout Itemize 1st Global IPv6 Summit in Sao Paul, Brazil -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlineinformation} -\end_inset +\end_inset Online information -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-joinipv6} -\end_inset +\end_inset Join the IPv6 backbone -\layout Standard +\end_layout +\begin_layout Standard More to be filled later...suggestions are welcome! -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-globalregistries} -\end_inset +\end_inset Global registries -\layout Itemize +\end_layout +\begin_layout Itemize IPv6 test backbone: \begin_inset LatexCommand \url[6bone]{http://www.6bone.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[How to join 6bone]{http://www.6bone.net/6bone_hookup.html} -\end_inset +\end_inset , -\newline +\newline \begin_inset LatexCommand \url[Teilnahme am 6bone]{http://www.join.uni-muenster.de/6bone/6bone-teilnahme.html} -\end_inset +\end_inset (german language), -\newline +\newline \begin_inset LatexCommand \url[6bone participation]{http://www.join.uni-muenster.de/6bone/6bone-participation.html} -\end_inset +\end_inset (english language) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-majorregionregistries} -\end_inset +\end_inset Major regional registries -\layout Itemize +\end_layout +\begin_layout Itemize America: \begin_inset LatexCommand \url[ARIN]{http://www.arin.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[ARIN / registration page]{http://www.arin.net/registration/ipv6/index.html} -\end_inset +\end_inset , \lang ngerman \begin_inset LatexCommand \url[ARIN / IPv6 guidelines]{http://www.arin.net/registration/ipv6/index.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize EMEA: \begin_inset LatexCommand \url[Ripe NCC]{http://www.ripe.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Ripe NCC / registration page]{http://www.ripe.net/ripencc/mem-services/registration/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Ripe NCC / IPv6 registration]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Asia/Pacific: \begin_inset LatexCommand \url[APNIC]{http://www.apnic.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[APNIC / IPv6 ressource guide]{http://www.apnic.net/services/ipv6_guide.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Latin America and Caribbea: \begin_inset LatexCommand \url[LACNIC]{http://lacnic.org/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[IPv6 Registration Services]{http://lacnic.net/en/bt-IPv6.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[IPv6 Allocation Policy]{http://lacnic.net/en/chapter-4-en.pdf} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Africa: \begin_inset LatexCommand \url[AfriNIC]{http://www.afrinic.org/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Also a list of major (prefix length 32) allocations per local registry is available here: \begin_inset LatexCommand \url[Ripe NCC / IPv6 allocations]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6allocs.html} -\end_inset +\end_inset . -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-joinipv6-tunnelbrokers} -\end_inset +\end_inset Tunnel brokers -\layout Standard +\end_layout +\begin_layout Standard Note: A list of available Tunnel broker can be found in the section \begin_inset LatexCommand \ref[Tunnel broker]{information-Tunnelbroker} -\end_inset +\end_inset below. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Sourcecode]{http://www.vermicelli.pasta.cs.uit.no/ipv6/students/vegars/TunnelBroker/} -\end_inset +\end_inset used in Vermicellis Master thesis about tunnelbroker, University of Tromso. -\layout Itemize +\end_layout +\begin_layout Itemize Former IPng. Tunnelbroker and IPv6 resources, now migrated to the \begin_inset LatexCommand \url[SixXs System]{http://www.sixxs.net/main/} -\end_inset +\end_inset . -\layout Itemize +\end_layout +\begin_layout Itemize Eckes' \begin_inset LatexCommand \url[IPv6-with-Linux]{http://sites.inka.de/lina/linux/ipv6.html} -\end_inset +\end_inset Page. -\layout Itemize +\end_layout +\begin_layout Itemize tunnelc - a perl based tunnel client script: -\newline +\newline freshmeat.net: \begin_inset LatexCommand \url[Project details for tunnel client]{http://freshmeat.net/projects/tunnelc} -\end_inset +\end_inset -\newline +\newline SourceForge: \begin_inset LatexCommand \url[Project Info - tunnelc]{http://sourceforge.net/projects/tunnelc} -\end_inset +\end_inset (also \begin_inset LatexCommand \url[here]{http://tunnelc.sourceforge.net/} -\end_inset +\end_inset ) -\layout Itemize +\end_layout +\begin_layout Itemize Linux Advanced Routing & Traffic Control HOWTO, \begin_inset LatexCommand \url[Chapter 6: IPv6 tunneling with Cisco and/or 6bone]{http://howtos.linuxbroker.com/howtoreader.shtml?file=Adv-Routing-HOWTO.html#LARTC.TUNNEL-IPV6.ADDRESSING} -\end_inset +\end_inset . -\layout Standard +\end_layout +\begin_layout Standard See also here for more information and URLs: \begin_inset LatexCommand \url[ipv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset . -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-joinipv6-6to4-tunneling} -\end_inset +\end_inset 6to4 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NSayer's 6to4 information]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[RFC 3068 / An Anycast Prefix for 6to4 Relay Routers]{http://www.faqs.org/rfcs/rfc3068.html} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-joinipv6-isatap-tunneling} -\end_inset +\end_inset ISATAP -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ISATAP (Intra-Site Automatic Tunnel Access Protocol) Information]{http://www.join.uni-muenster.de/Dokumente/Howtos/Howto_ISATAP.php?lang=en} -\end_inset +\end_inset by \begin_inset LatexCommand \url[JOIN]{http://www.join.uni-muenster.de/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Latest news and URLs to other documents -\layout Standard +\end_layout +\begin_layout Standard More to be filled later...suggestions are welcome! -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset , German forum -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Lot of URLs to others documents]{http://www.estoile.com/links/ipv6} -\end_inset +\end_inset by Anil Edathara -\layout Subsection +\end_layout +\begin_layout Subsection Protocol references -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6-related Request For Comments (RFCs) -\layout Standard +\end_layout +\begin_layout Standard Publishing the list of IPv6-related RFCs is beyond the scope of this document, but given URLs will lead you to such lists: -\layout Itemize +\end_layout +\begin_layout Itemize List sorted by \begin_inset LatexCommand \url[IPng Standardization Status]{http://playground.sun.com/pub/ipng/html/specs/standards.html} -\end_inset +\end_inset or \begin_inset LatexCommand \url[IPng Current Specifications]{http://playground.sun.com/pub/ipng/html/specs/specifications.html} -\end_inset +\end_inset by Robert Hinden -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Related Specifications]{http://www.ipv6.org/specs.html} -\end_inset +\end_inset on IPv6.org -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Current drafts of working groups -\layout Standard +\end_layout +\begin_layout Standard Current (also) IPv6-related drafts can be found here: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IP Version 6 (ipv6)]{http://www.ietf.org/ids.by.wg/ipv6.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Next Generation Transition (ngtrans)]{http://www.ietf.org/ids.by.wg/ngtrans.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Dynamic Host Configuration (dhc)]{http://www.ietf.org/ids.by.wg/dhc.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Domain Name System Extension (dnsext)]{http://www.ietf.org/ids.by.wg/dnsext.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Mobile IP (mobileip)]{http://www.ietf.org/ids.by.wg/mobileip.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Get any information about IPv6, from overviews, through RFCs & drafts, to implementations]{http://playground.sun.com/pub/ipng/html/ipng-main.html} -\end_inset +\end_inset (including availability of stacks on various platforms & source code for IPv6 stacks) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Others -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Network Sorcery / IPv6, Internet Protocol version 6]{http://www.networksorcery.com/enp/protocol/ipv6.htm} -\end_inset +\end_inset , IPv6 protocol header -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SWITCH IPv6 Pilot / References]{http://www.switch.ch/lan/ipv6/references.html} -\end_inset +\end_inset , big list of IPv6 references maintained by Simon Leinen -\layout Subsection +\end_layout +\begin_layout Subsection More information -\layout Standard +\end_layout +\begin_layout Standard More to be filled later...suggestions are welcome! -\layout Standard +\end_layout +\begin_layout Standard \lang ngerman - \begin_inset LatexCommand \url[DeepSpace6 / more interesting links]{http://www.deepspace6.net/sections/links.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Linux related -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / (Not only) Linux IPv6 Portal]{http://www.deepspace6.net/} -\end_inset +\end_inset - Italy ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-HowTo for Linux by Peter Bieringer]{http://www.bieringer.de/linux/IPv6/} -\end_inset +\end_inset - Germany, and his \begin_inset LatexCommand \url[Bieringer / IPv6 - software archive]{ftp://ftp.bieringer.de/pub/linux/IPv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Linux+IPv6 status by Peter Bieringer]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status.html} -\end_inset +\end_inset - Germany (going obsolete) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / IPv6 Status Page]{http://www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset - Italy ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset ) (will superseed upper one) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[USAGI project]{http://www.linux-ipv6.org/} -\end_inset +\end_inset - Japan, and their \begin_inset LatexCommand \url[USAGI project - software archive]{ftp://ftp.linux-ipv6.org/pub/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Linux Optimized Link State Routing Protocol (OLSR) IPv6 HOWTO]{http://www.tldp.org/HOWTO/OLSR-IPv6-HOWTO/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Linux related per distribution -\layout Description +\end_layout +\begin_layout Description PLD \begin_inset LatexCommand \url[PLD Linux Distribution]{http://www.pld-linux.org/} -\end_inset +\end_inset ( \begin_inset Quotes sld -\end_inset +\end_inset market leader \begin_inset Quotes srd -\end_inset +\end_inset in containing IPv6 enabled packages) -\layout Description +\end_layout -Red\SpecialChar ~ +\begin_layout Description +Red\InsetSpace ~ Hat \begin_inset LatexCommand \url[Red Hat Linux]{http://www.redhat.com/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[ Pekka Savola's IPv6 packages]{http://www.netcore.fi/pekkas/linux/ipv6/} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description Debian \begin_inset LatexCommand \url[Debian Linux]{http://www.debian.org/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Craig Small's IPv6 information and status]{http://people.debian.org/~csmall/ipv6/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Jim's insignificant LAN IPv6 global connectivity HOWTO]{http://www.jipo.org/jim/Jims_LAN_IPv6_global_connectivity_howto.html} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description \lang ngerman Novell/SuSE \begin_inset LatexCommand \url[Novell/SuSE Linux]{http://www.novell.com/linux/suse/} -\end_inset +\end_inset -\layout Description +\end_layout +\begin_layout Description Mandriva \begin_inset LatexCommand \url[Mandriva]{http://www.mandriva.com} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard For more see the \begin_inset LatexCommand \url[IPv6+Linux Status Distributions]{http://www.bieringer.de/linux/IPv6/status/IPv6+Linux-status-distributions.html} -\end_inset +\end_inset page. -\layout Subsubsection +\end_layout +\begin_layout Subsubsection General -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6.org]{http://www.ipv6.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6bone]{http://www.6bone.net/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UK IPv6 Resource Centre]{http://www.cs-ipv6.lancs.ac.uk/} -\end_inset +\end_inset - UK -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[WIDE project]{http://www.v6.wide.ad.jp/} -\end_inset +\end_inset - Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SWITCH IPv6 Pilot]{http://www.switch.ch/lan/ipv6/} -\end_inset +\end_inset - Switzerland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Corner of Hubert Feyrer]{http://www.feyrer.de/IPv6/} -\end_inset +\end_inset - Germany -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Vermicelli Project]{http://www.vermicelli.pasta.cs.uit.no/ipv6/} -\end_inset +\end_inset - Norway -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Forum]{http://www.ipv6forum.com/} -\end_inset +\end_inset - a world-wide consortium of leading Internet vendors, Research & Education Networks... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Playground.sun.com / IPv6 Info Page]{http://playground.sun.com/pub/ipng/html/ipng-main.html} -\end_inset +\end_inset - maintained by Robert Hinden, Nokia. Get any information about IPv6, from overviews, through RFCs & drafts, to implementations (including availability of stacks on various platforms & source code for IPv6 stacks). -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6INIT]{http://www.6init.com/} -\end_inset +\end_inset - IPv6 Internet Initiative - an EU Fifth Framework Project under the IST Programme. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Task Force (European Union)]{http://www.ipv6-taskforce.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Document Project]{http://www.v6.sfc.wide.ad.jp/v6doc/} -\end_inset +\end_inset (Japanese language) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6init]{http://www.6init.org/} -\end_inset +\end_inset - IPv6 INternet IniTiative -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IP Next Generation Overview]{http://www.isoc.org/HMP/PAPER/PT1/html/pt1.html.hinden} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: The New Version of the Internet Protocol]{http://www.usenix.org/publications/library/proceedings/ana97/summaries/deering.html} -\end_inset +\end_inset , by Steve Deering. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: The Next Generation Internet Protocol]{http://www.garykessler.net/library/ipv6_exp.html} -\end_inset +\end_inset , by Gary C. Kessler. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6: Next Generation Internet Protocol]{http://www.3com.com/nsc/ipv6.html} -\end_inset +\end_inset - 3Com -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Next Generation Internet Initiative]{http://www.ngi.gov/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[internet || site]{http://www.internet2.org/} -\end_inset +\end_inset and \begin_inset LatexCommand \url[internet2 Working Group]{http://ipv6.internet2.edu/} -\end_inset +\end_inset - \begin_inset LatexCommand \url[Presentation (HTML + PPT)]{http://ipv6.internet2.edu/presentations/} -\end_inset +\end_inset from IPv6 Workshops: (Stateless Autoconfiguration, IPv6 Addressing, USAGI, Provider Independent IPv6 Addressing and other topics). -\layout Itemize +\end_layout +\begin_layout Itemize NetworkWorldFusion: Search / Doc Finder: \begin_inset LatexCommand \url[searched for IPv6]{http://search.nwfusion.com/query.html?qt=IPv6&qp=&ch=cn&} -\end_inset +\end_inset (102 documents found 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[The Register]{http://www.theregister.co.uk/} -\end_inset +\end_inset (Search for IPv6 will result in 30 documents, 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ZDNet Search for IPv6]{http://zdnet.search.com/search?cat=279&q=IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TechTarget Search for IPv6]{http://whatis.techtarget.com/wsearchResults/1,290214,sid9,00.html?query=IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 & TCP Resources List]{http://www.faqs.org/faqs/internet/tcp-ip/resource-list/index.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Klingon IPv6 tools]{http://ipv6.klingon.nl/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Klingon IPv6 tools (native IPv6 only access)]{http://www.ipv6.klingon.nl/} -\end_inset +\end_inset : IPv6 firewall examples, bandwith testing and portscanner -\layout Standard +\end_layout +\begin_layout Standard Something missing? Suggestions are welcome! -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-marketresearch} -\end_inset +\end_inset Market Research -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[A Tale of Two Wireless Technology Trends: Processor Development Outsourcing and IPv6]{http://www.seminarinformation.com/wconnect/wc.dll?sis~details0~307~TSN} -\end_inset +\end_inset Yankee Group - 4/1/2002 - 12 Pages - ID: YANL768881 -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[The World Atlas of the Internet: Americas]{http://www.marketresearch.com/product/display.asp?SID=88602378-241489274-186851952&ProductID=803907} -\end_inset +\end_inset ; IDATE - 2/1/2002 - 242 PAges - ID: IDT803907. Countries covered: Central America, North America, South America; List: @@ -12385,1603 +14919,1657 @@ Yankee Group - 4/1/2002 - 12 Pages - ID: YANL768881 globe. Market assessment and forecasts up to 2006 for 34 countries: market structure: main ISPs and market shares; number of subscribers, of ISPs. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Early Interest Rising for IPv6]{http://www.amazon.com/exec/obidos/tg/detail/-/B000065T8E/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset by IDC (Author); List Price: $1,500.00; Edition: e-book (Acrobat Reader); Publisher: IDC; ISBN B000065T8E; (March 1, 2002) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-patents} -\end_inset +\end_inset Patents -\layout Itemize +\end_layout +\begin_layout Itemize Canadian Patent Database: \begin_inset LatexCommand \url[Home]{http://patents1.ic.gc.ca/intro-e.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Search]{http://patents1.ic.gc.ca/srch_sim-e.html} -\end_inset +\end_inset (Basic Search, just enter IPv6 in the search field ;-); 84 documents found 22.12.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Espacenet]{http://www.european-patent-office.org/espacenet/info/index.htm} -\end_inset +\end_inset - European patent information: -\newline +\newline \begin_inset LatexCommand \url[National Offices, Members of Espacenet]{http://www.european-patent-office.org/espacenet/info/access.htm} -\end_inset +\end_inset (IPv6: 84 documents, 22.12.2002) -\layout Itemize +\end_layout +\begin_layout Itemize Delphion Research: \begin_inset LatexCommand \url[Patent Search Page]{http://www.delphion.com/research/} -\end_inset +\end_inset . Basic (free) registration needed. Examples found 21.12.2002 searching for IPv6: -\newline +\newline \begin_inset LatexCommand \url[Communicating method between IPv4 terminal and IPv6 terminal and IPv4-IPv6 converting apparatus]{http://www.delphion.com/details?pn=US06118784__} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Translator for IP networks, network system using the translator, and IP network coupling method therefor]{http://www.delphion.com/details?pn=US06038233__} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection By countries -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Europe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[www.ist-ipv6.org]{http://www.ist-ipv6.org/} -\end_inset +\end_inset : IST IPv6 Cluster, European IPv6 Research and Development Projects -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Euro6IX]{http://www.euro6ix.org/} -\end_inset +\end_inset : European IPv6 Internet Exchanges Backbone -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Austria -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6@IKNnet and MIPv6 Research Group]{http://www.ikn.tuwien.ac.at/~ipv6/} -\end_inset +\end_inset : TU Vienna, Austria (IPv6: project, publications, diploma / doctor thesis, Conference Proceedings etc.) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Australia -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Carl's Australian IPv6 Pages]{http://oversteer.bl.echidna.id.au/IPv6/} -\end_inset +\end_inset (old content) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Belgium -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Brazil -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[BR6bone]{http://www.6bone.rnp.br/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Summit in Brazil]{http://www.ipv6summit.com.br/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 do Brasil]{http://www.ipv6dobrasil.com.br/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection China -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Czech -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Germany -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-net.org]{http://www.ipv6-net.de/} -\end_inset +\end_inset : German IPv6 forum -\layout Subsubsection +\end_layout +\begin_layout Subsubsection France -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Renater]{http://www.renater.fr/Projets/IPv6/index.htm} -\end_inset +\end_inset : Renater IPv6 Project Page -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 - RSVP - ATM at INRIA]{http://www.inria.fr/recherche/equipes/ipv6.fr.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NetBSD IPv6 Documentation]{http://www.netbsd.org/fr/Documentation/network/ipv6/} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Hungary -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Testing Experimental IPv6 Technology and Services in Hungary]{http://tipster6.ik.bme.hu/tipster6_en.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection India -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Italy -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Project6]{http://project6.ferrara.linux.it/} -\end_inset +\end_inset : IPv6 networking with Linux -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Linux IPv6 Users Group JP]{http://www.v6.linux.or.jp/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Yamaha IPv6]{http://www.rtpro.yamaha.co.jp/RT/ipv6/} -\end_inset +\end_inset (sorry, all in japanese native ...) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Korea -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ETRI]{http://www.krv6.net/} -\end_inset +\end_inset : Electronics and Telecommunications Research Institut -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Forum Korea]{http://www.ipv6.or.kr/english/index.new.htm} -\end_inset +\end_inset : Korean IPv6 Deployment Project -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Mexico -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Mexico]{http://www.ipv6.unam.mx/} -\end_inset +\end_inset (spain & english version): IPv6 Project Hompeage of The National Autonomous University of Mexico (UNAM) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Netherland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SURFnet]{http://www.ipv6.surfnet.nl/} -\end_inset +\end_inset : SURFnet IPv6 Backbone -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[STACK]{http://www.stack.nl/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[STACK (IPv6)]{http://www.stack.nl/ipv6/} -\end_inset +\end_inset : Students' computer association of the Eindhoven University of Technology, Netherland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPng.nl]{http://www.ipng.nl/} -\end_inset +\end_inset : collaboration between WiseGuys and Intouch -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Portugal -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[FCCN (National Foundation for the Scientific Computation)]{http://www.fccn.pt/projectos/ipv6/index_html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Russia -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Forum for Russia]{http://www.ipv6.ru/} -\end_inset +\end_inset : Yaroslavl State University Internet Center -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Switzerland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SWITCH]{http://www.switch.ch/network/ipv6/references.html} -\end_inset +\end_inset : The Swiss Education & Research Network -\layout Subsubsection +\end_layout +\begin_layout Subsubsection United Kingdom -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 in the UK]{http://www.ipv6.org.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UK IPv6 Resource Center]{http://www.cs-ipv6.lancs.ac.uk/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[British Telecom IPv6 Home]{http://www.bt.com/ipv6/} -\end_inset +\end_inset : BT's ISP IPv6 Trial, UK's first IPv6 Internet Exchange etc. -\layout Subsection +\end_layout +\begin_layout Subsection By operating systems -\layout Subsubsection +\end_layout +\begin_layout Subsubsection *BSD -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[KAME project]{http://www.kame.net/} -\end_inset +\end_inset (*BSD) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NetBSD's IPv6 Networking FAQ]{http://www.netbsd.org/Documentation/network/ipv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[FreeBSD Ports: Ipv6]{http://www.freebsd.org/ports/ipv6.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize BUGAT - BSD Usergroup Austria - \begin_inset LatexCommand \url[www.bugat.at]{http://www.bugat.at/} -\end_inset +\end_inset : \begin_inset LatexCommand \url[FreeBSD IPv6 Tunnel]{http://www.bugat.at/inforum/contentview.php/mini-howto/freebsd-ipv6.ihtml} -\end_inset +\end_inset (German language) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Cisco IOS -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Cisco IOS IPv6 Entry Page]{http://www.cisco.com/warp/public/732/Tech/ipv6/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 for Cisco IOS Software]{http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t2/ipv6/ftipv6c.htm} -\end_inset +\end_inset , File 2 of 3: Aug 2002 -- Table of Contents: IPv6 for Cisco IOS Software; Configuring Documentation Specifics; Enabling IPv6 Routing and Configuring; IPv6 Addressing; Enabling IPv6 Processing Globally. -\layout Itemize +\end_layout +\begin_layout Itemize Cisco Internet Networking Handbook, \begin_inset LatexCommand \url[Chapter IPv6]{http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/ipv6.htm} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Compaq -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 at Compaq]{http://www.compaq.com/ipv6/} -\end_inset +\end_inset - Presentations, White Papers, Documentation... -\layout Subsubsection +\end_layout +\begin_layout Subsubsection HPUX -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[comp.sys.hp.hpux FAQ]{http://www.faqs.org/faqs/hp/hpux-faq/index.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IBM -\layout Itemize +\end_layout +\begin_layout Itemize Now that IBM's announced the availability of z/OS V1.4, \begin_inset LatexCommand \url[what's new in this release?]{http://search390.techtarget.com/ateQuestionNResponse/0,289625,sid10_cid486367_tax292523,00.html} -\end_inset +\end_inset This question was posed on 15 August 2002 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Microsoft -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Microsoft Windows 2000 IPv6]{http://www.microsoft.com/windows2000/technologies/communications/ipv6/default.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[MSRIPv6]{http://www.research.microsoft.com/msripv6} -\end_inset +\end_inset - Microsoft Research Network - IPv6 Homepage -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Getting Started with the Microsoft IPv6 Technology Preview for Windows 2000]{http://msdn.microsoft.com/downloads/sdks/platform/tpipv6/start.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internet Connection Firewall Does Not Block Internet Protocol Version 6 Traffic]{http://support.microsoft.com/default.aspx?scid=kb;en-us;306203} -\end_inset +\end_inset (6.11.2001) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internet Protocol Numbers]{http://support.microsoft.com/default.aspx?scid=kb;en-us;289892} -\end_inset +\end_inset (8.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Technology Preview Refresh]{http://support.microsoft.com/default.aspx?scid=kb;en-us;273826} -\end_inset +\end_inset (16.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[HOW TO: Install and Configure IP Version 6 in Windows .NET Enterprise Server]{http://support.microsoft.com/default.aspx?scid=kb;en-us;325449} -\end_inset +\end_inset (26.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Windows .NET Server 6to4 Router Service Quits When You Advertise a 2002 Address on the Public Interface]{http://support.microsoft.com/default.aspx?scid=kb;en-us;329984} -\end_inset +\end_inset (28.10.2002) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[msdn - Microsoft Windows CE .NET - IPv6 commands]{http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcetcpip/htm/cmconIPv6exe.asp} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[msdn - search for IPv6]{http://search.microsoft.com/default.asp?qu=IPv6&boolean=ALL&nq=NEW&so=RECCNT&p=1&ig=01&i=00&i=01&i=02&i=03&i=04&i=05&i=06&i=07&i=08&i=09&i=10&i=11&i=12&i=13&i=14&i=15&i=16&i=17&i=18&i=19&i=20&i=21&i=22&i=23&i=24&i=25&i=26&i=27&i=28&i=29&i=30&i=31&i=32&i=33&i=34&i=35&i=36&i=37&i=38&i=39&i=40&i=41&siteid=us/dev} -\end_inset +\end_inset (100 results, 22.12.2002) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Solaris -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Sun Microsystems Solaris]{http://www.sun.com/software/solaris/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Solaris 2 Frequently Asked Questions (FAQ) 1.73]{http://www.cs.uu.nl/wais/html/na-dir/Solaris2/FAQ.html} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Sumitoma -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Sumitomo Electric has implemented IPv6 on Suminet 3700 family routers]{http://playground.sun.com/pub/ipng/html/ipng-implementations.html#Sumitomo} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection ZebOS -\layout Itemize +\end_layout +\begin_layout Itemize IpInfusion's \begin_inset LatexCommand \url[ZebOS Server Routing Software]{http://www.ipinfusion.com/products/server/products_server.html} -\end_inset +\end_inset -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-ipv6andsecurity} -\end_inset +\end_inset IPv6 Security -\layout Itemize +\end_layout +\begin_layout Itemize Internet Security Systems: Security Center, \begin_inset LatexCommand \url[X-Force Database Search]{http://www.iss.net/security_center/search.php?type=3&type=3&pattern=IPv6} -\end_inset +\end_inset (21.12.2002 - 6 topics found relating to IPv6) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NIST IPsec Project]{http://csrc.nist.gov/ipsec/} -\end_inset +\end_inset ( National Institute of Standards and Technology, NIST) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Information Security]{http://www.infosecuritymag.com/index.shtml} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NewOrder.box.sk (search for IPv6)]{http://neworder.box.sk/search.php3?srch=IPv6} -\end_inset +\end_inset (Articles, exploits, files database etc.) -\layout Subsection +\end_layout +\begin_layout Subsection Application lists -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / IPv6 Status Page]{http://www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Mirror]{http://mirrors.bieringer.de/www.deepspace6.net/docs/ipv6_status_page_apps.html} -\end_inset +\end_inset ) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6.org / IPv6 enabled applications]{http://www.ipv6.org/v6-apps.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Freshmeat / IPv6 search]{http://freshmeat.net/search/?q=IPv6} -\end_inset +\end_inset , currently (14 Dec 2002) 62 projects -\layout Itemize +\end_layout +\begin_layout Itemize IPv6 Forum: \begin_inset LatexCommand \url[IPv6 Router List]{http://www.ipv6forum.com/navbar/links/v6routerlist.htm} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Analyzer tools -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Ethereal]{http://ethereal.planetmirror.com/} -\end_inset +\end_inset - Ethereal is a free network protocol analyzer for Unix and Windows -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Radcom RC100-WL]{http://www.ip6.com/us/analyzer.htm} -\end_inset +\end_inset - Download Radcom RC100-WL protocol analyzer version 3.20 -\layout Subsubsection +\end_layout +\begin_layout Subsubsection IPv6 Products -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6wind]{http://www.6wind.com/} -\end_inset +\end_inset - solutions for IPv4/IPv6 Router, QoS, Multicast, Mobility, Security/VPN/Firewa ll. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Fefe's patches for IPv6 with djbdns]{http://www.fefe.de/dns/} -\end_inset +\end_inset Aug 2002 -- What is djbdns and why does it need IPv6? djbdns is a full blown DNS server which outperforms BIND in nearly all respects. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ZebOS Server Routing Suite ]{http://www.ipinfusion.com/products/server/products_server.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SPA Mail Server 2.21 ]{http://download.com.com/3000-2165-10153543.html?tag=lst-0-21} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Inframail (Advantage Server Edition) 6.0 ]{http://download.com.com/3000-2165-8202652.html?tag=lst-0-2} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[HTTrack Website Copier]{http://download.com.com/3000-2377-10149393.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[CommView 5.0]{http://download.com.com/3000-2085-10132748.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Posadis 0.50.6]{http://download.com.com/3000-2104-10149750.html?tag=lst-0-1} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TCP Wrapper (IPv6 aware)]{ftp://ftp.porcupine.org/pub/ipv6/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-snmp} -\end_inset +\end_inset SNMP -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[comp.protocpols.snmp SNMP FAQ Part 1 of 2]{http://www.cs.uu.nl/wais/html/na-dir/snmp-faq/part1.html} -\end_inset +\end_inset -\layout Section +\end_layout +\begin_layout Section IPv6 Infrastructure -\layout Subsection +\end_layout +\begin_layout Subsection Statistics -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 routing table history]{http://www.space.net/~gert/RIPE/} -\end_inset +\end_inset created by Gert Döring, \begin_inset LatexCommand \url[Space.Net]{http://www.space.net/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Official 6bone Webserver list Statisic]{http://6bone.informatik.uni-leipzig.de/ipv6/stats/stats.php3} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Allocation Data & Survey Results]{http://www.ripe.net/ripe/meetings/archive/ripe-42/presentations/ripe42-ipv6-survey/sld001.html} -\end_inset +\end_inset , IPv6 WG, Ripe 42, Ripe NCC -\layout Subsection +\end_layout +\begin_layout Subsection Internet Exchanges -\layout Standard +\end_layout +\begin_layout Standard Another list of IPv6 Internet Exchanges can be found here: \begin_inset LatexCommand \url[IPv6 Exchanges Web Site]{http://www.v6nap.net/} -\end_inset +\end_inset or \begin_inset LatexCommand \url[IPv6 status of IXPs in Europe]{http://www.euro-ix.net/isp/choosing/search/matrix.php} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-estonia} -\end_inset +\end_inset Estonia -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[TIX]{http://tix.estpak.ee/} -\end_inset +\end_inset (tallinn interneti exchange with ipv6 support) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-europe} -\end_inset +\end_inset Europe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Euro6IX]{http://www.euro6ix.net/} -\end_inset +\end_inset , European IPv6 Internet Exchange Backbone -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-france} -\end_inset +\end_inset France -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[French National Internet Exchange IPv6]{http://www.fnix6.net/} -\end_inset +\end_inset (since 1.11.2002 active). -\newline +\newline FNIX6 provides a free and reliable high speed FastEthernet interconnection between ISP located in TeleCity Paris. -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-germany} -\end_inset +\end_inset Germany -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[INXS]{http://www.inxs.de/} -\end_inset +\end_inset : (Cable & Wireless) Munich and Hamburg -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-japan} -\end_inset +\end_inset Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NSPIXP-6]{http://www.wide.ad.jp/nspixp6/} -\end_inset +\end_inset : IPv6-based Internet Exchange in Tokyo -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[JPIX]{http://www.jpix.co.jp/} -\end_inset +\end_inset , Tokyo -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-korea} -\end_inset +\end_inset Korea -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6NGIX]{http://www.ngix.ne.kr/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-netherlands} -\end_inset +\end_inset Netherlands -\layout Itemize +\end_layout +\begin_layout Itemize \lang ngerman - \begin_inset LatexCommand \url[AMS-IX]{http://www.ams-ix.net/} -\end_inset +\end_inset \lang english : Amsterdam Internet Exchange -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-uk} -\end_inset +\end_inset UK -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UK6X]{http://www.uk6x.com/} -\end_inset +\end_inset : London -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XchangePoint]{http://www.xchangepoint.net/} -\end_inset +\end_inset : London -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-ipv6exchanges-usa} -\end_inset +\end_inset USA -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6TAP]{http://www.6tap.net} -\end_inset +\end_inset : Chicago. Supports peerings around the globe. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NY6IX]{http://www.ny6ix.net/} -\end_inset +\end_inset : New York City IPv6 based Internet Exchange -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[PAIX]{http://www.paix.net/} -\end_inset +\end_inset : Palo Alto -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-Tunnelbroker} -\end_inset +\end_inset Tunnel broker -\layout Standard +\end_layout +\begin_layout Standard See also: \begin_inset LatexCommand \url[http://www.deepspace6.net/docs/tunnelbrokers.html]{http://www.deepspace6.net/docs/tunnelbrokers.html} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-belgium} -\end_inset +\end_inset Belgium -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Wanadoo]{http://tunnel.be.wanadoo.com/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-canada} -\end_inset +\end_inset Canada -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Freenet6]{http://www.freenet6.net/} -\end_inset +\end_inset - /48 Delegation, Canada -\newline +\newline \begin_inset LatexCommand \url[Getting IPv6 Using Freenet6 on Debian]{http://www.linuxjournal.com/article.php?sid=5963&mode=thread&order=0} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Freenet6 creater]{http://www.viagenie.qc.ca/en/index.shtml} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-china} -\end_inset +\end_inset China -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[CERNET-Nokia]{http://tb.6test.edu.cn/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-estonia} -\end_inset +\end_inset Estonia -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Estpak]{http://tunnelbroker.ipv6.estpak.ee/?tunnel&PHPSESSID=aa2184190cc2cc6d3a6f6ddd01ae3635} -\end_inset +\end_inset -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Europe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XS26 Distributed Tunnel Broker]{http://www.xs26.net/} -\end_inset +\end_inset , USA & Europe -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-germany} -\end_inset +\end_inset Germany -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6bone Knoten Leipzig]{http://6bone.informatik.uni-leipzig.de/} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Info bez. Hackangriff (2001)]{http://www.mail-archive.com/ipv6@uni-muenster.de/msg00056.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Berkom]{http://fix.ipv6.berkom.de/cgi-bin/tb.pl} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-italy} -\end_inset +\end_inset Italy -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Centro Studi e Laboratory Telecomunicazioni]{https://carmen.cselt.it/ipv6tb/} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Downloadpage: TunnelBroker Version 2.1.]{http://carmen.cselt.it/cgi-bin/download.pl?pkg=TunnelBroker} -\end_inset +\end_inset ) -\newline +\newline IPv6 Tunnel Broker: \begin_inset LatexCommand \url[Installation instructions]{http://carmen.cselt.it/ipv6/tools/ipv6tb/Installing-ipv6tb.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Comv6]{http://www.comv6.com/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Bersafe]{http://www.bersafe.it} -\end_inset +\end_inset (Italian language) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Telecom Italia LAB]{http://carmen.ipv6.tilab.com/} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Tunnelbroker Software Downloadpage]{http://carmen.ipv6.tilab.com/cgi-bin/download.pl?pkg=TunnelBroker} -\end_inset +\end_inset ) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-japan} -\end_inset +\end_inset Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Internet Initiative Japan]{http://www.iij.ad.jp/en/IPv6/} -\end_inset +\end_inset ( \begin_inset LatexCommand \url[Japanese language]{http://www.iij.ad.jp/IPv6/} -\end_inset +\end_inset ) - with IPv6 native line service and IPv6 tunneling Service -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-malaysia} -\end_inset +\end_inset Malaysia -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Manis]{http://tbroker.manis.net.my/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-netherlands} -\end_inset +\end_inset Netherlands -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XS26 - "Access to Six"]{http://www.xs26.net/} -\end_inset +\end_inset - with POPs in Slovak Republic, Czech Republic, Netherlands, Germany and Hungary. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPng Netherland]{http://www.ipng.nl/} -\end_inset +\end_inset - Intouch, SurfNet, AMS-IX, UUNet, Cistron, RIPE NCC and AT&T are connected at the AMS-IX. It is possible (there are requirements...) to get an static tunnel. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[SURFnet Customers]{http://www.ipv6.surfnet.nl/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-norway} -\end_inset +\end_inset Norway -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[UNINETT]{http://www.uninett.no/testnett/index.en.html} -\end_inset +\end_inset - Pilot IPv6 Service (for Customers): tunnelbroker & address allocation -\newline +\newline \begin_inset LatexCommand \url[Uninett-Autoupdate-HOWTO]{http://www.guruz.de/Uninett-Autoupdate-HOWTO} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-spain} -\end_inset +\end_inset Spain -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Consulintel]{http://tb.consulintel.euro6ix.org/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-switzerland} -\end_inset +\end_inset Switzerland -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Tunnelbroker AS8758]{http://tunnelbroker.as8758.net/} -\end_inset +\end_inset , Dolphins Network Systems (since 20.12.2002 online) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-uk} -\end_inset +\end_inset UK -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[NTT Europe]{http://www.uk.v6.ntt.net/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[NTT]{http://www.nttv6.net/} -\end_inset +\end_inset , United Kingdom - IPv6 Trial. IPv4 Tunnel and native IPv6 leased Line connections. POPs are located in London, UK Dusseldorf, Germany New Jersey, USA (East Coast) Cupertino, USA (West Coast) Tokyo, Japan -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[BtexacT IPv6 Tunnel Broker Service]{https://tb.ipv6.btexact.com/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPNG-UK]{http://ipng.org.uk/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-usa} -\end_inset +\end_inset USA -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ESnet]{http://www.es.net/hypertext/welcome/pr/ipv6.html} -\end_inset +\end_inset , USA - Energy Sciences Network: Tunnel Registry & Address Delegation for directly connected ESnet sites and ESnet collaborators. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6REN]{http://www.6ren.net/} -\end_inset +\end_inset , USA - The 6ren initiative is being coordinated by the Energy Sciences Network (ESnet), the network for the Energy Research program of the US Dept. of Energy, located at the University of California's Lawrence Berkeley National Laboratory. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[XS26 Distributed Tunnel Broker]{http://www.xs26.net/} -\end_inset +\end_inset , USA & Europe -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Hurricane Electric]{http://ipv6tb.he.net/} -\end_inset +\end_inset , US backbone; -\newline +\newline \begin_inset LatexCommand \url[Hurrican Electric Tunnelbroker]{http://tunnelbroker.net/} -\end_inset +\end_inset (also available under \begin_inset LatexCommand \url[http://tunnelbroker.com/]{http://tunnelbroker.com/} -\end_inset +\end_inset ) -\newline +\newline Press Release: \begin_inset LatexCommand \url[Hurricane Electric Upgrades IPv6 Tunnel Broker]{http://www.he.net/releases/release6.html} -\end_inset +\end_inset -\newline +\newline \begin_inset LatexCommand \url[Tunnel Broker Endpoint Autoupdate]{http://ipv6.he.net/tunnelbroker-update.php} -\end_inset +\end_inset , Perl Script -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-singapore} -\end_inset +\end_inset Singapore -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[http://tunnel-broker.singnet.com.sg/]{http://tunnel-broker.singnet.com.sg/} -\end_inset +\end_inset , with NAT and IPsec option -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-tunnelbroker-more} -\end_inset +\end_inset More Tunnel brokers... -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Public 6to4 relay routers]{http://www.kfu.com/~nsayer/6to4/} -\end_inset +\end_inset (MS IIE boycott!) -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{information-infrastructure-nativeipv6service} -\end_inset +\end_inset Native IPv6 Services -\layout Standard +\end_layout +\begin_layout Standard Note: These services are mostly only available with a valid IPv6 connection! -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6nntp} -\end_inset +\end_inset Net News (NNTP) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[news.ipv6.scarlet-internet.nl]{nntp://news.ipv6.scarlet-internet.nl/} -\end_inset +\end_inset (accessible through all the SixXS POPs) -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6gameserver} -\end_inset +\end_inset Game Server -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Quake2]{http://www.viagenie.qc.ca/en/ipv6/quake2/ipv6-quake2.shtml} -\end_inset +\end_inset over IPv6 -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6ircserver} -\end_inset +\end_inset IRC Server -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Cyconet]{http://ipv6.cyconet.org/?id=server} -\end_inset +\end_inset (Cyconet IRCnet Servers over IPv6) -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Radio Stations, Music Streams -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Experimental Live IPv6 Stream!]{http://aopteryx.informatik.uni-leipzig.de:8000/live.mp3} -\end_inset +\end_inset , University of Leipzig, Germany -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{information-nativeipv6webserver} -\end_inset +\end_inset Webserver -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Peter Bieringer's Home of Linux IPv6 HOWTO ]{http://www.ipv6.bieringer.de/} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Something missing? Suggestions are welcome! -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-maillists} -\end_inset +\end_inset Maillists -\layout Standard +\end_layout +\begin_layout Standard Lists of maillists are available at: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DeepSpace6 / Mailling Lists]{http://www.deepspace6.net/sections/lists.html} -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard Major Mailinglists are listed in following table: -\layout Standard +\end_layout +\begin_layout Standard . -\layout Standard +\end_layout - -\begin_inset Tabular +\begin_layout Standard +\begin_inset Tabular @@ -13994,834 +16582,916 @@ Major Mailinglists are listed in following table: \begin_inset Text -\layout Standard - +\begin_layout Standard Focus -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Request e-mail address -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard What to subscribe -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Maillist e-mail address -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Language -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Access through WWW -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Linux kernel networking including IPv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) oss.sgi.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard netdev -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard netdev (at) oss.sgi.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Archive]{http://oss.sgi.com/projects/netdev/archive/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Linux and IPv6 in general (1) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) list.f00f.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard linux-ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard linux-ipv6 (at) list.f00f.org (moderated) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Linux implementation of the IPv6 protocol -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Web-based, see URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard project6 (at) ferrara.linux.it -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://project6.ferrara.linux.it/sections/lists.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Subscription]{http://mailman.ferrara.linux.it/listinfo/project6} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Mobile IP(v6) for Linux -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) list.mipl.mediapoli.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard mipl -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard mipl (at) list.mipl.mediapoli.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.mipl.mediapoli.com/mailinglist.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.mipl.mediapoli.com/mail-archive/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Linux IPv6 users using USAGI extension -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard usagi-users-ctl (at) linux-ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard usagi-users (at) linux-ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info / Search]{http://www.linux-ipv6.org/ml/index.html#usagi-users} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.linux-ipv6.org/ml/usagi-users/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard IPv6 on Debian Linux -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Web-based, see URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard debian-ipv6 (at) lists.debian.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info/Subscription/Archive]{http://lists.debian.org/debian-ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard IPv6/6bone in Germany -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) atlan.uni-muenster.de -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 (at) uni-muenster.de -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard German/English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.join.uni-muenster.de/JOIN/ipv6/texte-englisch/mailingliste.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://www.join.uni-muenster.de/local/majordomo/ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard 6bone -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) isi.edu -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard 6bone -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard 6bone (at) isi.edu -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.6bone.net/6bone_email.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://mailman.isi.edu/pipermail/6bone/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard IPv6 discussions -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) sunroof.eng.sun.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipng -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipng (at) sunroof.eng.sun.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://playground.sun.com/pub/ipng/html/instructions.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{ftp://playground.sun.com/pub/ipng/mail-archive/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Mirror of archive]{http://www.wcug.wwu.edu/lists/ipng/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard IPv6 users in general -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard users -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard users (at) ipv6.org -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.ipv6.org/mailing-lists.html} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://news.gmane.org/thread.php?group=gmane.network.ipv6.general} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Bugtracking of Internet applications (2) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard bugtraq-subscribe (at) securityfocus.com -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard bugtraq (at) securityfocus.com (moderated) -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://online.securityfocus.com/popups/forums/bugtraq/intro.shtml} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://online.securityfocus.com/archive/1} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard IPv6 in general -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Web-based, see URL -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard +\begin_layout Standard -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 (at) ipng.nl -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard English -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info/Subscription]{http://mailman.ipng.nl/mailman/listinfo/ipv6/} -\end_inset +\end_inset , \begin_inset LatexCommand \url[Archive]{http://mailman.ipng.nl/pipermail/ipv6/} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard majordomo (at) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard ipv6 (at) mfa.eti.br -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - +\begin_layout Standard Portuguese -\end_inset +\end_layout + +\end_inset \begin_inset Text -\layout Standard - - +\begin_layout Standard \begin_inset LatexCommand \url[Info]{http://www.marcelo.pro.br/mailman/listinfo/ipv6} -\end_inset +\end_inset -\end_inset +\end_layout + +\end_inset -\end_inset +\end_inset -\layout Standard +\end_layout +\begin_layout Standard (1) recommended for common Linux & IPv6 issues. -\layout Standard +\end_layout +\begin_layout Standard (2) very recommended if you provide server applications. -\layout Standard +\end_layout +\begin_layout Standard Something missing? Suggestions are welcome! -\newline +\newline -\layout Standard +\end_layout +\begin_layout Standard Following other maillinglists & newsgroups are available via web: -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (France)]{http://www.tile.net/lists/showlists.php?list_id=35905} -\end_inset +\end_inset -\newline +\newline Description: ipv6 Cette liste existe pour discuter en francais de IP version 6. Elle s'adresse aux personnes desirant demarer des aujourd'hui des tests @@ -14830,163 +17500,163 @@ Description: ipv6 Cette liste existe pour discuter en francais de IP version Pour de plus amples informations: \begin_inset LatexCommand \url[http://www.urec.fr/IPng]{http://www.urec.fr/IPng} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Tunnelbroker Maillingliste (Germany)]{http://www.ipv6.uni-leipzig.de/~6bone/tb/maillist.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (Hungary)]{http://www.tile.net/lists/showlists.php?list_id=36611} -\end_inset +\end_inset -\newline +\newline Description: ipv6 Az IPv6 protokoll listaja Konfiguracios es adminisztracios kerdesek az IPv6-al kapcsolatban. \begin_inset LatexCommand \url[(Archivum)]{http://www.ipv6.fsz.bme.hu/mlists/ipv6/ipv6.html} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[student-ipv6 (India)]{http://groups.yahoo.com/group/student-ipv6} -\end_inset +\end_inset -\newline +\newline Description: This is the group for the Student Awareness group of IPv6 in India -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPV6-CNR@LISTSERV.CNR.IT (Italy)]{http://www.lsoft.com/scripts/wl.exe?SL1=IPV6-CNR&H=LISTSERV.CNR.IT} -\end_inset +\end_inset -\newline +\newline Description: Gruppo di interesse IPv6 del CNR -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-jp (Japan)]{http://www.tile.net/lists/showlists.php?list_id=14761} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6 (Japan)]{http://www.tile.net/lists/showlists.php?list_id=37305} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[sun-ipv6-users]{http://groups.yahoo.com/group/sun-ipv6-users} -\end_inset +\end_inset -\newline +\newline Description: Please report problems/suggestions regarding SUN Microsystems IPng implementation -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6-BITS]{http://groups.yahoo.com/group/IPv6-BITS} -\end_inset +\end_inset -\newline +\newline Description: This List will co-ordinate the working of Project Vertebrae. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[openbsd-ipv6]{http://www.tile.net/lists/showlists.php?list_id=23220} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6]{http://www.tile.net/lists/showlists.php?list_id=35203} -\end_inset +\end_inset -\newline +\newline Description: This mailing list is for technical discussion of the possibilities of ipv6/ipsec WRT OpenBSD. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[linux-bangalore-ipv6]{http://groups.yahoo.com/group/linux-bangalore-ipv6} -\end_inset +\end_inset -\newline +\newline Description: The IPv6 deployment list of the Bangalore Linux User Group -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[gab]{http://www.tile.net/lists/showlists.php?list_id=32034} -\end_inset +\end_inset -\newline +\newline Description: The intent is to discuss geographic addressing plans for IPv6. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[ipv6-bsd-user]{http://www.tile.net/lists/showlists.php?list_id=37430} -\end_inset +\end_inset -\newline +\newline Description: This mailing list is about the INRIA/IMAG IPv6 implementation. Cette liste de discussion est au sujet de l'implementation INRIA/IMAG IPv6. Elle est bilingue Francais/Anglais. The mailing list is biligual, French & English. If you wish to contact the implementors, try ipv6-bsd-core@imag.fr Si vous voulez contacter les implementeurs, essayez ipv6-bsd-core@imag.fr -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[gated-ipv6]{http://www.tile.net/lists/showlists.php?list_id=41375} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[packet-switching]{http://groups.yahoo.com/group/packet-switching} -\end_inset +\end_inset -\newline +\newline Description: This mailing list provides a forum for discussion of packet switching theory, technology, implementation and application in any relevant aspect including without limitation LAPB, X.25, SDLC, P802.1d, LLC, IP, IPv6, @@ -14994,889 +17664,1057 @@ Description: This mailing list provides a forum for discussion of packet protocols like SNMP, e-mail, network transparent window systems, protocol implementation, protocol verification, conformance testing and tools used in maintaining or developing packet switching systems. -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[mumbaiinternetgroup]{http://groups.yahoo.com/group/mumbaiinternetgroup} -\end_inset +\end_inset -\newline +\newline Description: This Forum will discuss current issues & developments in the field of Internet In Asia Pacific region.. This will cover discussion on..IPv4, IPv6, Multilingual DNS, Autonomous System Numbers, Internet Governence & Much more.... -\layout Itemize +\end_layout +\begin_layout Itemize de.comm.protocols.tcp-ip -\newline +\newline Description: Umstellung auf IPv6 -\newline +\newline Source: \begin_inset LatexCommand \url[Chartas der Newsgruppen in de.*]{http://www.faqs.org/faqs/de-newsgroups/chartas/index.html} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Google Group: \begin_inset LatexCommand \url[comp.protocols.tcp-ip]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=comp.protocols.tcp-ip} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Google Group: \begin_inset LatexCommand \url[linux.debian.maint.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=linux.debian.maint.ipv6} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Google Group: \begin_inset LatexCommand \url[microsoft.public.platformsdk.networking.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=microsoft.public.platformsdk.networking.ipv6} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Google Group: \begin_inset LatexCommand \url[fa.openbsd.ipv6]{http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF8&safe=off&group=fa.openbsd.ipv6} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlinetesttools} -\end_inset +\end_inset Online tools -\layout Subsection +\end_layout +\begin_layout Subsection Testing tools -\layout Itemize +\end_layout +\begin_layout Itemize finger, nslookup, ping, traceroute, whois: \begin_inset LatexCommand \url[UK IPv6 Resource Centre / The test page]{http://www.cs-ipv6.lancs.ac.uk/ipv6/testing/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize ping, traceroute, tracepath, 6bone registry, DNS: \begin_inset LatexCommand \url[JOIN / Testtools]{http://www.join.uni-muenster.de/lab/testtools.html} -\end_inset +\end_inset (German language only, but should be no problem for non German speakers) -\layout Itemize +\end_layout +\begin_layout Itemize traceroute6, whois: \begin_inset LatexCommand \url[IPng.nl]{http://www.ipng.nl/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize AAAA Lookup Checker \begin_inset LatexCommand \url[http://www.cnri.dit.ie/cgi-bin/check_aaaa.pl]{http://www.cnri.dit.ie/cgi-bin/check_aaaa.pl} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize Various tools: \begin_inset LatexCommand \url[IPv6tools]{http://www.ipv6tools.com/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 address analysis tool]{http://doc.tavian.com/ipv6util/index.htm} -\end_inset +\end_inset (something similar to ipv6calc's information option) -\layout Subsection +\end_layout +\begin_layout Subsection Information retrievement -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[6BONE Registry]{http://www.kessens.com/~david/6bone/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[List of worldwide all IPv6-aggregated IP-Blocks]{http://www.ripe.net/ripencc/mem-services/registration/ipv6/ipv6allocs.html} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection IPv6 Looking Glasses -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Looking Glass at SURRIEL]{http://linux.uninet.edu/lg/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DRENv6 Looking Glass]{http://www.v6.dren.net/lg/} -\end_inset +\end_inset -\layout Subsection +\end_layout +\begin_layout Subsection Helper applications -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Prefix Calculator]{http://www.tdoi.org/prefcalc.php} -\end_inset +\end_inset by \begin_inset LatexCommand \url[TDOI]{http://www.tdoi.org/} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[DNS record checker]{http://www.maths.tcd.ie/cgi-bin/check_dns.pl} -\end_inset +\end_inset -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-trainingsandseminars} -\end_inset +\end_inset Trainings, Seminars -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[IPv6 Training and Workshop]{http://www.aerasec.de/workshops/ipv6.html} -\end_inset +\end_inset , AERAsec, Germany (German language only at this time) -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Migrating to IPv6]{http://www.seminarinformation.com/wconnect/wc.dll?sis~details0~194045} -\end_inset +\end_inset , Learning Tree International -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[CIW Internetworking Professional Training CBT CD]{http://www.e-trainonline.com/html/ciw_internetworking_profession.html#IPv6} -\end_inset +\end_inset -\layout Itemize - +\end_layout +\begin_layout Itemize \begin_inset LatexCommand \url[Training Pages]{http://www.trainingpages.net/x/category.html?kw=125} -\end_inset +\end_inset , U.K. - Search for IPv6 (13 Courses, 22.12.2002) -\layout Standard +\end_layout +\begin_layout Standard Something missing? Suggestions are welcome! -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{information-onlinediscovery} -\end_inset +\end_inset 'The Online Discovery' ... -\layout Standard - +\end_layout +\begin_layout Standard \begin_inset LatexCommand \url[IPv6: Addressing The Needs Of the Future]{http://www.amazon.com/exec/obidos/tg/detail/-/B00006334Y/copernicshopper/103-1420916-1341420} -\end_inset +\end_inset [DOWNLOAD: PDF] -\newline +\newline by Yankee Group (Author) -\newline +\newline List Price: $595.00 -\newline -Edition: e-book (Acrobat Reader) -\newline +\newline +Edition: e-book + (Acrobat Reader) +\newline Pages: 3 (three) -\newline -Publisher: MarketResearch.com; ISBN B00006334Y; (November 1, 2001) -\newline +\newline +Publisher: MarketResearch.com; ISBN B00006334Y; + (November 1, 2001) +\newline -\layout Standard +\end_layout +\begin_layout Standard ;-) The number of copies would be interesting... -\newline +\newline -\layout Chapter +\end_layout +\begin_layout Chapter Revision history / Credits / The End -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{revision-history} -\end_inset +\end_inset Revision history -\layout Standard +\end_layout +\begin_layout Standard Versions x.y are published on the Internet. -\layout Standard +\end_layout +\begin_layout Standard Versions x.y.z are work-in-progress and published as LyX and SGML file on CVS. Because Deep Space 6 mirrors these SGML files and generate independend from TLDP public versions, this versions will show up there and also on its mirrors. -\layout Subsection +\end_layout +\begin_layout Subsection Releases 0.x -\layout Description +\end_layout +\begin_layout Description +0.49.1 2006-06-17/PB: major update of mobility section (contributed by Benjamin + Thery) +\end_layout + +\begin_layout Description 0.49 2005-10-03/PB: add configuration hints for DHCPv6, major broken URL cleanup (credits to Necdet Yucel) -\layout Description +\end_layout +\begin_layout Description 0.48.1 2005-01-15/PB: minor fixes -\layout Description +\end_layout +\begin_layout Description 0.48 2005-01-11/PB: grammar check and minor review of IPv6 IPsec section -\layout Description +\end_layout +\begin_layout Description 0.47.1 2005-01-01/PB: add information and examples about IPv6 IPsec, add some URLs -\layout Description +\end_layout +\begin_layout Description 0.47 2004-08-30/PB: add some notes about proftpd, vsftpd and other daemons, add some URLs, minor fixes, update status of Spanish translation -\layout Description +\end_layout +\begin_layout Description 0.46.4 2004-07-19/PB: minor fixes -\layout Description +\end_layout +\begin_layout Description 0.46.3 2004-06-23/PB: add note about started Greek translation, replace Taiwanese with Chinese for related translation -\layout Description +\end_layout +\begin_layout Description 0.46.2 2004-05-22/PB: minor fixes -\layout Description +\end_layout +\begin_layout Description 0.46.1 2004-04-18/PB: minor fixes -\layout Description +\end_layout +\begin_layout Description 0.46 2004-03-04/PB: announce Italian translation, add information about DHCPv6, minor updates -\layout Description +\end_layout +\begin_layout Description 0.45.1 2004-01-12/PB: add note about the official example address space -\layout Description +\end_layout +\begin_layout Description 0.45 2004-01-11/PB: minor fixes, add/fix some URLs, some extensions -\layout Description +\end_layout +\begin_layout Description 0.44.2 2003-10-30/PB: fix some copy&paste text bugs -\layout Description +\end_layout +\begin_layout Description 0.44.1 2003-10-19/PB: add note about start of Italian translation -\layout Description +\end_layout +\begin_layout Description 0.44 2003-08-15/PB: fix URLs, add hint on tcp_wrappers (about broken notation in some versions) and Apache2 -\layout Description +\end_layout +\begin_layout Description 0.43.4 2003-07-26/PB: fix URL, add archive URL for maillist users at ipv6.org, add some ds6 URLs -\layout Description +\end_layout +\begin_layout Description 0.43.3 2003-06-19/PB: fix typos -\layout Description +\end_layout +\begin_layout Description 0.43.2 2003-06-11/PB: fix URL -\layout Description +\end_layout +\begin_layout Description 0.43.1 2003-06-07/PB: fix some URLs, fix credits, add some notes at IPsec -\layout Description +\end_layout +\begin_layout Description 0.43 2003-06-05/PB: add some notes about configuration in SuSE Linux, add URL of French translation -\layout Description +\end_layout +\begin_layout Description 0.42 2003-05-09/PB: minor fixes, announce French translation -\layout Description +\end_layout +\begin_layout Description 0.41.4 2003-05-02/PB: Remove a broken URL, update some others. -\layout Description +\end_layout +\begin_layout Description 0.41.3 2003-04-23/PB: Minor fixes, remove a broken URL, fix URL to Taiwanese translation -\layout Description +\end_layout +\begin_layout Description 0.41.2 2003-04-13/PB: Fix some typos, add a note about a French translation is in progress -\layout Description +\end_layout +\begin_layout Description 0.41.1 2003-03-31/PB: Remove a broken URL, fix another -\layout Description +\end_layout +\begin_layout Description 0.41 2003-03-22/PB: Add URL of German translation -\layout Description +\end_layout +\begin_layout Description 0.40.2 2003-02-27/PB: Fix a misaddressed URL -\layout Description +\end_layout +\begin_layout Description 0.40.1 2003-02-12/PB: Add Debian-Linux-Configuration, add a minor note on translations -\layout Description +\end_layout +\begin_layout Description 0.40 2003-02-10/PB: Announcing available German version -\layout Description +\end_layout +\begin_layout Description 0.39.2 2003-02-10/GK: Minor syntax and spelling fixes -\layout Description +\end_layout +\begin_layout Description 0.39.1 2003-01-09/PB: fix an URL (draft adopted to an RFC) -\layout Description +\end_layout +\begin_layout Description 0.39 2003-01-13/PB: fix a bug (forgotten 'link \begin_inset Quotes srd -\end_inset +\end_inset on \begin_inset Quotes sld -\end_inset +\end_inset ip link set \begin_inset Quotes srd -\end_inset +\end_inset (credits to Yaniv Kaul) -\layout Description +\end_layout +\begin_layout Description 0.38.1 2003-01-09/PB: a minor fix -\layout Description +\end_layout +\begin_layout Description 0.38 2003-01-06/PB: minor fixes -\layout Description +\end_layout +\begin_layout Description 0.37.1 2003-01-05/PB: minor updates -\layout Description +\end_layout +\begin_layout Description 0.37 2002-12-31/GK: 270 new links added (searched in 1232 SearchEngines) in existing and 53 new (sub)sections -\layout Description +\end_layout +\begin_layout Description 0.36.1 2002-12-20/PB: Minor fixes -\layout Description +\end_layout +\begin_layout Description 0.36 2002-12-16/PB: Check of and fix broken links (credits to Georg Käfer), some spelling fixes -\layout Description +\end_layout +\begin_layout Description 0.35 2002-12-11/PB: Some fixes and extensions -\layout Description +\end_layout +\begin_layout Description 0.34.1 2002-11-25/PB: Some fixes (e.g. broken linuxdoc URLs) -\layout Description +\end_layout +\begin_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 -\end_inset +\end_inset used terms \begin_inset Quotes srd -\end_inset +\end_inset and add two German books -\layout Description +\end_layout +\begin_layout Description 0.33 2002-11-18/PB: Fix broken RFC-URLs, add parameter ttl on 6to4 tunnel setup example -\layout Description +\end_layout +\begin_layout Description 0.32 2002-11-03/PB: Add information about Taiwanese translation -\layout Description +\end_layout +\begin_layout Description 0.31.1 2002-10-06/PB: Add another maillist -\layout Description +\end_layout +\begin_layout Description 0.31 2002-09-29/PB: Extend information in proc-filesystem entries -\layout Description +\end_layout +\begin_layout Description 0.30 2002-09-27/PB: Add some maillists -\layout Description +\end_layout +\begin_layout Description 0.29 2002-09-18/PB: Update statement about nmap (triggered by Fyodor) -\layout Description +\end_layout +\begin_layout Description 0.28.1 2002-09-16/PB: Add note about ping6 to multicast addresses, add some labels -\layout Description +\end_layout +\begin_layout Description 0.28 2002-08-17/PB: Fix broken LDP/CVS links, add info about Polish translation, add URL of the IPv6 Address Oracle -\layout Description +\end_layout +\begin_layout Description 0.27 2002-08-10/PB: Some minor updates -\layout Description +\end_layout +\begin_layout Description 0.26.2 2002-07-15/PB: Add information neighbor discovery, split of firewalling (got some updates) and security into extra chapters -\layout Description +\end_layout +\begin_layout Description 0.26.1 2002-07-13/PB: Update nmap/IPv6 information -\layout Description +\end_layout +\begin_layout Description 0.26 2002-07-13/PB: Fill /proc-filesystem chapter, update DNS information about depricated A6/DNAME, change P-t-P tunnel setup to use of \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset only -\layout Description +\end_layout +\begin_layout Description 0.25.2 2002-07-11/PB: Minor spelling fixes -\layout Description +\end_layout +\begin_layout Description 0.25.1 2002-06-23/PB: Minor spelling and other fixes -\layout Description +\end_layout +\begin_layout Description 0.25 2002-05-16/PB: Cosmetic fix for 2\i \^{ } 128, thanks to José Abílio Oliveira Matos for help with LyX -\layout Description +\end_layout +\begin_layout Description 0.24 2002-05-02/PB: Add entries in URL list, minor spelling fixes -\layout Description +\end_layout +\begin_layout Description 0.23 2002-03-27/PB: Add entries in URL list and at maillists, add a label and minor information about IPv6 on RHL -\layout Description +\end_layout +\begin_layout Description 0.22 2002-03-04/PB: Add info about 6to4 support in kernel series 2.2.x and add an entry in URL list and at maillists -\layout Description +\end_layout +\begin_layout Description 0.21 2002-02-26/PB: Migrate next grammar checks submitted by John Ronan -\layout Description +\end_layout +\begin_layout Description 0.20.4 2002-02-21/PB: Migrate more grammar checks submitted by John Ronan, add some additional hints at DNS section -\layout Description +\end_layout +\begin_layout Description 0.20.3 2002-02-12/PB: Migrate a minor grammar check patch submitted by John Ronan -\layout Description +\end_layout +\begin_layout Description 0.20.2 2002-02-05/PB: Add mipl to maillist table -\layout Description +\end_layout +\begin_layout Description 0.20.1 2002-01-31/PB: Add a hint how to generate 6to4 addresses -\layout Description +\end_layout +\begin_layout Description 0.20 2002-01-30/PB: Add a hint about default route problem, some minor updates -\layout Description +\end_layout +\begin_layout Description 0.19.2 2002-01-29/PB: Add many new URLs -\layout Description +\end_layout +\begin_layout Description 0.19.1 2002-01-27/PB: Add some forgotten URLs -\layout Description +\end_layout +\begin_layout Description 0.19 2002-01-25/PB: Add two German books, fix quote entinities in exported SGML code -\layout Description +\end_layout +\begin_layout Description 0.18.2 2002-01-23/PB: Add a FAQ on the program chapter -\layout Description +\end_layout +\begin_layout Description 0.18.1 2002-01-23/PB: Move \begin_inset Quotes sld -\end_inset +\end_inset the end \begin_inset Quotes srd -\end_inset +\end_inset to the end, add USAGI to maillists -\layout Description +\end_layout +\begin_layout Description 0.18 2002-01-22/PB: Fix bugs in explanation of multicast address types -\layout Description +\end_layout +\begin_layout Description 0.17.2 2002-01-22/PB: Cosmetic fix double existing text in history (at 0.16), move all credits to the end of the document -\layout Description +\end_layout +\begin_layout Description 0.17.1 2002-01-20/PB: Add a reference, fix URL text in online-test-tools -\layout Description +\end_layout +\begin_layout Description 0.17 2002-01-19/PB: Add some forgotten information and URLs about global IPv6 addresses -\layout Description +\end_layout +\begin_layout Description 0.16 2002-01-19/PB: Minor fixes, remove \begin_inset Quotes sld -\end_inset +\end_inset bold \begin_inset Quotes srd -\end_inset +\end_inset and \begin_inset Quotes sld -\end_inset +\end_inset emphasize \begin_inset Quotes srd -\end_inset +\end_inset formats on code lines, fix \begin_inset Quotes sld -\end_inset +\end_inset too long unwrapped code lines \begin_inset Quotes srd -\end_inset +\end_inset using selfmade utility, extend list of URLs. -\layout Description +\end_layout +\begin_layout Description 0.15 2002-01-15/PB: Fix bug in addresstype/anycast, move content related credits to end of document -\layout Description +\end_layout +\begin_layout Description 0.14 2002-01-14/PB: Minor review at all, new chapter \begin_inset Quotes sld -\end_inset +\end_inset debugging \begin_inset Quotes srd -\end_inset +\end_inset , review \begin_inset Quotes sld -\end_inset +\end_inset addresses \begin_inset Quotes srd -\end_inset +\end_inset , 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 -\layout Description +\end_layout +\begin_layout Description 0.13 2002-01-05/PB: Add example BIND9/host, move revision history to end of document, minor extensions -\layout Description +\end_layout +\begin_layout Description 0.12 2002-01-03/PB: Merge review of David Ranch -\layout Description +\end_layout +\begin_layout Description 0.11 2002-01-02/PB: Spell checking and merge review of Pekka Savola -\layout Description +\end_layout +\begin_layout Description 0.10 2002-01-02/PB: First public release of chapter 1 -\layout Section - +\end_layout +\begin_layout Section \begin_inset LatexCommand \label{credits} -\end_inset +\end_inset Credits -\layout Standard +\end_layout +\begin_layout Standard The quickest way to be added to this nice list is to send bug fixes, corrections , and/or updates to me ;-). -\layout Standard +\end_layout +\begin_layout Standard If you want to do a major review, you can use the native LyX file (see \begin_inset LatexCommand \ref[original source]{general-original-source} -\end_inset +\end_inset ) and send diffs against it, because diffs against SGML don't help too much. -\layout Subsection - +\end_layout +\begin_layout Subsection \begin_inset LatexCommand \label{major-credits} -\end_inset +\end_inset Major credits -\layout Itemize +\end_layout +\begin_layout Itemize David Ranch : For encouraging me to write this HOWTO, his editorial comments on the first few revisions, and his contributions to various IPv6 testing results on my IPv6 web site. Also for his major reviews and suggestions. -\layout Itemize +\end_layout +\begin_layout Itemize Pekka Savola : For major reviews, input and suggestion s. -\layout Itemize +\end_layout +\begin_layout Itemize Martin F. Krafft : For grammar checks and general reviewing of the document. -\layout Itemize +\end_layout +\begin_layout Itemize John Ronan : For grammar checks. -\layout Itemize +\end_layout +\begin_layout Itemize Georg Käfer : For detection of no proper PDF creation (fixed now by LDP maintainer Greg Ferguson), input for German books, big list of URLs, checking all URLs, many more suggestions, corrections and contributions, and the German translation -\layout Itemize +\end_layout +\begin_layout Itemize Michel Boucey : Finding typos and some broken URLs, contribute some suggestions and URLs, and the French translation -\layout Itemize +\end_layout +\begin_layout Itemize Michele Ferritto : Finding bugs and the Italian translation -\layout Itemize +\end_layout +\begin_layout Itemize Daniel Roesen : For grammar checks -\layout Subsection +\end_layout +\begin_layout Itemize +Benjamin Thery : For contribution of + updated mobility section +\end_layout + +\begin_layout Subsection Other credits -\layout Subsubsection +\end_layout +\begin_layout Subsubsection Document technique related -\layout Standard +\end_layout +\begin_layout Standard Writing a LDP HOWTO as a newbie (in LyX and exporting this to DocBook to conform to SGML) isn't as easy as some people say. There are some strange pitfalls... Nevertheless, thanks to: -\layout Itemize +\end_layout +\begin_layout Itemize Authors of the \begin_inset LatexCommand \url[LDP Author Guide]{http://www.tldp.org/LDP/LDP-Author-Guide/} -\end_inset +\end_inset -\layout Itemize +\end_layout +\begin_layout Itemize B. Guillon: For his \begin_inset LatexCommand \url[DocBook with LyX HOWTO]{http://perso.libertysurf.fr/bgu/doc/db4lyx/} -\end_inset +\end_inset -\layout Subsubsection - +\end_layout +\begin_layout Subsubsection \begin_inset LatexCommand \label{content-related-credits} -\end_inset +\end_inset Content related credits -\layout Standard +\end_layout +\begin_layout Standard Credits for fixes and hints are listed here, will grow sure in the future -\layout Itemize +\end_layout +\begin_layout Itemize S .P. Meenakshi : For a hint using a \begin_inset Quotes sld -\end_inset +\end_inset send mail \begin_inset Quotes srd -\end_inset +\end_inset shell program on tcp_wrapper/hosts.deny -\layout Itemize +\end_layout +\begin_layout Itemize Frank Dinies : For a bugfix on IPv6 address explanati on -\layout Itemize +\end_layout +\begin_layout Itemize John Freed : For finding a bug in IPv6 multicast address explanation -\layout Itemize +\end_layout +\begin_layout Itemize Craig Rodrigues : For suggestion about RHL IPv6 setup -\layout Itemize +\end_layout +\begin_layout Itemize Fyodor : Note me about outdated nmap information -\layout Itemize +\end_layout +\begin_layout Itemize Mauro Tortonesi : For some suggestions -\layout Itemize +\end_layout +\begin_layout Itemize Tom Goodale : For some suggestions -\layout Itemize +\end_layout +\begin_layout Itemize Martin Luemkemann : For a suggestion -\layout Itemize +\end_layout +\begin_layout Itemize Jean-Marc V. Liotier : Finding a bug -\layout Itemize +\end_layout +\begin_layout Itemize Yaniv Kaul : Finding a bug -\layout Itemize +\end_layout +\begin_layout Itemize Arnout Engelen : For sending note about a draft was adopted to RFC now -\layout Itemize +\end_layout +\begin_layout Itemize Stephane Bortzmeyer : Contributing persistent configuration on Debian -\layout Itemize +\end_layout +\begin_layout Itemize lithis von saturnsys : Reporting a misaddressed URL -\layout Itemize +\end_layout +\begin_layout Itemize Guy Hulbert : Send a note that RFC1924 is probably an April fool's joke -\layout Itemize +\end_layout +\begin_layout Itemize Tero Pelander : Reporting a broken URL -\layout Itemize +\end_layout +\begin_layout Itemize Walter Jontofsohn : Hints for SuSE Linux 8.0/8.1 -\layout Itemize +\end_layout +\begin_layout Itemize Benjamin Hofstetter : Reporting a mispointing URL -\layout Itemize +\end_layout +\begin_layout Itemize J.P. Larocque : Reporting archive URL for maillist users at ipv6 dot org -\layout Itemize +\end_layout +\begin_layout Itemize Jorrit Kronjee : Reporting broken URLs -\layout Itemize +\end_layout +\begin_layout Itemize Colm MacCarthaigh : Hint for sendfile issue on Apache2 -\layout Itemize +\end_layout +\begin_layout Itemize Tiago Camilo : Contribute some URLs about Mobile IPv6 -\layout Itemize +\end_layout +\begin_layout Itemize Harald Geiger: Reporting a bug in how described the bit counting of the universal/global bit -\layout Itemize +\end_layout +\begin_layout Itemize Bjoern Jacke : Triggered me to fix some outdated informati on on xinetd -\layout Itemize +\end_layout +\begin_layout Itemize Christoph Egger : Sending note about \begin_inset Quotes sld -\end_inset +\end_inset ip \begin_inset Quotes srd -\end_inset +\end_inset has problems with IPv4-compatible addresses on SuSE Linux 9.0 and trigger to add a hint on 6to4-radvd example -\layout Itemize +\end_layout +\begin_layout Itemize David Lee Haw Ling : Sending information about a tunnel broker -\layout Itemize +\end_layout +\begin_layout Itemize Michael H. Warfield : Sending note about suffix for 6to4 routers -\layout Itemize +\end_layout +\begin_layout Itemize Tomasz Mrugalski : Sending updates for DHCPv6 section -\layout Itemize +\end_layout +\begin_layout Itemize Jan Minar : Reporting minor bugs -\layout Itemize +\end_layout +\begin_layout Itemize Kalin KOZHUHAROV : Fixing a not so well explanation -\layout Itemize +\end_layout +\begin_layout Itemize Roel van Dijk : Reporting broken URLs -\layout Itemize +\end_layout +\begin_layout Itemize Catalin Muresan : Reporting minor bugs -\layout Itemize +\end_layout +\begin_layout Itemize Dennis van Dok : Reporting minor bugs -\layout Itemize +\end_layout +\begin_layout Itemize Necdet Yucel : Reporting broken URLs -\layout Section +\end_layout +\begin_layout Section The End -\layout Standard +\end_layout +\begin_layout Standard Thanks for reading. Hope it helps! -\layout Standard +\end_layout +\begin_layout Standard If you have any questions, subscribe to proper \begin_inset LatexCommand \ref[maillist]{information-maillists} -\end_inset +\end_inset and describe your problem providing as much as information as possible. -\the_end +\end_layout + +\end_body +\end_document