Line 1: |
Line 1: |
− | {{Template:Networking_rutos_manual_fw_disclosure | + | {{Template: Networking_rutos_manual_fw_disclosure |
− | | fw_version = {{{series}}}_R_00.02.06 | + | | fw_version ={{Template: Networking_rutos_manual_latest_fw |
− | | series = {{{series}}} | + | | 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== | | ==Summary== |
| | | |
Line 16: |
Line 18: |
| }} | | }} |
| | | |
− | {{#ifeq:{{{portbased}}}|1| | + | {{#ifeq:{{{portbased}}}|0|| |
| ==Port Based== | | ==Port Based== |
| | | |
Line 30: |
Line 32: |
| | | |
| {{#ifeq:{{{wan}}}|1| | | {{#ifeq:{{{wan}}}|1| |
− | By default, devices with LAN and WAN ports (such as {{{name}}}) automatically have 2 VLANs created - one | + | By default {{{name}}} automatically have 2 VLANs created - one |
− | for LAN and one Wired WAN interfaces. These two VLANs cannot be modified. | + | for LAN and one Wired WAN interfaces. {{#ifeq:{{{name}}}|RUT241||These two VLANs cannot be modified.}} |
| | | | | |
− | By default, devices with LAN port(s) (such as {{{name}}}) automatically have 1 VLANs created | + | By default {{{name}}} automatically have 1 VLAN created |
| for LAN interface. This VLAN cannot be modified. | | for LAN interface. This VLAN cannot be modified. |
| }} | | }} |
| | | |
− | [[File:Networking_rutos_manual_vlan_port_based_{{{eth}}}_{{{wan}}}_v1.png|border|class=tlt-border]]
| + | {{#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"> | | <table class="nd-mantable"> |
Line 62: |
Line 81: |
| </tr> | | </tr> |
| </table> | | </table> |
− | | + | }} |
− | |}}
| + | {{#ifeq:{{{interfacebased}}}|0|| |
| ==Interface Based== | | ==Interface Based== |
| | | |
− | <!--
| + | This section is an overview of created VLAN Devices. |
− | | |
− | to do
| |
− | | |
− | -->
| |
− | | |
− | ===Q-IN-Q Devices===
| |
− | ----
| |
− | <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]] | + | [[File:Networking_rutos_manual_vlan_interface_based_devices.png|border|class=tlt-border]] |
| | | |
| ===Device Settings=== | | ===Device Settings=== |
Line 99: |
Line 104: |
| <td>Tag</td> | | <td>Tag</td> |
| <td>[1..4094]; default: <b>none</b></td> | | <td>[1..4094]; default: <b>none</b></td> |
− | <td>802.1 VLAN tag of this Q-in-Q Device.</td> | + | <td>802.1 VLAN tag.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <td>Type</td> | | <td>Type</td> |
− | <td>802.1AD | 802.1Q; default: <b>802.1AD</b></td> | + | <td>802.1AD {{!}} 802.1Q; default: <b>802.1AD</b></td> |
− | <td>The type of this Q-in-Q Device.</td> | + | <td>The type of this Device.</td> |
| </tr> | | </tr> |
| <tr> | | <tr> |
| <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 Q-in-Q Device. Network interfaces can be configured in the Network → [[{{{name}}} Interfaces|Interfaces]] page.</td> | + | <td>Ethernet network interface associated with this Device. Network interfaces can be configured in the Network → [[{{{name}}} Interfaces|Interfaces]] page.</td> |
| </tr> | | </tr> |
| </table> | | </table> |
| | | |
| + | ===Q-IN-Q Devices=== |
| + | ---- |
| + | <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]] |