Template:Networking rutos manual vlan: Difference between revisions
Gytispieze (talk | contribs) |
No edit summary |
||
| (20 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template: | {{Template: Networking_device_manual_fw_disclosure | ||
| fw_version ={{Template: | | series = {{{series}}} | ||
| name = {{{name}}} | |||
| fw_version ={{Template: Networking_device_manual_latest_fw | |||
| series = {{{series}}} | | series = {{{series}}} | ||
| name = {{{name}}} | |||
}} | }} | ||
}} | }} | ||
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} VLAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: | {{#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_device_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: | {{#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_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}} | ||
==Summary== | ==Summary== | ||
| Line 33: | Line 36: | ||
{{#ifeq:{{{wan}}}|1| | {{#ifeq:{{{wan}}}|1| | ||
By default {{{name}}} automatically have 2 VLANs created - one | By default {{{name}}} automatically have 2 VLANs created - one | ||
for LAN and one Wired WAN interfaces. {{# | for LAN and one Wired WAN interfaces. {{#switch:{{{series}}} | ||
|RUTX=These two VLAN instances cannot be deleted. | |||
|#default=The first VLAN instance cannot be deleted.}} | |||
| | | | ||
By default {{{name}}} automatically have 1 VLAN created | By default {{{name}}} automatically have 1 VLAN created | ||
for LAN interface. This VLAN cannot be | for LAN interface.{{#ifeq:{{{series}}} | OTD140 | | This VLAN instance cannot be deleted.}} | ||
}} | }} | ||
{{#switch:{{{series}}} | {{#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. | |RUT30X|RUT301=<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. | |RUT9|RUT9M|RUT952=<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. | |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}}} | {{#switch:{{{name}}} | ||
|RUTX08=[[File:Networking_rutos_manual_vlan_port_based_4_1_v1.png|border|class=tlt-border]] | |RUTX08|RUTX09|RUTX10|RUTX11|RUTXR1|RUTM08|RUTM09|RUTM10|RUTM11=[[File:Networking_rutos_manual_vlan_port_based_4_1_v1.png|border|class=tlt-border]] | ||
| | |RUTX12|RUTX14|RUTX50|RUTM12|RUTM50=[[File:Networking_rutos_manual_vlan_port_based_5_1_v2.png|border|class=tlt-border]] | ||
| | |RUT300|RUT301=[[File:Networking_rutos_manual_vlan_port_based_5_0_v1.png|border|class=tlt-border]] | ||
| | |RUT241|RUT200|RUT260|RUT140|RUT142=[[File:Networking_rutos_manual_vlan_port_based_1_1_v1.png|border|class=tlt-border]] | ||
| | |RUT950|RUT955=[[File:Networking_rutos_manual_vlan_port_based_3_0_v1.png|border|class=tlt-border]] | ||
| | |RUT951|RUT956|RUT901|RUT906=[[File:Networking_rutos_manual_vlan_port_based_4_1_1_v1.png|border|class=tlt-border]] | ||
| | |RUT952=[[File:Networking_rutos_manual_vlan_port_based_4_0_v1.png|border|class=tlt-border]] | ||
| | |OTD140=[[File:Networking_rutos_manual_vlan_port_based_2_0_v1.png|border|class=tlt-border]] | ||
| | |||
}} | }} | ||
| Line 113: | Line 117: | ||
<td>Interface</td> | <td>Interface</td> | ||
<td>ethernet network interface; default: <b>eth0</b></td> | <td>ethernet network interface; default: <b>eth0</b></td> | ||
<td>Ethernet network interface associated with this Device | <td>Ethernet network interface associated with this Device.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 125: | Line 129: | ||
After this you will be able to configure it's 802.1Q Tag and Tagged interface. | After this you will be able to configure it's 802.1Q Tag and Tagged interface. | ||
[[File: | [[File:Networking_rutos_manual_vlan_interface_based_q_in_q_v2.png|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
| Line 137: | Line 141: | ||
<td>[1..4094]; default: <b>none</b></td> | <td>[1..4094]; default: <b>none</b></td> | ||
<td>802.1Q VLAN tag.</td> | <td>802.1Q VLAN tag.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
}} | }} | ||
[[Category:{{{name}}} Network section]] | [[Category:{{{name}}} Network section]] | ||
Latest revision as of 07:34, 5 April 2024
The information in this page is updated in accordance with firmware version .
Summary
A Virtual LAN (VLAN) 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.
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Advanced" button, located at the top of the WebUI.
Port Based
The Port Based VLAN section allows you to create Port based and Tag based VLAN networks.
Port based 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.
Tag based 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.
By default {{{name}}} automatically have 1 VLAN created for LAN interface.This VLAN instance cannot be deleted.
| Field | Value | Description |
|---|---|---|
| VLAN ID | [1..4094]; default: none | VLAN Identification number. |
| LAN ports | Off | Untagged | Tagged; default: untagged | Select which Ethernet ports and how you want to use them with your VLAN.
|
Interface Based
This section is an overview of created VLAN Devices.
Device Settings
The Device Settings 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.
| Field | Value | Description |
|---|---|---|
| Tag | [1..4094]; default: none | 802.1 VLAN tag. |
| Type | 802.1AD | 802.1Q; default: 802.1AD | The type of this Device. |
| Interface | ethernet network interface; default: eth0 | Ethernet network interface associated with this Device. |
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.
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.
| Field | Value | Description |
|---|---|---|
| 802.1Q Tag | [1..4094]; default: none | 802.1Q VLAN tag. |
[[Category:{{{name}}} Network section]]