<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Active on Wirez</title><link>https://wirez.top/tags/active/</link><description>Recent content in Active on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 16 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/active/index.xml" rel="self" type="application/rss+xml"/><item><title>IPv6 native traffic: How to push past 80% at home</title><link>https://wirez.top/posts/ipv6-native-traffic-how-to-push-past-80-at-home/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ipv6-native-traffic-how-to-push-past-80-at-home/</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;strong>Debian ISO downloads&lt;/strong> forcing native connectivity, home networks can push &lt;strong>IPv6 traffic&lt;/strong> above &lt;strong>80%&lt;/strong> as proven by &lt;strong>Terry Sweester&lt;/strong>.&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></channel></rss>