Difference between revisions of "Template:Networking rutos manual vlan"

From Teltonika Networks Wiki
Line 1: Line 1:
 
{{Template:Networking_rutos_manual_fw_disclosure
 
{{Template:Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.04.1
+
| fw_version = {{{series}}}_R_00.02.05
 
| series    = {{{series}}}
 
| series    = {{{series}}}
 
}}
 
}}
Line 6: Line 6:
 
==Summary==
 
==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.
+
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''' function of '''RUTX''' devices.
+
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
 
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
Line 14: Line 16:
 
}}
 
}}
  
==VLAN Networks==
+
==VLAN Overview==
  
The '''VLAN Networks''' tab is used to manage Port based or Tag based VLAN. This feature is enabled by default.
+
You can configure two types of VLANs.
[[File:Networking_RUTX_manual_vlan_tag_port_v1.png|alt=|border|class=tlt-border|1101x1101px]]
 
===VLAN Settings===
 
----
 
'''Port based''' VLAN allows to assign different LAN port 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.
+
<ul>
 +
    <li><b>Port based</b> VLAN allows to assign different LAN port 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.</li>
 +
    <li><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.</li>
 +
</ul>
  
More information is provided below.
+
[[File:Networking_rutos_manual_vlan_port_status_eth_{{{eth}}}.png|border|class=tlt-border]]
[[File:Networking_RUTX_manual_vlan_tag_port_info_v1.png|border|class=tlt-border|1101x1101px]]
 
<br />
 
  
 
<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>VLAN ID</td>
       <td>[1..4094]; Default: " "</td>
+
       <td>[1..4094]; default: <b>none</b></td>
       <td>VLAN Identification number</td>
+
       <td>VLAN Identification number.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
       <td>LAN ports 1 {{!}} 2 {{!}} 3</td>
+
       <td>LAN/WAN ports</td>
       <td>off {{!}} untagged {{!}} tagged; Default: '''untagged'''</td>
+
       <td>Off | Untagged | Tagged; default: <b>untagged</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>Select which Ethernet ports and how you want to use them with your VLAN.
     </tr></table>
+
          <ul>
 +
              <li><b>Tagged</b> - used for tag-based VLAN.</li>
 +
              <li><b>Untagged</b> - used for port-based VLAN.</li>
 +
              <li><b>Off</b> - disables the port.</li>
 +
          </ul>
 +
        </td>
 +
     </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
 +
 
 +
[[File:Networking_rutos_manual_vlan_q-in-q_devices_add_button.png|border|class=tlt-border]]
 +
 
 +
After this you should be automatically redirected to the newly added Device's configuration page. However, if you wish to configure the Device later, it will be reachable from Q-IN-Q Devices section. Simply click the 'Edit' button next to a Device.
 +
 
 +
[[File:Networking_rutos_manual_vlan_q-in-q_devices_edit_button.png|border|class=tlt-border]]
 +
 
 +
===Device 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_RUTX_manual_Q_in_Q.png|border|class=tlt-border|1101x1101px]]
+
[[File:Networking_rutos_manual_vlan_q-in-q_devices_device_settings.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Tag</td>
 +
      <td>[1..4094]; default: <b>none</b></td>
 +
      <td>802.1 VLAN tag of this Q-in-Q Device.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Type</td>
 +
      <td>802.1AD | 802.1Q; default: <b>802.1AD</b></td>
 +
      <td>The type of this Q-in-Q Device.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Interface</td>
 +
      <td>ethernet network interface; default: <b>eth0</b></td>
 +
      <td>Ethernet network interface associated with this Q-in-Q Device. Network interfaces can be configured in the Network → [[{{{name}}} Interfaces|Interfaces]] page.</td>
 +
    </tr>
 +
</table>
  
 
[[Category:{{{name}}} Network section]]
 
[[Category:{{{name}}} Network section]]

Revision as of 12:43, 27 August 2020

Template:Networking rutos manual fw disclosure

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.

Networking rutos manual webui basic advanced mode 75.gif

VLAN Overview

You can configure two types of VLANs.

  • Port based VLAN allows to assign different LAN port 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.

[[File:Networking_rutos_manual_vlan_port_status_eth_{{{eth}}}.png|border|class=tlt-border]]

Field Value Description
VLAN ID [1..4094]; default: none VLAN Identification number.
LAN/WAN ports Off | Untagged | Tagged; default: untagged Select which Ethernet ports and how you want to use them with your VLAN.
  • Tagged - used for tag-based VLAN.
  • Untagged - used for port-based VLAN.
  • Off - disables the port.

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

Networking rutos manual vlan q-in-q devices add button.png

After this you should be automatically redirected to the newly added Device's configuration page. However, if you wish to configure the Device later, it will be reachable from Q-IN-Q Devices section. Simply click the 'Edit' button next to a Device.

Networking rutos manual vlan q-in-q devices edit button.png

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.

Networking rutos manual vlan q-in-q devices device settings.png

Field Value Description
Tag [1..4094]; default: none 802.1 VLAN tag of this Q-in-Q Device.
Type 802.1AD | 802.1Q; default: 802.1AD The type of this Q-in-Q Device.
Interface ethernet network interface; default: eth0 Ethernet network interface associated with this Q-in-Q Device. Network interfaces can be configured in the Network → [[{{{name}}} Interfaces|Interfaces]] page.

[[Category:{{{name}}} Network section]]