1990512028, 1:58 |Pv6 tunneling over IPvé Configuration Search Q © IPv6 tunneling over IPv4 Configuration Since 1Pv4 and IPV6 are not compatible with each other, we need some migration strategies. One technique that we can use is tunneling. Basically, it means that we encapsulate IPv6 packets into IPv4 packets (or the other way around) so they can be routed. In this lesson, Il show you how to configure IPV6 static tunneling over an IPv4 network. There are two methods: * Manual tunnels * GRE (Generic Routing Encapsulation) tunnels Both tunnel types are very similar, with just minor differences. Both support IPV6 IGPs through the tunnel interface and forwarding of multicast traffic. The manual tunnels refer to RFC 4213, which defines how to encapsulate IPv6 packets in IPv4. GRE is a generic encapsulation type that rides on top of IPv4 and isn't only for IPv6. It can carry many different protocols and if you ever configured an IPSEC VPN with IGPs running through it you had to use GRE. 1, Configuration Let’s continue by looking at some examples and how to configure the static point-to-point IPv6 tunnels. htpsnetworklessons.comiscolece-routing-swtchinghhow-1o-conigure-ipv8-tunneling-over-ipvd sno1990512028, 1:58 |Pv6 tunneling over IPvé Configuration 1/128 LO: 821/ €:T00Z 2001:: This is the topology welll be using. Three routers are running IPv4. R1 and R3 also run IPv6, and we want connectivity between them without adding IPv6 support on R2. Let's configure all IPv4 and IPv6 addresses: Ri(config)#interface loopback @ Ri(config-if)#ipvé address 2601 R1(config-if)#exit Ri(config)#interface fastEthernet 0/2 Ri(config-if)#ip address 192.168.12.1 255.255.255.0 /128 R2(config)#interface fastEthernet 0/2 Ra(config-if)#ip address 192.168.12.2 255.255.255.0 R2(config-if)texit Ra(config)#interface fastEthernet 1/2 R2(config-if)#ip address 192.168.23.2 255.255.255.0 R3(config)#interface fastEthernet 0/2 R3(config-if)#ip address 192.168.23.3 255.255.255.0 R3(config-if)texit R3(config)#interface loopback @ R3(config-if)#ipvé address 2601 128 © Our next step is to create a tunnel interface between R1 and R3. They need to be able to reach each other through IPv4. Ill create a new loopback interface on R1 and R3, advertise them in EIGRP, and use these hps:inetworklessons.comiciscalecie-outing-switchingihow-to-conigu ipv6tunneling over pvt 2101990512028, 1:58 |Pv6 tunneling over IPvé Configuration a R1(config)#interface loopback 1 Ri(config-if)#ip address 1.1.1.1 255.255.255.0 R1(config-if)#exit Ri(config)#router eigrp 123 R1(config-router)#no auto-sunmary R1(config-router)#network 192.168.12.0 R1(config-router)#network 1.1.1.0 R2(config)#router eigrp 123 R2(config-router)#no auto-sunmary R2(config-router)#network 192.168.12.0 R2(config-router)#network 192.168.23.0 R3(config)#interface loopback 1 R3(config-if)#ip address 3.3.3.3 255.255.255.0 R3(config-if)#exit R3(config)#router eigrp 123 R3(config-router)#no auto-sunmary R3(config-router)#network 192.168.23.0 R3(config-router)#network 3.3.3.0 | could also use physical interfaces, but they can go down. Whenever a physical interface goes down, our IGP (EIGRP in this example) could find another path to the loopback interfaces (if there is one). R1(config)#interface tunnel @ R1(config-if)#tunnel source loopback 1 R1(config-if)#tunnel destination 3.3.3.3 Ri(config-if)#tunnel mode ipvéip 13 (contig)sintenface tunnel @ © R3(config-if)#tunnel source loopback 1 a3 (contig-if}stumel destination 1.1.2.1 R3(config-if)#tunnel mode ipv6ip tps networklessons.comiscofece-routing-swtchinghhow-1o-conigure-ipv8-tunneling-overipvd ano1990512028, 1:58 |Pv6 tunneling over IPvé Configuration a Rishow interfaces tunnel @ Tunnel@ is up, line protocol is up Hardware is Tunnel MTU 1514 bytes, BW 9 Kbit, DLY 5@0000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation TUNNEL, loopback not set Keepalive not set Tunnel source 1.1.1.1 (Loopback1), destination 3.3.3.3 Tunnel protocol/transport IPv6/1P R3ishow interfaces tunnel @ Tunnel@ is up, line protocol is up Hardware is Tunnel MTU 1514 bytes, BW 9 Kbit, DLY 5e0000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation TUNNEL, loopback not set keepalive not set Tunnel source 3.3.3.3 (Loopback1), destination 1.1.1.1 Tunnel protocol/transport IPv6/1P Use the show interfaces tunnel command to check if the tunnel is working, You can see mine is up, and the encapsulation type is TUNNEL. Our tunnel is working now, but we have some things left to do. We'll enable IPV6 routing, and advertise the loopback and tunnel interfaces in RIPNG! Ri(config)#ipv6 unicast-routing R1(config)#ipv6 router rip RIPNG Ra (config-rtr)#exit R1(config)#interface loopback @ Ri(config-if)#ipv6 rip RIPNG enable R1(config-if)#exit R1(config)#interface tunnel @ e R1(config-if)#ipv6 enable R1(config-if)#ipvé rip RIPNG enable tps networklessons.comiscofece-routing-swtchinghhow-1o-conigure-ipv8-tunneling-overipvd ano1990512028, 1:58 |Pv6 tunneling over IPvé Configuration a Ro\WunTagyHapye rouLer rap nurne R3(config-rtr)#exit R3(config)#interface loopback @ R3(config-if)#ipv6 rip RIPNG enable R3(config-if)Hexit R3(config)#interface tunnel @ R3(config-if)#ipv6 enable R3(config-if)#ipv6 rip RIPNG enable | enabled RIPNG (I could have chosen OSPFv3 or EIGRP) on the loopback and tunneld interface. You can see | also added an IPv6 address on the tunneld interfaces. We don't need any IPva addresses on our tunnel0 interfaces. Let's check the routing tables: Rifshow ipvé route rip IPv6 Routing Table - 4 entries Codes: C = Connected, L = Local, S - Static, R - RIP, B = BGP U - Per-user Static route I1 = ISIS 4, 12 + ISIS L2, IA = ISIS interarea, IS - ISIS summary © - OSPF intra, OL - OSPF inter, OE1 - OSPF ext 1, £2 - OSPF ext 2 ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2 R 2001::3/128 [126/2] via FE8@::303:303, Tunnel@ R3ishow ipvé route rip IPv6 Routing Table - 4 entries Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP U - Per-user Static route I - ISIS L1, 12 - ISIS L2, IA - ISIS interarea, IS - ISIS summary © - OSPF intra, OL - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2 ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2 R 2001::1/128 [126/2] via FEB 1@1:11, Tunnele © You can see both routers learned about each other IPv6 networks. Let's try a ping: tps networklessons.comiscofece-routing-swtchinghhow-1o-conigure-ipv8-tunneling-overipvd so1990512028, 1:58 |Pv6 tunneling over IPvé Configuration Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001::2, timeout is 2 seconds: Packet sent with a source address of 2001::1 win Success rate is 100 percent (5/5), round-trip min/avg/max = 8/8/8 ms ‘A quick ping proves that we have connectivity. That's all you have to do to create a manual tunnel and encapsulate IPv6 packets in IPv4 packets. Not that bad, right? How about GRE? You can easily change the tunnel type: R1(config)#interface tunnel @ Ri(config-if)#tunnel mode gre ip R3(config)#interface tunnel @ R3(config-if)#tunnel mode gre ip Use tunnel mode gre ip or type no tunnel mode ipv6ip so it switches back to the default (GRE). Let's check the tunnel: Rishow interfaces tunnel @ Tunnel@ is up, line protocol is up Hardware is Tunnel MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation TUNNEL, loopback not set Keepalive not set Tunnel source 1.1.1.1 (Loopback1), destination 3.3.3.3 Tunnel protocol/transport GRE/IP e It looks pretty much the same, except it now says GRE, The only difference between GRE and the manual tunnel is that GRE has a higher MTU by default, and there's something with the link-local IPv6 address of the tunnel interface: tps networklessons.comiscofece-routing-swtchinghhow-1o-conigure-ipv8-tunneling-overipvd ano1990512028, 1:58 |Pv6 tunneling over IPvé Configuration a * The link-local address for the manual tunnel is FE80::/96 + 32 bits from the tunnel source IPv4 address. Want to take a look for yourself? Here you will find the final configuration of each device. R2 ~ hostname R2 interface fastéthernet 0/0 ip address 192.168.12.2 255.255.255.0 ! interface fastethernet 1/0 ip address 192.168.23.2 255.255.255.0 router eigrp 123 no auto-sunmary network 192.168.12.0 network 192.168.23.0 ! end R3 ~ hostname R3 ! ipve unicast-routing ! interface loopback @ ipve address 2001: :3/128 interface loopback 1 ip address 3.3.3.3 255.255.255.0 hitpstnetworklessons.comicsca/ece-ruting-switchingthow-lo-confg ipvS-unneling-overipva m01990512028, 1:58 |Pv6 tunneling over IPvé Configuration a ip address 192.168.23.3 255.255.255.0 interface tunnel @ tunnel source loopback 1 tunnel destination 1.1.1.1 tunnel mode ipvéip tunnel mode gre ip ipv6 rip RIPNG enable 1 router eigrp 123 no auto-sunmary network 192.168.23.0 network 3.3.3.0 ipvé router rip RIPNG ipvé general-prefix MYPREFIX 6to4 fastEthernet 6/2 end R1 hostname Ri 1 ipv6 unicast-routing interface loopback @ ipvé address 2002: :1/128 ipv6 rip RIPNG enable 1 interface loopback 1 ip address 1.1.1.1 255.255.255.0 ! interface fastethernet 0/8 © ip address 192.168.12.1 255.255.255.0 interface tunnel @ tunnel source loopback 1 hitpsnetworklessons.comciscofece-rouing-swtchinghhow-1o-conigure-ipv8-tunning-overipvd ano1990512028, 1:58 |Pv6 tunneling over IPvé Configuration tunnel mode gre ip ipv6 rip RIPNG enable ! router eigrp 123 no auto-summary network 192.168.12.6 network 1.1.1.8 ipv6 router rip RIPNG ipve general-prefix MYPREFIX 6to4 fastethernet @/0 end ‘And that’s how you configure IPv6 static tunneling. If you have any questions just leave a comment! K Previous Lesson Next Lesson) IPv6 Access-List IPv6 Automatic 6to4 Tunnelling ® Tags: GRE, Tunnel Forum Replies sytem Tunnel interface ip is not required.s it not necessary? es IPv6 uses the link-local addresses as the next-hop for routing entries so there is no need to configure a “global” IPv6 e address, hnps:networklessons.comiciscalecie-outing-switchingihow-1conigurepyS-unneling-overipv4 sno1990512028, 1:58 |Pv6 tunneling over IPvé Configuration a Hello, | see that you are using multiple interfaces, but our router is only base license... which means we can only have up to 2 Interfaces(that are not psychical) Will t be possible with only 2 interfaces and{loopback 081) and have the tunnel psychical? | see that you write that it ‘can be psychical, but what kind of changes would we need to do if so? HiTor, The tunneld interface is using the source IP addresses of my loopback interfaces. You can also build the tunnel between the IP addresses on the Fastéthernet0/0 interfaces. Just use those as the source and destination and you are ready to go, Rene & oxen Hello Rene, and thanks for previous answer. We got t fixed, we changed two of the routers to cisco 1812, and the one running ipv4 only is a asa 5505, we are kinda stuck again though. Iwant all the other fastethernet ports(1-9) behind lets say destiny(cisco 1812), to access the servers behind cryo. Whatever I do, it wont work. Thanks again, regards {20 more replies! Ask a question or join the discussion by visiting our Community Forum Disclaimer Privacy Policy Support About © 2013 - 2023 NetworkLessons.com 5218 e hlps:inetworklessons.comiciscaocie-routing-switchingihow4o-confg ipvS-unneling-overipva r010