วีดีโอ

hey @CJ-vg4tg, thanks for dropping by the channel. I want to make sure to clarify that this process is a "hack", as I have to knowingly cause a loop between the Gateway and the Switch, so I do not recommend this for "normal" use. If you have a chain of switches like you do, this makes it more complicated. I suggest you set up one SG2210P switch as distribution switch, make a dual connection to two LAN ports of ER7206 (make sure the LAN ports have the exact same configuration with each other i.e. all VLANs are defined on both LAN ports) and single uplinks from that distribution switch to the two other access switches. Good hunting!

@@deadmeats thanks yes I eventually got it sorted. I used 2 ports in a LAG configuration, so 1 ether and 1 fibre both working together to increase bandwidth and adding redundancy if 1 port/cable goes down. Working well so far. There is also anoption for spanning tree under the lag config that you need to tick.

hey there @DV_Food_khmer, thanks for dropping by the channel. I have not tested Omada with that number of clients, but TP Link use-cases and business scenarios that cover 4000 clients, so based on that info, TP Liink can support it. See link below for more info: www.tp-link.com/us/business-networking/

hey @Work-ht7bu I am just copy/pasting what I replied on your other comments (thanks for "binge-watching" my videos): Thanks for watching so many videos! When I was making these videos, I never really imagine people will watch more than 1 at a time :). I do get these feedbacks more often now, so more people are watching more videos in one seating, and I understand how it will impact your experience, and more importantly, learning. I will be making changes in future videos. Btw, apologies for delay with my reply, as life has thrown me a very hard wrench so I am a bit slow. Thanks again for watching the videos, and for your feedback, they mean a lot for small channel like mine. Good hunting!

hey @Godfreythegolden, good catch. It seems I may have missed showing what is in there. It is just Port 53 and no subnet is defined. It is because I needed to use it for blocking Internet access specific per VLAN. You will notice this is used in ACL 1 at 8:20 time stamp to block Camera devices from accessing the Internet.

hey @Work-ht7bu I am just copy/pasting what I replied on your other comments (thanks for "binge-watching" my videos): Thanks for watching so many videos! When I was making these videos, I never really imagine people will watch more than 1 at a time :). I do get these feedbacks more often now, so more people are watching more videos in one seating, and I understand how it will impact your experience, and more importantly, learning. I will be making changes in future videos. Btw, apologies for delay with my reply, as life has thrown me a very hard wrench so I am a bit slow. Thanks again for watching the videos, and for your feedback, they mean a lot for small channel like mine. Good hunting!

hey @Work-ht7bu I am just copy/pasting what I replied on your other comments (thanks for "binge-watching" my videos): Thanks for watching so many videos! When I was making these videos, I never really imagine people will watch more than 1 at a time :). I do get these feedbacks more often now, so more people are watching more videos in one seating, and I understand how it will impact your experience, and more importantly, learning. I will be making changes in future videos. Btw, apologies for delay with my reply, as life has thrown me a very hard wrench so I am a bit slow. Thanks again for watching the videos, and for your feedback, they mean a lot for small channel like mine. Good hunting!

hey @Work-ht7bu I am just copy/pasting what I replied on your other comments (thanks for "binge-watching" my videos): Thanks for watching so many videos! When I was making these videos, I never really imagine people will watch more than 1 at a time :). I do get these feedbacks more often now, so more people are watching more videos in one seating, and I understand how it will impact your experience, and more importantly, learning. I will be making changes in future videos. Btw, apologies for delay with my reply, as life has thrown me a very hard wrench so I am a bit slow. Thanks again for watching the videos, and for your feedback, they mean a lot for small channel like mine. Good hunting!

hey @Work-ht7bu I am just copy/pasting what I replied on your other comments (thanks for "binge-watching" my videos): Thanks for watching so many videos! When I was making these videos, I never really imagine people will watch more than 1 at a time :). I do get these feedbacks more often now, so more people are watching more videos in one seating, and I understand how it will impact your experience, and more importantly, learning. I will be making changes in future videos. Btw, apologies for delay with my reply, as life has thrown me a very hard wrench so I am a bit slow. Thanks again for watching the videos, and for your feedback, they mean a lot for small channel like mine. Good hunting!

hey @Work-ht7bu I am just copy/pasting what I replied on your other comments (thanks for "binge-watching" my videos): Thanks for watching so many videos! When I was making these videos, I never really imagine people will watch more than 1 at a time :). I do get these feedbacks more often now, so more people are watching more videos in one seating, and I understand how it will impact your experience, and more importantly, learning. I will be making changes in future videos. Btw, apologies for delay with my reply, as life has thrown me a very hard wrench so I am a bit slow. Thanks again for watching the videos, and for your feedback, they mean a lot for small channel like mine. Good hunting!

hey, thanks for watching so many videos! When I was making these videos, I never really imagine people will watch more than 1 at a time :). I do get these feedbacks more often now, so more people are watching more videos in one seating, and I understand how it will impact your experience, and more importantly, learning. I will be making changes in future videos. Btw, apologies for delay with my reply, as life has thrown me a very hard wrench so I am a bit slow. Thanks again for watching the videos, and for your feedback, they mean a lot for small channel like mine. Good hunting!

Thanks for the feedback @Work-ht7bu. I'll try to incorporate your feedback in future videos. Good hunting!

Hey @Work-ht7bu, thanks for dropping by the channel, I'll be more mindful of the sound in future videos.

hey @Godfreythegolden, thanks for dropping by the channel. The custom L2ALL is my own take to ensure that if I ever have other Omada Layer 3 Switch, that I can separate which "All" is really All VLANs. The default "All" is Omada's ALL VLANs, while the L2ALL is just for that Layer 3 Switch. If you ONLY have 1 Omada Layer 3 Switch, you don't have to worry about it. The complexity arise when you have multiple Layer 3 Switches. For example, you have L3SwitchA with VLANS 1, 10, 20 and another L3SwitchB VLANS 1, 30, 40. Omada's "All" will include VLANs 1, 10, 20, 30, 40. When you use a custom "xAll" per Layer 3 Switch, for example, call it L3SwitchA_All or L3SwitchB_All, it can bring more clarity on which "All" to use, whether the Omada's built-in one, or just specific to all the VLANs defined per Layer 3 Switch. I covered this more extensively in other videos after this, but I just want to mention it here in case experienced users gets hit with that scenario (multiple L3 Switch with variable VLANs) so that they dont need to wait for future videos. Good hunting!

Thanks for the quick response. That makes perfect sense for multiple switch scenarios. I only have a single switch setup, so I was wondering what the identical profile was for. Your channel has been incredibly helpful.

@Godfreythegolden you are welcome, glad you find my videos useful

hey @rafalbremer432, thanks for dropping by the channel. For the DNS, it depends on you. It can be local to a single VLAN, or to a router that serves multiple VLAN. If you need granularity, you will need to manually point each VLAN to your PiHole, this is how I have it configured on my home. If you want simplicity, you can point your router to the PiHole but note that PiHole has its own quirks, so you will have to be aware of that in case trouble shows up and in this case, the Admin VLAN 101 is a good choice to place it. As for controller, the location is mostly based on my personal use-case, because I need the controller to be easily accessible by the router but it can be connected to a PoE switch if your Gateway doesn't support PoE. Good hunting!

Hey @prasetiyot9480, thanks for dropping by the channel, I am glad you are enjoying the advanced topics! Good hunting!

hey @francisohernandez524, it looks like I am late to answer your other post, but I am glad you found what you are looking for. Check out my other videos when you have some time, as I usually cover niche use cases, and some may apply to you, and even if it didn't, I am sure you will gain some insight on how to use Omada. Good hunting!

hello @francisohernandez524, thank you for dropping by the channel. If you are talking about the "Wall" type of EAP, yes, they can have different VLAN on their wired ethernet port. Good hunting!

hey @ryanv640899, thanks for dropping by the channel. I don't see any issue doing that approach if you are using just TP Link Gateway and OPNsense. But be aware that if you plan to use Omada Controller "under" OPNsense "LAN", you will have to tell your Gateway how to reach the Controller, and you may need to make ACL to allow that communication to happen. Good hunting!

hello @allenbradleysevilla4305, thanks for dropping by the channel. Try mo mag create ng Profile Group specific for one device i.e. SpecialPC. Tapos, sa QoS, under Class Rule, i-select mo yung Profile SpecialPC na ito at i-assign sa Class (let's say Class 1). Yung ibang network/profiles, lagay mo as Class 2 (or 3). Sa settings mo, assign mo 90% (or 100%) sa Class 1. Good hunting.

Hey @jaycahow4667, thanks for dropping by. At the time, I think I wasn't sure but as you mentioned, it can be done. Hope you are enjoying your Omada Gateway!

hey @falkens_maze , thanks for dropping by the channel. I am glad you learned something new, that's always one of my goal: impart those niche use cases ;)

hello @agalperin, Thanks for dropping by the channel, I appreciate your feedback on the clapping. I'll be more mindful of it in future videos. Btw, since you reached the clapping parts, it's mostly the "proof" portion meaning, most of the configuration as done by that time and it's mostly showing the results of the test, Thanks again!

hello @CentioleInc, thanks for dropping by the channel. Is there something on the guide that you are unable to follow? The guide should work regardless of how many ISPs you have. Good hunting!

hello @jolandichoso1814, thank you for dropping by the channel. You can select which SSID and Network to use for your hotspot/portal. Settings > Authentication > Portal > SSID & Network. Good hunting!

hello @CallMeCribby, thank you for dropping by the channel. Apologies for late reply as real life has been so busy right now. As for your issue, make sure Static LAG is enabled on both switches and LAG is sometimes finicky, so the best way to enable them is connect all LAG port members "at the same time" . That is, try to configure LAG ports while NOT in use (let's call it Ports X1, Y1 on Switch 1 and X2, Y2 on Switch 2) . This means you have another port connecting the two switches (let's call it Port Z1 on Switch1 and Z2 on Switch2). As soon as both switch have LAG ports configured, disconnect Ports Z1 and Z2 and connect X1/Y1 to X2/Y2. Btw, since EasySmart only supports Static LAG, make sure to set Omada as Static as well. Good hunting.

@@deadmeats I got it working. Found out my I had 3 connections between the switches and not just two. The wires were crossed so it explains why the LAG wasn't working right. Thanks again, great tutorial!

hey @Garfield_Paramin, first of all, thanks for checking out and following my channel for that long, I appreciate it! As for your books/sites, If you have seen EP01 to EP34, I will try and review my videos from EP35 and later. I made many videos, and sometimes, I do post links to certain sites on some of my episodes but generally, the books I used are the old-school ones (in the 90s, early 2000s mostly Cisco/BayNetwork/Nortel CLI configuration guides and Windows Server/NT/XP Networking Configuration) and for the the "newer" ones, you can mostly find book-topics in Wikipedia, product documentations, and even other YT videos. As for the sites, I mostly visit manufacturer sites for official documentations and specifications. Specific to YT guides, I don't have anything specific, the main reason I don't mention any specific channel is that, I feel disingenuous for mentioning the popular ones because I don't really need to mention them: they are really large channels that if you type "TP Link Omada" in the YT search, there's 99.999999% chance that the big channels will show up, and 99% chance, my channel/videos will not show anywhere, there is a huge chance my videos will show up under "Previously Watched" videos because you watched them already. I even put up a link to YT search in all my video description now :) If you are just starting to rebuild, I suggest you watch EP67 for a newer approach to LAN Design, and EP34 for NewGen series, which you already knew and watched. Link below for Layer 3 Switching / EP67 video Layer 3 Switching: th-cam.com/video/-8m3390KVzU/w-d-xo.htmlsi=Q9dAm6WrJv_mnG-9

hello @davidesguerra7837, thanks for dropping by, Yes sir. Yung STP, and purpose nya is to block loops. Pag in-enable mo sya sa LACP mo, baka ma-block yung uplinks kaya hindi mo na sya kailangan. Ang problema pag walang STP, posible ka magka roon ng loop kaya siguraduhin mo na ayos yung mga uplinks. i..e kung 3 yung switch mo, iwas ka sa "cascade", ang gawin mo eh "distributed" (i.e avoid Switch 1 <> Switch 2 <> Switch 3, instead do Switch 1 <> Switch 2 and Switch 1 <> Switch 3).

hey there @Mark-px3rq, thanks for dropping by the channel. It may seem like I have confused you on my videos so me let just try and clarify. "Network Routing" is performed at the Layer 3 and usually performed by a device called Router and in Omada, they call it Internet Gateway. Routing is performed in "Layer 3" of the network stack and deals with things like IP address. "Network Switching" is performed at the "Layer 2" and done by a device called "Switch", and deals with things like "MAC address", These two are required to have a fully functioning network. However, ACL is not, it is a functionality that grants or denies access (hence Access Control List name). This means, Routing and Switching, while impacted by ACL are completely different, they all work together and intermixed but while the two are basic building blocks of networking, ACL is not. With NeXTGen - ACL I used are Switch-based i.e. they work in the Switch but that doesn't mean "routing" happens in the switch. The ACLs are working in the Layer 2 and not in Layer 3, but the ACL is NOT responsible for "routing" because ACL is not routing, it is about granting/denying access whether there is routing or not. The easiest way to test, create a traditional Omada LAN: a) Make sure you have more than 1 VLANs defined in your Omada LAN i.e. VLAN 1, VLAN 10, VLAN 20 and all are Gateway Interface (i.e. not Layer 3 Switching) b) Make sure you are using Omada Gateway and Omada Switch c) Make sure no VLAN Interface is enabled on the Switch except for VLAN 1 (default) d) Make sure you have no ACL active. e) Plug at least one host per VLAN on the Omada Switch, including the Admin PC/Host Testing: 0. Make sure your admin pc/host is connected to the switch 1. On the admin host, open 2 (or more) consoles, do consistent ping for each host on VLAN 10 and VLAN 20 2. Remove the cable between Switch and the Router. Without the Gateway uplink, ping will fail. This means the Switch is NOT doing routing even if the Switch has all the VLANs defined on it, With Layer 3 Switching (this video's goal), this will work since Switch is responsible for InterVLAN routing. Hope this helps!

hello @beremismachado, thank you as well for dropping by the channel!

hey @manzoorchaudhary6596, thanks for dropping by the channel. I am not clear with the scenario, but TP Link "sites" are just logical groupings. Your devices doesn't have to be in different "physical" location (i.e. one is in City A and other in City B). For example, in my set up, I have multiple Gateways across multiples "sites" but all devices are in the same physical location connected via Ethernet cable in my Home Lab (they are on top of each other). If your two er605 are in different physical locations that are too far apart for cable, you can use or wireless bridge. If Wireless bridge is not an option, and there is no Internet, I have no idea how to connect them. Good hunting.

hello @JekaCZE, thanks for dropping by. I am not sure what list you are referring to, but I will assume it is for DHCP reservation. So the instruction I will show is for that, see below: Settings (the gear in the lower left corner) > Services > DHCP Reservation Also, due to real life stuff, I take longer to reply than usual. If you have other inquires or question, I suggest you reach out to Official Forum or contact tp link support (links below): * Official Forum - community.tp-link.com/en/business/forum/794 * Official Tech Support - www.tp-link.com/us/support/contact-technical-support/

@@deadmeats Hi, thank you for your response. I already found it. It was hidden in services.

@@JekaCZE hey, that is awesome. I am happy for you (and just so you know, I did mention that as a solution as well :))

hello @goldgaelectronics4356, yes sir, pero dito lang ako sa YT pwede mag support so limited lang kasi bisi sa real-life. para sigurado ang support, suggestion ko eh kontakin mo si TP Link sa official forum nya or the tech support line nya (email or phone). Heto yung mga links nila: * Official Forum - community.tp-link.com/en/business/forum/794 * Official Tech Support - www.tp-link.com/us/support/contact-technical-support/

hey @michaelsalano5879, thanks for dropping by the channel. yes you can!

hey @nickramsay7568, thanks for dropping by the channel. I do not have access to my devices at the moment, but as you mentioned and have "clues" already, the Switch ACL applies only to TP Link Switches. If you have a Switch, even if it's TP Link, but if it's not in the Omada eco-system, the settings will not take effect. Your ER605 Gateway "LAN" ports will only work with Gateway ACLs. I am not sure about the latest firmware now, but iirc, a more granular Gateway ACLs has been requested in the past so hopefully, you can now do more granular ACLs on your router. I suggest you check the official TP Link forum or contact their tech support (links below) : * Official Forum - community.tp-link.com/en/business/forum/794 * Official Tech Support - www.tp-link.com/us/support/contact-technical-support/

hey @eranoceli5097, thanks for dropping by the channel. I assume you want to improve your North/South (Internet) traffic. If that is your goal, you already have a great set up. But remember, ER605 is limited with 1Gbps uplink for LAN and WAN, and you can't improve Internet traffic beyond 1Gbps. If your other router supports more than 1Gbps, you can replace your ER605 and use that other router instead. The other switch will not improve Internet traffic, but you can improve LAN to LAN traffic if you implement LAG between the two, but you will need to refer to the other switch's direction on how to do that. You can use the guide here to configure the TP Link switches. Good hunting!

hehe yep :)...thanks for dropping by the channel!

hey @SotirNikolov, thanks for dropping by the channel. TP Link Gateways takes a really long time to boot up, to the point you think it's stuck. For this device, it has been awhile since I rebooted mine and note that, each firmware revision affects boot time, but at the time, this device takes about ~5min. Good hunting!

hey @stan79yt, thanks for dropping by the channel. There is no change with ACL, since this is all purely Omada implementation. You can allow/deny access to VLAN 101 via Switch ACL and/or Gateway ACL, based on your use case. I cover a revised LAN design which covers ACL in later implementations of this, link below: th-cam.com/video/yraDD9P-PZk/w-d-xo.html Good hunting!

hey @hendihendi7577, welcome to the channel and thanks for dropping by. They are used differently and can be turned on at the same time. Policy Routing is choosing which WAN provider will be used/not-used (i.e. which road to take) and Gateway QoS is about shaping your Internet traffic (i.e. how wide/narror is the road). Good hunting!

hey there @michaelsalano5879, welcome to the channel. i tried checking on Amazon and TP Link, and cant find any mention about core count. However, I found side-by-side comparison of this router with other line up which may help. See link below. www.tp-link.com/us/compare/?type=smb&typeId=5802&productIds=69366%2C45943%2C54877

heya @sethb.pooten8305, welcome to channel and thanks for feedback. For muffled audio, I already upgraded my mic from the basic one to a better one, I don't really plan to change this, at least not yet. As for the way I speak, I can't really change much the way I speak, but I did add close-captioning.