Slate 7 WireGuard speeds as advertised

I am very happy (so far) with the Slate 7 coming from a Firewalla Purple as a travel router.

After a few days of testing, I can confirm that WireGuard speeds are in fact around 500Mbps

Right now I have the router hard-wired on WAN to my guest network running on pfSense. The VPN tunnel is all local (no WiFi or ISP involved). Obviously in real-world applications, I will likely see slower speeds due to hotel WiFi and bandwidth limits, but it's good to know the hardware is capable of it!

1 Like

Doing some further testing with iperf3 running through WireGuard for 10min between my Slate 7 and a VP2410 running pfSense here are the CPU loads:

Slate 7:

VP2410 (pfSense):
image

It's interesting that the Slate 7 exceeds 4! Turbo mode?

Hello,

Thanks for your test, very happy to hear that you are satisfied with Slate7 WG speed.

Since the VPN data (and iperf) does not undergo hardware acceleration, and needs to rely on CPU resource to complete calculate encryption/decryption, it is not surprising that the CPU load reaches 4.0 and more.

When we use OpenSpeedtest to test the VPN peak rate, we saw that the CPU is up to about 3.5.
PC1 OpenSpeedtest server --- MT6000 WG server --- Main router --- BE3600 WG client --- PC2 OpenSpeedtest client (webpage)

Do you have other functions enabled besides VPN? For example, ADG.
Or are you running iperf -s in router SSH?

I am running iperf on the Slate7 from ssh as "iperf3 -s".

Other than WireGuard and iperf3, I have nothing else running on the Slate 7.

I do get these occasionally in the WebUI which I have not been able to diagnose:
image

Are you using a Mac or an iPad to access the router (Safari)?
Because this pops up for me too but when I tried a Windows machine with an Edge browser it didn’t show up.

I think I was getting it when connected to my home network through WiFi on WAN. The Slate 7 got into a funk after messing with it for a week. I have to return it to factory settings and reconfigure it and it was fine. I'm not sure what I did, but it's fine now.

1 Like