Topic33 problems· 5 reviewed

Firewall and Proxy Paths

33 incident problems about Firewall and Proxy Paths. Start with the reviewed ones.

All problems (33)

NETWORK-1485A BGP community policy looks symmetric and one route reflector still leaks defaultsDefault routes leak only during maintenance refreshes and not during normal convergence.NetworkAdvanced12 minPro NETWORK-1481A pfSense policy route looks correct and return traffic still escapesReturn traffic still uses the old WAN path after a gateway group failover policy update.NetworkAdvanced12 minPro NETWORK-060SD-WAN policy prefers the worse pathThe controller has path metrics, but the application policy still chooses the higher-latency circuit because the SLA measurement feeding the decision is scoped incorrectly.NetworkAdvanced27 minPro NETWORK-039VRF leak design misses the import policy for a shared services subnetThe route exists in the source VRF, but shared services remain unreachable because the target VRF never imports the right route target or policy match.NetworkAdvanced27 minPro NETWORK-1484An NGINX upstream DNS update is correct and one pool still serves dead backendsTraffic continues hitting dead backend IPs after a DNS cutover behind NGINX.NetworkIntermediate10 minPro NETWORK-030Blue-green cutover misses webhook callback allowlistThe new stack goes live, but one callback provider still points at the old address because its allowlist and DNS cutover are out of sync.NetworkIntermediate19 minPro NETWORK-022Internal DNS resolves the old targetMost clients pick up the new destination, but a subset stays on the stale IP because resolver behavior is inconsistent.NetworkIntermediate21 minPro NETWORK-028TLS handshake fails only through one CDN POPTLS handshake fails only (Certificate Trust Failure) is a hands-on troubleshooting drill. Most regions succeed, but a single edge location negotiates an older TLS path and breaks the request. Azure Firewall and Proxy Paths needs to be checked by narrowing scope, recent change,...NetworkIntermediate22 minPro NETWORK-008Packet loss that recurs only between the application and the DBStep-by-step narrowing of a situation where the whole network looks fine but loss occurs on only a specific path.NetworkAdvanced26 minPro NETWORK-005Only certain gRPC requests intermittently fail due to an MTU mismatchTracks MTU and segment size in a situation where small requests work but only large requests break in the middle.NetworkAdvanced27 minPro NETWORK-023Packet loss appears only under east-west service mesh trafficPacket loss appears only (Firewall and Proxy Paths) is a hands-on troubleshooting drill. North-south traffic looks stable, but encrypted internal mesh traffic drops packets under burst load. Firewall and Proxy Paths needs to be checked by narrowing scope, recent change, and th...NetworkAdvanced27 minPro NETWORK-018A proxy keepalive setting difference makes latency spike for only certain APIsA situation where, on the same server, only some paths are unusually slow because of a difference in upstream connection reuse policy.NetworkIntermediate20 minPro NETWORK-025HTTP keepalive pool sends requests to drained backendHTTP keepalive pool sends requests to drained backend is a hands-on troubleshooting drill. A backend has been removed from the balancer, but idle pooled connections continue sending requests there for a while. DNS and Routing needs to be checked by narrowing scope, recent chan...NetworkIntermediate20 minPro