Anthony Roux

I Fired One Bullet in Fortnite. Here’s What the Internet Did.

Anthony Roux at a gaming mouse beside a Fortnite island and a network rack. One bullet. What happened?

INSIGHTS   /   NETWORKING I fired one bullet in Fortnite. Here’s what the internet did. Anthony Roux · Technical Lead · 5 min read Drop into a chapter The shot The packet The lag Field notes The experiment The verdict The author The video I line up a shot. Click. Muzzle flash. The other player keeps running. I’m already reaching for the oldest excuse in gaming. “That was lag.” Maybe. My aim also deserves a place on the suspect list. Before I blame my Fortnite ping, I want to know what happened between my finger moving and the other player seeing the result. Who decides whether my shot lands? My mouse reports the click to my PC. The game processes the input and can show immediate feedback, like recoil or a flash. That makes firing feel responsive. Meanwhile the other player’s machine is drawing its own view of the encounter. Online, we need a shared version of events. In a server-authoritative game, the server processes relevant actions against the game rules and sends updates back to the players. The two screens can briefly show different moments in the same fight. Follow the shot Your mouse registers the click. Fortnite shows the shot on your screen. Your PC sends a network update. The server processes the action. Both players receive an updated view. That’s a simplified journey. Games can bundle actions into updates. A single click doesn’t give me a tidy little packet labelled “Anthony missed again”. What travels in a network packet? My PC passes data to its network interface. Ethernet carries it down a cable, or Wi-Fi carries it over the air to an access point. For a destination outside my home network, the next stop is usually my default gateway, the router. The router forwards IP packets towards their destination. My ISP carries them onwards, sometimes through other networks before they reach the game service. Each router needs enough addressing and routing information to choose the next hop. It has no particular interest in who won the fight. What’s inside a packet? Think of an addressed envelope. An IP packet carries a header with information such as source and destination addresses, plus a payload. A capture can reveal packet lengths and arrival times even when the game data inside is protected. Fortnite ping, jitter and packet loss A speed test mostly answers how much data your connection can move per second. In a fight, I also care about when the next small update arrives. Ping · how long for a round trip? A Fortnite ping reading of 80 ms is an estimate of a trip to a game endpoint and back. Input processing, server work and rendering can add time before I see a result. Jitter · how consistent is the timing? Imagine round trips of 40, 42, 39 and then 170 ms. The spike can disturb a fight even if the average looks respectable. Packet loss · what failed to arrive? Missing updates can leave a client working with old information. Depending on how the game handles that gap, movement can appear to stutter or snap. Bandwidth · how much fits? A big upload can fill a queue and delay small game updates. More Mbps may help a saturated link. It won’t shorten the physical distance to a faraway server. Frame rate is another clue. If my whole view judders while the network statistics stay steady, I check local frame times too. Two faults can feel surprisingly similar from behind a mouse. From the island to the server cabinet From my field photos. A link light is a starting point. It tells me far less about the path beyond that cabinet. I once spent hours working through a client’s connectivity issue. The clue was a DNS change on the ISP side. Equipment was powered up and the link was active, yet a service people relied on still appeared broken. DNS helps a device look up a service by name. It gives me a different line of enquiry when a game can’t connect at all than when I’m already playing and get a burst of packet loss. Asking when it fails saves a lot of random changes. How to test your Fortnite ping in a match Take a baseline. In Fortnite, open Settings → Game UI. Under HUD, enable Net Debug Stats and apply the change. Epic’s packet-loss guide shows where to find it. Note the region, connection type, usual ping, visible spikes and reported loss. Mark the moment something feels wrong. Change one thing. If possible, switch the same PC from Wi-Fi to Ethernet. Keep the region and background traffic similar. Play another comparable session. Compare the bad moments. If spikes repeatedly disappear on Ethernet, investigate signal strength, airtime and interference. If both runs spike, look further along the path. One match is a clue. Repeat before calling it a fix. Go deeper with Wireshark On your own PC, choose the interface carrying the game traffic. Capture a short idle stretch and then a short stretch of play. Compare packet timing, lengths and traffic volume. Other applications share that interface, and encrypted or proprietary traffic limits what you can identify. A burst when you fired is a clue. It takes more evidence to identify the shot. Download the Fortnite networking worksheet (PDF) Back to that missed shot The next time I watch someone duck behind cover just as I fire, I’ve got three places to look. What did my PC draw? How steady was the network? What update did the server send back? Sometimes I can measure enough to explain it. Sometimes I’ll have to admit the oke had better aim. That’s what I love about networking. The same questions follow me from a Fortnite lobby to a warehouse cabinet. Where did the information need to go, and what can I actually observe along the way? About Anthony Roux I’m a South African technical lead working on business networks, servers and CCTV. I learned networking

The Reality of Working in Managed IT

The Real Life of IT — Anthony Roux in a golf shirt holding a TOTAL drill, with network cabling and equipment behind him. Illustrated cover artwork.

Working in managed IT has taken me from keyboards to ladders, cable pulling, crimping, drilling and server rooms. This is the real work behind a business that just works.

5 Microsoft 365 Mistakes I See Over and Over

A practical look at five common Microsoft 365 problems I repeatedly encounter in real-world business environments — and what you can do about them. Reading time: 35–40 minutes Introduction Microsoft 365 has become a standard part of running a modern business. Email, Microsoft Teams, OneDrive, SharePoint, Office applications and user accounts can all be managed from one Microsoft 365 environment. But having Microsoft 365 does not automatically mean that it has been configured or managed properly. Over the years, I’ve worked with businesses where Microsoft 365 was technically working, but there were still some fairly serious problems hiding underneath the surface. Sometimes it was something as simple as users not having multi-factor authentication enabled. Other times, it was a tenant where far too many people had Global Administrator access, former employees still had active accounts, or a business was paying for licenses it didn’t actually need. Then there are the problems that seem small until they suddenly aren’t — like printers and scanners that were configured years ago to send email and suddenly stop working. None of these problems are particularly unusual. In fact, they are some of the things I find repeatedly when looking at business Microsoft 365 environments. So in this article, I’m going to look at five Microsoft 365 mistakes I see over and over, why they matter, and what businesses should be doing instead. 1. No Multi-Factor Authentication If there is one Microsoft 365 security setting I would want every business to look at first, it is multi-factor authentication (MFA). And yet, it is still something I encounter surprisingly often: Microsoft 365 accounts where MFA has not been properly enabled, accounts where only some users are protected, or environments where MFA was configured but never properly enforced. The problem is that a username and password are no longer a particularly strong security boundary on their own. Passwords get reused. They get written down. They get entered into fake login pages. They can be exposed through data breaches elsewhere. Users can also be tricked into handing over their credentials through phishing attacks. Once an attacker has a valid Microsoft 365 username and password, they may be able to access much more than just someone’s email. Depending on the user’s permissions, they could potentially gain access to: This is why protecting the login itself matters so much. What MFA Actually Does MFA adds another layer of verification when a user signs in. Instead of Microsoft 365 asking only: “Do you know the password?” it can also require something else that helps prove the person signing in is actually the legitimate user. That second factor might involve an authenticator application, security key, or another supported authentication method. The important point is that knowing the password is no longer enough by itself. If an attacker manages to obtain a user’s password, they still have another barrier to overcome. That doesn’t make an organisation impossible to compromise, but it significantly improves the security of the account compared with relying on passwords alone. “But We’re a Small Business” This is one of the arguments I hear from smaller businesses: “We’re too small for someone to bother attacking us.” Unfortunately, being a small business doesn’t make your Microsoft 365 environment uninteresting to attackers. In many cases, attackers aren’t specifically targeting a company because of its size or reputation. They’re looking for accounts that are poorly protected. A small business can also contain valuable information: Your Microsoft 365 account is therefore part of your business security infrastructure, regardless of whether you have five employees or five hundred. MFA Shouldn’t Be an Afterthought Another problem is treating MFA as something that can be switched on later. It should form part of the basic setup of a Microsoft 365 environment. When a new user is created, security should already be considered. When an employee leaves, their access should be removed. When administrator accounts are created, those accounts should receive particular attention because compromising an administrative account can have much greater consequences. Security should be built into the environment rather than added after something goes wrong. Don’t Stop at “MFA Is Enabled” There is also an important distinction between having MFA available and actually having a properly secured environment. A business should know: In other words, ticking an “MFA enabled” box is not the end of the conversation. It is the beginning of properly managing identity security. A Practical Starting Point If you’re responsible for a Microsoft 365 environment and you’re not sure where things stand, start with a simple review. Look at your users and ask: Does every person who needs access have appropriate MFA protection? Then look specifically at administrator accounts. Are there any accounts with elevated privileges that aren’t properly protected or no longer need those permissions? Finally, look for exceptions. If someone isn’t using MFA, is there a legitimate business reason — or was it simply never configured? These are simple questions, but they can reveal problems that have been sitting unnoticed for months or even years. MFA isn’t the complete Microsoft 365 security strategy. It is, however, one of the fundamental layers that should be in place before you start worrying about the more advanced stuff. And that brings us to another problem I regularly encounter: too many people having more access than they actually need. 2. Too Many Global Administrators The second Microsoft 365 mistake I see quite often is giving Global Administrator permissions to far too many people. This one can be particularly dangerous because it often starts with a perfectly understandable reason. Someone needs to configure something. They can’t access it. Someone gives them administrator permissions. The problem is solved. Six months later, nobody remembers why that person has those permissions, and there are suddenly several users with access to parts of Microsoft 365 that they don’t actually need. It is convenient, but convenience and security don’t always make good partners. What Is a Global Administrator? Global Administrator is one of the highest levels of administrative access within

Free IT Worksheets & Downloads

A growing library of free IT resources — self-audits, checklists, and templates built for real-world use. Download what you need and put it to work in your job, business, or home lab.