zeropage.de | IT | IPv6

zeropage is © by the L13-Crew, all part of TUI-NET

IPv6 | misc

alles unsortiert, quasi ...

Vorteile

vergrösserter Adressraum - 128bit (gegenüber 32bit bei IPv4) -> über eine halbe Quadrillionen (ne 5 mit 23 Nullen - wer hätte es gedacht? ;-) Adressen pro m² Erde
einfachere Autokonfiguration
bestimmte Features, die bei IPv4 optional eingeführt wurden, sind jetzt mandatory

Nachteile

Adressen nicht mehr "human remindable"

supported OS

N/A means: not included and no third-party implementation found yet
MSRIPv6 means: there is an implementation from MS-Research, but this is incomplete (virtually no support for mobile IPv6, IPsec and such IPv6-related features)
be aware: the Microsoft Research IPv6 implementation (MSRIPv6) differs from the releases in WinXP, W inServer2003 and newer products

Windows 3.x: N/A (maybe an implementation by Trumpet)
Windows 9x: N/A (maybe an implementation by Trumpet)
Windows ME: not checked yet
Windows NT 3.5x: N/A
Windows NT 4.0: MSRIPv6
Windows 2000: MSRIPv6
Windows XP w/o SP: not checked yet
Windows XP w/ SP1: included
Windows Server 2003: included
Linux previous to 2.4: N/A
Linux 2.4: included (backported)
Linux 2.6: included
MacOS previous to Version X: not checked yet
BSD (all variants): included
AmigaOS: not checked yet
Solaris: available
...

misc

URLs im Browser: z.B. http://[2001:...:1](see also: RFC2732).

IPv6 == IP protocol 41
auch "IP Next Generation" genannt (IPNG)
etwa 75% des IPv4-Adressraums wurden den USA zugeteilt
radvd
.int vs .arpa
"End2end secure always-on connection"
no more NAT, no more broadcasts ...
cryptographically generated addresses
IMS: IP Multimedia Subsystem
IPv6 in cellular networks?
SAC: stateless (address) auto-configuration
dynamisches routing (inkl. RIPng): Zebra, Quagga
SIT: Simple Internet Transition
IPv6 in VMware?
shared secrets - TSIG (transaction signature)
Windows: CLI-tools: ipv6, netsh

unsorted MAC -> Interface-ID:
1. MAC == MAC + 02:00:00:00:00:00 (The Universal/Local bit, the second low-order bit of the first byte of the MAC address, is complemented. If it is a 1, it is turned to 0, and if it is a 0, it is turned to 1.) 2. I/F-ID == uuvv:wwFF:FExx:yyzz
3. link-local-address == FE80::uuvv:wwFF:FExx:yyzz
example: 00:50:DA:51:AE:06 -> fe80::250:daff:fe51:ae06

Ne das ist das alte "nibble format" das so funktionierte wie Reverse DNS bei IPv4 und es sollte das einzigste sein was unter "*.ip6.int." unterstützt wird. Unter ARPA sollte imho das alte "nibble format" und das neue "Bitstring Format" funktionieren... Nur wie gesagt... es geht ned... achim Windows: - ipv6 install - ipv6 uninstall - bei Version ab ... (XP SP1?) direkt in Netzwerkeinstellungen "Internetverbindungsfreigabe" scheint das router advertisement für IPv6 zu aktivieren
Linux:
(echo 0 > /proc/sys/net/ipv6/conf/eth0/forwarding) echo 1 > /proc/sys/net/ipv6/conf/eth0/accept_ra IPv6 default gw loeschen (z.B. wenn keine Connection ins "Internet6": ip route delete ::/0 RA:

Client auto-config mit link-local-address (FE80::llll/10), mit duplicate address detection im lokalen Netz
Router sendet RA (Router Advertisements), enthält Prefix (pppp::/64) und default-gateway
Client bildet aus link-local-address und dem RA seine global gültige Adresse (pppp::llll)

deb http://ftp.uni-erlangen.de/pub/Linux/debian/ unstable main non-free contrib deb-src http://ftp.uni-erlangen.de/pub/Linux/debian/ unstable main non-free contrib 6to4: packets with the following characteristics should not be allowed as valid 6to4 packets, and some firewalling seems to be justified for them: unspecified v4 source/destination address: 0.0.0.0/8 loopback address in outer (v4) source/destination: 127.0.0.0/8 IPv4 multicast in source/destination: 224.0.0.0/4 limited broadcasts: 255.0.0.0/8 subnet broadcast address as source/destination: depends on your v4 setup Kernel: Networking options The IPv6 protocol:yes IPv6: enable EUI-64 token format:yes IPv6: disable provider based address: yes http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html?page=3 http://ezine.daemonnews.org/200101/6to4.html When pinging a link-local or site-local address, it is recommended to specify the scope-ID to make the destination address unambiguous. The notation to specify the scope-ID is address%scope-ID. For link-local addresses, the scope-ID is equal to the interface number as displayed in the ipv6 if command. For site-local addresses, the scope-ID is equal to the site number as displayed in the ipv6 if command. For example, to send Echo Request messages to Host B using scope-ID 4, use the following command: ping6 fe80::260:97ff:fe02:6ea5%4
TO-DO: eMails, News, IPv6-Verz., Papierkrams, summit, BigSister, Hauptseminar, ahzf's Dinge