Differences

This shows you the differences between two versions of the page.

--- configuration:extend-ethernet-port-with-vlan [2022/01/24 15:17] – schmitt
+++ configuration:extend-ethernet-port-with-vlan [2022/02/09 15:45] (current) – [Advanced Configuration] schmitt
@@ Line 1: / Line 1: @@
 ====== Use Case ======
-The function is mainly used to operate several WANs on one Ethernet port of the NB2800.
+This Use Case describes the possibility to easily increase the number of ethernet ports in the link-managment.
-For this purpose, a trunk is configured between the NB2800 and a managed switch, over which multiple VLANs can be transmitted. The switch assigns the VLANs to the appropriate ports and then resolves them. So the end device does not need any VLAN functions.
+This Ports can be used as WAN or LAN connections.
-A use case would be an emergency car, which drives mobile missions, whose terminals have to connect to different uplinks.
+We will configure multiple VLANs on the NB2800 which will be seperated again on a managed switch.
+The VLAN can be configured individually and the enddevices do not need to have vlan functions
+A typical use case would be an emergency command car. Where you have multiple wanlinks (e.g. 5G, WLAN, Sat-Modem, Ethernet) and need to be used according to the current situation.
 ======VLAN Management======
 If you want to get access to multiple Networks with one Ethernet interface, you can use the VLAN Manager funktion. The following szenario shows an possible usecase.
 {{ :configuration:vlan_mngmnt.png?nolink |}}
-With this function you can create multiple virtual VLAN interfaces on top of one lan interface. Each of these interfaces can be assigned to a seperate network. To hold the assignment, the switch needs information, called VID, which is placed in the frame between the MAC and IP header.
+With this function you can create multiple virtual VLAN interfaces on top of one lan interface. Each of these interfaces can be assigned to a seperate network.
+For this configuration you need a VID (Virtual LAN ID) which is used by the switch to assign the correct port.
+==== VLAN Router====
-====Configuration Router====
 A virtual interface can be configuered in the WEB Manager at INTERFACE->VLAN MANAGEMENT-> ADD.
 {{ :configuration:vlan1.png?nolink |}}
-It is possible to set on which physical interface a subinterface is created, which VID it gets and with which priority the VLAN should be routed. The Networkmode remains routed. The prioritization classes correspond to 802.1p.
+Please choose the LAN Interface which is connected to the external switch.
-To create the VLAN interface, click apply.
+  * The ID need to be uniqe per VLAN (1-1024)
+  * Use network-mode routed.
+  * The prioritization classes can stay on background for every vlan.
 {{ :configuration:vlan2.png?nolink |}}
@@ Line 26: / Line 35: @@
 {{ :configuration:vlan3.png?nolink |}}
+==== IP Configuration ====
-====Configuration Switch====
+Afterwards you need to define the IP Configuration of each VLAN Interface.
-The Switch need to be configured to connect Ethernet Ports to the VLAN Trunk. This is ussually a Portbased to Tag-Base VLAN conversion.
-So that the distinction of the packages is not lost on the switch, there has to exist a Port on the Switch, which tag and untag the packages with the 802.1q(VID) header and forwards the packets to the correct Vlans. This Port has to be member in every VLAN.
-{{ :configuration:vlan_switch.png?nolink |}}
+You need to define the Mode of the VLAN Interface which can be LAN or WAN.
-Port 1,2 and 3 belong to the respective VLAN's with ID 1,2 and 3 but do not add a VLAN Tag.
+In WAN mode this link will be part of our link-managment for outgoing connections.
-Port 4 is the VLAN Trunk. It will forward the Ethernet Packets with an added VLAN Tag to the Router.
-==== Advanced Configuration ====
+In LAN mode you will be able to be part of a local network and serve as a DHCP/DNS Server.
-To check and improve the connection of the VLAN interfaces, by using supervision, you have to declaire each vlan as a WAN link under Interfaces -> IP Settings. The IP address can be assigned statically or via DHCP.
+The IP address can be assigned statically or via DHCP. PPPoE is also possible for DSL-Modem scenarios-
-(In case of PPPoE you have to configure the access data, service name and mac adress.)
 {{ :configuration:ip_settings.png?nolink |}}
@@ Line 46: / Line 52: @@
 {{ :configuration:ip_settings2.png?nolink |}}
+==== Link Configuration ====
 Now they will be displayed under Interfaces -> Link Management.
 {{ :configuration:VLAN_LinkManagement.png?nolink |}}
+====Configuration Switch====
+This Configuration was done on a Netgear GS108E Plus Switch, but most of the managed switches have this function.
+As shown in the picture above, we will use Port 4 as the so called trunk. And Port 1,2 and 3 as the untagged Port.
+The Switch need to be configured to connect Ethernet Ports to the VLAN Trunk.
+This is a portbased to tagBased VLAN conversion.
+As you can see in the table below Port 4 is member of every VLAN ID. And will hold the tagged Packages.
+Port 1,2 and 3 is only part of every individual VLAN ID, which will have the untagged packages.
+{{ :configuration:vlan_switch.png?nolink |}}
+To configure this behavior you need to choose the port Membership either as tagged or as untagged.
+We have created this settings with the Netgear ProSafe Switch for you as an example.
+The following pictures show the configration. This menu can bereached at VLAN -> 802.1Q -> Advanced -> VLAN
+Membership.
+{{ :configuration:vlan_switch_tag.png?nolink |}}
+{{ :configuration:vlan_switch2_tag.png?nolink |}}
+{{ :configuration:vlan_switch3_tag.png?nolink |}}
+====Advanced Configuration====
+To check established connections, the router sends pings to a host at a user defined intervall. At Interfaces -> Supervision you can choose options like interface, host, ping intervall and emergency actions.
+{{ :configuration:vlan_supervision_settings.png?nolink |}}
+The Supervision page after configuration.
+{{ :configuration:vlan_supervision.png?nolink |}}
+For more details about configuration : [[config:link-supervision|Use the Link supervison for a stable connection]]

User Tools

Site Tools

Differences

Page Tools