วีดีโอ

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.

heya @Raden.Mas.Romo.Unggul.Sejagat sorry for late reply as I am still swamped with real-life stuff. But yes, you can. However, you have to know the network ports that your application is using. TP Link already have the well-known ports created such as FTP (for FTP clients and servers), ssh, and others. But for custom applications, let's says Minecraft use 25565, it can be entered. So for WhatsApp and other Social Media apps, you need to check their ports. Remember, since it's a network port, it will affect all applications that use that network port i.e. if your social media use 80 and 443 then even web browsing will be affected since they use the same port. To set up your applications, you need to: Step 0: Get the network port of your applications. Use network analyzer such as WireShark Step 1: Create that Application in Omada. Profiles > Gateway QoS Service > Create New Gateway QoS Service > [Fill in the values] Step 2: Create Gateway QoS in Omada: Transmission > Gateway QoS > Bandwidth Control > Create New Rule > [Configure the way you want] Step 3: Create Class Rule QoS in Omada: Transmission > Gateway QoS > Class Rule > Create New Class Rule > [Fill info] Make sure the Service Name is the Service you created in Step 1 Good hunting!

@@deadmeats hello man, thank you very much. i will try this on my environment. Great to know more about this configuration from you, it's very useful. If you don't mind, let us keep more contact to discuss deeper about Omada.

@@Raden.Mas.Romo.Unggul.Sejagat heya, you can always post your questions here or any of my other videos. I try to get to them whenever I have time. I also highly suggest posting in the reddit forum, and contacting official community and tech support. I started adding these links to all my newer video description now, because many are not sure where to get support. I'll post the links below: If you need technical assistance: * Official Forum - community.tp-link.com/en/business/forum/794 * Official Tech Support - www.tp-link.com/us/support/contact-technical-support/ * Reddit - www.reddit.com/r/TPLink_Omada/ * Big YT Channels - th-cam.com/users/results?search_query=tplink+omada Good hunting!

@@deadmeats thank you man 🙏

hey there @life2enjoi , salamat sa pagbisita sa channel. malamang eh hindi mo sya na-add sa DNS Access List. Sensya na at di ko sya na-cover dito, kasi kaka-discuss ko lang sya sa previous episode LC77, starting at 27:18 (link sa baba, saktong timestamp). haba kasi lalo ng video pag na-include ko lahat ng parts, saka dati may nagreklamo, ulit ulit daw hehe. anyway, try mo to: Services > DNS Resolver > Access List > Add > [Fill Up Details] Make sure you add all your IP networks that needs access i.e. 192.168.100.0/24. Kung may time ka, check mo yung link sa baba para sa exact steps. Okidoks.... LC77: th-cam.com/video/2V4f_kxMN9s/w-d-xo.htmlsi=FdlueY9LNTk4ov-I&t=1638

@@deadmeats salamat boss.. naka setup naman lahat ang mali lang rules sir.. address nagamit ko nde subnet. salamat ulit. oks tong channel mo OMADA X PFSENSE!

hey there @unrelativistic, thanks for dropping by the channel. And I agree, with anything about security, it's always a cat/trap-and-mouse approach. Build a better cat/trap to catch more mouse, and mouse evolves to get around the cat/trap :). If you are really paranoid though, you can do whitelisting and just block everything except those you want to go out ;)

hey @Shotgonaso , thank you for dropping by!!! It's a bit old, so I am glad you still found it useful. The new video is pinned in the top comment. Thanks again!

hey @michaelmcallister711, thanks for dropping by and thanks for the feedback :)

hey @waltmummert393, thanks for dropping by the channel! Good hunting!

hey @stanleypang1614, thank you for dropping by the channel. i just tested this and you can still block Port 53 as long as the ACL is defined on the Switch. If you would like to deny internet access from the Gateway, make sure direction is LAN > WAN, then select Source Network, and Destination is IP Group : IP Group any (no port required). Good hunting!

hey @mmo-tech, your "logical" set up sounds like my recently released video (LC79, see link below). Your SX3008F is equivalent to my SG2008 (not in specs, but in their role) as it's the main core/distribution and Layer 3 Switch. But just in case it's different, yes you got things right. Since you will be configuring the Switches in Omada (with their VLANs), the only thing you need to make sure is that the ports that SX3008F and another switch (i.e. SX3206HPP or SG3210XHP-M2) have the profile "All". You don't really need to create a new Profile since the other two switches are just "Access Switches" . This video uses multiple Layer 3 Switches, but your set up only has one so you don't need to create L3ALL, the default "All" should work for you. LC79: Replace Omada Gateway with pfSense: th-cam.com/video/okNQ1gZKyQ8/w-d-xo.htmlsi=qQGs5aqoujhGTP_D

hey @user-tl2to2mm6r, thanks for dropping by. if you just want the user to stop "using" their time, you can set up the voucher as "Client Duration" (i.e. how long is the client connected). Every time the client disconnect, the duration stops. However, most use I have seen is "Voucher Duration", i.e. if Voucher Duration is 1 hour but client only used 15min, it will still expire after 1hour. You can also force expire a voucher using Voucher Manager. You can find more info here: static.tp-link.com/upload/manual/2024/202405/20240517/1910013634_Omada%20SDN%20Controller_User%20Guide_REV5.14.pdf Good hunting!

hey there @mmo-tech, thanks for dropping by. the L2ALL profile is useful if you have multiple Layer 3 Switch environments. If you only have one Layer 3 switch, you do not have to worry about this implementation. But if you have multiple, let's say, two(2) Layer 3 Switches (A and B) in completely isolated implementation (i.e. different companies), you need to know which "All" you are working with. In L3Switch A, you have VLANs 10 and 20, and L3Switch B, you have VLANs 11 and 21. If you use a normal "All" profile, that profile will have VLANs 1, 10, 11, 20, and 21 (literally, ALL of the VLANs in the Omada). You normally do not want these type of configuration, unless you absolutely understand what you are doing because you will never want these two companies have any mix up whatsoever :). Good hunting!

hey there @dLLund. this device use the term VLAN very loosely. It is an unmanaged switch, but it does offer "device port" isolation (as per manual). I did add those notes in 1:59 and 9:01. Steamemo never mentioned 802.1q VLAN, just "AI VLAN" which is "port isolation" :)... Hope that helps...

hey there @mohamedramalybary576, thanks for dropping by the channel. I can get to my Omada interface because my model is operating in "bridge" mode. Good hunting!

hey there @xxbloodreinaxx9917, sorry to hear about it. I don't have this keyboard anymore and I can't find the manual for it. It is very similar (if not the same) as VicTsing PC355A so if you can find anyone who have that keyboard, then you can check that one out. In the mean time, I suggest you try "forgetting" the keyboard on the device it is paired and see if that will work. Also it has BT1 and BT2, try if the other one is not paired and use that instead. Worst case scenario, use the 2.4Ghz dongle. I know they are not what you are asking, but just offering alternatives in case you have not tried those. Wish you all the best!

@@deadmeats thank you so much!!!!! The help you provided is still very much appreciated!!!

@@xxbloodreinaxx9917 heya, at 00:59 of this video, it shows the "BT" label on the ESC key (upper left key). It means you can hold and press Fn1 (or maybe Fn2) + ESC key. You may need to hold down both Fnx + ESC at the same time to go into pairing mode i.e. press Fn1 + ESC at same time for 5s (or 10s) and check. If that doesn't work, try Fn2 + ESC and do the same thing. I hope you are able to get it to work!.

@@deadmeats it did!!! Thank you!!!!!

hey @Alden351 , thanks for stopping by the channel. If you are going to deploy network to any critical environment (i.e. involves safety), I highly suggest you reach out not just to TP Link directly but to other manufacturers and vendors as well. TP Link Omada is mostly suited for small/medium business but they may have enterprise-grade equipment or equipment better suited for your specific environment. For example, will you need High Availability? With current switches, you can have it with Omada but not for their Gateways (pre-2024 release). According to TP Link Omada use-cases, their target sectors are Hospitality, Education, Retail, Office, and Catering. They also have decent tools in their websites to help you decide. You can find more info here: Environments - www.tp-link.com/us/omada-sdn/ Deployment Advisor - www.tp-link.com/us/smb/select-product/ Good hunting!

@@deadmeats Thank you very much for answering my Query I appreciate it very much. also for the links. God Bless you more.

@@Alden351 you are very welcome! Wish you all the best!

hello @svetoslavvalchanov5080, welcome to the channel and thanks for dropping by. The Omada Gateway (which includes ER707-M2) is a Gateway Router and in TP Link world , this means, it can not support trunk ports. I am not familiar with your Asus router, but your SG3428MP is a Switch. It can not do the "WAN" function of your Asus Router. However, your switch can do Layer 3 Switching so you can definitely use your SG3428MP to adapt the settings I am showing here. You will need to configure your Asus router to have static routes pointing to your L3 Switch so that your L3 Switch clients can have internet access. I have a video that will reflect your set up, but instead of using an Asus Router, I am using a non-Omada Router. You will need to adopt the settings of my non-Omada router to your Asus router, but the general steps are the same. You can find the video here: th-cam.com/video/D7al4Yw21bI/w-d-xo.htmlsi=2aEqibZqGuvh4TFK You can find a write up about it here: community.tp-link.com/en/business/forum/topic/667126 Good hunting!

hello @necatibilen4130, each network device from different network vendor have different ways of configuring VLANs. If you are not using Omada, I can only suggest that you refer to your device manual or contact your vendor manufacturer for technical support. You can also reach out to big TH-cam channels since they offer paid technical support. Good hunting!

hey there @necatibilen4130, a switch port with multiple VLANs is normally referred to as "trunk" port. Traditionally, trunk port is used to connect between two switches. However, trunk ports can be used with non-switch devices as well for example, one cable going to your VoIP Phone and that phone have another port that goes to the PC. Because the switch port the Phone is connected to have 2 (or more) VLANs, the switch port can support both the Phone and the PC with just one port port on the switch. If you are new to networking, I suggest you start with basics and there are many topics covering that in YT! Good hunting!

heya @Fragnatix, the major difference is that the Gateway is Stateful and the Switch isn't. Good hunting!

@@deadmeats Right, it seems that the stateful rules should be on the switch level too. At least, omada shows options of one way ACL but it isnt. Any how, at least we can do this on the gateway

hey @NaseebjanNaseebjan-h2t, it is huge :)

Hello @DaKabayanTek, check mo yung SG-3200 series for budget versions. Kung meron ka pang extra $$$, check mo rin ang SG-3400 series or SG-3400X series (yung X usually means 10g ports). Heto yung official list ng TP Link: www.tp-link.com/us/business-networking/omada/switch/ Good hunting!

@@deadmeats Thank you brother. Looking for a video na pwede kong i-access ang multiple vlans...