Search results

^^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

They never include change logs. @ribeiro_lucio did you notice anything different after install?

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.

True, but you can do multiple instances of iperf3. There's a parameter "-B" that binds an instance to a specific local ip address.

@Eviljay I would do baseline testing with iperf3 before adding more variables (filesystem, disk, etc) to the mix.

^^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...

IMO, if buying any switch these days, it should at the bare minimal provide vlan capability. This will come in handy eventually.

^^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...

The amz version is still $100USD after coupon - https://www.amazon.com/gp/product/B0CFQKYDRM .

Wow! I did not experience that with the intel nic - i340-t4.

No, single port. Doesn't matter. Usually on a multiport nic, each interface is individually addressable.

I got some no name china brand from amazon where the above does work. It's part of a cron job that runs at boot which primes the wol flag.

Did you ever figure this out? In debian/ubuntu wol can be enabled for this card using ethtool ( ethtool -s enp1s0 wol g ). Adjust enp1s0 to reflect your interface name. Question is, how do I do the same on freebsd?

PVID refers to the default vlan for untagged inbound (into that port) traffic. I usually assign this to the same vlan as the tagged id. Another example, I have an AP that allows assigning ssid's to different vlans. I use vlan id 3, 4, 5. However 4 is the pvid for that port. So an ssid NOT...

I see, so these newer 8+1 type switches are theoretically more efficient because there's less hardware involved for the same functionality. I only have a few 2.5gb clients, but have done continuous iperf testing for 30min+ without any meltdowns.

^^I dare not apply that concept to updating my car's infotainment. Each new update seems to break/remove features. IE when I got the car originally it had a manual day/night/auto adjustment for display. After the first update, they took that away, auto only now. That's progress!!

^^Wow. That's too bad. With most devices, previous backups usually import fine into newer fw, just not the other way around. Will have to keep that in mind if/when I ever update the fw on this again. Realistically, unless there's some significant bug fixes or new features added, how often do...