home

Supported platforms

Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers
Getting startedOverviewArchitectureSupported platformsRelease notesWhite papers

Vyatta documentation

Learn how to install, configure, and operate the Vyatta Network Operating System (Vyatta NOS) and Orchestrator, which help drive our virtual networking and physical platforms portfolio.

Show On this page:

thumbnailSupported platforms

Tunneling IPv6 traffic in IPv4 with SIT

Create a SIT tunnel

R1 and R2 must be configured to create a tunnel between them to encapsulate the IPv6 traffic. To configure R1 to create a tunnel that uses SIT encapsulation between 15.0.0.1 and 15.0.0.2, perform the following steps in configuration mode.

Table 1. Configuring a tunnel interface on R1
Step Command

Create a tunnel with SIT encapsulation. 


vyatta@R1# set interfaces tunnel tun0 encapsulation sit

Specify the local IP address. 


vyatta@R1# set interfaces tunnel tun0 local-ip 15.0.0.1

Specify the remote IP address. 


vyatta@R1# set interfaces tunnel tun0 remote-ip 15.0.0.2

Configure the IPv6 address on the interface. 


vyatta@R1# set interfaces tunnel tun0 address 2001:db8:2::1/64

Commit the changes. 


vyatta@R1# commit

To configure R2 to create a tunnel that uses SIT encapsulation between 15.0.0.2 and 15.0.0.1, perform the following steps in configuration mode.

Table 2. Configuring a tunnel interface on R2

Step

Command

Create a tunnel with SIT encapsulation. 


vyatta@R2# set interfaces tunnel tun0 encapsulation sit

Specify the local IP address. 


vyatta@R2# set interfaces tunnel tun0 local-ip 15.0.0.2

Specify the remote IP address. 


vyatta@R2# set interfaces tunnel tun0 remote-ip 15.0.0.1

Configure the IPv6 address on the interface. 


vyatta@R2# set interfaces tunnel tun0 address 2001:db8:2::2/64

Commit the changes. 


vyatta@R2# commit

At this point, connectivity exists between R1 and R2 across the tunnel interface. The following example shows the capture of a ping from 2001:db8:2::1 to 2001:db8:2::2. Notice that the IPv6 ping packet is encapsulated by the IPv4 header.

Capture of a ping


Frame 22 (138 bytes on wire, 138 bytes captured)
Ethernet II, Src: Vmware_d6:81:80 (00:0c:29:d6:81:80), Dst: Vmware_4e:fc:b6 (00:0c:29:4e:fc:b6)
    Destination: Vmware_4e:fc:b6 (00:0c:29:4e:fc:b6)
    Source: Vmware_d6:81:80 (00:0c:29:d6:81:80)
    Type: IP (0x0800)
Internet Protocol, Src: 15.0.0.1 (15.0.0.1), Dst: 15.0.0.2 (15.0.0.2)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
    Total Length: 124
    Identification: 0x0000 (0)
    Flags: 0x04 (Don't Fragment)
    Fragment offset: 0
    Time to live: 255
    Protocol: IPv6 (0x29)
    Header checksum: 0x5d56 [correct]
    Source: 15.0.0.1 (15.0.0.1)
    Destination: 15.0.0.2 (15.0.0.2)
Internet Protocol Version 6
    0110 .... = Version: 6
    .... 0000 0000 .... .... .... .... .... = Traffic class: 0x00000000
    .... .... .... 0000 0000 0000 0000 0000 = Flowlabel: 0x00000000
    Payload length: 64
    Next header: ICMPv6 (0x3a)
    Hop limit: 64
    Source: 2001:db8:2::1 (2001:db8:2::1)
    Destination: 2001:db8:2::2 (2001:db8:2::2)
Internet Control Message Protocol v6
    Type: 129 (Echo reply)
    Code: 0
    Checksum: 0x2fca [correct]
    ID: 0xe825
    Sequence: 0x001b
    Data (56 bytes)
0000  9b a8 25 49 58 0c 07 00 08 09 0a 0b 0c 0d 0e 0f   ..%IX...........
0010  10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f   ................
0020  20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f    !"#$%&'()*+,-./
0030  30 31 32 33 34 35 36 37                           01234567

Last updated: May 7, 2021