In this example, two GRE tunnel interfaces are configured on different virtual routers of an E-series router. The source of the first tunnel interface matches the destination of the second tunnel interface and vice versa.
![]() |
Note: This example contains an ATM interface configuration for an ERX-7xx model, ERX-14xx model, or ERX-310 router that uses the slot/port format. |
- host1#virtual-router boston
The IP address of this interface appears in the header of tunneled frames and is used for forwarding traffic.
- host1:boston#interface atm 12/0.5
- host1:boston(config-if)#ip address 10.5.5.5
255.255.255.0
- host1:boston(config)#interface tunnel gre:ChicagoTunnel
- host1:boston(config-if)#tunnel source 10.5.5.5
- host1:boston(config-if)#tunnel destination
10.6.6.6
- host1:boston(config-if)#tunnel mtu 8000
- host1:boston(config-if)#ip address 10.7.7.7
255.255.255.0
- host1(config)#virtual-router chicago
- host1:chicago(config)#interface atm 12/1.5
- host1:chicago(config-if)#ip address 10.6.6.6
255.255.255.0
The name of the tunnel interface can differ from the tunnel interface configured in Step 3.
- host1:chicago(config-if)#interface tunnel
gre:BostonTunnel
The destination of this tunnel interface matches the source of the tunnel interface configured in Step 3 and vice versa.
- host1:chicago(config-if)#tunnel source 10.6.6.6
- host1:chicago(config-if)#tunnel destination
10.5.5.5
The MTU must match the MTU configured in Step 3.
- host1:chicago(config-if)#tunnel mtu 8000
- host1:chicago(config-if)#ip address 10.9.9.9
255.255.255.0