IPv4
— Internet Protocol version 4IPv4 is the fourth version of the Internet Protocol and one of the core protocols of standards-based internetworking methods. It routes packets across network boundaries using 32-bit addresses formatted as dotted-decimal notation (e.g. 192.0.2.1).
Interactive Session: How IPv4 Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of IPv4.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
Source address spoofing
SpoofingPackets carry a forged source address, hiding the sender and enabling reflection attacks.
Forge the source
The attacker sets the source address to the victim or to an address that passes filters.
Packets arriving on an interface with a source that does not belong to that path.
Attribution failure and reflected traffic toward a victim.
Defences that matter
- Ingress and egress filtering (BCP 38)
- Unicast reverse path forwarding
- Do not rely on IP addresses alone for authentication
This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.
Protocol Specification & Architecture
Key characteristics, real-world deployment patterns, and trade-offs.
Core Technical Features
- 32-bit address space yielding ~4.29 billion unique addresses
- Best-effort, connectionless packet delivery
- Packet fragmentation and reassembly mechanism
- Time-To-Live (TTL) hop count preventing infinite routing loops
Real-World Use Cases
- Global Internet packet routing
- Enterprise LAN addressing
- VPN tunneling
Advantages & Strengths
- Ubiquitous universal hardware & software compatibility
- Well-understood routing architectures
Limitations & Vulnerabilities
- Address exhaustion requires NAT workarounds
- No built-in encryption (requires IPSec)