Hi like all your previous videos this is a very informative video and thanks for responding to my query. That clarifies. 😃😃😃 I have a quick question, I have the following set up Gateway--> SX3008F, SX3008F-->SX3206HPP and SX3008F-->SG3210XHP-M2. The SX3008F is the aggregator. All VLANs are to be handled by SX3008F. SX3206HPP has all devices on a single VLAN i.e. Home/Nas (VID: 10), SX3206HPP houses Lab(VID:20) and IOT(VID: 30). Also I have a separate Management VLAN (VID:40). All Switches and OC200 are to be managed through VID 40. My Gateway is handled separately via Simple modem+router in the future OPNSense + modem. If I understand your explanation correctly the interface port between switches needs to be on profile L3All (contains all VID 10-40) and the individual switches need to enable the VLANs that they currently house, and the management VLAN in the VLAN interface in the config section. Is this the correct assumption or am I still assuming something wrong? I understand it might be a very specific question. But if you get some time and can answer then it would be a great help. In any case thanks in advance. 🙏🙏🙏
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: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-okNQ1gZKyQ8.htmlsi=qQGs5aqoujhGTP_D
Hello, many thanks for the content you are producing, it has been really helpful and educative for me. However I have a question. Maybe I am stupid and missing something, but how would I achieve in Layer 3 switching a fixed IP addresses for clients. ie. I created a VLAN (type VLAN - not an interface) say .30.0 for my cameras, since I have them set in NVR with respective IP addresses I want to set a fixed IP for each camera from within omada, some of my cameras are cameras without webinterface and setting fixed ip on them is really tedious process. when i have them connected to VLAN (type) interface I can just in the client config tick a box "use fixed IP" reboot camera and bang... it has an IP I have assigned in omada. Is this achievable with L3 VLANs routing? Thanks in advance.
hey there @PetrFence, welcome to the channel and thanks for the kind words. Don't worry, you are not stupid. I have not seen this feature in Omada as well. It could be that we're both missing it, but since this important for you, you can check with TP Link. If the feature is not (yet) available, you can submit this as a feature request. If it is, then it's just a matter of the tech team providing you info on how to set it up in the Controller. Good hunting!
heya @Juuurinha, thanks for the kind words. Unfortunately, TP Link Gateways doesn't provide DNS for IPv4 or IPv6. You can sort of use mDNS but only for supported devices and only for basic name resolution and none of the features by AdGuardHome such as AdBlocking and all the fancy stuff. You can try PiHole and see if that will work for you. Here's an article I found about PiHole and IPv6: discourse.pi-hole.net/t/pi-hole-and-ipv6-how-to-make-it-work/58503/2 Good hunting!
