Mikrotik Ipv6
Mikrotik Ipv6
Mikrotik Ipv6
Manual:IPv6 Overview
Applies to RouterOS: 3, v4
IPv6 overview
Internet Protocol version 6 (IPv6) is the new version of the Internet Protocol (IP). It was initially expected to replace
IPv4 in short enough time, but for now it seems that these two version will coexist in Internet in foreseeable future.
Nevertheless, IPv6 becomes more important, as the date of unallocated IPv4 address pool's exhaustion approaches.
The two main benefits of IPv6 over IPv4 are:
• much larger address space;
• support of stateless and statefull address autoconfiguration;
• built-in security;
• new header format (faster forwarding).
Supported programms
MikroTik IPv6 support at the moment (RouterOS 3.28/4.0beta4):
• static addressing and routing;
• router advertisement daemon (for address autoconfiguration);
• dynamic routing: BGP+, OSPFv3, and RIPng protocols;
• firewall (filter, mangle, address lists);
• queue tree;
• DNS name servers;
• 6in4 (SIT) tunnels;
• all PPP (Point-to-point protocols);
• telnet;
• ping;
• traceroute;
• web proxy;
• sniffer and fetch tools;
Features not yet supported:
• DHCPv6;
• IPSEC;
• SSH, FTP, API, Winbox, Webbox access;
• simple queues;
• automatic tunnel creation;
• policy routing;
• multicast routing;
• MPLS;
• torch, netwatch, bandwidth test and other tools;
Manual:IPv6 Overview 2
Addressing
IPv6 uses 16 bytes addresses compared to 4 byte addresses in IPv4. IPv6 address syntax and types are described in
RFC 4291.
Read more>>
Routing
For static routing, the basic principles of IPv6 are exactly the same as for IPv4. Read more >>
Warning: All dynamic routing protocols also require a valid Router ID to function. If the Router ID is not
configured manually, one of router's IPv4 addresses are used as the Router ID. If no IPv4 addresses are
present, the router ID selection process will fail. This means that dynamic routing will not work on a router
that has no IPv4 addresses, unless you configure the Router ID manually!
BGP
Because of it's design BGP naturally supports multiple address families, and migration to IPv6 is straightforward
here.
Example: configure iBGP between routers A and B, AS 65000, that will exchange IPv4 and IPv6 routes.
Router A:
[admin@A] > routing bgp peer add remote-address=10.0.0.134 remote-as=65000 address-families=ip,ipv6
Router B:
[admin@B] > routing bgp peer add remote-address=10.0.0.133 remote-as=65000 address-families=ip,ipv6
IPv6 addresses can also be used in peer configuration in remote-address and update-source fields - to make a BGP
connection over IPv6.
OSPF
Unlike to BGP, adding IPv6 support to OSPF required a lot of changes and resulted in a new, incompatible, version
of OSPF: protocol version 3. (For IPv4, OSPF version 2 is used). The new version is described in RFC 2740.
OSPFv3 uses the same fundamental mechanisms as OSPFv2 — LSAs, flooding, the SPF algorithm, etc. However, it
adds not only support to a new address family, but also some improvements to the protocol itself. The new version
avoids some potential problems and inefficiencies present in the operation of OSPFv2.
OSPFv3 configuration syntax largely remains the same as for OSPFv2. One mayor difference is that there is no
configuration for networks anymore, and interface configuration becomes mandatory, since OSPFv3 runs on link,
not IP subnet, basis.
Example:
Configure OSPF on router A:
RIP
Similarly to OSPF, a new version of RIP was required to add IPv6 support. The new version is called RIPng (RIP
new generation) and described in RFC 2080. Just like OSPFv3, RIPng runs on link, not IP subnet, basis - this means
that you need to configure interfaces, not IP networks, on which to run RIPng.
Example:
Configure RIP on router A:
Now you need to add a IPv6 address to the tunnel interface. The address should be in form "2002 + <IPv4 address
in hex> + <custom id>" . A bash script can be used to generate such IPv6 address for you:
atis@atis-desktop:~$ ipv4="1.2.3.4"; id="1"; printf "2002:%02x%02x:%02x%02x::$id\n" `echo $ipv4 | tr "." " "`
2002:0102:0304::1
Add route to global IPv6 Internet through the tunnel interface using the anycast IPv4 address:
Now try to ping some IPv6 host (e.g. ipv6.google.com, 2001:4860:a003::68) to check your IPv6 connectivity.
See also 6in4 [1] and 6to4 [2] in Wikipedia.
Manual:IPv6 Overview 5
To demonstrate that the dual stack is working, we connect to the web proxy at 10.0.0.131/fc00:1::1 using telnet,
issue "GET /" request, and observe generated error message.
Connecting via IPv4:
References
[1] http:/ / en. wikipedia. org/ wiki/ 6in4
[2] http:/ / en. wikipedia. org/ wiki/ 6to4
Article Sources and Contributors 6