Migration techniques

IPv4/IPv6 in IPv4 tunnels

An IPv4/IPv6 in IPv4 tunnel is the association of two tunnel endpoints. The equipment at each tunnel endpoint must be configured in a coherent manner.

  • Create an IPv4 tunnel interface:

    router{conf:myconfig}ip4tunX
    
    X

    Decimal identifier of the IPv4 tunnel interface.

  • Delete an IPv4 tunnel interface:

    router{conf:myconfig}delete ip4tunX
    
  • Configure the tunnel encaspulating addresses

    router{conf:myconfig-ip4tunX}tunnel any|LOCAL REMOTE
    
    any|LOCAL

    Encapsulating IPv4 address of the local endpoint of the tunnel. It must be a valid address on one of the interfaces. If you do not know this address, you can choose any. Then the IPv4 source address of the 6in4 packets that are originated by the router will be the first IPv4 address of the outgoing interface that is used to reach the remote IPv4 endpoint.

    REMOTE

    Encapsulating IPv4 address of the remote endpoint of the tunnel. It must be a valid address on one of the interfaces of the remote endpoint.

Once configured, IPv4 tunnels can be configured just like any other interface. Packets routed through this interface will be encapsulated and sent to the remote endpoint.

See also

Network interfaces and Managing IP adresses sections.

Note

The maximum number of tunnels depends on the performance of the router.

Example

router{conf:myconfig}ip4tun0
router{conf:myconfig-ip4tun0}tunnel 192.0.0.1 192.0.0.2
router{conf:myconfig-ip4tun0}ipaddress 3ffe::1 peer 3ffe::2

This command will create a logical interface named ip4tun0 and whose IPv6 interface address is 3ffe::1.

router{}show interface
...
ip4tun0: <POINTOPOINT,MULTICAST,NOARP,UP,RUNNING> mtu 1500 qdisc noqueue
    link/ipip 192.0.0.1 peer 192.0.0.2
    inet6 3ffe::1 peer 3ffe::2/128 scope global xmsd
    inet6 fe80::c000:1/128 scope link
router{}

IPv4/IPv6 in IPv6 tunnels

An IPv4/IPv6 in IPv6 tunnel is the association of two tunnel endpoints. The equipment at each tunnel endpoint must be configured in a coherent manner.

  • Create an IPv6 tunnel interface:

    router{conf:myconfig}ip6tunX
    
    X

    Decimal identifier of the IPv6 tunnel interface.

  • Delete an IPv6 tunnel interface:

    router{conf:myconfig}delete ip6tunX
    
  • Configure the tunnel encaspulating addresses

    router{conf:myconfig-ip6tunX}tunnel any|LOCAL REMOTE
    
    any|LOCAL

    Encapsulating IPv6 address of the local endpoint of the tunnel. It must be a valid address on one of the interfaces. If you do not know this address, you can choose any, then the IPv6 source address of the 6in6 packets that are originated by the router will be the first IPv6 address of the outgoing interface that is used to reach the remote IPv6 endpoint.

    REMOTE

    Encapsulating IPv6 address of the remote endpoint of the tunnel. It must be a valid address on one of the interfaces of the remote endpoint.

Once configured, IPv6 tunnels can be configured just like any other interface. Packets routed through this interface will be encapsulated and sent to the remote endpoint.

See also

Network interfaces and Managing IP adresses sections.

Note

The maximum number of tunnels depends on the performance of the router.

Example

router{conf:myconfig}ip6tun0
router{conf:myconfig-ip6tun0}tunnel 3ffe:34:107:1::1 3ffe:34:107:1::2
router{conf:myconfig-ip6tun0}ipaddress 8888::1 peer 8888::2

This command will create a logical interface named ip6tun0 and whose IPv6 interface address is 8888::1.

router{}show interface
...
ip6tun0: <POINTOPOINT,MULTICAST,UP,RUNNING> mtu 1500 qdisc noqueue
    link/tunnel6 3ffe:34:107:1::1 peer 3ffe:34:107:1::2
    inet6 8888::1 peer 8888::2/128 scope global xmsd
    inet6 fe80::230:1bff:feb5:4901/64 scope link
router{}

Showing migration information

The show interface command lists running interfaces and some of their characteristics.

Example

router{}display myconfig ip4tun1
# INTERFACE STATEMENTS
# IPV4 STATEMENTS
# IPV4 ADDRESSES
# IPV6 STATEMENTS
# IPV6 ADDRESSES
  ipaddress 3ffe::1 peer 3ffe::2
# IPV6 PREFIXES
# XIN4 STATEMENTS
  tunnel 192.0.0.1 192.0.0.2
router{}display myconfig ip4tun2
# INTERFACE STATEMENTS
# IPV4 STATEMENTS
# IPV4 ADDRESSES
  ipaddress 192.168.1.1 peer 192.168.1.2
# IPV6 STATEMENTS
# IPV6 ADDRESSES
# IPV6 PREFIXES
# XIN4 STATEMENTS
  tunnel 81.24.12.44 81.24.12.45
router{}display myconfig ip6tun1
# INTERFACE STATEMENTS
# IPV4 STATEMENTS
# IPV4 ADDRESSES
  ipaddress 192.168.0.1 peer 192.168.0.2
# IPV6 STATEMENTS
# IPV6 ADDRESSES
# IPV6 PREFIXES
# XIN6 STATEMENTS
  tunnel 3ffe:abcd::1 3ffe:abcd::2
router{}display myconfig ip6tun2
# INTERFACE STATEMENTS
# IPV4 STATEMENTS
# IPV4 ADDRESSES
# IPV6 STATEMENTS
# IPV6 ADDRESSES
  ipaddress 8888::1 peer 8888::2
# IPV6 PREFIXES
# XIN6 STATEMENTS
  tunnel 3ffe:34:107:1::1 3ffe:34:107:1::2

router{}show interface
...
ip4tun1: <POINTOPOINT,MULTICAST,NOARP,UP,RUNNING> mtu 1500 qdisc noqueue
    link/ipip 192.0.0.1 peer 192.0.0.2
    inet6 3ffe::1 peer 3ffe::2/128 scope global xmsd
       valid_lft forever preferred_lft forever
    inet6 fe80::c000:1/64 scope link
       valid_lft forever preferred_lft forever
ip4tun2: <POINTOPOINT,MULTICAST,NOARP,UP,RUNNING> mtu 1500 qdisc noqueue
    link/ipip 81.24.12.44 peer 81.24.12.45
    inet 192.168.1.1 peer 192.168.1.2/32 scope global xmsd ctu2
    inet6 fe80::5118:c2c/64 scope link
       valid_lft forever preferred_lft forever
ip6tun1: <POINTOPOINT,MULTICAST,NOARP,UP,RUNNING> mtu 1500 qdisc noqueue
    link/tunnel6 3ffe:abcd::1 peer 3ffe:abcd::2
    inet 192.168.0.1 peer 192.168.0.2/32 scope global xmsd stu1
    inet6 fe80::2d0:c9ff:fe98:9351/64 scope link
       valid_lft forever preferred_lft forever
ip6tun2: <POINTOPOINT,MULTICAST,NOARP,UP,RUNNING> mtu 1500 qdisc noqueue
    link/tunnel6 3ffe:34:107:1::1 peer 3ffe:34:107:1::2
    inet6 8888::1 peer 8888::2/128 scope global xmsd
       valid_lft forever preferred_lft forever
    inet6 fe80::2d0:c9ff:fe98:9351/64 scope link
       valid_lft forever preferred_lft forever

router{}