Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

6to4 Softwires

date_range 13-Jan-21

Configuring a 6to4 Provider-Managed Tunnel

When configuring a 6to4 provider-managed tunnel (PMT), replace the Anycast destination with the address of a managed relay in the provider network.

6to4 tunnels are supported on Multiservices 100, 400, and 500 PICs on M Series routers, and on MX Series routers equipped with Multiservices DPCs. 6to4 tunnels are not supported on MX Series routers with MS-MPCs or MS-MICs.

To configure a 6to4 PMT:

  1. Configure the ingress interface for 6to4 traffic. Include the name of the service set that identifies the rules for input and output service on this interface.
    content_copy zoom_out_map
    [edit interfaces ge-0/2/1]
    user@host# set unit logical-unit-number family family service input service-set-name
    user@host# set unit logical-unit-number family family service output service-set-name
    user@host# set unit logical-unit-number family family address addres
    

    For example:

    content_copy zoom_out_map
    [edit interfaces ge-0/2/1]
    user@host# set unit 0 family inet service input service-set v6to4-pmt
    user@host# set unit 0 family inet service output service-set v6to4-pmt
    user@host# set unit 0 family inet address 130.130.130.1/24
    
  2. Configure the egress interface.
    content_copy zoom_out_map
    [edit interfaces ge-0/2/2]
    user@host# set unit logical-unit-number family family address address
    

    For example:

    content_copy zoom_out_map
    [edit interfaces ge-0/2/2]
    user@host# set unit 0 family inet6 address 4ABC::1/16
    
  3. Configure the service interface that contains the rules for processing incoming traffic. Include a syslog option and associate a logical unit.
    content_copy zoom_out_map
    [edit interfaces sp-2/0/0]
    user@host# edit services-options syslog host host-name services any
    user@host# edit unit logical-unit-number family family
    user@host# edit unit 0 family family
    

    For example:

    content_copy zoom_out_map
    [edit interfaces sp-2/0/0]
    user@host# set services-options syslog host local services any
    user@host# set unit 0 family inet
    user@host# set unit 0 family inet6
    
  4. Configure the softwire concentrator and softwire rule for 6to4. In the Junos OS, 6to4 PMT configuration uses the same options as 6rd.
    content_copy zoom_out_map
    [edit services softwire softwire-concentrator v6rd v6to4]
    user@host# set softwire-address softwire-addres
    user@host# set ipv4-prefix ipv4-prefix
    user@host# set v6rd-prefix v6rd-prefix
    user@host# set mtu-v4 mtu-v4 
    

    For example:

    content_copy zoom_out_map
    [edit services softwire softwire-concentrator v6rd v6to4]
    user@host# set softwire-address 192.88.99.1
    user@host# set ipv4-prefix 130.130.130.2/32
    user@host# set v6rd-prefix 2002::0/16
    user@host# set mtu-v4 9192 
    
  5. Define the softwire rule that will process traffic on the ingress interface.
    content_copy zoom_out_map
    [edit services softwire rule v6to4-r1]
    user@host# set match-direction input
    user@host# set term term-name then v6rd softwire-concentrator
    

    For example:

    content_copy zoom_out_map
    [edit services softwire rule v6to4-r1]
    user@host# set match-direction input
    user@host# set term t1 then v6rd v6to4
    
  6. Define a stateful firewall rule that will accept all incoming traffic on the ingress interface.
    content_copy zoom_out_map
    [edit services stateful-firewall rule sfw-r1]
    user@host# set match-direction direction
    user@host# set term term-name then accept
    user@host# set term term-name then syslog
    

    For example:

    content_copy zoom_out_map
    [edit services stateful-firewall rule sfw-r1]
    user@host# set match-direction input-output
    user@host# set term t1 then accept
    user@host# set term t1 then syslog
    
  7. Define the NAT pool to be used for IPv6 NAT translation. This pool supports translation of the Anycast 6to4 relay addresses to addresses at the provider-managed relay.
    content_copy zoom_out_map
    [edit services nat pool v6to4-pmt]
    user@host# set address address
    user@host# port automatic
    

    For example:

    content_copy zoom_out_map
    [edit services nat pool v6to4-pmt]
    user@host# set address 3ABC::1/128
    user@host# set port automatic
    
  8. Define the NAT rule for translation.
    content_copy zoom_out_map
    [edit services nat rule rule-name]
    user@host# set match-direction input
    user@host# set term term-name then translated source-pool pool-name
    user@host# set term t1 then translated translation-type translation-type
    

    For example:

    content_copy zoom_out_map
    [edit services nat rule v6to4-pmt-r1]
    user@host# set match-direction input
    user@host# set term t1 then translated source-pool v6to4-pmt
    user@host# set term t1 then translated translation-type napt-66
    
  9. Define the service set that specifies the softwire rule and NAT rule.
    content_copy zoom_out_map
    [edit services service-set v6to4-pmt]
    user@host# set softwire-rules rule-name
    user@host# set stateful-firewall-rules rule-name
    user@host# set nat-rules rule-name
    user@host# set interface-service service-interface interface-name
    

    For example:

    content_copy zoom_out_map
    [edit services service-set v6to4-pmt]
    user@host# set softwire-rules v6to4-r1
    user@host# set stateful-firewall-rules sfw-r1
    user@host# set nat-rules v6to4-pmt-r1
    user@host# set interface-service service-interface sp-2/0/0
    
footer-navigation