Many have commented, but I want to echo one comment in particular...for a Newbie, this is a GREAT introduction. Now to setup the switch...lol. Thank you
In TP-Link VLAN configurations, "tagged" and "untagged" refer to how VLAN traffic is treated on specific Ethernet ports (also known as VLAN member ports) in relation to a particular VLAN. Tagged VLAN Ports: Tagged Ports are Ethernet ports that are configured to carry traffic for one or more specific VLANs. When a port is tagged for a VLAN, it means that all frames leaving that port include VLAN tags. These tags are used to identify the VLAN to which the frames belong. Tagged ports are typically used when connecting devices that are VLAN-aware, such as managed switches, routers, or other networking equipment. The VLAN tags allow these devices to understand and properly route or process traffic for different VLANs. Untagged VLAN Ports: Untagged Ports (also sometimes referred to as "access ports") are Ethernet ports that are configured to carry traffic for a specific VLAN without adding VLAN tags to the frames. Frames leaving an untagged port are assumed to belong to the configured VLAN. Untagged ports are often used to connect devices that are not VLAN-aware, such as computers, printers, or IP phones. These devices are typically not configured to understand VLAN tags. When traffic leaves an untagged port, it is assumed to belong to the designated VLAN, and the switch removes any VLAN tags before sending the traffic to the device. Here's an example to illustrate the concept: Suppose you have a TP-Link managed switch with two VLANs configured: VLAN 10 and VLAN 20. If you configure port 1 as a tagged port for VLAN 10 and port 2 as an untagged port for VLAN 10, any traffic coming out of port 1 will have VLAN tags for VLAN 10. Devices connected to port 1 need to be VLAN-aware to interpret and use this tagged traffic. On the other hand, any traffic coming out of port 2 will not have VLAN tags. Devices connected to port 2 do not need to be VLAN-aware and will simply see the traffic as part of VLAN 10. In summary, tagging and untagging are methods for controlling how VLAN traffic is handled on specific ports in a TP-Link managed switch. Tagged ports add VLAN tags to frames, while untagged ports do not. These configurations are used to ensure that devices on the network receive and send traffic for the appropriate VLANs based on their capabilities and the network's requirements.
The purpose of a tagged or "trunked" port is to pass traffic for multiple VLAN's, whereas an untagged or "access" port accepts traffic for only a single VLAN. Generally speaking, trunk ports will link switches, and access ports will link to end devices.
Great, detailed voice content but with a heavy rumble with headphones. My laptop has a eq so i rolled off hard below 100 Hz. This is definately the BEST video on the ER7206! I've subscibed.
Gee, I hope you know by now why you would or wouldn't need a tagged port but it's certainly true that the particular topography in your example would likely use untagged ports. Thanks for the video!
Hi there. Thanks for the detailed explanation and your diagram was very helpful to a newbie like me. Can you please explain how a managed switch and a wireless access point would fit into the scenario you have described regarding setting up VLANS, separate DHCP's etc. Would this still be done at the router level, the switch level or both? Many thanks once again
i wonder if the failover is seamless, like if u are playing games and main isp dies so failover happens, would u notice the transition to the secondary isp?
It can't be totally seamless because you have to give the router some time trigger the failing circumstance. This is usually done through a ping mechanism and when the requests time out, the router switches to the second connection. During that time, your game will have issues too.
Hi. Quick question. Does this router (or any other router) merge two slow internet connections to make one faster output by merging the speed of multiple inputs (WLAN)
What about if I want a RDP server on same IP of internal server but I want to work on all 2 Wan interface ? So if I call the RDP on first ISP it will answer to that ISP and if I want to work on second ISP, will answer on that... Can I do it ? Thanks for the video
Tagged VLANs are not always compatible with legacy and older networking devices that are not “VLAN-aware.” Tagged VLANs also don't work with most end-user devices. Untagged VLANs are compatible with most network devices.
How fast would the failover be? thinking of getting this for starlink with a 4glte for backup during dropouts. My main concern is mitigating dropouts / hitches in zoom meetings
Can one install a VPN onto the Omada ER605 VPN Router, so that every device that connects to the router will be by default utilize the VPN connection going out (thereby eliminating to create a VPN on each individual device on the network)? And if this is doable, can one create a rule that configures a single device to bypass the VPN? If yes and yes... anyone tell a tutorial or more on this? Without and with the connector... too much to ask? Newb, but capable of following directions.
quick question.. Im thinking about getting the TP-Link ER605 .... i have several Asus routers in a Mesh. but they do no support VLANS. can I buy the TP-Link ER605 , and turn the other Asus routers in a AP, and have it work with vlans .. for my IoT devices / camera networks?
has the same question. from reading Amazon reviews for ER605, if you search for VLAN, it sounds like there are some serious problems with how it was implemented on the ER605 specifically. i ended up going with ER7206, but you could probably find other routers for slightly cheaper. Amazon also has used/refurbed ER7206s for ~$100 right now.
@JaiManny - so if the Asus routers doesnt support Vlans ... well you can untag each port on the ER605 to different vlan, or connect all Asus routers into some managed switch and send Vlans in trunk mode into the switch and then propagate the vlans into different Asus routers. Unfortunatelly I have feeling that what you want to achieve is multiple WiFi networks on every Asus device and each Wifi should have own network. so in this case if Asus routers are not designed to support Vlans - it would be impossible to achieve this. But the ER605 is a good start, unfortunatelly you need some other routers/AP which support the Vlans and multiple ssid's. As you already think about the ER605 - a nice solution for that would be going to omada devices from Tplink too. Also as you are already mentioning the IoT case - most probably you have some raspberry or other computer running all the time, where you can install omada controller with f.e. docker and then have a single point of managing everything via wegui
@@eldarshamukhamedov4521 there are no problems with implementing vlans via er605 - but you need to have a little bit more knowledge than in this movie, f.e. the difference between tag and untag vlans and how to assign them and of course you need to do it also on the device connected to the second end of the cable connected to the port where you mess with vlans :)
@@brzoza100 I just received an Asus router that can do vlans... So I will experiment with that and see ... Thanks for the information. I had a feeling I had to completely move over to the omada hardware
The purpose of a tagged or "trunked" port is to pass traffic for multiple VLANs, whereas an untagged or "access" port accepts traffic for only a single VLAN. Generally speaking, trunk ports will link switches, and access ports will link to end devices.
Many have commented, but I want to echo one comment in particular...for a Newbie, this is a GREAT introduction. Now to setup the switch...lol. Thank you
In TP-Link VLAN configurations, "tagged" and "untagged" refer to how VLAN traffic is treated on specific Ethernet ports (also known as VLAN member ports) in relation to a particular VLAN.
Tagged VLAN Ports:
Tagged Ports are Ethernet ports that are configured to carry traffic for one or more specific VLANs. When a port is tagged for a VLAN, it means that all frames leaving that port include VLAN tags. These tags are used to identify the VLAN to which the frames belong.
Tagged ports are typically used when connecting devices that are VLAN-aware, such as managed switches, routers, or other networking equipment. The VLAN tags allow these devices to understand and properly route or process traffic for different VLANs.
Untagged VLAN Ports:
Untagged Ports (also sometimes referred to as "access ports") are Ethernet ports that are configured to carry traffic for a specific VLAN without adding VLAN tags to the frames. Frames leaving an untagged port are assumed to belong to the configured VLAN.
Untagged ports are often used to connect devices that are not VLAN-aware, such as computers, printers, or IP phones. These devices are typically not configured to understand VLAN tags. When traffic leaves an untagged port, it is assumed to belong to the designated VLAN, and the switch removes any VLAN tags before sending the traffic to the device.
Here's an example to illustrate the concept:
Suppose you have a TP-Link managed switch with two VLANs configured: VLAN 10 and VLAN 20.
If you configure port 1 as a tagged port for VLAN 10 and port 2 as an untagged port for VLAN 10, any traffic coming out of port 1 will have VLAN tags for VLAN 10. Devices connected to port 1 need to be VLAN-aware to interpret and use this tagged traffic.
On the other hand, any traffic coming out of port 2 will not have VLAN tags. Devices connected to port 2 do not need to be VLAN-aware and will simply see the traffic as part of VLAN 10.
In summary, tagging and untagging are methods for controlling how VLAN traffic is handled on specific ports in a TP-Link managed switch. Tagged ports add VLAN tags to frames, while untagged ports do not. These configurations are used to ensure that devices on the network receive and send traffic for the appropriate VLANs based on their capabilities and the network's requirements.
The purpose of a tagged or "trunked" port is to pass traffic for multiple VLAN's, whereas an untagged or "access" port accepts traffic for only a single VLAN. Generally speaking, trunk ports will link switches, and access ports will link to end devices.
Great, detailed voice content but with a heavy rumble with headphones. My laptop has a eq so i rolled off hard below 100 Hz.
This is definately the BEST video on the ER7206! I've subscibed.
BIG Thanks! Thank you for the knowledge.,
You are welcome. Thank you and appreciate the support.
Excellent video. Thank you so much!
Gee, I hope you know by now why you would or wouldn't need a tagged port but it's certainly true that the particular topography in your example would likely use untagged ports. Thanks for the video!
thank you soo much good instructor
Can you and how to set-up VLANs not based on router ports but on the MAC addresses?
Hi there. Thanks for the detailed explanation and your diagram was very helpful to a newbie like me. Can you please explain how a managed switch and a wireless access point would fit into the scenario you have described regarding setting up VLANS, separate DHCP's etc. Would this still be done at the router level, the switch level or both? Many thanks once again
i wonder if the failover is seamless, like if u are playing games and main isp dies so failover happens, would u notice the transition to the secondary isp?
It can't be totally seamless because you have to give the router some time trigger the failing circumstance. This is usually done through a ping mechanism and when the requests time out, the router switches to the second connection. During that time, your game will have issues too.
How many devices does it support simultaneously?
Hi. Quick question.
Does this router (or any other router) merge two slow internet connections to make one faster output by merging the speed of multiple inputs (WLAN)
Very good explain 🙏
does it mean i bypass the router the isp gave me and plug their cable directly to the tplink multi wan?
hello drear brother i like watching your video look very amazing. so can you show how to configure TP-link ER7520T?
What about if I want a RDP server on same IP of internal server but I want to work on all 2 Wan interface ?
So if I call the RDP on first ISP it will answer to that ISP and if I want to work on second ISP, will answer on that...
Can I do it ?
Thanks for the video
Excellant sir
I would like to ask about how the IT department needs to set up the printer if it wants to connect to the CEO. Thank you.
Usually the printer will be on the same vlan or network.
Does this tplink router support subinterface config..I mean router on a stick..I have about six Vlans but the ports on this router is just 4.
Just make the tag ports that will automatically passes all of the vlans.
THanks a lot...
Thanks a lot...✅☑✔
Tagged VLANs are not always compatible with legacy and older networking devices that are not “VLAN-aware.” Tagged VLANs also don't work with most end-user devices. Untagged VLANs are compatible with most network devices.
and share printer, how to work?
How fast would the failover be? thinking of getting this for starlink with a 4glte for backup during dropouts. My main concern is mitigating dropouts / hitches in zoom meetings
you can check mikrotik but it is more complicated to set up but it is very versatile router
Mantap
I can build VLAN. thanku~~
Nice
Can one install a VPN onto the Omada ER605 VPN Router, so that every device that connects to the router will be by default utilize the VPN connection going out (thereby eliminating to create a VPN on each individual device on the network)? And if this is doable, can one create a rule that configures a single device to bypass the VPN? If yes and yes... anyone tell a tutorial or more on this? Without and with the connector... too much to ask? Newb, but capable of following directions.
quick question.. Im thinking about getting the TP-Link ER605 .... i have several Asus routers in a Mesh. but they do no support VLANS. can I buy the TP-Link ER605 , and turn the other Asus routers in a AP, and have it work with vlans .. for my IoT devices / camera networks?
has the same question. from reading Amazon reviews for ER605, if you search for VLAN, it sounds like there are some serious problems with how it was implemented on the ER605 specifically. i ended up going with ER7206, but you could probably find other routers for slightly cheaper. Amazon also has used/refurbed ER7206s for ~$100 right now.
@JaiManny - so if the Asus routers doesnt support Vlans ... well you can untag each port on the ER605 to different vlan, or connect all Asus routers into some managed switch and send Vlans in trunk mode into the switch and then propagate the vlans into different Asus routers. Unfortunatelly I have feeling that what you want to achieve is multiple WiFi networks on every Asus device and each Wifi should have own network. so in this case if Asus routers are not designed to support Vlans - it would be impossible to achieve this. But the ER605 is a good start, unfortunatelly you need some other routers/AP which support the Vlans and multiple ssid's. As you already think about the ER605 - a nice solution for that would be going to omada devices from Tplink too. Also as you are already mentioning the IoT case - most probably you have some raspberry or other computer running all the time, where you can install omada controller with f.e. docker and then have a single point of managing everything via wegui
@@eldarshamukhamedov4521 there are no problems with implementing vlans via er605 - but you need to have a little bit more knowledge than in this movie, f.e. the difference between tag and untag vlans and how to assign them and of course you need to do it also on the device connected to the second end of the cable connected to the port where you mess with vlans :)
@@brzoza100 I just received an Asus router that can do vlans... So I will experiment with that and see ... Thanks for the information. I had a feeling I had to completely move over to the omada hardware
The purpose of a tagged or "trunked" port is to pass traffic for multiple VLANs, whereas an untagged or "access" port accepts traffic for only a single VLAN. Generally speaking, trunk ports will link switches, and access ports will link to end devices.