Internet connection stress test how to#
Internet connection stress test Pc#

Pinging router-1 gives us no packet loss whatsoever. But also, pinging router-2 also gives us 1.6% packet loss. So, what do we see here? Well, we see that pinging the web server unsurprisingly gives us 2% packet loss. That should take between a minute and a half and 2 minutes (approx 100 seconds) to run each one: We’ll send 1,000 pings at a 0.1 second interval. So let’s ping each host in turn, starting from the web-server and working backwards towards us. Also, to keep things tidy, let’s throw in the -q flag to stop telling us about every single ping. We’re going to use the -i flag to ping, which sets the ping interval, along with the -c flag to set the number of pings. This is where some advanced usage of the ping command comes in. Now, you’d expect the packet loss to be between 192.16.194.38 and 172.16.73.146 (that’s router-2 and web-server), wouldn’t you? Well, let’s just confirm that shall we. It shows that there is obviously something up with the network. You see the packet loss? 1.5% isn’t much, but it’s enough to be annoying. I’m not going to tell you where the packet-loss is. There is no problem.īut what if we introduce a bit of a fault? Maybe a little bit of packet-loss somewhere along the line? Well, that’s easy enough to do on my VM based test-rig. All is well with this network – all the packets we are sending out are being returned to us.

Notice that the switches don’t appear – they are invisible to IP traffic. You can see the three machines – router 1, router 2 and the web server. So this is MTR running on Your-PC checking the link to Web-Server: Note how the two routers have two IP addresses – the one on their LAN and the one on the Internet connection. Your web server is hosted at your ISP (router 2) and the rest of the Internet leads on from there. That switch then goes on to a third switch in the downstairs office (Switch 3) where there is a file server. This in turn connects to a switch in the communications room (Switch 2) where the router that connects you to the Internet is (Router 1).

Internet connection stress test Pc#

Your PC connects to a switch in your office (Switch 1). There’s nothing out of the ordinary here. In this my network is actually going to be a collection of virtual machines, but it will be just the same as if we were playing with a real network. Now let’s make us a nice network to play with. (your Linux system may be slightly different, or may expect a slightly different package name) Mtr can be installed on most Linux systems with one of these: It’s great for monitoring a network path while we do things to it. Instead of just tracing the route once, it does it over and over and over and over until you tell it not to. Mtr performs the same job as normal traceroute, but does it oh so much better. No, it’s not actually mine! That’s its name! Honest! Meet my little friend mtr, or “My Trace Route”. But, could it go unnoticed.?įirst off I’d like to introduce you to the tools we’ll be using during this testing.

Trip over a wire and pull it out of the wall – could cripple your network.

What happens if we use lots of small packets, or some really really huge ones?.

Just how much data can we push through those wires at once without it breaking?.

So what sort of things are we going to be looking at? Well, here’s a brief summary: Network Throughput

From this we will be able to work out ways to make the network better, faster, stronger… Why would we want to do such a destructive thing? Well, we want our networks to run as fast and as reliably as they can, and we can’t know what the limits of speed and reliability are unless we really push our networks to the max. We’re going to try to get those wires to burst, spilling data all over the carpet.

Internet connection stress test how to#

In this episode I shall show you how to stress test your network to the max. Welcome to part 2 of my little network masterclass.