Did you try setting up VLAN tagging up on your router? Normally traffic is untagged and arrives untagged over VLAN1, from what I understand, if you enable VLAN mode it will start tagging the traffic coming out of the ports to VLAN tags, so whatever you connect to the uplink port needs to understand VLAN tags (can be a NIC or another switch/router). Or you need to use another switch to untag that traffic to a specific port again.
I think it creates a VLAN for each port, then only the uplink/SFP port is a member of all VLANS. In addition it may also be that it requires you to tag VLAN with your clients (cameras) on each of those ports.
I think this extend function is designed to create a VLAN trunk between 2 of these switches using the uplink ports, then each port 's VLAN ID is trunked to the other switch creating 8 VLANS, so port 1 mapped to port 1 on the other switch. This is my best guess!
Okay the only way the Vlan will work on these unmanaged switches that have the magic vlan button and still have access to the outside world is that you have to be using the SFP port. they really should specify that in documentation, but they dont. But if you have an SFP try it out, works great on separating them from one another. you cant "set them up" with in the switch, but in pfsense you can, but again it has to all be though the SFP port in order to function.
The point of VLAN is creating a virtual LAN (invite only), Meaning.. any NIC that is not configured to run on that VLAN is totally unaware of the presence of DATA going trough the cable. Assign the VLAN to your Pfsense box and it should work as planned.
I also have 8port gigabit version. 1 uplink. It has VLAN switch. I haven't tried feeding vlans on it since you can't control what port will be untagged and and what VLAN ID.
Ok, this is interesting so I did some looking into. This is a strange device, and IMHO has very little use, but anyway. So what this device does is take all 8 VLAN's (tagged traffic) and puts them into a VLAN trunk on the uplink port(s?) like you eluded to. So, you were on the right track, but pfsense requires a little more configuration. You have to define the vlan(s) on the interface they are coming in on, then assign the interfaces, and then create the firewall rules to enable them to talk to each other. The reason why everything stopped talking is by default all traffic is on "vlan 1", which is untagged. At the point that the VLAN's are enabled, you all the sudden get all tagged traffic only. pfsense doesn't know how to route the traffic. It's basically like connecting 8 different networks to one cable. pfSense has to know what to do with all those networks. I also would like to clarify (as it seemed in the video) SFP is a "modular" port, you can put fiber, copper (twinax, etc), baseT, etc modules in there depending on your needs. What's kind of a bummer with this device is that it's not even SFP+, so you're still limited to 1Gig. Anyone reading this and is interested in things like vlans, I recommend getting a used CISCO/HP/DELL managed switch instead of this thing. There is a lot of disadvantages, namely not being able to define the vlan numbers, being restricted to 1-8 is terrible. You can't really use this as a "backbone" switch, because your bandwidth is very limited. I just don't understand the use of it.
Further, sitting here thinking about it, I don't understand who the market for this would be. If you don't know what VLAN's are, then you wouldn't be implementing them and you would just buy a cheaper unmanaged switch. If you do know what they are, then you would need more control than a button. If you are learning about VLAN's, you still need more control. If you are implementing this in a commercial environment, then you still need more control, and you need a reputable brand.
@@mikerm19 Perhaps the one use case is IP cameras and/or access points? Separating all the ports gives it a back haul to the router, but prevents compromising other devices on the same switch. For example, an IP camera outside a business. Someone disconnects the camera and connects a laptop hoping to infect other cameras with a RAT. Because that camera/port can only talk to the NVR (hopefully more secure, but probably not), the attacker can't infect other cameras. Or maybe you want 8 different APs connected for 8 different guest networks? Perhaps these would be going to apartments or hotel rooms? Really can't think of any plausible reason to use this over a proper managed switch though.
I almost think this would work or almost work for what I need. I have a 36 Ch NVR that has 4 Gig (non POE ports). According to its diagrams, you would chain a POE switch off each those Four Gig ports (or use POE injectors, Yuck). I think this switch will or could work for what I want to do, except my concern is that maybe the total power budget is too small depending on the cam's power needs. I mean 8 Ports x 30w (port Max) would be 240watts, this has a max budget of 120Watts. Even if you back off the power need to say 24 watts, that would still be 192 watts and over budget. All things being equal, across the 8 ports you'd have a max of 15 watts per port.. Is that making sense? I don't need the cams on each port (1-8) to reach each other, just that they be able to reach the NVR upstream from the POE switch.
I have a MokerLink 18 Port POE G162G that has the Extend slidable switch as well. For Cameras this is great. each port is isolated. In one of the uplinks I had to connect an access point so that the cameras could get WiFi (Internet). Then the other uplink is trunked to another switch or router.
If I was to design a small unmanaged gigabit switch for novice users say between 8 and 16 ports that does NOT have a silly little "vlan" button on it, what kinds of features would you want?
I totally understand how someone that is not experienced with VLANs will how no idea what is going on. Jason if it is unmanaged I think like everyone else how commented since it will have no idea which vlan will come into a port they need to be trunked ports. Which means it will expect all VLANs 1-4095. You have to tagg you devices to communicate on that vlan vlan themselfs to work. The other idea is that maybe the switch is just tagged on a predefined vlan for every port? However I so little to no use for this implementation.
I have 10 ports PoE switch that has a 3-way switch, It can act like a normal unmanaged switch, VLAN mode, or extended mode. On their manual, VLAN will be applied to port 1-8 but you can access via uplink ports, this helps broadcast storm between PoE device. Extended mode is used for long distance UTP cable (>100 meters
Vlans isolate by design. Not sure how you could get an unmanaged switch off vlan1 unless all the ports are trunks. Definitely strange but never the less router on a stick with sub interfaces is necessary for inter vlan communication.
It sounds pointless outside of creating a highspeed intranet of servers isolated from the net, which would want a higher throughput then that switch gives you anyways. Sounds like a pointless gimmick for sales.
I guess you need a master managed switch from the same brand to use vlans and manage them from the master switch, each port must have its own vlan id . Its my guess 😉🔅🔅🔅
I'm also checking these switches , luckily didn't bought one since it's unmanged switch and will force you to change Devices Vlan tag instead of doing it on switch itself lol ,. 1click vlan tag my ass
Yeah. if you flip the switch and all the ports were turned into access ports for each vlan, the lights should still blink... I think you may have a bad unit.
@@jlficken What is that port above the uplink port? I presumed this was some sort of chinese knock hackware, and it was like a kludged together from higher and and lower end parts. I looked at it and said, ok there is some sort of console port too. I guess they just stuck an extra port on for the heck of it? (not being sarcastic towards you, products like this mystify me in terms of why do they even bother).
@@thtadthtshldntbe The labeling makes it look like they are both uplink ports. I'd guess they intend one to be used from say your router to this switch and then the other one is used to uplink to another switch in your network from this switch.
linking this video here as i bought this switch on the buy it as it works and supports vlans. Yup it does I have zero problems with this switch. Please Note flash the firmware to the latest as it fixes a bug, Jason if your looking for a cheep good managed switch thats not too hard but supports vlans buy this switch its 40 buxs. th-cam.com/video/5ohLAFHnOHg/w-d-xo.html
Before you make videos make sure its running. What a waste of my internet data. By the way, use vlan tagging on an uplink port and tagged it in the router or switch.
yo stop making these videos if they just don't contain any info at all. If I wanted to see an unmanaged switch review I would have searched for it. Like it doesn't add anything at all in the video, and I asume the switch is more expensive than a regular unmanaged switch. So the point is that this doesn't help or give advise to me at all. Why? That is the reason that Linus is so succesfull: he doesn't post things that ain't useful. And he is just honest I mean I would call the thing (also because of bad info from the company) just a piece of sh*t. (now I do see some comments about other ways to get it to work like untagged traffic etc.) But still, from what I can see from your video it is just a junkswitch with a big name on it. Your other videos are great but this just was a bit unnecessary...
Did you try setting up VLAN tagging up on your router? Normally traffic is untagged and arrives untagged over VLAN1, from what I understand, if you enable VLAN mode it will start tagging the traffic coming out of the ports to VLAN tags, so whatever you connect to the uplink port needs to understand VLAN tags (can be a NIC or another switch/router). Or you need to use another switch to untag that traffic to a specific port again.
I think it creates a VLAN for each port, then only the uplink/SFP port is a member of all VLANS. In addition it may also be that it requires you to tag VLAN with your clients (cameras) on each of those ports.
I think this extend function is designed to create a VLAN trunk between 2 of these switches using the uplink ports, then each port 's VLAN ID is trunked to the other switch creating 8 VLANS, so port 1 mapped to port 1 on the other switch. This is my best guess!
Okay the only way the Vlan will work on these unmanaged switches that have the magic vlan button and still have access to the outside world is that you have to be using the SFP port. they really should specify that in documentation, but they dont. But if you have an SFP try it out, works great on separating them from one another. you cant "set them up" with in the switch, but in pfsense you can, but again it has to all be though the SFP port in order to function.
The point of VLAN is creating a virtual LAN (invite only), Meaning.. any NIC that is not configured to run on that VLAN is totally unaware of the presence of DATA going trough the cable.
Assign the VLAN to your Pfsense box and it should work as planned.
The switch didn't try any communication though, at least according to the lights.
I also have 8port gigabit version. 1 uplink. It has VLAN switch. I haven't tried feeding vlans on it since you can't control what port will be untagged and and what VLAN ID.
Ok, this is interesting so I did some looking into. This is a strange device, and IMHO has very little use, but anyway. So what this device does is take all 8 VLAN's (tagged traffic) and puts them into a VLAN trunk on the uplink port(s?) like you eluded to. So, you were on the right track, but pfsense requires a little more configuration. You have to define the vlan(s) on the interface they are coming in on, then assign the interfaces, and then create the firewall rules to enable them to talk to each other. The reason why everything stopped talking is by default all traffic is on "vlan 1", which is untagged. At the point that the VLAN's are enabled, you all the sudden get all tagged traffic only. pfsense doesn't know how to route the traffic. It's basically like connecting 8 different networks to one cable. pfSense has to know what to do with all those networks. I also would like to clarify (as it seemed in the video) SFP is a "modular" port, you can put fiber, copper (twinax, etc), baseT, etc modules in there depending on your needs. What's kind of a bummer with this device is that it's not even SFP+, so you're still limited to 1Gig. Anyone reading this and is interested in things like vlans, I recommend getting a used CISCO/HP/DELL managed switch instead of this thing. There is a lot of disadvantages, namely not being able to define the vlan numbers, being restricted to 1-8 is terrible. You can't really use this as a "backbone" switch, because your bandwidth is very limited. I just don't understand the use of it.
Further, sitting here thinking about it, I don't understand who the market for this would be. If you don't know what VLAN's are, then you wouldn't be implementing them and you would just buy a cheaper unmanaged switch. If you do know what they are, then you would need more control than a button. If you are learning about VLAN's, you still need more control. If you are implementing this in a commercial environment, then you still need more control, and you need a reputable brand.
@@mikerm19 Perhaps the one use case is IP cameras and/or access points? Separating all the ports gives it a back haul to the router, but prevents compromising other devices on the same switch.
For example, an IP camera outside a business. Someone disconnects the camera and connects a laptop hoping to infect other cameras with a RAT. Because that camera/port can only talk to the NVR (hopefully more secure, but probably not), the attacker can't infect other cameras.
Or maybe you want 8 different APs connected for 8 different guest networks? Perhaps these would be going to apartments or hotel rooms?
Really can't think of any plausible reason to use this over a proper managed switch though.
I almost think this would work or almost work for what I need. I have a 36 Ch NVR that has 4 Gig (non POE ports). According to its diagrams, you would chain a POE switch off each those Four Gig ports (or use POE injectors, Yuck).
I think this switch will or could work for what I want to do, except my concern is that maybe the total power budget is too small depending on the cam's power needs.
I mean 8 Ports x 30w (port Max) would be 240watts, this has a max budget of 120Watts.
Even if you back off the power need to say 24 watts, that would still be 192 watts and over budget.
All things being equal, across the 8 ports you'd have a max of 15 watts per port..
Is that making sense? I don't need the cams on each port (1-8) to reach each other, just that they be able to reach the NVR upstream from the POE switch.
I have a MokerLink 18 Port POE G162G that has the Extend slidable switch as well. For Cameras this is great. each port is isolated. In one of the uplinks I had to connect an access point so that the cameras could get WiFi (Internet). Then the other uplink is trunked to another switch or router.
If I was to design a small unmanaged gigabit switch for novice users say between 8 and 16 ports that does NOT have a silly little "vlan" button on it, what kinds of features would you want?
I totally understand how someone that is not experienced with VLANs will how no idea what is going on. Jason if it is unmanaged I think like everyone else how commented since it will have no idea which vlan will come into a port they need to be trunked ports. Which means it will expect all VLANs 1-4095. You have to tagg you devices to communicate on that vlan vlan themselfs to work. The other idea is that maybe the switch is just tagged on a predefined vlan for every port? However I so little to no use for this implementation.
I have 10 ports PoE switch that has a 3-way switch, It can act like a normal unmanaged switch, VLAN mode, or extended mode.
On their manual, VLAN will be applied to port 1-8 but you can access via uplink ports, this helps broadcast storm between PoE device.
Extended mode is used for long distance UTP cable (>100 meters
I just bought this recently, and I can't figure out VLAN. A tutorial at this point might be helpful from the manufacturer.
I have the same switch - ports 8, and the two uplink ports suddenly died on mine...
Do you need two routers connected SFP to SFP? Then VLAN 1 would connect to VLAN 1, 2 to 2 etc... Just a thought.
Do you have a router that allows you to create sub interfaces so you could have intervlan routing
Vlans isolate by design. Not sure how you could get an unmanaged switch off vlan1 unless all the ports are trunks. Definitely strange but never the less router on a stick with sub interfaces is necessary for inter vlan communication.
Connect to pfsense and do a packet capture
is that poe switch still alive?
It sounds pointless outside of creating a highspeed intranet of servers isolated from the net, which would want a higher throughput then that switch gives you anyways. Sounds like a pointless gimmick for sales.
I can use poe and poe+ ethernet switch
I guess you need a master managed switch from the same brand to use vlans and manage them from the master switch, each port must have its own vlan id . Its my guess 😉🔅🔅🔅
Exactly the Same case With me i Have Bought the 4+2 ports switch
I'm also checking these switches , luckily didn't bought one since it's unmanged switch and will force you to change Devices Vlan tag instead of doing it on switch itself lol ,. 1click vlan tag my ass
Yeah. if you flip the switch and all the ports were turned into access ports for each vlan, the lights should still blink... I think you may have a bad unit.
You probably have to console in to it, and command set up the vlans.
There's no console port though that I see. Do you mean SSH into it?
Either way though that would mean that it's a managed switched (Layer 2 at least).
@@jlficken What is that port above the uplink port? I presumed this was some sort of chinese knock hackware, and it was like a kludged together from higher and and lower end parts. I looked at it and said, ok there is some sort of console port too. I guess they just stuck an extra port on for the heck of it? (not being sarcastic towards you, products like this mystify me in terms of why do they even bother).
@@thtadthtshldntbe The labeling makes it look like they are both uplink ports. I'd guess they intend one to be used from say your router to this switch and then the other one is used to uplink to another switch in your network from this switch.
linking this video here as i bought this switch on the buy it as it works and supports vlans. Yup it does I have zero problems with this switch. Please Note flash the firmware to the latest as it fixes a bug, Jason if your looking for a cheep good managed switch thats not too hard but supports vlans buy this switch its 40 buxs.
th-cam.com/video/5ohLAFHnOHg/w-d-xo.html
Before you make videos make sure its running. What a waste of my internet data. By the way, use vlan tagging on an uplink port and tagged it in the router or switch.
According to the Amazon reviews ....everyone likes it. Maybe you got a bad unit ?
yo stop making these videos if they just don't contain any info at all. If I wanted to see an unmanaged switch review I would have searched for it. Like it doesn't add anything at all in the video, and I asume the switch is more expensive than a regular unmanaged switch. So the point is that this doesn't help or give advise to me at all. Why? That is the reason that Linus is so succesfull: he doesn't post things that ain't useful. And he is just honest I mean I would call the thing (also because of bad info from the company) just a piece of sh*t. (now I do see some comments about other ways to get it to work like untagged traffic etc.) But still, from what I can see from your video it is just a junkswitch with a big name on it. Your other videos are great but this just was a bit unnecessary...
Kool
I’ll stick to my unifi switches thanks 👍
First
FOURTH!