Search…
GRE
TIP OpenWiFi 2.0
OpenWiFi 2.0 supports Generic Routing Encapsulation as an available "tunnel" protocol type.
This makes it possible to configure GRE for multiple types of deployments as any interface may be encapsulated by the "tunnel" parameter.
For example, to send all content of a specific SSID over an GRE tunnel, the following configuration would apply.
1
"interfaces": [
2
{
3
"name": "WAN",
4
"role": "upstream",
5
"ethernet": [
6
{
7
"select-ports": [
8
"WAN*"
9
]
10
}
11
],
12
"ipv4": {
13
"addressing": "dynamic"
14
}
15
},
16
{
17
"name": "GRE",
18
"role": "upstream",
19
"vlan": {
20
"id": 20
21
},
22
"tunnel": {
23
"proto": "gre",
24
"peer-address": "far end IP address",
25
},
26
"ssids": [
27
{
28
"name": "Tunneled SSID via GRE from VLAN 20 Interface",
29
"wifi-bands": [
30
"2G", "5G"
31
],
32
"bss-mode": "ap",
33
"encryption": {
34
"proto": "none",
35
"ieee80211w": "optional"
36
},
37
"rate-limit": {
38
"ingress-rate": 100,
39
"egress-rate": 100
40
},
41
"roaming": {
42
"message-exchange": "ds",
43
"generate-psk": true
44
}
45
}
46
]
47
},
Copied!
In the above example, the WAN untagged port will request DHCP in addition to present a VLAN interface with id 20 that both initiates the GRE tunnel as well as passes SSID traffic over that tunnel. Optionally the GRE tunnel itself may also carry a VLAN encapsulated payload. In the above example a WAN presentation of VLAN interface 20 has GRE tunnel. Within the GRE tunnel on WAN interface of VLAN 20 is a GRE payload with VLAN 30 in the payload header.
Last modified 5mo ago
Export as PDF
Copy link