How many public IPv4 addresses does a homelab need?
A practical way to size public IPv4 addresses for a homelab: which services can share one address behind a reverse proxy, and which ones need their own.
Guides on tunnel protocols, routed IPv4, and network infrastructure.
A practical way to size public IPv4 addresses for a homelab: which services can share one address behind a reverse proxy, and which ones need their own.
Give a Minecraft Java server a public IPv4 through WireGuard when port forwarding cannot work behind CGNAT. Route it, secure it, and test it.
Two ways to get a real public IPv4 with no registry step: ask your host, or route one through a tunnel. Setup steps, diagrams, and common mistakes.
Real IPv4 brokers, leasing marketplaces, and routed providers compared, with what each one costs, requires, and the fraud checks to run before paying.
Learn the difference between buying a /24 IPv4 block and getting one routed public address without an ASN or BGP.
Compare GRE and WireGuard for routed IPv4, home servers, and network links, including encryption, NAT, MTU, routing, and setup tradeoffs.
Set up a routed public IPv4 address on a Linux home server through WireGuard, including firewall, Docker, DNS, return routing, and testing.
Route one public IPv4 address to each Proxmox VM through a tunnel, with working host, guest, return-path and testing steps.
A practical guide to building a small VPS host with Proxmox VE, routed IPv4, backups, abuse handling, and capacity limits that survive real customers.
Port forwarding does nothing because your router never had a public address. How carrier-grade NAT works, how to check in a minute, and the ways around it.
IPv4 sells for about $20 an address, leases for under 50 cents a month, and costs $3.60 a month at AWS. Why the same address carries four different prices, and which one applies to you.