Technical data

Configure GRE Tunnels
© 2012 Meru Networks, Inc. Configuring Security 123
default# show gre
GRE Name Remote External Address Tunnel IP address Tunnel IP Netmask LocalExternal
vlan1 172.27.0.162 12.12.12.12 255.255.0.0 1
gre1 172.27.0.206 13.13.13.13 255.255.0.0 2
GRE Configuration(2 entries)
To configure the GRE ESSID, specify the GRE profile name, a tunnel-type and Security
Profile, as shown in the following example:
default(config)# essid guest
default(config-essid)# gre name guest
default(config-essid)# tunnel-type gre
default(config-essid)# security-profile default
default(config)# exit
The GRE ESSID name must be the same as the GRE Tunnel Profile name specified
in the preceding GRE Configuration procedure (for example, guest). The GRE
Tunnel Profile name is specified in the gre name.
For the tunnel-type, the gre parameter must be specified for GRE Tunnel
configuration.
Specify the Security Profile name with the security-profile command—typically
the default profile is used.
To check the status of the a GRE tunnel, use the command:
default# test gre gre_name ip_address
where gre_name is the GRE Profile name and ip_address is the IP address of the
machine that is connected behind the tunnel (optional).
The following points should be noted when configuring a GRE tunnel:
The DHCP relay pass-through flag always should be off for a GRE tunnel. This
ensures the DHCP relay is always on and hence the DHCP request packets are
forwarded to the DHCP Server specified by DHCP Server IP Address.
DHCP traffic associated with users connecting to a GRE tunnel are relayed to the
configured DHCP Server located at the remote location through the associated
GRE tunnel.
Only IPv4 support is provided for GRE tunneling.
Note:
By default, the command will ping the remote endpoint.