Chapter 12
Tunneling and VPNs
Section 12.6
Managing Generic Tunnels
The Layer 2 Tunnel Daemon supports a generic mode of operation based on the Ethernet type of Layer 2 data
traffic seen by the router. Multiple tunnels may be configured, each one with:
• an Ethernet type
• a tunnel ingress (Ethernet interface)
• a tunnel egress (either another locally connected Ethernet interface, or the remote IP address of another Layer 2
Tunnel daemon instance running on another Router)
CONTENTS
•
Section 12.6.1, "Viewing the Generic Tunnel Statistics"
•
Section 12.6.2, "Viewing a List of Generic Tunnels"
•
Section 12.6.3, "Adding a Generic Tunnel"
•
Section 12.6.4, "Deleting a Generic Tunnel"
•
Section 12.6.5, "Managing Remote Daemon IP Addresses for Generic Tunnels"
•
Section 12.6.6, "Managing Remote Daemon Egress Interfaces for Generic Tunnels"
•
Section 12.6.7, "Managing Ethernet Types for Generic Tunnels"
Section 12.6.1
Viewing the Generic Tunnel Statistics
To view the generic tunnel statistics, type:
show tunnel l2tunneld status generic
A table or list similar to the following example appears:
ruggedcom# show tunnel l2tunneld status generic
TUNNEL
NAME
IFNAME
ERRORS
---------------------------------------------------------------------------------------------
iso
switch.0002
0
This table or list provides the following information:
Parameter
tunnel-name
ifname
rx-frames
392
RX
TX
RX
FRAMES
FRAMES
CHARS
5
6
300
Synopsis: A string 1 to 32 characters long
The generic tunnel name.
This parameter is mandatory.
Synopsis: A string 1 to 15 characters long
The name of the ingress interface.
This parameter is mandatory.
Synopsis: A 32-bit unsigned integer
TX
CHARS
ERRORS
REMOTE IP
360
0
192.168.5.1
Description
RUGGEDCOM ROX II
CLI User Guide
RX
TX
RX
PACKETS
PACKETS
BYTES
11
0
704
Managing Generic Tunnels
TX
BYTES
0