From ca605c69429fb74f9e05eff449f25ec7f4da4d12 Mon Sep 17 00:00:00 2001 From: srividya0208 Date: Mon, 12 Apr 2021 05:42:38 -0400 Subject: T3458-e:1.3 ver:tunnel interface:replaced GRETAP with GRE-Bridge Bymistakenly wrote gretap for 1.3 version, corrected with "GRE-Bridge" parameter as expected --- docs/configuration/interfaces/tunnel.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/configuration/interfaces/tunnel.rst b/docs/configuration/interfaces/tunnel.rst index 22648095..e7301549 100644 --- a/docs/configuration/interfaces/tunnel.rst +++ b/docs/configuration/interfaces/tunnel.rst @@ -201,12 +201,12 @@ An example: set interfaces tunnel tun0 address 172.16.17.18/24 set interfaces tunnel tun0 parameters ip key 20 -GRETAP -^^^^^^ +GRE-Bridge +^^^^^^^^^^ -While normal GRE is for layer 3, GRETAP is for layer 2. GRETAP can encapsulate -Ethernet frames, thus it can be bridged with other interfaces to create -datalink layer segments that span multiple remote sites. +While normal GRE is for layer 3, GRE-Bridge is for layer 2. GRE-Bridge can +encapsulate Ethernet frames, thus it can be bridged with other interfaces to +create datalink layer segments that span multiple remote sites. Layer 2 GRE example: @@ -214,7 +214,7 @@ Layer 2 GRE example: set interfaces bridge br0 member interface eth0 set interfaces bridge br0 member interface tun0 - set interfaces tunnel tun0 encapsulation gretap + set interfaces tunnel tun0 encapsulation gre-bridge set interfaces tunnel tun0 local-ip 198.51.100.2 set interfaces tunnel tun0 remote-ip 203.0.113.10 -- cgit v1.2.3