ZYXEL XGS1250-12 1/2.5/5/10G SwitchZYXEL XGS1250-12 1/2.5/5/10G

[Notconnected]

Hi everyone. Am wondering if the

ZYXEL XGS1250-12 1/2.5/5/10G Switch is missing any of the​

features required to run small home network.
All I want to do is connect a few pc's and access my POE camers, but they need to be separated
for security, I do not want the cameras to have access to the internet ever,..
I will also be connecting to an always on low power device that I store files on for backups,
it has a connected USB SSD drive for this purpose.

I am thinking this switch will suit my limited needs, and is not a power hogg either, whcih is important to me.
Does anyone know of any problems with this particular device, should I avoid it, and how does one
allow PC's internet access and disallow cameras access. I currently use a small wifi router to access
the cameras via an offline device, this allows me to see all around the property as it is only the size of
a phone and I take it with me through the house alongside my phone, the cameras are connected
to a monitor for proper viewing when required.

Look forward to your response, thank you all.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[degrub]

Use an NVR that accepts the feed from the cameras. May need an interposing switch if not enough ethernet ports on the NVR. Then interface the NVR to your network through its management port and access the cameras through it. You may have to put the management port on a VLAN if it accesses the internet to get to your phone or if you want remote access. A VPN server (wireguard for example) running on your router with a client on your phone/other PC would give you secure access remotely..

 

[Notconnected]

Use an NVR that accepts the feed from the cameras. May need an interposing switch if not enough ethernet ports on the NVR. Then interface the NVR to your network through its management port and access the cameras through it. You may have to put the management port on a VLAN if it accesses the internet to get to your phone or if you want remote access. A VPN server (wireguard for example) running on your router with a client on your phone/other PC would give you secure access remotely..

Thanks for posting.
I have my camers connected to a NVR that also provides the POE to power them, I currently take a HDMI cable to a large monitor to view the cameras, there is also a mouse and keyboard connected to the NVR so I can navigate to the various camera feeds.
I then took an RJ45 cable from the NVR to my wireless hotspot via a switch, this allows me to use an 8 inch device to view my cameras over RTSP, which I find very convenient instead of being tied to a fixed monitor for when am out around the propert, I can select any camera and view it in full screen from the listed camera feeds on the device.

MY idea is to have only one switch in the network, connect it to my opnsence router, this router then allows internet acces to any device connected to the switch.
I am not at all well versed in setting up switches or routers, but I want to use my 8 inch device over a hotspot so I can view my camera feeds like I do now, but I leave the router off so the cameras can not access the internet, I do not know how to put cameras on a vlan and disallow acces to the internet.

 

[tgl]

I have that exact switch (or at least, what Zyxel was selling under that name three years ago --- possibly there have been hardware revisions since). It's a perfectly-fine basic managed switch; it can do VLAN support, but it has no PoE output.

However, I don't think it's enough for isolating your cameras, unless you're okay with having them completely isolated from the rest of your gear. In that case you could put the cameras and the recording device on one VLAN, with everything else on another one. That setup would act as though you had two switches with no connection between them. But more usually you want some of the PCs to be able to get at the cameras. For that, you'd need cross-VLAN routing, which the XGS1250 can't handle. Some "L3" switches can do that, but more usually people use a router.

 

[Notconnected]

I have that exact switch (or at least, what Zyxel was selling under that name three years ago --- possibly there have been hardware revisions since). It's a perfectly-fine basic managed switch; it can do VLAN support, but it has no PoE output.

However, I don't think it's enough for isolating your cameras, unless you're okay with having them completely isolated from the rest of your gear. In that case you could put the cameras and the recording device on one VLAN, with everything else on another one. That setup would act as though you had two switches with no connection between them. But more usually you want some of the PCs to be able to get at the cameras. For that, you'd need cross-VLAN routing, which the XGS1250 can't handle. Some "L3" switches can do that, but more usually people use a router.

Thank you for posting, I do not know and have not heard of inter vlan routing, I bought
a D-Link 1210 24 port Managed switch that was too cheap to pass up, I do not recall
seeing anything about inter vlan routing in it either, may be some other term is used to
describe this function. Any idea if this model dlink will do that.
Has anyone a link to a tutorial on how this inter vlan routing is set up.
I want my camers on a separate vlan with no internet access, but this
switch will be connected to the internet, and as such how do I prevent the
vlan the cameras are on from accessing the internet, can this be done on
the switch.
Thanks

 

[tgl]

I know zip about D-Link, sorry. However, if it can do VLANs at all then it should be easy to split it into two (or more) logically-isolated switches, if that's enough to solve your problem.
There should be a VLAN configuration panel that allows you to assign one VLAN number as "untagged" on each port, and optionally one or more VLAN numbers as "tagged" on that port. For this use-case, just set up ports in group A as untagged VLAN 1, no tagged VLANs, and ports in group B as untagged VLAN 2, again no tagged VLANs, etc. You can use any VLAN numbers up to 4095, doesn't have to be 1 and 2. However, the switch's own configuration IP address is probably tied to VLAN 1, so whatever port you want to make switch management connections from had better be in VLAN 1. (Alternatively, there might be a setting to change the "management VLAN" from 1 to something else. But if you do, you'd still better be sure that there's a port that's connected to that VLAN.)

Terminology around this seems to vary a bit --- some people refer to a port's untagged VLAN as its native VLAN.