Dynamic routing IPv6

From Ilianko
Revision as of 10:46, 10 December 2013 by Anko (talk | contribs) (→‎IPv6)

IPv6

Ipv6.png

  • 48 бита Routing Prefix:
    • 23 бита Registry
    • 9 бита ISP Prefix
    • 16 бита Site Prefix
  • 16 бита Subnet Prefix
  • 64 бита Interface ID


Три вида адреси:

  • Unicast: Идентификатор на интерфейс. Пакет изпратен до unicast адрес се изпраща до интерфейса настроен с този адрес. Примерни адреси:
    • FEDC:BA98:7654:3210:FEDC:BA98:7654:3210
    • 1080:0:0:0:8:800:200C:417A ( 1080::800:200C:417A)
  • Anycast: Идентификатор на група интерфейси (най-често принадлежащи на различни комуникационни точки (нодове). Пакет изпратен към anycast адрес се доставя на един от интерфейсите от тази група ("най-близкия" според метриката рутиращия протокол)
  • Multicast: Идентификатор на група интерфейси (най-често принадлежащи на различни комуникационни точки (нодове). Пакет изпратен до мултикаст адрес се доставя до всеки интерфейс, който се идентифицира с този адрес.

Не съществуват broadcast адреси. Тяхната функция се замества от multicast адресите.

Мрежа на опитната постановка

Special addresses

There are a number of addresses with special meaning in IPv6:<ref name=rfc5156>RFC 5156, Special-Use IPv6 Addresses, M. Blanchett (April 2008)</ref>

Unicast Addresses

Unspecified address

  •  ::/128 — The address with all zero bits is called the unspecified address (corresponding to 0.0.0.0/32 in IPv4).
    This address must never be assigned to an interface and is to be used only in software before the application has learned its host's source address appropriate for a pending connection. Routers must not forward packets with the unspecified address.
    Applications may be listening on one or more specific interfaces for incoming connections, which are shown in listings of active internet connections by a specific IP address (and a port number, separated by a colon). When the unspecified address is shown it means that an application is listening for incoming connections on all available interfaces.

Default route

  •  ::/0 — The default unicast route address (corresponding to 0.0.0.0/0 in IPv4).

Local addresses

  •  ::1/128 — The loopback address is a unicast localhost address. If an application in a host sends packets to this address, the IPv6 stack will loop these packets back on the same virtual interface (corresponding to 127.0.0.1/8 in IPv4).
  • fe80::/10 — Addresses in the link-local prefix are only valid and unique on a single link. Within this prefix only one subnet is allocated (54 zero bits), yielding an effective format of fe80::/64. The least significant 64 bits are usually chosen as the interface hardware address constructed in modified EUI-64 format. A link-local address is required on every IPv6-enabled interface—in other words, applications may rely on the existence of a link-local address even when there is no IPv6 routing. These addresses are comparable to the auto-configuration addresses 169.254.0.0/16 of IPv4.

Unique local addresses

Template:Main

  • fc00::/7 — Unique local addresses (ULAs) are intended for local communication. They are routable only within a set of cooperating sites.<ref name=rfc1918>RFC 1918, Address Allocation for Private Internets, Y. Rekhter, B. Moskowitz, D. Karrenberg, G.J. De Groot, E. Lear (February 1996)</ref> The block is split into two halves, the upper half (fd00::/8) is used for "probabilistically unique" addresses in which a 40-bit pseudorandom number is used to obtain a /48 allocation. This means that there is only a small chance that two sites that wish to merge or communicate with each other will have conflicting addresses. No allocation method for the lower half of the block is currently defined.

Transition from IPv4

Template:Main

  •  ::ffff:0:0/96 — This prefix is designated as an IPv4-mapped IPv6 address. With a few exceptions, this address type allows the transparent use of the Transport Layer protocols over IPv4 through the IPv6 networking application programming interface. Server applications only need to open a single listening socket to handle connections from clients using IPv6 or IPv4 protocols. IPv6 clients will be handled natively by default, and IPv4 clients appear as IPv6 clients at their IPv4-mapped IPv6 address. Transmission is handled similarly; established sockets may be used to transmit IPv4 or IPv6 datagram, based on the binding to an IPv6 address, or an IPv4-mapped address. (See also Transition mechanisms.)
  •  ::ffff:0:0:0/96 — A prefix used for IPv4-translated addresses which are used by the Stateless IP/ICMP Translation (SIIT) protocol.
  • 64:ff9b::/96 — The "Well-Known" Prefix. Addresses with this prefix are used for automatic IPv4/IPv6 translation.<ref name=rfc6052>RFC 6052, "IPv6 Addressing of IPv4/IPv6 Translators", C. Bao, C. Huitema, M. Bagnulo, M. Boucadair, X. Li, (October 2010)</ref>

Template:Main

  • 2002::/16 — This prefix is used for 6to4 addressing. Here, an address from the IPv4 network 192.88.99.0/24 is also used.

Special-purpose addresses

Template:Main

IANA has reserved a so-called 'Sub-TLA ID' address block for special assignments<ref name=rfc4773>RFC 4773, Administration of the IANA Special Purpose IPv6 Address Block, G. Huston (December 2006)</ref><ref name=rfc2928>RFC 2928, Initial IPv6 Sub-TLA ID Assignments, R. Hinden, S. Deering, R. Fink, T. Hain (September 2000) The Internet Society</ref> which consists of 64 network prefixes in the range 2001:0000::/29 through 2001:01f8::/29. Three assignments from this block have been made:
  • 2001::/32 — Used for Teredo tunneling (which also falls into the category of IPv6 transition mechanisms).
  • 2001:2::/48 — Assigned to the Benchmarking Methodology Working Group (BMWG)<ref name=rfc5180>RFC 5180, IPv6 Benchmarking Methodology for Network Interconnect Devices, C. Popoviciu, A. Hamza, G. Van de Velde, D. Dugatkin (May 2008)</ref> for benchmarking IPv6 (corresponding to 198.18.0.0/15 for benchmarking IPv4).
  • 2001:10::/28 — ORCHID (Overlay Routable Cryptographic Hash Identifiers).<ref name=rfc4843>RFC 4843 (experimental), An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID), P. Nikander, J. Laganier, F. Dupont (April 2007)</ref> These are non-routed IPv6 addresses used for Cryptographic Hash Identifiers.

Documentation

  • 2001:db8::/32 — This prefix is used in documentation.<ref name=rfc3849>RFC 3849, IPv6 Address Prefix Reserved for Documentation, G. Huston, A. Lord, P. Smith (July 2004)</ref> The addresses should be used anywhere an example IPv6 address is given or model networking scenarios are described (corresponding to 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24 in IPv4.)<ref name=rfc5737>RFC 5737, IPv4 Address Blocks Reserved for Documentation, J. Arkko, M. Cotton, L. Vegoda (January 2010), ISSN: 2070-1721</ref>

Deprecated and obsolete addresses

Template:Further2

Multicast addresses

The multicast addresses ff00::0/8 are reserved<ref name=rfc4291 /> and should not be assigned to any multicast group. The Internet Assigned Numbers Authority (IANA) manages address reservations.<ref>IANA Internet Protocol Version 6 Multicast Addresses.</ref>

Some common IPv6 multicast addresses are the following:

Address Description Available Scopes
ff0X::1 All nodes address, identify the group of all IPv6 nodes Available in scope 1 (interface-local) and 2 (link-local):
  • ff01::1 → All nodes in the interface-local
  • ff02::1 → All nodes in the link-local
ff0X::2 All routers Available in scope 1 (interface-local), 2 (link-local) and 5 (site-local):
  • ff01::2 → All routers in the interface-local
  • ff02::2 → All routers in the link-local
  • ff05::2 → All routers in the site-local
ff02::5 OSPFIGP 2 (link-local)
ff02::6 OSPFIGP Designated Routers 2 (link-local)
ff02::9 RIP Routers 2 (link-local)
ff02::a EIGRP Routers 2 (link-local)
ff02::d All PIM Routers 2 (link-local)
ff02::1a All RPL Routers 2 (link-local)
ff0X::fb mDNSv6 Available in all scopes
ff0X::101 All Network Time Protocol (NTP) servers Available in all scopes
ff02::1:1 Link Name 2 (link-local)
ff02::1:2 All-dhcp-agents 2 (link-local)
ff02::1:3 Link-local Multicast Name Resolution 2 (link-local)
ff05::1:3 All-dhcp-servers 5 (site-local)
ff02::1:ff00:0/104 Solicited-node multicast address. See below 2 (link-local)
ff02::2:ff00:0/104 Node Information Queries 2 (link-local)

Solicited-node multicast address

The least significant 24 bits of the solicited-node multicast address group ID are filled with the least significant 24 bits of the interface's unicast or anycast address. These addresses allow link-layer address resolution via Neighbor Discovery Protocol (NDP) on the link without disturbing all nodes on the local network. A host is required to join a Solicited-Node multicast group for each of its configured unicast or anycast addresses.


IPv6 за локална мрежа

Задаляне на адресно пространство за локална мрежа ( Unique Local IPv6 Unicast Addresses - IPv4 - 192.168.0.0). 

| 7 bits |1|  40 bits   |  16 bits  |          64 bits           |
+--------+-+------------+-----------+----------------------------+
| Prefix |L| Global ID  | Subnet ID |        Interface ID        |
+--------+-+------------+-----------+----------------------------+
  • Prefix - FC00 :: / 7 префикс за идентифициране на локални IPv6 Unicast

aдреси;

  • Global ID - 40-битов глобален идентификатор, използван за създаване на

уникален префикс;

  • Subnet ID - 16-битов идентификатор на подмрежата;
  • Interface ID- 64-битов интерфейс ID.


RFC 4193 - Unique Local IPv6 Unicast Addresses

Избор на GlobalID

Генератор на псевдослучаен адрес - http://www.simpledns.com/private-ipv6.aspx


=== Избор на Заявка на адрес:

=

Retrieved from "https://ilianko.com/index.php?title=Dynamic_routing_IPv6&oldid=4871"