IMO, if buying any switch these days, it should at the bare minimal provide vlan capability. This will come in handy eventually.
As far as I know, not writing changes you make to the config to flash until you actively tell it to is quite common on enterprise switches and routers. That's probably why the switch behaves like that, even though it cleary isn't an enterprise switch.^^That was one of the complaints on amz about it not saving settings. It would appear to be by design. One needs to manually save the settings before rebooting or updating fw.
It is... I think it's also the same when making changes to the firewall rules in Linux too.As far as I know, not writing changes you make to the config to flash until you actively tell it to is quite common on enterprise switches and routers. That's probably why the switch behaves like that, even though it cleary isn't an enterprise switch.
Seems like it was a vendor essentially posting an ad about their products. While the user made some valid points, posting your own products as an alternative makes it hard not to question whether the concerns raised are actually credible.
Thank you! This helps. What protocol was used when bonding the two NICs together?I have a HORACO ZX-SWTGW218AS, ASUSTOR AS6706T and a computer with two 2.5Gb
ports. For home, you do not need to configure any Aggregation Channels on the switch. The cable is laid category 5E. It's enough to do this.
In the NAS, I checked the SMB multichannel checkbox and we get 5Gb/s
View attachment 33382View attachment 33384
It's just that each adapter gets its own IP. The NAS also just gets 2 IPs. Everything is by default. There is no need to configure anything on the switches. You can also use an unmanaged switch. Everything is done by multi SMB in NAS.Thank you! This helps. What protocol was used when bonding the two NICs together?
@JBI You're not bonding the two NICs? Just the multichannel checkbox from the pictures above? Guess I was way over complicating it.It's just that each adapter gets its own IP. The NAS also just gets 2 IPs. Everything is by default. There is no need to configure anything on the switches. You can also use an unmanaged switch. Everything is done by multi SMB in NAS.
I was unable to run testing with the -B option.True, but you can do multiple instances of iperf3. There's a parameter "-B" that binds an instance to a specific local ip address.
Yes. There is no need to combine anything. You can even use an external USB 2.5 network card. I do not recommend using a dual 2.5 PCIe x1 card. She can't skip all 5Gbit at once.@JBI You're not bonding the two NICs? Just the multichannel checkbox from the pictures above? Guess I was way over complicating it.
I was able to verify this worked. Had to reboot everything but now full speeds.
What error message?I was unable to run testing with the -B option.
I run it on NAS: iperf3 -s
I run it on my computer: iperf3 -B 192.168.3.10 -c 192.168.3.11
Gives an error message. Maybe I'm doing something wrong?
192.168.3.7 & 192.168.3.8 – clientWhat error message?
Verify your ip addresses. From the above, the client ip is 192.168.3.10 (ip you want to bind instance to), and server is 192.168.3.11? Also verify you're using a version of iperf3 that actually supports -B. Execute iperf3 by itself to see available options.