Once the right to use a SW option has been authorized by means of license installation, the SW
functionality can be enabled using the appropriate CLI command (as explained in the following
subsections).
Example:
# ip pep enable [redirect|trans|httpa]]
18.1 Generic Routing Encapsulation (GRE) and IP Tunneling
The VSAT supports configuration of one IP tunnel from its DVB (Satellite) interface with Generic
Routing Encapsulation (GRE) as specified in RFC 2784. Only the tunnel destination IP address and the
subnet to be tunneled needs to be specified when setting up a GRE tunnel over the SatLink network, since
the GRE tunnel by default will apply the reachable DVB interface IP address as the tunnel source IP
address.
A GRE tunnel can also be used to extend a VLAN across the SatLink network. Please see section 18.5 for
a description of how this is done.
Example:
#ip gre add 192.168.1.0 255.255.255.0 10.20.1.1
This will set up a GRE tunnel with the DVB interface IP address as the tunnel source and the IP address
10.20.1.1 as the tunnel destination. The GRE tunnel will accept traffic for the subnet
192.168.1.0/255.255.255.0.
To verify that a GRE tunnel and a GRE interface have been created, use the CLI command ip gre
show.
Example:
# ip gre show
GRE Tunnel Interfaces:
----------------------
If Tunnel Local Address Tunnel Remote Address
4 192.168.255.2 10.20.1.1
As shown above, interface number 4 has been allocated for the GRE interface. Use the CLI command ip
show to verify that a new IP interface has been created and that two entries have been added to the IP
routing table. One entry is used to route traffic with the destination address equal to the tunnel destination
IP address to the DVB interface—e.g. the GRE tunnel packets themselves. Another entry is used to route
traffic with destination addresses belonging to the GRE tunnel subnet into the GRE tunnel. Traffic
arriving through the GRE tunnel is routed to the applicable interface.
To Next Page
Loading...