 All right, we're going to take a look today at the Unify USG security gateway and answer a quick question that I've seen a lot of people have about this. What's the thorough put? Very valid question. My confusion is the people who are saying they can't get very good thorough put out of this and they can't get very thorough put with the DPI turned on. So this is a standard standard model USG, the one that's a little over $100. And I have it all configured and set up. And as of December 1st, this would be the latest firmware on it, which is the 44125032482. So as of December 3rd here, that should be the latest firmware on it. It's been up and running for about an hour. I've been running some tests on it. I have deep pack and inspection turned on so we can look at some of the traffic. I played around on Reddit and Facebook. Actually, I played way more than I was expected to. But I wanted to make sure I had some statistics in here, which is easy enough. I got sucked into Reddit for a little while. And let me go over here to the settings to show you that it's still turned on. Settings, DPI, still cleared, still turned on. No filtering right now. So I don't have any restrictions on it. And I don't think they make any difference. We're going to run two tests to make sure. So first one I'm going to do is give you an idea of how this network is configured. So this 192.168.3.164 is the IP address of the USG itself. Behind the USG, I'm going to show you the network settings real quick. Settings, routing and firewall, port forwarding. Behind there I have IPerf3 running on my laptop on the other side of the network. And its IP address is 192.168.1.66. And IPerf3 uses port 5201. Here's IPerf3. Now we're going to run a 60-second test. And what this 60-second test is going to do, bring it back to the dashboard. And I've already run a bunch of them here. And you can see pretty fast throughput at like 990 megs a second. Some of the peaks in here. We're going to run this for 60 seconds and show you the speed and throughput that I can get here with DPI turned on. So I'll play this to make it go a little faster as you don't want to hear for 60 seconds, but I'll leave the screen on so you can see what it's actually doing. And here's our final result of 924 megabits a second. Now I'm actually going to add one more thing to the test. We're going to add a dash P 100, which means start 100 streams at once. That way, instead of just measuring one stream, we've got more streams to filter through. And we're going to see that I've tested this already, but I know the results will be the same. But I'll still run through this and you can kind of get an idea. And you can see in the end, we still got the same results. So 924 with the 100 streams and 926 when we run in single stream. So not substantially different. I do notice this, like we're done running the stream. There's no data. This kind of likes to stick all around a little while. Once it decides to peek out, it doesn't refresh very often. We would force the refreshing. I can force refresh during to see the speed test. And now it's back down to zero. There's really no speed difference. Now I will admit this. Here are the CPU usage. So we are seeing, but not 100%, we are seeing some higher CPU usage here running the DPI and doing these tests. So this was the provisioning where it kind of peeked out here. Here's all the tests were running way down here. So we're seeing a CPU usage in a 10%. All right. Next thing is, let's take a look at what happens when we add some filters onto there and see if we get any difference at all. So we're going to go over here to the DPI, default, add restrictions. Keep me off social networks. That is my time suck. Really, you can block security updates. And we'll say games, block all matching traffic, save, save. All right. Apply the changes. Make sure it provisions. Provisioning the changes. That'll keep me from playing around on Facebook. OK, it's all set and provisioned. Go back to our dashboard here. And we'll run another 60-second test. And same speed result as before, 924. I mean, we're seeing sometimes a small variation like 924, 926. But essentially, you're talking about a switch that can still route at full gigabit. If you have more than a gigabit connection, it may or may not be the switch at that point. At some point, you need faster than gigabit connection on there. These only have gigabit ports. Therefore, it can't go any further. And I don't really see, and we refresh this real quick, I'm not seeing any CPU usage that's any greater running the multiple. So there's our CPU expanded. I zoomed it into the five minutes here. It's not peaking out the CPU. So you're not seeing any type of absolute massive processor usage. It routes at full speed. So hopefully, this just clears that up for people wondering how fast it is. It will route at full gigabit speeds. I didn't have any issues with it. I didn't notice it being slower or anything when I tested it previously. But I figured, latest version, may as well do a full speed test on it to answer that question. If you're not familiar with how to use Iperf, I'll leave also a link in the description how to use Iperf. It's a really simple tool built into the Debian repositories. It's also a free download. If you Google Iperf, you can find it. The version I'm using specifically is called Iperf 3. All right. If you like the content here, like and subscribe. Hopefully, it answers questions about speed, about the Unify USG. Thanks.