Tagged “networking”
-
The Names That Only Exist on Your Own Network
Printers and shared drives answer to names no public resolver has heard of. Two things break them: a tunnel swallowing them, or them leaking out.
-
What Your Device Announces to a Network Before You Open Anything
Joining a network makes your device introduce itself: a name, a request pattern, service advertisements. A tunnel covers none of it.
-
Which Route Wins When the Tunnel and the Local Network Disagree
Your device holds several overlapping routes at once. The rule that picks between them explains the tunnel-is-up-but-unused failure exactly.
-
What a Guest Network Actually Separates
A guest SSID either puts visitors on their own address range or merely stops them reaching each other. Which one you have is a question you can answer.
-
Why a Router VPN Behaves Differently From a VPN App
Moving the tunnel to your router covers every device and gives up per-device control, kill switches, and easy server switching.
-
What an ASN and Reverse DNS Reveal About Your Connection
Every IP address belongs to a registered network with a name attached. That is how sites tell a home connection from a data centre.
-
What a Traceroute Shows Before and After You Connect
A traceroute lists the network hops to a destination. Comparing one with and without a VPN makes the tunnel visible.
-
Why Port Forwarding Breaks Behind a VPN
Inbound connections arrive at the VPN server, not your router. Your forwarding rules are correct and never get consulted.
-
What MAC Address Randomization Hides, and What It Doesn't
A MAC address identifies your device to the local network only. Randomizing it helps against Wi-Fi tracking and does nothing online.
-
How to Read Your Own Network Settings
Address, gateway, subnet mask, and resolver: what each field means and what it tells you when a VPN misbehaves.
-
How DNS Resolution Works, Step by Step
Turning a hostname into an IP address involves caches, a resolver, and a chain of authoritative servers. Each step is a place things can leak.
-
Why a VPN Gives You Two IP Addresses
Connecting a VPN adds a virtual network adapter with its own private address. Understanding it explains most routing confusion.
-
What CGNAT Means for Your IP Address
Carrier-grade NAT puts many subscribers behind one public address. It changes what inbound connections can reach you and how a VPN helps.
-
Static vs Dynamic IP Addresses: What Actually Changes
A static address stays put; a dynamic one is leased and may be reassigned. The difference matters more for reachability than for privacy.
-
Why Your Home IP Address Changes on Its Own
Home connections get their public address on a lease that can be renewed or reassigned. Here is what triggers a change and what it means for privacy.
-
Public vs Private IP Addresses: Which One a VPN Changes
Your device has a private address on your own network and a public one facing the internet. A VPN replaces one of them, not both.
-
Nobody Can Sell You the Fastest VPN: Measure Your Own Instead
A published speed figure describes a path you will never use. What actually sets your throughput, and a procedure for measuring your own result.
-
VPN vs Smart DNS: What Changing Only Your Resolver Can Do
Smart DNS changes which resolver answers you and encrypts nothing. That makes it the clearest illustration of what name resolution alone affects.
-
VPN vs Tor: How Many Parties Can Connect Both Ends?
Both substitute the address a site sees. The real difference is how many independent operators are involved, and what that design costs you.
-
VPN vs Proxy: One Is an Application Setting, the Other Is a Route
A proxy is configured inside a program; a VPN edits your routing table. That single difference decides the scope and who resolves your names.
-
Do I Need a VPN at Home? What Changes on a Network You Run Yourself
On a network you administer, most of the usual case for a VPN does not apply. Here is what genuinely remains, and when it adds up to yes.
-
How Does a VPN Work? Follow a Single Packet Out and Back
The path one packet takes with a VPN connected, and what changes at each step: the interface, the route, the wrapping, the exit, the reply.
-
What Your Internet Provider Still Sees While the Tunnel Is Up
A tunnel hides which sites you reach from your access network. It does not hide that you connected, to where, for how long, or how much moved.
-
An Obfuscated Server Hides That You Are Using a VPN
Obfuscation disguises the tunnel's own signature, not its contents. It answers one narrow question and adds nothing to your privacy.
-
How a VPN Kill Switch Fails Closed, and Where It Doesn't
A kill switch is a firewall rule that only permits traffic on the tunnel interface. Where those rules live decides whether it survives a crash.
-
How OpenVPN and WireGuard Differ by Design
Two tunnels built to opposite briefs: a configurable session with a large codebase, or a minimal stateless one with fixed choices.
-
Which Part of Your VPN Is the Protocol?
The protocol is the negotiation and the packet format between your device and one server. Routes, resolvers, and firewall rules are separate layers.
-
Where the Slowdown Comes From When You Connect a VPN
Longer paths, an extra header on every packet, packet-size limits, shared server capacity, protocol behaviour. Which one is yours is knowable.
-
Finding and Reading Your VPN's Exit Address
The address the internet sees is not on your device at all. How to find it, and what its owner, reverse name, and reuse tell you.
-
Narrowing Down Why Your VPN Is Not Working
A VPN failure lives in one of five places on your device. Here is the question that eliminates each, in the order worth asking them.
-
Installing a VPN on a Firestick: Why the Realistic Answer Is Upstream
A Fire TV stick can run a client, but you cannot inspect it and sideloading one is a trust problem. Covering it upstream is the honest answer.
-
Putting the VPN on Your Router: What You Are Committing To
A router tunnel covers devices that can never run a client, and commits you to one shared exit address and a piece of infrastructure that fails silently.
-
A VPN on a Chromebook: Which of the Three Layers Gets Covered
A Chromebook runs the browser, an Android container and a Linux container. A VPN in one does not cover the others, so check which yours reaches.
-
A VPN on an iPhone: What Happens Between Networks
An iPhone's tunnel belongs to the operating system and is rebuilt every time the network changes. What happens in those intervals is the real subject.
-
A VPN on Windows 11: The Adapter, the Route, and the Resolver
Windows gives you a built-in client, a virtual adapter and an interface metric to inspect — plus a name-resolution habit that quietly undoes a tunnel.
-
Setting Up a VPN: Which Layer You Put the Tunnel On
Setting up a VPN is mostly choosing which layer carries the tunnel — one app, one device, or the whole network — and what happens when it drops.