| Name |
Define a GRE tunnel name for new
configurations |
| Tunneled VLANs |
Define the VLAN connected clients use to route
GRE tunneled traffic within their respective
WLANs |
| Native VLAN |
Set a numerical VLAN ID (1 to 4,094) for the
native VLAN. The native VLAN allows an Ethernet
device to associate untagged frames to a VLAN when
no 802.1Q frame is included in the frame.
Additionally, the native VLAN is the VLAN untagged
traffic is directed over when using a port in trunk
mode |
| Native VLAN tagged |
Select this option to tag the native VLAN. The
IEEE 802.1Q specification is supported for tagging
frames and coordinating VLANs between devices. IEEE
802.1Q adds four bytes to each frame identifying the
VLAN ID for upstream devices that the frame belongs.
If the upstream Ethernet device does not support
IEEE 802.1Q tagging, it does not interpret the
tagged frames. When VLAN tagging is required between
devices, both devices must support tagging and be
configured to accept tagged VLANs. When a frame is
tagged, the 12 bit frame VLAN ID is added to the
802.1Q header so upstream Ethernet devices know
which VLAN ID the frame belongs to. The device reads
the 12 bit VLAN ID and forwards the frame to the
appropriate VLAN. When a frame is received with no
802.1Q header, the upstream device classifies the
frame using the default or native VLAN assigned to
the Trunk port. The native VLAN allows an Ethernet
device to associate untagged frames to a VLAN when
no 802.1Q frame is included in the frame. This
feature is not available by default |
| IPv4 MTU |
Set an IPv4 tunnel‘s maximum transmission unit
(MTU) from 900 to 1,476. The MTU is the largest
physical packet size (in bytes) transmittable within
the tunnel. Any messages larger than the MTU are
divided into smaller packets before being sent. A
larger MTU provides greater efficiency because each
packet carries more user data while protocol
overheads, such as headers or underlying per-packet
delays, remain fixed; the resulting higher
efficiency means a slight improvement in bulk
protocol throughput. A larger MTU results in the
processing of fewer packets for the same amount of
data. For IPv4, the overhead is 24 bytes (20 bytes
IPv4 header + 4 bytes GRE Header), thus the default
setting for an IPv4 MTU is 1,476 |
| IPv6 MTU |
Set an IPv6 tunnel‘s MTU from 1,236 to 1,456. The
MTU is the largest physical packet size (in bytes)
transmit able within the tunnel. Any messages larger
than the MTU are divided into smaller packets before
being sent. A larger MTU provides greater efficiency
because each packet carries more user data while
protocol overheads, such as headers or underlying
per-packet delays, remain fixed; the resulting
higher efficiency means a slight improvement in bulk
protocol throughput. A larger MTU results in the
processing of fewer packets for the same amount of
data. For IPv6, the overhead is 44 bytes (40 bytes
IPv6 header + 4 bytes GRE header), thus the default
setting for an IPv6 MTU is 1,456 |
