H3C Routers
IPv6 over IPv4 GRE Tunnel Configuration Examples

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Contents

Introduction· 1

Prerequisites· 1

Example: Configuring an IPv6 over IPv4 GRE tunnel 1

Network configuration· 1

Analysis· 2

Software versions used· 2

Restrictions and guidelines· 2

Procedures· 2

Verifying the configuration· 4

Configuration files· 4

Device A· 4

Device B· 4

Device C· 5

Related documentation· 5

 

Introduction

The following information provides IPv6 over IPv4 GRE configuration examples.

Prerequisites

The following information applies to Comware 9-based routers. Procedures and information in the examples might be slightly different depending on the software or hardware version of the routers.

The configuration examples were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

This document assumes that you have basic knowledge of IPv6 over IPv4 GRE.

Example: Configuring an IPv6 over IPv4 GRE tunnel

Network configuration

As shown in Figure 1, Device A, Device B, and Device C are connected to each other through the IPv4 network. Device A and Device B are connected to IPv6 hosts PC A and PC B, respectively.

Configure a GRE tunnel between the two border dual-stack devices (Device A and Device B) to allow the two IPv6 PCs to communicate with each other over the IPv4 network.

Figure 1 Network diagram

‌

Analysis

·     To allow the two IPv6 PCs to communicate over the IPv4 network, configure the GRE tunnel mode as GRE/IPv4 (GRE over IPv4) and assign an IPv6 address to the GRE tunnel interface.

·     To direct traffic sent from PC A to PC B to the GRE tunnel, configure a route reaching the destination network through the tunnel on Device A. Configure the route destination address as the packet destination address before GRE encapsulation (IPv6 address of PC B) and next hop address as the tunnel interface address on the tunnel remote device Device B, or specify the route's outgoing interface as the local GRE tunnel interface. You can configure this route by configuring a static route or configuring a dynamic routing protocol on both the tunnel interface and the Layer 3 interface connecting PC A. This example uses a static route. The corresponding configuration is also required on Device B.

·     To ensure that the two ends of the GRE tunnel can reach other through IPv4, configure a static route to the peer on Device A and Device B, respectively.

Software versions used

This configuration example was created and verified on R9141P16 of the MSR2630E-X1 device.

Restrictions and guidelines

You must configure the tunnel source address and destination address at both ends of a tunnel. The tunnel source or destination address at one end must be the tunnel destination or source address at the other end.

Procedures

Configuring Device A

# Assign an IPv6 address to interface GigabitEthernet 1/0/1.

<DeviceA> system-view

[DeviceA] interface gigabitethernet 1/0/1

[DeviceA-GigabitEthernet1/0/1] ipv6 address 1001::1 64

[DeviceA-GigabitEthernet1/0/1] quit

# Assign IP addresses to other interfaces on Device A in the same way. (Details not shown.)

Create tunnel interface Tunnel 0, and specify the GRE/IPv4 tunnel mode.

[DeviceA] interface tunnel 0 mode gre

# Assign an IPv6 address to the tunnel interface.

[DeviceA-Tunnel0] ipv6 address 3001::1 64

# Configure the source address of the tunnel.

[DeviceA-Tunnel0] source 192.13.2.2

# Configure the destination address of the tunnel.

[DeviceA-Tunnel0] destination 131.108.5.2

[DeviceA-Tunnel0] quit

# Configure a static route from Device A through Tunnel 0 to PC B.

[DeviceA] ipv6 route-static 2001::2 64 tunnel 0

# Configure a static route from Device A to the tunnel remote end (Device B).

[DeviceA] ip route-static 131.108.5.0 255.255.255.0 192.13.2.1

Configuring Device B

# Assign an IPv6 address to interface GigabitEthernet 1/0/2.

<DeviceB> system-view

[DeviceB] interface gigabitethernet 1/0/2

[DeviceB-GigabitEthernet1/0/2] ipv6 address 2001::1 64

[DeviceB-GigabitEthernet1/0/2] quit

# Assign IP addresses to other interfaces on Device B in the same way. (Details not shown.)

Create tunnel interface Tunnel 0, and specify the GRE/IPv4 tunnel mode.

[DeviceB] interface tunnel 0 mode gre

# Assign an IPv6 address to the tunnel interface.

[DeviceB-Tunnel0] ipv6 address 3001::2 64

# Configure the source address of the tunnel.

[DeviceB-Tunnel0] source 131.108.5.2

# Configure the destination address of the tunnel.

[DeviceB-Tunnel0] destination 192.13.2.2

[DeviceB-Tunnel0] quit

# Configure a static route from Device B through Tunnel 0 to PC A.

[DeviceB] ipv6 route-static 1001::2 64 Tunnel 0

# Configure a static route from Device B to the tunnel remote end (Device A).

[DeviceB] ip route-static 192.13.2.0 255.255.255.0 131.108.5.1

Configuring Device C

# Assign an IPv6 address to interface GigabitEthernet 1/0/1.

<DeviceC> system-view

[DeviceC] interface gigabitethernet 1/0/1

[DeviceC-GigabitEthernet1/0/1] ip address 192.13.2.1 24

[DeviceC-GigabitEthernet1/0/1] quit

# Assign an IPv6 address to interface GigabitEthernet 1/0/2.

[DeviceC] interface gigabitethernet 1/0/2

[DeviceC-GigabitEthernet1/0/2] ip address 131.108.5.1 24

[DeviceC-GigabitEthernet1/0/2] quit

Verifying the configuration

PC A and PC B can ping each other.

C:\>ping6 2001::2

 

Pinging 2001::2

from 1001::1 with 32 bytes of data:

 

Reply from 2001::2: bytes=32 time<1ms

Reply from 2001::2: bytes=32 time<1ms

Reply from 2001::2: bytes=32 time<1ms

Reply from 2001::2: bytes=32 time<1ms

 

Ping statistics for 2001::2:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Configuration files

Device A

#

interface GigabitEthernet1/0/1

 port link-mode route

 ip address 192.13.2.2 255.255.255.0

#

interface GigabitEthernet1/0/1

 port link-mode route

 ipv6 address 1001::1/64

#

interface Tunnel0 mode gre

 ipv6 address 3001::1/64

 source 192.13.2.2

 destination 131.108.5.2

#

 ip route-static 131.108.5.0 255.255.255.0 192.13.2.1

#

 ipv6 route-static 2001::2 64 Tunnel 0

#

Device B

#

interface GigabitEthernet1/0/2

 port link-mode route

 ip address 131.108.5.2 255.255.255.0

#

interface GigabitEthernet1/0/2

 port link-mode route

 ipv6 address 2001::1/64

#

interface Tunnel0 mode gre

 ipv6 address 3001::2/64

 source 131.108.5.2

 destination 192.13.2.2

#

ip route-static 192.13.2.0 255.255.255.0 131.108.5.1

#

ipv6 route-static 1001::2 64 Tunnel 0

#

Device C

#

interface GigabitEthernet1/0/1

 port link-mode route

 ip address 192.13.2.1 255.255.255.0

#

interface GigabitEthernet1/0/2

 port link-mode route

 ip address 131.108.5.1 255.255.255.0

#

Related documentation

·     IP Tunneling and Security VPN Configuration Guide in H3C MSR1000[2600][3600] Routers Configuration Guides(V9)

·     IP Tunneling and Security VPN Command Reference in H3C MSR1000[2600][3600] Routers Command References(V9)