This offer matches our front page deal from March 2025 and also our extremely popular front page deal from February 2025 which earned over 110 thumbs up.
Rated 4.7 out of 5 stars on Amazon based on over 165 customer reviews.
Please see the original post for additional details and/or view the Wiki and forum comments for further helpful discussion if available.
This collaborative space allows users to contribute additional information, tips, and insights to enhance the original deal post. Feel free to share your knowledge and help fellow shoppers make informed decisions.
This offer matches our front page deal from March 2025 and also our extremely popular front page deal from February 2025 which earned over 110 thumbs up.
Rated 4.7 out of 5 stars on Amazon based on over 165 customer reviews.
Please see the original post for additional details and/or view the Wiki and forum comments for further helpful discussion if available.
Model: NETGEAR 8-Port Gigabit Ethernet Plus Switch (GS308E) - Desktop or Wall Mount, Home Network Hub, Office Ethernet Splitter, Silent Operation
Deal History
Deal History includes data from multiple reputable stores, such as Best Buy, Target, and Walmart. The lowest price among stores for a given day is selected as the "Sale Price".
Sale Price does not include sale prices at Amazon unless a deal was posted by a community member.
Our community has rated this post as helpful. If you agree, why not thank aegrotatio
I just set mine up. I don't see any problem with a managed switch for only $25, especially with VLAN management.
Anyway, you can provision two sets of two ports with link aggregation. That's where they get the "2.5 Gb" figure from.
No one uses 1G Ethernet these days, it's 2.5 or you might as well use dial up
Not true at all. Even if you use 2.5gbe for some of your network like your NAS and PCs, you'll still have things that only need gigabit. For example, your home media center, where you might be connecting your streaming box, gaming consoles, etc. Those are going to be capped at your WAN speeds, which is still a gigabit or lower for most of us.
Not true at all. Even if you use 2.5gbe for some of your network like your NAS and PCs, you'll still have things that only need gigabit. For example, your home media center, where you might be connecting your streaming box, gaming consoles, etc. Those are going to be capped at your WAN speeds, which is still a gigabit or lower for most of us.
Noob question, but I know the networking gurus lurk these threads. Can this be used to VLAN out different SSIDs on a TP Link AP (EAP610)? I do not have an Omada controller and just use it as an AP configured with the app. Thanks.
Like
Helpful
Funny
Not helpful
Sign up for a Slickdeals account to remove this ad.
Our community has rated this post as helpful. If you agree, why not thank artcab
Quote
from jmm1122
:
Noob question, but I know the networking gurus lurk these threads. Can this be used to VLAN out different SSIDs on a TP Link AP (EAP610)? I do not have an Omada controller and just use it as an AP configured with the app. Thanks.
The VLANs have to be defined at the router level. Neither this switch nor the EAP610 can be used to define VLANs, only to assign certain ports to certain VLANs on the switch, or to associate an existing VLAN with an SSID in the case of the EAP610 AP; but again in both cases the VLANs have to be defined at the router level, these devices can't create VLANs, they can only see them and assign them at the port level if needed (they are "VLAN aware", not capable of defining VLANs themselves).
Since your EAP610 is VLAN aware, it could be hard wired to a LAN port on your router (where the VLANs are defined), and that hardwired connection will carry both untagged traffic and tagged traffic (tagged with the VLAN ID(s) defined at the router level) to the EAP610, which can see and assign those VLAN IDs to specific SSIDs.
The switch in this deal will not allow you to define a VLAN, only to tag ports on the switch to specific VLAN IDs defined at the router level and carried to it via an ethernet cable (in my case, I have hardwired IoT hub devices on this VLAN aware switch that are connected to ports defined to segregate and carry my IoT VLAN ID only).
If your router doesn't support VLANs, you'll need to get one that does, and at that point you can wire the EAP610 to the router and do your VLAN assignments to specific SSIDs. The only reason you'd need this VLAN aware switch is if you plan to hardwire devices like IoT hubs to VLAN specific ports on the switch.
Our community has rated this post as helpful. If you agree, why not thank FishKilla
Quote
from artcab
:
The VLANs have to be defined at the router level. Neither this switch nor the EAP610 can be used to define VLANs, only to assign certain ports to certain VLANs on the switch, or to associate an existing VLAN with an SSID in the case of the EAP610 AP; but again in both cases the VLANs have to be defined at the router level, these devices can't create VLANs, they can only see them and assign them at the port level if needed (they are "VLAN aware", not capable of defining VLANs themselves).
Since your EAP610 is VLAN aware, it could be hard wired to a LAN port on your router (where the VLANs are defined), and that hardwired connection will carry both untagged traffic and tagged traffic (tagged with the VLAN ID(s) defined at the router level) to the EAP610, which can see and assign those VLAN IDs to specific SSIDs.
The switch in this deal will not allow you to define a VLAN, only to tag ports on the switch to specific VLAN IDs defined at the router level and carried to it via an ethernet cable (in my case, I have hardwired IoT hub devices on this VLAN aware switch that are connected to ports defined to segregate and carry my IoT VLAN ID only).
If your router doesn't support VLANs, you'll need to get one that does, and at that point you can wire the EAP610 to the router and do your VLAN assignments to specific SSIDs. The only reason you'd need this VLAN aware switch is if you plan to hardwire devices like IoT hubs to VLAN specific ports on the switch.
Oh Lord, this post is so fraught with wrong information I don't even know where to begin.
You have no idea what you are talking about and should not post in the managed switch thread.
Vlans are layer 2. Switch is layer 2. Routers are layer 3. They route between Vlans. You can google that and read, then maybe come back and post LOL
I have both, and consider them interchangeable, and buy based on price when I need one. They both obviously have a different web interface menu system for defining VLANs, neither one more or less good than the other, both intuitive enough and can be figured out in a couple minutes. I have both in use with no issues, the Netgear for years and the TP-Link version for about 6 months. I am really only using them to segregate VLANs to hard wire IoT devices (hubs that support ethernet connectivity) and both work fine - I can't speak to other managed features that may be more important to you. HTH
Thinking about doing what you've done with IoT devices using a VLAN. I want to separate my IoT stuff (mostly but not all wifi) from the four hard wired machines that are used for work. First timer trying anything like that. Using a small older VLAN capable router from Ubiquity and their 'saucer' access points, but like all their stuff, the router was not meant to be configured by mere mortals.
From what I read, the VLAN actually has to be created in your router, then you can use a switch like this to distribute the two segments. In other words, you can't just come from a single segment router and then use something like this to create two fully isolated VLAN segments. Is that right? Thanks.
Thinking about doing what you've done with IoT devices using a VLAN. I want to separate my IoT stuff (mostly but not all wifi) from the four hard wired machines that are used for work. First timer trying anything like that. Using a small older VLAN capable router from Ubiquity and their 'saucer' access points, but like all their stuff, the router was not meant to be configured by mere mortals.From what I read, the VLAN actually has to be created in your router, then you can use a switch like this to distribute the two segments. In other words, you can't just come from a single segment router and then use something like this to create two fully isolated VLAN segments. Is that right? Thanks.
Yes, the VLAN has to be defined on the router, in my case a pFsense device. Once it's defined on the router, the managed functions on these switches can be used to isolate certain ports to the defined VLAN(s). My original response says "defining" but should say "assigning" when referring to the switch in this deal.
I have both, and consider them interchangeable, and buy based on price when I need one. They both obviously have a different web interface menu system for defining VLANs, neither one more or less good than the other, both intuitive enough and can be figured out in a couple minutes. I have both in use with no issues, the Netgear for years and the TP-Link version for about 6 months. I am really only using them to segregate VLANs to hard wire IoT devices (hubs that support ethernet connectivity) and both work fine - I can't speak to other managed features that may be more important to you. HTH
can you just plug and play without needing to configure anything?
can you just plug and play without needing to configure anything?
I don't know as I don't use it that way - I'd suggest at least assigning a static IP outside of your DHCP range and changing the default password though.
Top Comments
30 Comments
Sign up for a Slickdeals account to remove this ad.
Our community has rated this post as helpful. If you agree, why not thank aegrotatio
Anyway, you can provision two sets of two ports with link aggregation. That's where they get the "2.5 Gb" figure from.
I think you fed the troll.
Sign up for a Slickdeals account to remove this ad.
Our community has rated this post as helpful. If you agree, why not thank artcab
Since your EAP610 is VLAN aware, it could be hard wired to a LAN port on your router (where the VLANs are defined), and that hardwired connection will carry both untagged traffic and tagged traffic (tagged with the VLAN ID(s) defined at the router level) to the EAP610, which can see and assign those VLAN IDs to specific SSIDs.
The switch in this deal will not allow you to define a VLAN, only to tag ports on the switch to specific VLAN IDs defined at the router level and carried to it via an ethernet cable (in my case, I have hardwired IoT hub devices on this VLAN aware switch that are connected to ports defined to segregate and carry my IoT VLAN ID only).
If your router doesn't support VLANs, you'll need to get one that does, and at that point you can wire the EAP610 to the router and do your VLAN assignments to specific SSIDs. The only reason you'd need this VLAN aware switch is if you plan to hardwire devices like IoT hubs to VLAN specific ports on the switch.
Our community has rated this post as helpful. If you agree, why not thank FishKilla
Since your EAP610 is VLAN aware, it could be hard wired to a LAN port on your router (where the VLANs are defined), and that hardwired connection will carry both untagged traffic and tagged traffic (tagged with the VLAN ID(s) defined at the router level) to the EAP610, which can see and assign those VLAN IDs to specific SSIDs.
The switch in this deal will not allow you to define a VLAN, only to tag ports on the switch to specific VLAN IDs defined at the router level and carried to it via an ethernet cable (in my case, I have hardwired IoT hub devices on this VLAN aware switch that are connected to ports defined to segregate and carry my IoT VLAN ID only).
If your router doesn't support VLANs, you'll need to get one that does, and at that point you can wire the EAP610 to the router and do your VLAN assignments to specific SSIDs. The only reason you'd need this VLAN aware switch is if you plan to hardwire devices like IoT hubs to VLAN specific ports on the switch.
Oh Lord, this post is so fraught with wrong information I don't even know where to begin.
You have no idea what you are talking about and should not post in the managed switch thread.
Vlans are layer 2. Switch is layer 2. Routers are layer 3. They route between Vlans. You can google that and read, then maybe come back and post LOL
From what I read, the VLAN actually has to be created in your router, then you can use a switch like this to distribute the two segments. In other words, you can't just come from a single segment router and then use something like this to create two fully isolated VLAN segments. Is that right? Thanks.
Sign up for a Slickdeals account to remove this ad.