When you get into the realm of VLAN aware switches it's not "what the upstream wifi router told that specific port to do" but what you configured that port to do.pjp wrote:What I'd like to do is use another downstream switch with two VLANs. 1 general use, and 1 for tftp booting or similar.
I've never used a "plug-and-play network extender" switch, but I presume they would only be able to do what the upstream wifi router told that specific port to do. I'm also guessing 1 port can handle only one VLAN
Just a "managed" switch, sometimes referred to as "layer 3", but not necessarily.pjp wrote:What kind of switch would RTR2 need to be to handle at least 2 VLANs. I presume it could not be one of the "network extender" varieties, but I don't know what to look for.
In this use case, possibly, it depends how many LAN ports you need, if it's more than 4 in total then you are better off just getting a managed switch downstream of your router.pjp wrote:The TP-Link BE3600 lists "Tag VLAN", but I'm anticipating that it is RTR2 which should handle the VLANs.

To clarify, you'd need a "VLAN-aware switch", that is, one that supports IEEE standard 802.1Q. I believe most "managed switches" —i. e. those that provide a user interface for configuring the switch— sold these days should be VLAN-aware.Ralphred wrote:Just a "managed" switch, sometimes referred to as "layer 3", but not necessarily.pjp wrote:What kind of switch would RTR2 need to be to handle at least 2 VLANs. I presume it could not be one of the "network extender" varieties, but I don't know what to look for.
A single port can handle multiple VLANs, as Hu said, provided the device supports transmission and reception of VLAN-tagged Ethernet frames, which any VLAN-aware switch should do.pjp wrote:I'm also guessing 1 port can handle only one VLAN?
Ionen wrote:As a packager I just don't want things to get messier with weird build systems and multiple toolchains requirements though
Thanks for clarifying, but that is what I meant. I have sufficient experience to know I should ask questions (my CCNA was from the mid 00s, and I never held a role where it was my primary responsibility). I also thought a port could handle more than one VLAN, but doubted my vague recollection.Ralphred wrote:When you get into the realm of VLAN aware switches it's not "what the upstream wifi router told that specific port to do" but what you configured that port to do.
I'll have to revisit what I've seen available, given what I've read about what Netgear hardware supports.Ralphred wrote:Just a "managed" switch, sometimes referred to as "layer 3", but not necessarily.
That's what I'm leaning towards. 4 probably isn't sufficient.Ralphred wrote:In this use case, possibly, it depends how many LAN ports you need, if it's more than 4 in total then you are better off just getting a managed switch downstream of your router.
I've tried to identify the distinct components, but it seems impractical. I'd still have to identify the switch (which I should have called SW1 instead of RTR2... I hastily tried to be more clear using fewer words). Then I need a WAP. The modem-router is currently provided by the ISP.Ralphred wrote:The problem is that it's become ubiquitous amongst the average user to think of a router as something that is a modem-router-WAP-switch all rolled into one, and the use of VLAN's is generally an SME level solution, meaning you are buying SME level equipment for all 4 components when you go "all in one", in your case you'd only justify the use of an SME level switch.
I probably don't need 2.5G, but it is available without too much additional cost. Residential fibre is supposedly on it's way, but no specific schedule. I've seen ISP related vehicles in the area and have heard it's close by, so who knows. As a hedge, the port could be used to connect to SW1, and eithe rof those TP-Link BE models I think should be able to replace my ISP's modem/router device, though I'd have to verify.Ralphred wrote:When it comes to specifying switches I use d-link for cheap domestic, draytek for decent domestic, HP for cheap commercial, Cisco for decent commercial, but if you anticipate wanting a 2.5G switch within 2 years then TP-link will do, 4 years and you'll get away with netgear.
Well, the device seems much more convenient with less power draw. I'd like to use WoL to shut most of the hardware down when not in use. I've looked for low power devices to take on that role, but few have enough ports or capacity to do much of anything else. On the plus side, the first result for a 4 port NIC was only ~$70.Ralphred wrote:NAT type routing ("masquerading" or "overload") and firewalling happens in software, so personally I've always just stuck a second nic* in my "server" and done it there - seems a waste of time, energy, space and cash to have a little box do what can be done by pppd the kernel and iptables. This also leaves you free to buy a PoE powered WAP and stick it somewhere sensible with a single cable, or get a normally powered one and still not drag your switch/modem and it's associated cabling with it.
I'm not familiar with HP, but Cisco tend to be very loud due to the small screaming fans. Then there's availability and cost. I don't use e-bay, and most companies idea of support is to not provide it. In particular I'm thinking of getting used hardware that has problems.Ralphred wrote:If I were you, I'd get a second hand one gig managed ProCurve or Cisco switch with enough ports to serve your whole network, and consider it the the first step in unrolling the modem-router-WAP-switch bundle.
In theory a good switch should make it easier. I once configured a PC to act as a router, and also used TUN/TAP for VMs on a system. But for 8 or 16 ports, the dedicated solution seems easier. Except for the lack of ssh acccess. All web interfaces are heinous and only exis to make life difficult (in my experience).Ralphred wrote:*though, with a managed Gbit switch you could do it virtually on one nic for most "broadband" set-ups.
I didn't realize how bad consumer grade equipment was, even when target at business use. I doubted my memory on the multiple VLANs/port thing. If I recall, it may have been (then) recommended against for performance considerations.Hu wrote:VLANs are a software construct, so how much or little you can do with them depends heavily on the quality of the software involved. A quality switch can allow multiple VLANs on the same port, and restrict which VLANs that port is allowed to send on.
Managed seems to be the minimum, which I presumed to be the case. The more difficult challenge finding one of sufficient quality to claims made ratio.GDH-gentoo wrote:To clarify, you'd need a "VLAN-aware switch", that is, one that supports IEEE standard 802.1Q. I believe most "managed switches" —i. e. those that provide a user interface for configuring the switch— sold these days should be VLAN-aware.
VLAN-aware switches can be just "layer 2 switches" (only capable of "bridging", i. e. MAC layer forwarding), or "layer 3 switches" (capable of both bridging and IP forwarding). Depending on how you plan to "handle 2 VLANs", you might not need the "layer 3" functionality.
That pretty much guarantees I won't buy Netgear.The switch will prompt you to create a Netgear cloud account to manage the device and offer you 'limited access' to the device until you do so. According to the Netgear knowledge base, however, this 'limited access mode' should still allow you to update the firmware.
There are two ways to work around this:
Block access to 8.8.8.8 from the device in your router's firewall.
Connect the switch to a computer without internet access.
This method sometimes fails. Be prepared to open the device and solder a pin header for serial console. The holes are filled with solder, so having desoldering tools is also highly recommended!
Try this link switches.pjp wrote:OpenWRT seems like a great idea, but I can never find anything on the site that's available, and it generally seems to focus on the all-in-one devices. Which makes sense.
This is same problem everywhere. There is no way to easy identify exact product. You can't even do this in a store because the packaging. And Marketing usually intentionally made it unclear for lesser liability.pjp wrote:Amazon is the only place I see with which I'm familiar. I can find the 8-port on some other sites, as well as the 24 and 24E models.
Oh, the 16 is unmanaged. I still can tell what version though. I'd buy it without hesitation if I thought I could just use simply use it.
Unfortunately openwrt doesn't list a page for those, only the 8 and 10. I'm also unable to determine versions of those available.
I don't expect to not have to use a web browser, but I wonder if any of those really mean Chrome. Then there's the issue as with Netgear and whether they force you to create an account to manage it. What if it isn't internet connected?Cloud Smart Switch ... comes with the lightweight SwOS which is easy to configure from your web browser. It gives you all the basic functionality for a managed switch, and more:
MAC-based access for initial configuration
WinBox – standalone Windows GUI configuration tool
Webfig - advanced web-based configuration interface
MikroTik - Android and iOS-based configuration tool
Powerful command-line configuration interface with integrated scripting capabilities, accessible via local terminal, serial console, telnet and ssh
API - the way to create your own configuration and monitoring applications
Haven't worked with them myself, but a few of those were used in a company I worked for;but if mikrotik includes command line, then that's a strong case for not trying to make it difficult to use.
I can confirm that Mikrotik's web UI doesn't require Chrome. While they have their faults, they're not that kind of company... their "Winbox" software has worked fine under Wine for years but they have recently released a (beta) version which runs on Linux / Mac natively as well. (Maybe I shouldn't admit here that my Mikrotik router is actually currently running OpenWRT!)pjp wrote:That could make it a lot easier.
I was still going to see about resellers (low expectations) and possibly contact a manufacturer or two for clarification, but if mikrotik includes command line, then that's a strong case for not trying to make it difficult to use. As long as local web interface doesn't require Chrome, I'd probably use that most of the time, but sometimes it's nice to get a quick response.
I'll give their hardware another look this weekend. Thanks for finding that!
I'm running an Omada network both at home and at work. The switches are all pretty decent and the APs are good from my experience. Routers can be a little lacking compared to more comprehensive solutions.pjp wrote:It's not looking good so far for anything better than an all-in-one but not enterprise $.
TP-Link JetStream TL-SG3428 (24port) and TL-SG3210 V3 (8port) both list Omada centralized management. At least for some devices it requires a separate "on premises" device to not manage it from the cloud. I'm not sure which ones if it is limited.
I presume "Chrome required" is an effective result rather than a goal. But it's good to know there stuff isn't. They have an AP that references a management tool that can be run from some of their devices. Maybe that's fine, but it seems obnoxiously complicated. On the plus side, many of their devices have console ports. Rhetorically, can I configure the AP from the router directly? I suspect not, and that the special software has to do it. If I go that route, those are some of the questions I'll have to ask them. I'm leaning toward not at this time though. The total price of ~$300 is more than I'd set out to spend. I'll keep it in mind though if fibre arrives anytime soon. Which is another reason to put off buying expensive equipment that I won't use.AJM wrote:I can confirm that Mikrotik's web UI doesn't require Chrome. While they have their faults, they're not that kind of company... their "Winbox" software has worked fine under Wine for years but they have recently released a (beta) version which runs on Linux / Mac natively as well. (Maybe I shouldn't admit here that my Mikrotik router is actually currently running OpenWRT!)
Thanks. I really don't want to have to use a VM to manage anything. It's simply not required for small office / home setups in my opinion. That does somewhat confirm my concerns about their move away from easily configurable devices. (And no, a VM or the cloud does not make it "easy.")AJM wrote:One point regarding Ubiquiti - once configured, their Unifi APs / switches do not require the controller to be running in order to work; it's possible (easy) to self-host the controller software in a VM and only run it when you want to (re)configure something or add new hardware. I look after a fair number of UniFi wifi deployments and their system is pretty easy to manage, far easier than Mikrotik at scale; far less flexible than Mikrotik at small scale though.
Thank you. I don't recall if I noticed price much for their devices. Now that you mention it, I do recall the "software controller", but it very much seems geared toward large deployments.saellaven wrote:I'm running an Omada network both at home and at work. The switches are all pretty decent and the APs are good from my experience. Routers can be a little lacking compared to more comprehensive solutions.
The Omada controller can be done from the cloud, a hardware controller, or a software controller.
You don't absolutely need a controller and can configure it all standalone, but the controller gives you some extra benefits like fast roaming on your APs.
My home consists of 2 switches and 4 APs (soon to be 6 to extend things outside) and my business 3 switches and 4 APs.pjp wrote:Thank you. I don't recall if I noticed price much for their devices. Now that you mention it, I do recall the "software controller", but it very much seems geared toward large deployments.saellaven wrote:I'm running an Omada network both at home and at work. The switches are all pretty decent and the APs are good from my experience. Routers can be a little lacking compared to more comprehensive solutions.
The Omada controller can be done from the cloud, a hardware controller, or a software controller.
You don't absolutely need a controller and can configure it all standalone, but the controller gives you some extra benefits like fast roaming on your APs.
https://www.tp-link.com/us/business-net ... ontroller/
"Up to 1,500 Omada access points, JetStream switches, and Omada routers."
That's all good and well, but I'm going to have 1 or maybe 2. They do list supporting some Linux OSes, so that's nice. I may see if I can download it and get it working, or if I need the device first (it says it is freely downloadable).
"Ubuntu 14.04/16.04/18.04, CentOS 6.x/7.x, Fedora 20 (or above) and Debian 8/9"
You can configure and use any Mikrotik AP directly (built in web ui, mobile app, ssh etc) without any other Mikrotik device or software involved. They also have an optional managed wifi controlled feature (like UniFi/Omada) for which the controller (called CAPSMAN) can be run on any device running Mikrotik RouterOS (so you could run it on an AP to manage other APs for example, or run it on a MT router).pjp wrote:They have an AP that references a management tool that can be run from some of their devices. Maybe that's fine, but it seems obnoxiously complicated. On the plus side, many of their devices have console ports. Rhetorically, can I configure the AP from the router directly? I suspect not, and that the special software has to do it.