9,455
edits
Changes
Template:Networking rutos manual vlan (view source)
Revision as of 15:03, 13 January 2022
, 15:03, 13 January 2022no edit summary
{{Template:Networking_rutos_manual_fw_disclosure
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.03.1
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} VLAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} VLAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
==Summary==
A <b>Virtual LAN</b> (<b>VLAN</b>) is any broadcast domain that is partitioned and isolated in a computer network at the data link layer (OSI layer 2). LAN is the abbreviation for local area network and in this context virtual refers to a physical object recreated and altered by additional logic. VLANs work by applying tags to network packets and handling these tags in networking systems - creating the appearance and functionality of network traffic that is physically on a single network but acts as if it is split between separate networks. In this way, VLANs can keep network applications separate despite being connected to the same physical network, and without requiring multiple sets of cabling and networking devices to be deployed.
VLANs allow network administrators to group hosts together even if the hosts are not on the same network switch. This can greatly simplify network design and deployment, because VLAN membership can be configured through software. Without VLANs, grouping hosts according to their resource needs necessitates the labor of relocating nodes or rewiring data links. It also has benefits in allowing networks and devices that must be kept separate to share the same physical cabling without interacting, for reasons of simplicity, security, traffic management, or economy. For example, a VLAN could be used to separate traffic within a business due to users, and due to network administrators, or between types of traffic, so that users or low priority traffic cannot directly affect the rest of the network's functioning. Many Internet hosting services use VLANs to separate their customers' private zones from each other, allowing each customer's servers to be grouped together in a single network segment while being located anywhere in their datacenter. Some precautions are needed to prevent traffic "escaping" from a given VLAN, an exploit known as VLAN hopping.
This chapter is an overview of the VLAN section for {{{name}}} devices.
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = {{{series}}}
| series = {{{series}}}
}}
}}
==Summary==
{{#ifeq:{{{portbased}}}|0||
==Port Based==
The <b>Port Based</b> VLAN section allows you to create Port based and Tag based VLAN networks.
<b>Port based</b> VLAN allows you to assign different LAN ports to desired LAN networks.
The method is pretty simple: first you have to create a VLAN, choose which LAN port(s)
will provide addresses for that network and then configure LAN network.
<b>Tag based</b> VLAN allows a single router port to carry traffic from multiple VLAN's.
Tags containing the respective VLAN identifiers indicating the VLAN to which
the frame belongs are attached to the individual Ethernet frames.
{{#ifeq:{{{wan}}}|1|
By default {{{name}}} automatically have 2 VLANs created - one
for LAN and one Wired WAN interfaces. {{#ifeq:{{{name}}}|RUT241||These two VLANs cannot be modified.}}
|
By default {{{name}}} automatically have 1 VLAN created
for LAN interface. This VLAN cannot be modified.
}}
{{#switch:{{{series}}}
|RUT30X=<b>Note</b>: due to limitations by device, {{{name}}} single port cannot be <b>tagged</b> and <b>untagged</b> in different VLANs at the same time. Use <b>tagged</b> and <b>off</b> or <b>untagged</b> and <b>off</b> instead.
|RUT9=<b>Note</b>: due to limitations by device, {{{name}}} single port cannot be <b>tagged</b> and <b>untagged</b> in different VLANs at the same time. Use <b>tagged</b> and <b>off</b> or <b>untagged</b> and <b>off</b> instead.
|RUT2=<b>Note</b>: due to limitations by device, {{{name}}} single port cannot be <b>tagged</b> and <b>untagged</b> in different VLANs at the same time. Use <b>tagged</b> and <b>off</b> or <b>untagged</b> and <b>off</b> instead.
}}
{{#switch:{{{name}}}
|RUTX08=[[File:Networking_rutos_manual_vlan_port_based_4_1_v1.png|border|class=tlt-border]]
|RUTX09=[[File:Networking_rutos_manual_vlan_port_based_4_1_v1.png|border|class=tlt-border]]
|RUTX10=[[File:Networking_rutos_manual_vlan_port_based_4_1_v1.png|border|class=tlt-border]]
|RUTX11=[[File:Networking_rutos_manual_vlan_port_based_4_1_v1.png|border|class=tlt-border]]
|RUTXR1=[[File:Networking_rutos_manual_vlan_port_based_4_1_v1.png|border|class=tlt-border]]
|RUTX12=[[File:Networking_rutos_manual_vlan_port_based_5_1_v2.png|border|class=tlt-border]]
|RUTX14=[[File:Networking_rutos_manual_vlan_port_based_5_1_v2.png|border|class=tlt-border]]
|RUT300=[[File:Networking_rutos_manual_vlan_port_based_5_0_v1.png|border|class=tlt-border]]
|RUT241|RUT200=[[File:Networking_rutos_manual_vlan_port_based_2_1_v1.png|border|class=tlt-border]]
|RUT950|RUT951|RUT955|RUT956=[[File:Networking_rutos_manual_vlan_port_based_3_0_v1.png|border|class=tlt-border]]
}}
<table class="nd-mantable">
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer}}
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>VLAN ID</td>
<td>[1..4094]; default: <b>none</b></td>
<td>VLAN Identification number.</td>
</tr>
<tr>
<td>LAN{{#ifeq:{{{wan}}}|1|/WAN|}} ports</td>
<td>Off {{!}} Untagged {{!}} Tagged; default: <b>untagged</b></td>
<td>Select which Ethernet ports and how you want to use them with your VLAN.
<ul>
<li><b>Tagged</b> - used for <b>tag-based</b> VLAN.</li>
<li><b>Untagged</b> - used for <b>port-based</b> VLAN.</li>
<li><b>Off</b> - disables the port.</li>
</ul>
</td>
</tr>
</table>
}}
{{#ifeq:{{{interfacebased}}}|0||
==Interface Based==
This section is an overview of created VLAN Devices.
==VLAN Networks==
[[File:Networking_rutos_manual_vlan_interface_based_devices.png|border|class=tlt-border]]
===Device Settings===
===VLAN Settings===
----
----
The <b>Device Settings</b> section is used to configure the main parameters of a Q-in-Q device. Refer to the tables below for information on the configuration fields in the Q-in-Q Device Settings section.
[[File:Networking_rutos_manual_vlan_q-in-q_devices_device_settings.png|border|class=tlt-border]]
[[File:Networking_RUTX_manual_vlan_tag_port_info_v1.png|border|class=tlt-border|1101x1101px]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<th>field name</th>
<th>Field</th>
<th>value</th>
<th>Value</th>
<th>description</th>
<th>Description</th>
</tr>
</tr>
<tr>
<tr>
<td>VLAN ID</td>
<td>Tag</td>
<td>[1..4094]; Default: " "</td>
<td>[1..4094]; default: <b>none</b></td>
<td>VLAN Identification number</td>
<td>802.1 VLAN tag.</td>
</tr>
<tr>
<td>Type</td>
<td>802.1AD {{!}} 802.1Q; default: <b>802.1AD</b></td>
<td>The type of this Device.</td>
</tr>
</tr>
<tr>
<tr>
<td>LAN ports 1 {{!}} 2 {{!}} 3</td>
<td>Interface</td>
<td>off {{!}} untagged {{!}} tagged; Default: '''untagged'''</td>
<td>ethernet network interface; default: <b>eth0</b></td>
<td>Select which and how to use your LAN ports with VLAN. If you check a port as "'''untagged'''", it will be used as port based. If you check a port as "'''tagged'''", it will be used as tag based. If you set it as "'''Off'''", it will disable the port</td>
<td>Ethernet network interface associated with this Device. Network interfaces can be configured in the Network → [[{{{name}}} Interfaces|Interfaces]] page.</td>
</tr></table>
</tr>
</table>
===Q-IN-Q Devices===
===Q-IN-Q Devices===
----
----
Q-in-Q VLAN tunnel enables a possibility to segregate the traffic of different users in their infrastructure, while still giving a full range of VLANs for their internal use by adding a second tag to an already tagged frame. Below is an example of Q-IN-Q configuration section.
<b>Q-in-Q</b> VLAN tunnel enables a possibility to segregate the traffic of different users in their infrastructure,
while still giving a full range of VLANs for their internal use by adding a second tag to an already tagged frame.
By default the Q-in-Q Devices list is empty. To create a new Q-in-Q Device, enter as custom name for it and click the 'Add' button.
After this you will be able to configure it's 802.1Q Tag and Tagged interface.
[[File:Networking_rutos_manual_vlan_interface_based_q_in_q.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>802.1Q Tag</td>
<td>[1..4094]; default: <b>none</b></td>
<td>802.1Q VLAN tag.</td>
</tr>
<tr>
<td>Tagged Interface</td>
<td>vlan device; default: <b>none</b></td>
<td>The Device (Interface) this Q-in-Q device will be tagged with.</td>
</tr>
</table>
}}
[[Category:{{{name}}} Network section]]
[[Category:{{{name}}} Network section]]
