Now everything is working fine but i have crushed over the poor performance of the gs1900-24e switch. It seemed to be a good managed switch...
it has so poor performance that my download internet speed (a simple 100m fttc vdsl) does not go over 20mb/s and the transfer rate between different vlan zone does not go over 20mb/s.
When i bought it i thought it could be a little better but i hadn't the knowledge to evaluate it...
I have a lot of question but i will limit to these?
which hardware could let me transfer near gigabit speed using vlans? and not throwing a lot of bucks? consider i nedd at least 16 ports for cabled devices.
is there a way to use it (eg putting router between internet router and a zyxel) and that let me bypass the poor forwarding rate?
i have done a lot of work to get this architecture and to migrate all the devices (more than 100), so i'm a little bit depressed having these results and i woul not like to go back to have all in single lan... and i would not like to throw everyting away
You need a device that is capable of routing. Many cheap plastic all-in-one wifi routers can run circles around a switch for routing, even ones that are old and slow (by today's standards). That's because they have specialized hardware specifically designed for routing at high speeds. Your switch has hardware that will switch at high speeds, but all routing needs to be done by the very weak CPU which is not designed for this task.
You can still use your switch as a VLAN aware switch, but all routing needs to be done on a real router.
I knew it had poor performance, but i discovered it after i bought it.
I've continued to use it because i needed to separate devices in vlan for security reason. Done that now i can consider the task to get better performance.
Considering i have 2 or 3 devices that need to have one ethernet interface on more than one vlan (e.g. home assistant).
To avoid make the switch route packet, the home assistant server should have one physical interface for every vlan, right?
So the router should have one interface for every vlan. Is this assumption correct?
Basically, anytime the traffic needs to cross over an L3 boundary, it needs to be routed. So for example, if you have hosts on the 192.168.1.0/24 network that need to reach hosts on 192.168.3.0/24, routing is required.
Any traffic that is traversing the same L2 network (i.e. devices on 192.168.1.0/24 to other devices on the same 192.168.1.0/24 network) do not need to be routed.
So it's not so much about how many networks are present on a port, but rather about the source and destination of the traffic. And this includes when the goes to/from the internet.
Is your modem a combo modem+router device, or is it a modem only? From your diagram, it looks like it's a combo unit, so it will handle routing to the internet at normal speeds. Therefore, assuming that is correct, all the traffic on 192.168.1.0/24 coming from or going to the Internet should traverse the switch at L2, which means you will get the expected ISP speeds. All of the other networks, though, will be really slow -- both between each other and to/from the internet.
thanks for the very clear explanation.
my isp router is a combo, it routes traffic to internet at the expected speed. is on the 192.168.1.x network.
all my other devices are on a 172.30.10/20/30/99 (vlan 10, 20, 30, 99) network so all cross the L3 boundary network.
Probably i didn't understand well, sorry for the dumb question.
My future router
eth0 -> 192.168.1. -> to internet router
eth1 (172.30.x.x with 4 vlan tagged) -> to port 1 of the switch zyxel (with 4 vlan tagged)
the traffic outgoing to internet will be switched on the port 1 and the router will route traffic to the internet. so no routing will be made from the switch.
Insted, is there a "workaround" to solve the slow routing between vlans?
Your future router will handle all of the routing activities. You'll have an uplink from the switch to the router that will be a trunk (a trunk is a single link/cable carrying all of your VLANs). The switch traffic will traverse the switch and reach the router where all the routing will be handled.
So you'll move the configuration of all of your L3 interfaces to the main router, and the switch will simply have a bunch of VLANs with the appropriate port-vlan memberships.
Also, it should go without saying that you need a router that is either supported by OpenWrt, or one that is at least capable of VLANs with its existing firmware. Obviously, I'd recommend getting a device that you can use with OpenWrt.
Do you have permanently powered low power x86 like NAS in your network? A single virtual machine positioned between VLANs will jump around in circles of switch management SoC in routing performance.
Performing routing on VMs can be rather challenging, mainly as a function of the host OS and the virtualizer environment configuration. I do not recommend virtualized routers in most cases because of these additional complications (and the fact that they quickly become out of scope for this forum).
Running a device bare-metal with OpenWrt or any other properly VLAN aware routing firmware is almost always more straightforward.
I should have a low power mini pc, a little bit aged for what they are used now, but i will check if it's suppoerted by owrt, it should, because it's an x64 architecture. At the momenti debian 12 is installed on it. I should get right with a usb3 gigabit adapter for the second nic.
