[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Configuring Tunnel Interfaces (SRC CLI)
A tunnel allows direct connection between
a remote location and an application running on the C-series Controller;
a tunnel lets you use the redirect server in deployments where a JUNOSe
router does not have a direct connection to the C-series Controller.
The C-series Controller supports the following
types of tunnel interfaces:
- GRE—Generic routing encapsulation. Encapsulates
traffic that can use various network protocols within IP. For C-series
Controllers, the tunnel interface encapsulates IP packets.
- IP-over-IP—Encapsulates IP packets within IP packets.
- SIT—Encapsulates IPv6 traffic in an IPv4 tunnel.
This type of tunnel allows compatibility of IPv6 traffic within an
IPv4 network.
The other endpoint for the tunnel on a device
must be configured for the tunnel to be operational.
The local address of a tunnel connection is an
IP address that is configured for a unit (logical interface). Before
you configure a tunnel interface, configure the interface on the C-series
Controller.
See Configuring Gigabit Ethernet Interfaces for IPv4 (SRC CLI) .
Use the following configuration statements to configure
tunnel interfaces at the [edit] hierarchy level:
- interfaces name tunnel
{
- mode (ipip | gre | sit);
- destination destination ;
- source source;
- key key ;
- interface interface ;
- ttl ttl ;
- }
- interfaces name unit unit-number family inet {
- address address ;
- }
To configure a tunnel interface on a
C-series Controller:
- From configuration mode, access the configuration statement
that configures tunnel interfaces.
- [edit]
- user@host# edit interfaces name tunnel
For example:
- [edit]
- user@host# edit interfaces ip-tunnel tunnel
- Configure the type of tunnel.
- [edit interfaces ip-tunnel tunnel]
- user@host# set mode ipip
or
- [edit interfaces ip-tunnel tunnel]
- user@host# set mode gre
or
- [edit interfaces ip-tunnel tunnel]
- user@host# set mode sit
- Specify the IP address of the remote end of the tunnel.
- [edit interfaces ip-tunnel tunnel]
- user@host# set destination destination
For example:
- [edit interfaces ip-tunnel tunnel]
- user@host# set destination 192.0.2.20
- (Optional) Specify an IP address that will not change
for the local tunnel endpoint. It must be an address on another interface
of this host.
- [edit interfaces ip-tunnel tunnel]
- user@host# set source source
For example:
- [edit interfaces ip-tunnel tunnel]
- user@host# set source 192.20.10.5
- (Optional) For a GRE tunnel, specify a key.
- [edit interfaces ip-tunnel tunnel]
- user@host# set key key
For example:
- [edit interfaces ip-tunnel tunnel]
- user@host# set key 250
- (Optional) Specify an existing physical
interface on the C-series Controller.
- [edit interfaces ip-tunnel tunnel]
- user@host# set interface interface
For example:
- [edit interfaces ip-tunnel tunnel]
- user@host# set interface eth0
- (Optional) Specify the lifetime of tunneled packets.
- [edit interfaces ip-tunnel tunnel]
- user@host# set ttl ttl
For example:
- [edit interfaces ip-tunnel tunnel]
- user@host# set ttl 110
- Verify the configuration by running the show command.
For example:
[edit interfaces]
user@host# show
unit 0 {
family {
inet6 {
address 192.2.0.10/24;
}
}
}
ip-tunnel {
tunnel {
mode ipip;
destination 192.0.2.20;
source 192.20.10.5;
interface eth0;
ttl 110;
}
}
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]