^^I think all of these fw's are exactly the same. Look at post 135 for the sodola one.
It probably pulls certain identifiers from nvram such as the model #. Something the firmware doesn't touch.
Received the fw for sodola switch. Same md5 as in post #128.
File: sodola_RF_V1.9_SL-SWTGW218AS_0104.bin
CRC-32: b59ac72d
MD5: 559fbd81a07ed7ce954a710c7fb2a249
SHA-1: b2e137f2c29075b842e2b8dbd9b017eccd5db960
SHA-256: 2609eb5f3108fb5cd6916d764d9b15a89cc70e69a8ca97d14f025306efdaceec
Looks good, at least as far as raw network performance. You should also test with -R on the client as the above is sending from the client to the server.
On the server side - you can also add the -D parameter for each server instance to run it as daemon rather than interactive.
iperf3 -B 192.168.3.10 -s
iperf3 -B 192.168.3.11 -s
On the client side
iperf3 -B 192.168.3.7 -c 192.168.3.10 <other options>
iperf3 -B 192.168.3.8 -c 192.168.3.11...
What 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.
^^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.
Don't think it's a good idea to set the switch to dhcp. I keep all my switches and servers set to static ip's. No...
^^Your query is outside the scope of this thread. But in general, vlans on a switch will segregate traffic into virtual "lanes" (imagine concrete barriers between them). You still need supporting software to route the traffic from the vlans (to internet), and/or between vlans (cross over lanes...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.