Q: You see logs indicating that packets arriving from the public internet have a source IP of `10.0.5.50` (a private IP in your own corporate network). What is this attack, and how is it stopped at the network border?
Isolating network failures requires proving whether packets are dropped by route tables, security groups, or stateless NACLs. The interviewer is testing: IP Spoofing, uRPF (Unicast Reverse Path Forwarding), ingress filtering..
Want to master this scenario in a live sandbox? KodeKloud's Istio Service Mesh & Advanced Kubernetes Networking Course covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Isolating network failures requires proving whether packets are dropped by route tables, security groups, or stateless NACLs. The interviewer is testing: IP Spoofing, uRPF (Unicast Reverse Path Forwarding), ingress filtering.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
This is an IP Spoofing attack. The attacker manually alters the IP header of their malicious packet to falsely claim it originated from an internal, trusted IP, hoping your internal network implicitly trusts it and bypasses firewalls. This is thwarted using uRPF (Unicast Reverse Path Forwarding) globally on border routers (often enforced by ISPs per BCP38), and Strict Ingress Filtering on corporate firewalls. The border firewall evaluates the packet: "If I wanted to reply to this source IP 10.0.5.50, my routing table says it lives on my internal LAN interface. But the packet just physically arrived on my external WAN interface. It's geographically impossible." The router instantly drops it as a spoofed packet.
- Immediate Triage: This is an IP Spoofing attack. The attacker manually alters the IP header of their malicious pa
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Treating stateless Network ACLs as stateful firewalls without specifying outbound ephemeral return ports when configuring Networking logs indicating Security Groups track connection state automatically, whereas stateless Network ACLs require explicit ephemeral port rules (1024-65535) for return traffic.
- Opening short-lived non-pooled TCP client connections, exhausting ephemeral ports in TIME_WAIT state when configuring Networking logs indicating Rapidly opening and closing short-lived TCP sockets without connection pooling exhausts ephemeral ports, causing connection refusal errors.
- Directing load balancer health checks to heavy computational endpoints rather than dedicated health routes when configuring Networking logs indicating Deep health check paths amplify database load during traffic spikes and risk cascading eviction of healthy application nodes.
- Triggering BGP route dampening by rapidly announcing and withdrawing multihomed network prefixes when configuring Networking logs indicating Rapidly flapping BGP route announcements triggers upstream ISP route dampening, effectively blackholing network traffic for hours.