<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Path on Wirez</title><link>https://wirez.top/tags/path/</link><description>Recent content in Path on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/path/index.xml" rel="self" type="application/rss+xml"/><item><title>RPKI route validation cuts $4.44M breach risk</title><link>https://wirez.top/posts/rpki-route-validation-cuts-444m-breach-risk/</link><pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-route-validation-cuts-444m-breach-risk/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With cybercrime costing $10.5 trillion in 2026, ignoring &lt;strong>cryptographic route validation&lt;/strong> is financial negligence. The stability of the global network now demands that operators abandon fragile manual databases for &lt;strong>RPKI Route Origin Authorizations&lt;/strong> to prevent catastrophic hijacking. Readers will examine the critical transition from the error-prone &lt;strong>Internet Routing Registry&lt;/strong> to modern cryptographic standards that bind prefixes to origin ASNs automatically. We dissect the mechanics of &lt;strong>AS path authorization&lt;/strong>, detailing how routers drop invalid routes in real-time rather than relying on outdated static lists. Finally, the analysis covers practical deployment using &lt;strong>MyAPNIC&lt;/strong> and &lt;strong>DASH monitoring&lt;/strong> to visualize complex data streams. &lt;a href="https://blog.apnic.net/2025/12/12/nro-rpki-program-2025-in-review/" target="_blank" rel="noopener noreferrer">APNIC&amp;#039;s nro rpki program 2025 in review&lt;/a>&lt;/p></description></item><item><title>SCION routing fixes BGP's 40-year security gap</title><link>https://wirez.top/posts/scion-routing-fixes-bgps-40-year-security-gap/</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/scion-routing-fixes-bgps-40-year-security-gap/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Over 7,000 route entries remained invalid in March 2020 despite decades of patch attempts. The Border Gateway Protocol fundamentally lacks native mechanisms to verify address ownership, rendering current fixes like RPKI insufficient against sophisticated &lt;strong>route hijacks&lt;/strong>. While extensions such as &lt;strong>BGPsec&lt;/strong> attempt to secure the AS_PATH attribute, they impose heavy computational overhead and fail to address the core architectural rot of a forty-year-old system.&lt;/p></description></item><item><title>ASPA validation stops Cloudflare route hijacks now</title><link>https://wirez.top/posts/aspa-validation-stops-cloudflare-route-hijacks-now/</link><pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/aspa-validation-stops-cloudflare-route-hijacks-now/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">&lt;a href="https://www.cloudflare.com/" target="_blank" rel="noopener noreferrer">Cloudflare&lt;/a>, handling over 20% of global traffic, now validates BGP paths to stop leaks that origin checks miss. &lt;a href="https://blog.cloudflare.com/white-house-routing-security/" target="_blank" rel="noopener noreferrer">Cloudflare&amp;#039;s white house routing security&lt;/a> &lt;strong>ASPA&lt;/strong> closes the critical security gap between simple route origin validation and full path verification by cryptographically authorizing upstream providers. While the broader network security market races toward $47.37 billion by 2031, core internet infrastructure still relies on trust-based protocols vulnerable to detours. Readers will learn why validating the &lt;strong>AS_PATH&lt;/strong> chain is essential when standard &lt;strong>RPKI&lt;/strong> mechanisms fail to detect unauthorized intermediate hops. We examine how &lt;strong>Cloudflare&amp;#039;s&lt;/strong> March 2026 implementation allows networks to publish authorized provider lists, ensuring traffic traverses only approved chains. The discussion details the operational steps for creating &lt;strong>ASPA objects&lt;/strong> and monitoring their propagation to eliminate route leaks.&lt;/p></description></item><item><title>PMTUD black holes stall your video calls now</title><link>https://wirez.top/posts/pmtud-black-holes-stall-your-video-calls-now/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/pmtud-black-holes-stall-your-video-calls-now/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">When packets exceed 1500 bytes, &lt;a href="https://www.cloudflare.com/" target="_blank" rel="noopener noreferrer">Cloudflare&lt;/a>&amp;#039;s 2026 data confirms that silent ICMP drops create a &lt;strong>zombie state&lt;/strong> where connections hang indefinitely. &lt;a href="https://blog.cloudflare.com/client-dynamic-path-mtu-discovery/" target="_blank" rel="noopener noreferrer">Cloudflare&amp;#039;s client dynamic path mtu discovery&lt;/a> The industry must abandon fragile reliance on legacy feedback loops in favor of &lt;strong>Dynamic Path MTU Discovery&lt;/strong> to ensure connectivity across restrictive modern networks. This article details how active probing architectures utilizing &lt;strong>QUIC&lt;/strong> and &lt;strong>MASQUE&lt;/strong> protocols bypass firewall restrictions that traditionally block essential size-limit notifications. We examine the mechanics of the &lt;strong>PMTUD Black Hole&lt;/strong>, specifically how encrypted overhead in FIPS 140-2 compliant clients exacerbates fragmentation issues on LTE/5G and FirstNet links. Furthermore, we outline enterprise deployment strategies for hybrid environments, demonstrating how shifting from static configurations to dynamic discovery prevents data streams from failing during critical video calls or large file transfers. By adopting these methods, organizations can finally resolve the decades-old conflict between rigid infrastructure expectations and the reality of variable path limits without sacrificing security metadata.&lt;/p></description></item><item><title>Active path verification stops blackhole errors</title><link>https://wirez.top/posts/active-path-verification-stops-blackhole-errors/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/active-path-verification-stops-blackhole-errors/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With &lt;a href="https://datatracker.ietf.org/doc/html/rfc6480" target="_blank" rel="noopener noreferrer">RPKI&lt;/a> adoption for leased prefixes surging from 29.9% in 2021 to 71.0% by late 2024, validating &lt;strong>blackhole routes&lt;/strong> remains dangerously ambiguous. Blindly propagating these filters across all points of view often collapses complex routing topologies into a single, erroneous perspective that the source ASN never authorized.&lt;/p></description></item><item><title>Blackhole route checks: Stop accidental outages</title><link>https://wirez.top/posts/blackhole-route-checks-stop-accidental-outages/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/blackhole-route-checks-stop-accidental-outages/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With the SDN market projected to grow over 4x in the next decade, automating &lt;strong>blackhole route&lt;/strong> validation is no longer optional. Reliance on legacy Internet Routing Registry (IRR) data creates critical vulnerabilities where unauthorized traffic suppression can cascade across networks due to blind acceptance of unverified path requests.&lt;/p></description></item><item><title>Blackhole validation must use active path data now</title><link>https://wirez.top/posts/blackhole-validation-must-use-active-path-data-now/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/blackhole-validation-must-use-active-path-data-now/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Strict path verification now overrides legacy IRR checks, as 2026 mandates enforce penalties for invalid blackhole route requests. The industry has decisively shifted from voluntary filtering to rigid &lt;strong>enforcement protocols&lt;/strong>, where regulators and Tier-1 providers penalize operators who fail to validate traffic forwarding paths accurately. Job Snijders confirmed in a March 2026 NANOG discussion that modern &lt;strong>blackhole validation&lt;/strong> must discard reliance on unverified IRR data, noting that such arbitrary lists lack the provenance required for today&amp;#039;s compliance environment. Instead, operators must verify if IP traffic is actively forwarded to the requesting entity before honoring any mitigation request.&lt;/p></description></item><item><title>ASPA records prove your upstream provider ties</title><link>https://wirez.top/posts/aspa-records-prove-your-upstream-provider-ties/</link><pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/aspa-records-prove-your-upstream-provider-ties/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">&lt;a href="https://www.cloudflare.com/" target="_blank" rel="noopener noreferrer">Cloudflare&lt;/a> handles over 20% of global Internet traffic, yet standard BGP routing remains vulnerable to undetected path manipulation. &lt;a href="https://blog.cloudflare.com/bgp-hijack-detection/" target="_blank" rel="noopener noreferrer">Cloudflare&amp;#039;s bgp hijack detection&lt;/a> The deployment of &lt;strong>ASPA records&lt;/strong> under &lt;strong>RFC 9582&lt;/strong> represents the critical shift from verifying only traffic origins to validating the entire transmission path against configuration errors and malicious leaks. While &lt;strong>ROA&lt;/strong> systems successfully mitigate origin hijacks, they fail to detect when traffic traverses unauthorized intermediate networks, a gap this new cryptographic standard explicitly closes.&lt;/p></description></item><item><title>RPKI path security: The shift past origin checks</title><link>https://wirez.top/posts/rpki-path-security-the-shift-past-origin-checks/</link><pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/rpki-path-security-the-shift-past-origin-checks/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">A 539% surge in Unique &lt;a href="https://datatracker.ietf.org/doc/html/rfc9582" target="_blank" rel="noopener noreferrer">ASPA&lt;/a> Customer ASIDs proves the &lt;strong>RPKI database&lt;/strong> has shifted from simple origin checks to complex path validation.&lt;/p></description></item><item><title>ASPATH length traps: When short routes risk security</title><link>https://wirez.top/posts/aspath-length-traps-when-short-routes-risk-security/</link><pubDate>Thu, 01 Jan 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/aspath-length-traps-when-short-routes-risk-security/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Shorter &lt;strong>AS_PATH lengths&lt;/strong> win route selection when other BGP criteria tie, per RFC 4271.&lt;/p>
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">In reality, actual reachability depends entirely on external &lt;strong>filtering policies&lt;/strong> and &lt;strong>RPKI validation&lt;/strong>, not just path metrics. As bogdancyber clarified on the NANOG mailing list in January 2026, conflating path brevity with trust creates dangerous blind spots in &lt;strong>risk modeling&lt;/strong> for potential hijacks.&lt;/p></description></item></channel></rss>