BFD
— Bidirectional Forwarding DetectionBidirectional Forwarding Detection provides a fast, protocol-independent failure signal. Two systems negotiate a transmit interval and a detection multiplier, then exchange small control packets over UDP; when the agreed number of packets goes missing, BFD declares the path down long before a routing protocol hello timer would expire.
Interactive Session: How BFD Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of BFD.
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.
BFD session forgery
SpoofingForged BFD control packets can keep a dead path looking alive or flap a healthy one.
Match the session
The attacker discovers the discriminators and timing.
BFD packets from an unexpected source.
Delayed failover and extended outages.
Defences that matter
- BFD authentication
- Control-plane policing and TTL checks
- Independent path monitoring
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
- Asynchronous control packets over UDP port 3784, with echo mode on port 3785
- Detection time equals the negotiated transmit interval multiplied by the detection multiplier
- Discriminator values demultiplex sessions independently of interface addresses
- Single-hop and multi-hop modes with optional authentication
- Routing protocols and static routes register as clients to receive state changes
Real-World Use Cases
- Sub-second failover for OSPF, IS-IS, or BGP peering sessions
- Monitoring MPLS label-switched paths and static routes
- Detecting failures across Layer 2 transport that hides a link-down event
Advantages & Strengths
- Millisecond detection that is independent of routing protocol timers
- Very low bandwidth and CPU cost per monitored session
Limitations & Vulnerabilities
- Aggressive timers can produce false positives during congestion or microbursts
- Requires support on both endpoints and careful tuning over long paths