<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Weberblog.net</title>
	<atom:link href="https://weberblog.net/feed/" rel="self" type="application/rss+xml" />
	<link>https://weberblog.net</link>
	<description>IT-Security, Networks, IPv6, VPN, DNSSEC, NTP</description>
	<lastBuildDate>Sun, 01 Nov 2026 17:30:44 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://weberblog.net/wp-content/uploads/2018/05/cropped-webernetz-logo-4-icon-2000x2000-1-32x32.png</url>
	<title>Weberblog.net</title>
	<link>https://weberblog.net</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">52315419</site>	<item>
		<title>Is a registered Domain really Unavailable?</title>
		<link>https://weberblog.net/is-a-registered-domain-really-unavailable/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=is-a-registered-domain-really-unavailable</link>
					<comments>https://weberblog.net/is-a-registered-domain-really-unavailable/#comments</comments>
		
		<dc:creator><![CDATA[Marco Davids]]></dc:creator>
		<pubDate>Wed, 30 Sep 2026 19:04:25 +0000</pubDate>
				<category><![CDATA[DNS/DNSSEC]]></category>
		<category><![CDATA[DNS]]></category>
		<category><![CDATA[registrar]]></category>
		<category><![CDATA[RFC]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14637</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" fetchpriority="high" srcset="https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image.jpg 1920w" sizes="(max-width: 300px) 100vw, 300px" />There is a small but surprisingly important piece of information that the DNS does not normally tell you. You query a domain name and discover that it is already registered. From the perspective of a registrar&#8217;s availability checker, that is usually the end of the story. But it may not be. The domain may be &#8230; <a href="https://weberblog.net/is-a-registered-domain-really-unavailable/" class="more-link">Continue reading <span class="screen-reader-text">Is a registered Domain really Unavailable?</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" srcset="https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/09/Is-a-registered-Domain-really-Unavailable-featured-image.jpg 1920w" sizes="(max-width: 300px) 100vw, 300px" /><p>There is a small but surprisingly important piece of information that the DNS does not normally tell you. You query a domain name and discover that it is already registered. From the perspective of a registrar&#8217;s availability checker, that is usually the end of the story.</p>
<p>But it may not be. The domain may be parked. It may be unused. It may be held by a domain investor. And, quite possibly, its owner may be perfectly happy to sell it.</p>
<p>So, there are really two different questions:</p>
<p><strong><div class="su-note"  style="border-color:#d88a59;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#f2a473;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">&#8220;Is this domain name registered?&#8221;</strong> vs. &#8220;<strong>Is this domain name obtainable?&#8221;</div></div></strong></p>
<p>DNS, WHOIS and RDAP are good at answering the first question. Until recently, there was no simple, standardised way to answer the second. That is what <a href="https://www.rfc-editor.org/rfc/rfc10023.html" target="_blank" rel="noopener"><strong>RFC 10023</strong></a> tries to fix.</p>
<p><span id="more-14637"></span></p>
<h2>The missing bit of information</h2>
<p>Consider a perfectly ordinary DNS query:</p>
<p><code>$ dig example.com A<br />
example.com. 300 IN A 192.0.2.1</code></p>
<p>You now know that <code>example.com</code> exists and that it has an A record. And if you check registration data, you may also learn that someone holds the domain.</p>
<p>What you don&#8217;t know is whether the holder would sell it.</p>
<p>That distinction matters because the market for already-registered domain names is substantial. There are registrars and marketplaces offering brokerage services, domain investors maintaining portfolios, and automated systems watching domains that are about to expire. None of this is new, and RFC 10023 certainly does not attempt to change that market.</p>
<p>In fact, there is a slightly uncomfortable observation behind the whole idea: <strong>Domain names are already being traded. We just don&#8217;t have a particularly good way of signalling that fact.</strong></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetfalcon-packet-capture" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketFalcon.1208x232.webp" /></a></div>
<h2>The &#8220;digital for-sale sign&#8221;</h2>
<p>RFC 10023 introduces a deliberately boring solution: <strong>a DNS TXT record at a reserved name</strong>:</p>
<p><code>_for-sale.example.com. IN TXT "v=FORSALE1;"</code></p>
<p>That&#8217;s it.</p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">The <code>_for-sale</code> label indicates that the parent domain is available for purchase. The indicator can be added or removed by the domain holder, without changing the domain&#8217;s normal DNS operation.</div></div>
<p>The record can also contain additional information. For example:</p>
<p><code>_for-sale.example.com. IN TXT "v=FORSALE1;furi=https://example.com/sale"<br />
_for-sale.example.com. IN TXT "v=FORSALE1;fval=EUR5000"<br />
_for-sale.example.com. IN TXT "v=FORSALE1;ftxt=This domain is for sale"</code></p>
<p>The convention supports machine-readable URIs, asking prices, human-readable text, and processor-specific codes. Multiple TXT records can coexist, with each record carrying at most one content item.</p>
<p>There is no new protocol, no new transport, no API and no registry-wide database that needs to be synchronised.</p>
<p>You simply ask DNS:</p>
<p><code>$ dig TXT _for-sale.example.com</code></p>
<p>And DNS can answer.</p>
<h2>Why put this in DNS?</h2>
<p>This is where I think the idea becomes more interesting to DNS people. DNS is not a domain marketplace. It does not need to become one. It is, however, a globally distributed naming system in which domain holders already control their own zone data. <strong>That makes DNS a surprisingly good place for a simple statement of intent.</strong></p>
<p>The <code>_for-sale</code> record is not a transaction. It is not proof of ownership. It is not a binding offer. It does not define how a sale is negotiated, who acts as broker, or what happens after somebody makes an offer.</p>
<p>It simply says: <strong>&#8220;This registered domain is available for purchase.&#8221;</strong></p>
<p>The actual transaction remains completely outside DNS. This is an important design boundary. RFC 10023 defines the signalling mechanism; it deliberately does not attempt to standardize the domain-sales process itself.</p>
<h2>From humans reading DNS to machines discovering inventory</h2>
<p>The really interesting part is what happens when software starts looking for this signal.</p>
<p>Today, a domain search typically works something like this:</p>
<ol>
<li>A user enters <code>interesting-domain.example</code> into a registrar&#8217;s search interface.</li>
<li>The registrar determines that the domain is already registered.</li>
<li>The user sees something equivalent to &#8220;unavailable&#8221;.</li>
<li>The user tries another name.</li>
</ol>
<p>But suppose the domain publishes:</p>
<p><code>_for-sale.interesting-domain.example. IN TXT "v=FORSALE1;furi=https://..."</code></p>
<p>Now the result can be different: <strong>Registered &#8211; but available for purchase</strong>.</p>
<p>That is a much more useful answer. A registrar, search engine, domain marketplace or other application can query the <code>_for-sale</code> node automatically and incorporate the result into its own interface.</p>
<p>The user no longer needs to know that the domain happens to be listed on Marketplace X, Brokerage Y or some obscure landing page. The signal is attached to the domain itself. This is potentially a fairly fundamental change in domain discovery:</p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">Instead of searching marketplaces to find domains, applications can discover domains for sale directly from DNS.</div></div>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetfalcon-packet-capture" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketFalcon.1208x232.webp" /></a></div>
<h2>But isn&#8217;t this just helping domainers?</h2>
<p>This is probably the most legitimate objection. The domain aftermarket has a complicated reputation. Domain investors, brokers and especially drop-catchers are not universally loved, and for good reason in some cases.</p>
<p><strong>So why would we want to make domain trading easier? Because the alternative isn&#8217;t a world without domain trading.</strong> It is a world where a domain holder who no longer wants a domain may simply let it expire &#8211; while someone else with better tooling, better timing and more resources catches it milliseconds later.</p>
<p>Consider the following situation: Someone registered <code>great-example.tld</code> five years ago. They no longer need it. They don&#8217;t have a website there. They don&#8217;t particularly care about the domain, but they also don&#8217;t know how to sell it. Eventually they stop renewing it.</p>
<p>When the domain is released, a drop-catching service catches it and puts it into a portfolio. The former holder gets nothing. The new holder may subsequently sell it for €500, €5,000 or perhaps much more. That is already part of today&#8217;s domain ecosystem.</p>
<p>A simple <code>_for-sale</code> signal introduces another possibility:</p>
<p><strong>Owner wants to sell &#8211;&gt; publishes _for-sale &#8211;&gt; buyers can discover it &#8211;&gt; direct negotiation / broker / marketplace &#8211;&gt; owner receives the proceeds</strong></p>
<p>The domain doesn&#8217;t have to go through the drop cycle first. That doesn&#8217;t eliminate domain investors. It doesn&#8217;t eliminate brokers. It doesn&#8217;t eliminate drop-catching.</p>
<p>And it certainly doesn&#8217;t prevent somebody from making a profit by buying a domain cheaply and selling it later.</p>
<p>What it potentially does is <strong>move some transactions from an opaque &#8220;let it drop and see who catches it&#8221; mechanism towards an explicit &#8220;the owner wants to sell it&#8221; mechanism</strong>. That seemed like a worthwhile direction.</p>
<h2>A more balanced aftermarket</h2>
<p>There is an interesting asymmetry in the current domain market. If you want to sell a car, you can put a &#8220;For Sale&#8221; sign on it, advertise it, or list it on a marketplace. If you want to sell a domain, you can certainly do those things too. But there is no universally recognized signal attached to the domain itself saying that it is for sale.</p>
<p>A domain can therefore be simultaneously:</p>
<ul>
<li>registered,</li>
<li>unused,</li>
<li>potentially valuable,</li>
<li>and available for purchase,</li>
</ul>
<p>while most automated domain discovery systems simply report: <strong>Taken</strong>. That is a surprisingly lossy representation of reality.</p>
<p>RFC 10023 adds one bit of information: <strong>Taken &#8211; but for sale</strong>.</p>
<p>And that bit can be consumed by anyone. This openness is important. A domain holder doesn&#8217;t have to commit to a particular marketplace. A registrar can build support into its own tooling. A broker can use it. A registry can use it. A completely independent application can query DNS directly.</p>
<p>The standard deliberately does not make one commercial intermediary the gatekeeper.</p>
<h2>The DNS record is not the marketplace</h2>
<p>There is also a subtle security and operational benefit to keeping the standard small. RFC 10023 doesn&#8217;t attempt to turn TXT records into a mini e-commerce protocol. It does not define auctions. It does not define authentication of purchase offers. It does not define how a registrar transfers a domain after a successful sale. And it does not say that a price found in DNS constitutes a binding offer. <strong>It is simply a signalling convention.</strong></p>
<p>For example, a registry could use an opaque <code>fcod</code> value that maps to a controlled sales landing page:</p>
<p><code>_for-sale.example.com. IN TXT \<br />
"v=FORSALE1;fcod=EXAMPLE-abc123"</code></p>
<p>A registrar or registry can then decide what that code means and where the interested party is sent.</p>
<p>Alternatively, an owner could publish a URI directly:</p>
<p><code>_for-sale.example.com. IN TXT \<br />
"v=FORSALE1;furi=https://example.com/buy"</code></p>
<p>Or even just:</p>
<p><code>_for-sale.example.com. IN TXT \<br />
"v=FORSALE1;ftxt=Domain name is for sale"</code></p>
<p>The convention remains useful at all three levels.</p>
<h2>And yes, this can be automated</h2>
<p>The most interesting applications may not be human-facing DNS tools at all.</p>
<p>Imagine a registrar&#8217;s search engine receiving:</p>
<p><code>example.com          registered<br />
example.net          available<br />
example.org          registered</code></p>
<p>Today, the first and third results are effectively dead ends.</p>
<p>With RFC 10023 they can become:</p>
<p><code>example.com          registered – for sale<br />
example.net          available<br />
example.org          registered – (no for sale sign)</code></p>
<p>That distinction enables new user interfaces and discovery mechanisms.</p>
<ul>
<li>A domain suggestion engine could include domains that are registered but purchasable.</li>
<li>A marketplace could automatically discover owner-published inventory rather than relying entirely on manually submitted listings.</li>
<li>A broker could monitor DNS for domains whose owners explicitly signal an intention to sell.</li>
<li>And a domain holder could potentially reach prospective buyers without first handing the domain to a marketplace.</li>
</ul>
<p>This is where the &#8220;digital for-sale sign&#8221; metaphor becomes quite literal.</p>
<h2>Why not just use the website?</h2>
<p>A natural question is: why not put &#8220;This domain is for sale&#8221; on the website? &#8211;&gt; Because the website may not exist.</p>
<p>A domain for sale is quite often parked, unused, or configured with completely unrelated content. In some cases, there isn&#8217;t even a functioning web server.</p>
<p>The DNS, however, is already the infrastructure used to establish that the domain exists and how it is operated.</p>
<p>And <code>_for-sale</code> is deliberately a leaf node. It does not interfere with existing records:</p>
<p><code>example.com.              IN A     192.0.2.1<br />
www.example.com.          IN CNAME example.com.<br />
_for-sale.example.com.    IN TXT   "v=FORSALE1;"</code></p>
<p>The site can continue running normally while the domain is being offered for sale. The RFC explicitly allows the convention to be used even when the domain remains actively in use.</p>
<h2>DNS as a signalling layer</h2>
<p>There is a broader lesson here. DNS already carries a remarkable amount of metadata about how names are intended to be used. We routinely use <a href="https://www.iana.org/assignments/dns-parameters#underscored-globally-scoped-dns-node-names" target="_blank" rel="noopener">underscored names for service discovery</a> and other operational signalling.</p>
<p>RFC 10023 uses exactly that mechanism, registering <code>_for-sale</code> as an underscored and globally scoped DNS node name.</p>
<p>The interesting property is not the TXT syntax itself. It is the separation between <strong>the name</strong> and <strong>the information about the name</strong>.</p>
<p>A DNS query can tell us: &#8220;This name exists.&#8221;</p>
<p>A <code>_for-sale</code> query can additionally tell us: &#8220;The holder says this name is available for purchase.&#8221; That is a tiny addition to the DNS namespace, but it can remove a surprisingly large amount of ambiguity from applications built on top of it.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/network-traffic-tapping" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRaven.1208x232.webp" /></a></div>
<h2>Don&#8217;t confuse a signal with a guarantee</h2>
<p>There is, of course, a caveat. DNS says what the zone says. It does not magically make that statement legally binding. The presence of <code>_for-sale</code> does not obligate the holder to complete a transaction. The record may have been published in error, or the owner may withdraw the domain from sale later. RFC 10023 explicitly acknowledges this distinction.</p>
<p>Likewise, automatically consuming asking prices deserves some caution. A price in DNS should not be treated as an unconditional purchase commitment.</p>
<p>And publishing an email address or telephone number in DNS has obvious privacy and abuse implications. The RFC therefore also discusses scraping, spam and unwanted contact.</p>
<p>These are not reasons to reject the mechanism. They are reasons to use it sensibly.</p>
<h2>One tiny DNS record, one useful bit of information</h2>
<p>There is something appealing about the simplicity of RFC 10023.</p>
<p>No new protocol.<br />
No new port.<br />
No registry API.<br />
No centralized database.<br />
No requirement to choose a particular marketplace.<br />
No requirement to park the domain.<br />
No requirement to take the existing website offline.</p>
<p>Just:</p>
<p><code>_for-sale.example.com. IN TXT "v=FORSALE1;"</code></p>
<p>And suddenly an important distinction becomes machine-readable. A registered domain isn&#8217;t necessarily unavailable. That may sound obvious to anyone involved in the domain industry. But for software, &#8220;registered&#8221; has traditionally been a rather poor proxy for &#8220;not obtainable&#8221;.</p>
<p>RFC 10023 gives applications a better answer. And perhaps more importantly, it gives domain holders a way to say:</p>
<p><strong>&#8220;Don&#8217;t wait for me to drop this domain. I actually want to sell it.&#8221;</strong></p>
<p>The domain aftermarket isn&#8217;t going away. Nor should a DNS convention attempt to regulate it.</p>
<p>But if domain trading is already happening, there is a good argument for making the market <strong>more transparent, more discoverable and a little more balanced between the people who own domain names and the people who have the tools to find them when they expire.</strong></p>
<p>Sometimes the most useful DNS extensions are not the complicated ones.</p>
<p>Sometimes all you need is a sign.</p><pre class="urvanov-syntax-highlighter-plain-tag">+----------------------+
                    |      example.com     |
                    |                      |
                    |      Website / DNS   |
                    +----------+-----------+
                               |
                               |
                    _for-sale.example.com
                               |
                               v
                       "v=FORSALE1;"
                               |
             +-----------------+-----------------+
             |                 |                 |
             v                 v                 v
          Registrar         Broker          Search engine
             |                 |                 |
             +-----------------+-----------------+
                               |
                               v
                         Potential buyer</pre><p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">The domain is registered. The DNS says it is for sale. Now the Internet can know the difference.</div></div>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@markusspiske?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/photos/a-mannequin-in-a-window-display-with-a-sale-sign-WIpNUhklTQg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/is-a-registered-domain-really-unavailable/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14637</post-id>	</item>
		<item>
		<title>October 2026: Another leap second coming???</title>
		<link>https://weberblog.net/october-2026-another-leap-second-coming/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=october-2026-another-leap-second-coming</link>
					<comments>https://weberblog.net/october-2026-another-leap-second-coming/#comments</comments>
		
		<dc:creator><![CDATA[Steven Sommars]]></dc:creator>
		<pubDate>Thu, 17 Sep 2026 16:07:34 +0000</pubDate>
				<category><![CDATA[NTP]]></category>
		<category><![CDATA[Bug]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[leap second]]></category>
		<category><![CDATA[NTP Pool Project]]></category>
		<category><![CDATA[UTC]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14610</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" srcset="https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image.jpg 1920w" sizes="(max-width: 300px) 100vw, 300px" />An unknown number of NTP servers may mistakenly announce an upcoming leap second during October 2026. If this occurs some NTP clients&#8217; time could briefly be in error by one second. The atomic second used in coordinated universal time (UTC) is defined by a specified atomic transition in cesium (caesium) atoms is constant. The solar &#8230; <a href="https://weberblog.net/october-2026-another-leap-second-coming/" class="more-link">Continue reading <span class="screen-reader-text">October 2026: Another leap second coming???</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/09/October-2026-Another-leap-second-coming-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>An unknown number of NTP servers may mistakenly announce an upcoming leap second during October 2026. If this occurs <strong>some NTP clients&#8217; time could briefly be in error by one second</strong>.</p>
<p><span id="more-14610"></span></p>
<p>The atomic second used in coordinated universal time (UTC) is defined by a specified atomic transition in cesium (caesium) atoms is constant. The solar second, computed using the Sun&#8217;s position in the sky, has changed measurably over the past century. <strong>The<a href="https://en.wikipedia.org/wiki/Leap_second" target="_blank" rel="noopener"> leap second</a> was introduced so that UTC would not drift appreciably from solar time.</strong> On dates announced in advance by the International Earth Rotation and Reference Systems Service (IERS), a leap second is added or subtracted from UTC. All previous leap seconds have occurred on June 30, or December 31. The most recent leap second occurred on December 31, 2016.</p>
<p>The<strong><a href="https://en.wikipedia.org/wiki/Global_Positioning_System" target="_blank" rel="noopener"> Global Positioning System</a> (GPS)</strong> distributes GPS-time, an indication of an upcoming leap second, and the GPS-UTC time difference (integral number of seconds). The specification for the second item, notification of an upcoming leap second, has sometimes been misinterpreted.</p>
<p>The <a href="https://www.rfc-editor.org/info/rfc5905/" target="_blank" rel="noopener"><strong>Network Time Protocol</strong></a><strong> (NTP)</strong>, used to transfer time between two IP-connected computers, uses a two-bit leap second indicator to inform clients that &#8220;an impending leap second to be inserted or deleted in the last minute of the current month&#8221; [RFC5905].</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetlion-aggregation-packet-broker" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketLion.1208x232.webp" /></a></div>
<p>On two separate days in November 2021, 256 weeks after the previous occurrence, a <a href="https://weberblog.net/partial-ntp-pool-the-leap-second-that-wasnt/"><em>spurious</em> leap second</a> was advertised by several NTP servers. <strong>256 weeks after that, in October 2026, some NTP servers are expected to again incorrectly advertise an upcoming leap second.</strong> One group of NTP servers may advertise on Saturday, October 24, 2026 and another group of servers on October 31, 2026. Some NTP servers contain logic to defer leap second advertisement until the last day of the current month, thus the October 31, 2026 date. A short technical discussion can be found <a href="https://febo.com/pipermail/time-nuts_lists.febo.com/2025-November/thread.html#110278" target="_blank" rel="noopener">here</a>, <strong>the root cause is a GPS specification misinterpretation</strong>. The raw leap second data is provided correctly by the GPS receiver, but is incorrectly converted before being sent to the NTP server.</p>
<p>The November 2021 errors affected 150+ NTP servers, but I saw no reports of ill effects. The extent of any October 2026 errors is unknown, I&#8217;ve notified several administrators in advance. There are hundreds of millions NTP clients in the world. Whether any given client would be affected is an &#8220;it depends&#8221; question. One of the best ways to protect clients from spurious notifications is through the use of a <a href="https://kb.meinbergglobal.com/kb/time_sync/ntp/configuration/ntp_leap_second_file" target="_blank" rel="noopener">leap seconds file</a>, if that is supported in the client&#8217;s NTP software.</p>
<p>I will update this note with results later. It would be prudent to install the latest software from your NTP server vendor.</p>
<p>Update 2026-10-24 00:10 UTC    37 NTP stratum 1 servers are announcing leap=1.</p>
<p>Update 2026-11-01 16:00 UTC.   The bogus leap second happened this morning.  I observed  24 NTP servers advertising leap=1 prior to midnight.  Some servers were seen executing a leap second procedure (time changed by one second).</p>
<p>Were <em>clients</em> affected by the incorrect leap second? I monitored client requests on five separate NTP Pool servers (these did not advertised a leap second). Four of the servers showed very few client requests with leap=1. An NTP server in London had over 1% of its clients sending requests with leap=1, however.</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@joseph3088?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Duncan Sanchez</a> on <a href="https://unsplash.com/photos/black-framed-dali-uhr-clock-QyaFwkWuEDk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/october-2026-another-leap-second-coming/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14610</post-id>	</item>
		<item>
		<title>Modbus Fundamentals</title>
		<link>https://weberblog.net/modbus-fundamentals/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=modbus-fundamentals</link>
					<comments>https://weberblog.net/modbus-fundamentals/#respond</comments>
		
		<dc:creator><![CDATA[Martin Mayer]]></dc:creator>
		<pubDate>Wed, 26 Aug 2026 05:16:11 +0000</pubDate>
				<category><![CDATA[Operational Technology (OT)]]></category>
		<category><![CDATA[Modbus]]></category>
		<category><![CDATA[TCP]]></category>
		<category><![CDATA[Ultimate PCAP]]></category>
		<category><![CDATA[Wireshark]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14572</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />If you’re dealing with industrial protocols, you’ll certainly have seen Modbus packets in your network. But what are these packets used for, and what data do they contain? Before we dive into Modbus, let’s have a quick look at an example. Let&#8217;s assume you have a meeting in your meeting room. You enter the room &#8230; <a href="https://weberblog.net/modbus-fundamentals/" class="more-link">Continue reading <span class="screen-reader-text">Modbus Fundamentals</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-Fundamentals-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>If you’re dealing with industrial protocols, you’ll certainly have seen <strong>Modbus packets</strong> in your network. <strong>But what are these packets used for, and what data do they contain?</strong></p>
<p><span id="more-14572"></span></p>
<p>Before we dive into Modbus, let’s have a quick look at an example. Let&#8217;s assume you have a meeting in your meeting room. You enter the room one hour before the meeting starts to have everything prepared, and you notice that it’s quite cold. Fortunately, there is a small display beside the door telling you that somebody set the room temperature to 19 °C.  Four presses on the button with the up-arrow and you’re quite confident that the room temperature will reach 23 °C until the meeting starts.</p>
<p>So, what happens in the background? Somewhere in the building, a PLC (Programmable Logic Controller) is responsible for controlling and orchestrating all the devices which play a role in cooling or heating the air which flows into the meeting room.</p>
<p>This PLC needs to read the setpoint from the small device on which you recently changed the setpoint from 19 to 23 °C. Afterwards, it spins up the fan’s rotation speed and tells a second PLC, which controls the heater, to increase the output.</p>
<p>Additionally, the technical staff oversees, controls and supervises all processes in the building using a SCADA system by acquiring data from the PLCs or sending data to them.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetroo-data-diode" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRoo.1208x232.webp" /></a></div>
<p>The conclusion of this example is that <strong>a lot of entities need to exchange information to have their job done</strong>. Historically, these communications have been realised using bus systems, as has Modbus using RS-232 or RS-485 (Modbus/RTU). (There also exists Modbus/ASCII, which uses ASCII characters, but we’ll not focus on this.)</p>
<p>To overcome the limitations of local buses, <strong>the Modbus protocol was slightly modified to be transported using TCP</strong>. Modbus/TCP was born.</p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-14575 size-large" src="https://weberblog.net/wp-content/uploads/2026/07/Modbus.drawio-1024x216.png" alt="" width="604" height="127" srcset="https://weberblog.net/wp-content/uploads/2026/07/Modbus.drawio-1024x216.png 1024w, https://weberblog.net/wp-content/uploads/2026/07/Modbus.drawio-300x63.png 300w, https://weberblog.net/wp-content/uploads/2026/07/Modbus.drawio-768x162.png 768w, https://weberblog.net/wp-content/uploads/2026/07/Modbus.drawio.png 1496w" sizes="auto, (max-width: 604px) 100vw, 604px" /></p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">Basically, t<strong>he payload of Modbus/TCP equals Modbus/RTU</strong>, but with some necessary modifications.</div></div>
<p>The CRC field was dropped because TCP already cares about integrity. Additionally, an MBAP header (Modbus Application Protocol), which carries information about identifiers and data length, was prepended to the payload.</p>
<h2>Terminology</h2>
<p>Let’s talk about Modbus terminology. In Modbus, there are two types of devices. Devices which read from or write to other devices are called <strong>clients</strong>. Contrary, devices which receive and serve read or write requests are called <strong>servers</strong>. On serial lines, there can be only one client (formerly called master) but several servers (formerly called slaves), which all need to have a unique ID on the bus to be addressed properly (you may have noticed “Slave ID” in the figure above).</p>
<p>With Modbus/TCP, the information about a certain target ID for a particular message is obsolete as the TCP connection itself is already a one-to-one connection. Nevertheless, the ID field remains present as “Unit ID”, which becomes important for addressing if Modbus-to-Modbus-Gateways (e.g TCP &lt;-&gt; RTU) are used or if vendors use it as an additional identifier for their implementation.</p>
<p>Info: All the now discussed types are included in the <a href="https://weberblog.net/the-ultimate-pcap/">Ultimate PCAP</a>. Download and have a look at it by yourself! ;)</p>
<h2>Functions and Data</h2>
<p>Now, as we know how to reach a server, we should talk about function codes which are used to signal our intent about what to do (read/write) on one or multiple data entities. (We will only discuss the most common ones.)</p>
<ul>
<li>Code 1: Read Coils</li>
<li>Code 2: Read Discrete Inputs</li>
<li>Code 3: Read Holding Registers</li>
<li>Code 4: Read Input Registers</li>
<li>Code 5: Write Coil</li>
<li>Code 6: Write Register</li>
<li>Code 15: Write Multiple Coils</li>
<li>Code 16: Write Multiple Registers</li>
</ul>
<p>Modbus has basically four types of addressable data entities, each having their respective functions for reading and writing (if possible).</p>
<p><strong>Coils</strong> represent switchable binary outputs. As they can be turned off and on, they are typically writable (until being write-protected) to set their state, and readable to retrieve their current state. Example: Relay output.</p>
<p><strong>Discrete Inputs</strong> are binary inputs which are read-only. Example: Alarm input.</p>
<p><strong>Input Registers</strong> allow read-only access to 2-byte registers, typically measurements. Example: Temperature sensor.</p>
<p><strong>Holding Registers</strong> represent 2-byte registers with read and write access, typically measurements, setpoints or controller states. Example: Your 23°C setpoint.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packethawk-inline-bypass-network-tap" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketHawk.1208x232.webp" /></a></div>
<h2>Addressing</h2>
<p>Now the tricky part, which can be a bit confusing for beginners. Because we need to read and write data, we also need to address a certain entity for doing this.</p>
<p>As we have already seen, there are four data entities (coils, discrete inputs, input registers, holding registers), each with 2-byte addresses, ranging from 0 &#8211; 65.535 (2^16).</p>
<p>A Modbus PDU contains the function code, the reference to the address (either the bit or register number) and the length. The length field determines how many consecutive bits or registers we want to read or write ahead of the address.</p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-14576 size-full" src="https://weberblog.net/wp-content/uploads/2026/07/Modbus-01-Reference-Number.png" alt="" width="651" height="207" srcset="https://weberblog.net/wp-content/uploads/2026/07/Modbus-01-Reference-Number.png 651w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-01-Reference-Number-300x95.png 300w" sizes="auto, (max-width: 651px) 100vw, 651px" /></p>
<p>As you might suspect, reading address 44 using function code 3 may return a different value than when function code 4 is used. This is simply because function code 3 addresses a different data block (holding registers) than function code 4 (input registers) does.</p>
<p>Vendors and implementors often document addresses with prefixes per data block.</p>
<ul>
<li>Prefix 0: Coils</li>
<li>Prefix 1: Discrete Inputs</li>
<li>Prefix 3: Input Registers</li>
<li>Prefix 4: Holding Registers</li>
</ul>
<p>With this model, a vendor/implementor may refer to a measured temperature at address 4044. This address implies that the value of interest is stored in a holding register and should be read with function code 3. The actual on-wire address is 44 (see screenshot above).</p>
<p>A general recommendation is to use 6-digit representations. This prevents address ambiguity and therefore address 4044 from being interpreted as either holding register 44 or coil 4044 (coil prefix 0).</p>
<p>It’s also crucial to know about the indexing scheme. Let’s say you are interested in the very first holding register. Usually, it is located at register 0 but may be referred to as address 400000 (0-indexed) or 400001 (1-indexed).</p>
<p>As modern PLCs mostly have a complete process image stored in memory, usually a shared address space approach is used, which may be either shared globally or may be divided into a binary and a register address block. This means that a temperature stored at address 44 and it can be read using either function code 3 or 4 (because both read 2-byte registers), but using function code 1 would access the binary address block.</p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">Take-away: Consult the vendor’s or implementor’s manual, really!</div></div>
<h2>Data Types</h2>
<p>Accessing coils or inputs is quite simple, as a single entity (address) can only be 0 or 1 (off or on). There is no need to distinguish between data types or representations. With registers, this is completely different.</p>
<p>Each register has a fixed length of one word (2 bytes). This is the most important information to keep in mind!</p>
<p>In a real-world scenario, we are interested in different types of values. A counter may be an unsigned integer which either fits in one or two bytes (UINT8, UINT16), so a single register is totally fine:</p>
<p><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14579" src="https://weberblog.net/wp-content/uploads/2026/07/Modbus-02-1-word-read.png" alt="" width="647" height="240" srcset="https://weberblog.net/wp-content/uploads/2026/07/Modbus-02-1-word-read.png 647w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-02-1-word-read-300x111.png 300w" sizes="auto, (max-width: 647px) 100vw, 647px" /></p>
<p>A floating-point value requires 4 bytes to be stored. In this case, we need two consecutive registers to hold such a value:</p>
<p><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14580" src="https://weberblog.net/wp-content/uploads/2026/07/Modbus-03-2-words-read.png" alt="" width="648" height="241" srcset="https://weberblog.net/wp-content/uploads/2026/07/Modbus-03-2-words-read.png 648w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-03-2-words-read-300x112.png 300w" sizes="auto, (max-width: 648px) 100vw, 648px" /></p>
<p>As Modbus can only read and write data at a certain address with a certain length, but has no information about the data type, the implementor and user must not only be aware of addresses, but also of data lengths and their interpretation.</p>
<p>The Wireshark Modbus dissector allows switching between different types of data representation:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/07/Modbus-04-Wireshark-Register-Format.png"><img loading="lazy" decoding="async" class="aligncenter wp-image-14581 size-full" src="https://weberblog.net/wp-content/uploads/2026/07/Modbus-04-Wireshark-Register-Format.png" alt="" width="1009" height="303" srcset="https://weberblog.net/wp-content/uploads/2026/07/Modbus-04-Wireshark-Register-Format.png 1009w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-04-Wireshark-Register-Format-300x90.png 300w, https://weberblog.net/wp-content/uploads/2026/07/Modbus-04-Wireshark-Register-Format-768x231.png 768w" sizes="auto, (max-width: 1009px) 100vw, 1009px" /></a></p>
<h2>Modbus/UDP and TLS</h2>
<p>The standard implementation of Modbus over networks is <strong>Modbus/TCP</strong>. Additionally, Modbus can be encapsulated into UDP packets. The on-wire format is the same, but implementations may be easier on low-powered devices because of the lower complexity and memory requirements.</p>
<p>Contrary, to make it a bit more complex, Modbus/TCP can also be secured with TLS.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetlion-aggregation-packet-broker" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketLion.1208x232.webp" /></a></div>
<h2>Conclusion</h2>
<p>A Modbus client can read and write data from or to a Modbus server. The data is made up of a variable number of consecutive bits (off/on) or registers (2-byte values, words), referenced by a starting address. Data is organised in four different data blocks, each having their respective read and write functions (function code). A server may share the exact same data in different data blocks at the same address, but it depends on the implementation. Modbus does not care about the actual data and its representation. It’s up to you to have bytes interpreted in the way they should.</p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">Key take-away: Read the manual! The more tables and figures, the better you’ll understand what the vendor or implementor did.</div></div>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@sunburned_surveyor?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Scott Blake</a> on <a href="https://unsplash.com/photos/aerial-view-of-crane-tower-4h7zRkuWLvI?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/modbus-fundamentals/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14572</post-id>	</item>
		<item>
		<title>Bidirectional Forwarding Detection (BFD) on a Palo</title>
		<link>https://weberblog.net/bidirectional-forwarding-detection-bfd-on-a-palo/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=bidirectional-forwarding-detection-bfd-on-a-palo</link>
					<comments>https://weberblog.net/bidirectional-forwarding-detection-bfd-on-a-palo/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Tue, 18 Aug 2026 09:05:26 +0000</pubDate>
				<category><![CDATA[Palo Alto Networks]]></category>
		<category><![CDATA[Routing]]></category>
		<category><![CDATA[BFD]]></category>
		<category><![CDATA[Cisco Router]]></category>
		<category><![CDATA[Logical Router]]></category>
		<category><![CDATA[OSPF]]></category>
		<category><![CDATA[OSPFv3]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14451</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />To improve the convergence times of a routing protocol, BFD can be used. This feature monitors the adjacencies using some kind of ping packets. It detects link failures much faster than the routing protocol&#8217;s built-in keepalive timeouts. The interesting part: You must only enable BFD rather than configure it in detail. The BFD peers are &#8230; <a href="https://weberblog.net/bidirectional-forwarding-detection-bfd-on-a-palo/" class="more-link">Continue reading <span class="screen-reader-text">Bidirectional Forwarding Detection (BFD) on a Palo</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/Bidirectional-Forwarding-Detection-BFD-on-a-Palo-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>To improve the convergence times of a routing protocol, BFD can be used. This feature monitors the adjacencies using some kind of ping packets. <strong>It detects link failures much faster than the routing protocol&#8217;s built-in keepalive timeouts.</strong></p>
<p>The interesting part: You must only enable BFD rather than configure it in detail. The <strong>BFD peers are derived from the routing protocol&#8217;s adjacencies, e.g. the OSPF neighbours</strong>. Let&#8217;s have a look:</p>
<p><span id="more-14451"></span></p>
<p>For this example, I&#8217;m using a PA-440 with <strong>PAN-OS 11.2.12</strong>, ARE/LR enabled. The adjacent routers are 2x other Palos (one via 2x VPNs) and a Cisco router 2811, IOS Version 15.1(4)M12a. <strong>OSPF for legacy IP</strong> and <strong>OSPFv3 for IPv6</strong> are used.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packethawk-inline-bypass-network-tap" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketHawk.1208x232.webp" /></a></div>
<h2>Enabling BFD</h2>
<p>I&#8217;m using the default BDF profile with a 1000 ms interval and a multiplier of 3. This profile is referenced in the OSPF/OSPFv3 global settings, while the OSPF-enabled interfaces only inherit those global settings:</p>

<a href='https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-01-BFD-Profile-default.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-01-BFD-Profile-default-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-02-OSPF-BFD-Profile.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-02-OSPF-BFD-Profile-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-03-OSPF-Interface.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-03-OSPF-Interface-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-04-OSPFv3-BFD-Profile.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-04-OSPFv3-BFD-Profile-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-05-OSPFv3-Interface.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-05-OSPFv3-Interface-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>

<h2>Verifying BFD</h2>
<p>When new BFD peers appear, you&#8217;ll see such entries in the system log:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-06-System-Logs.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14463" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-06-System-Logs-1024x283.png" alt="" width="604" height="167" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-06-System-Logs-1024x283.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-06-System-Logs-300x83.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-06-System-Logs-768x213.png 768w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-06-System-Logs-1536x425.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-06-System-Logs.png 1933w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>You can further investigate the BFD peers at the &#8220;More Runtime Stats&#8221; of the logical router:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-07-Logical-Router-BFD-Summary-Information.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14464" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-07-Logical-Router-BFD-Summary-Information-1024x554.png" alt="" width="604" height="327" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-07-Logical-Router-BFD-Summary-Information-1024x554.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-07-Logical-Router-BFD-Summary-Information-300x162.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-07-Logical-Router-BFD-Summary-Information-768x416.png 768w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-07-Logical-Router-BFD-Summary-Information.png 1160w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>Session details:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-08-Logical-Router-BFD-Detailed-Information.png"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14465" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-08-Logical-Router-BFD-Detailed-Information.png" alt="" width="882" height="1007" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-08-Logical-Router-BFD-Detailed-Information.png 882w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-08-Logical-Router-BFD-Detailed-Information-263x300.png 263w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-08-Logical-Router-BFD-Detailed-Information-768x877.png 768w" sizes="auto, (max-width: 882px) 100vw, 882px" /></a></p>
<p>Just another example: These are the logs that were generated during a reboot of the Cisco router (dual-stack, hence 1x IPv4 and 1x IPv6 neighbour/peer). That is: everything went down and up again:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-09-System-Logs-during-router-reboot.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14466" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-09-System-Logs-during-router-reboot-1024x265.png" alt="" width="604" height="156" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-09-System-Logs-during-router-reboot-1024x265.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-09-System-Logs-during-router-reboot-300x78.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-09-System-Logs-during-router-reboot-768x199.png 768w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-09-System-Logs-during-router-reboot-1536x397.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/Palo-Alto-Firewall-BFD-09-System-Logs-during-router-reboot.png 1960w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>And by the way, this is the plus of traffic through those BFD packets, measured by Checkmk. (Before I enabled BFD, it was only the <a href="https://weberblog.net/redundant-vpn-with-failover-on-a-palo-ngfw/">Palo&#8217;s tunnel monitor on this VPN</a>.) [Note that the IF-MIB counters for tunnel interfaces on a Palo have a well-known <del>feature</del> bug, which doubles the incoming packet counters due to the tunnel inspection. 🤦 Anyway:]
<p><a href="https://weberblog.net/wp-content/uploads/2026/07/Palo-Alto-Firewall-BFD-10-BFD-traffic-Checkmk.png"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14468" src="https://weberblog.net/wp-content/uploads/2026/07/Palo-Alto-Firewall-BFD-10-BFD-traffic-Checkmk.png" alt="" width="979" height="341" srcset="https://weberblog.net/wp-content/uploads/2026/07/Palo-Alto-Firewall-BFD-10-BFD-traffic-Checkmk.png 979w, https://weberblog.net/wp-content/uploads/2026/07/Palo-Alto-Firewall-BFD-10-BFD-traffic-Checkmk-300x104.png 300w, https://weberblog.net/wp-content/uploads/2026/07/Palo-Alto-Firewall-BFD-10-BFD-traffic-Checkmk-768x268.png 768w" sizes="auto, (max-width: 979px) 100vw, 979px" /></a></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetlion-aggregation-packet-broker" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketLion.1208x232.webp" /></a></div>
<p>Those who prefer the <strong>CLI</strong> can use the following commands: <code>show advanced-routing bfd summary</code>, <code>show advanced-routing bfd details interface &lt;interface-id&gt;</code>, <code>show counter global | match bfd</code>.</p>
<p>Examples:</p><pre class="urvanov-syntax-highlighter-plain-tag">weberjoh@pa-home&gt; show advanced-routing bfd summary

SESSION ID: 8
    Interface:      tunnel.12
    Logical Router: default (id:1)
    Local IP Address:         172.16.12.2
    Neighbor IP Address:      172.16.12.1

    Discriminator (local/remote):  0x11919912 / 0x88e9b610
    State:          up
    rState:         up
    Up Time:        1d 20h 5m 32s 580ms
    Agent DP:       Slot 1 - DP 0
    Errors:         0

SESSION ID: 9
    Interface:      tunnel.11
    Logical Router: default (id:1)
    Local IP Address:         172.16.11.2
    Neighbor IP Address:      172.16.11.1

    Discriminator (local/remote):  0xd52c54a3 / 0x3ab549a2
    State:          up
    rState:         up
    Up Time:        1d 1h 13m 57s 380ms
    Agent DP:       Slot 1 - DP 0
    Errors:         0

SESSION ID: 10
    Interface:      ae1.3
    Logical Router: default (id:1)
    Local IP Address:         fe80::3efa:30ff:fe03:1230
    Neighbor IP Address:      fe80::3efa:30ff:fe04:9110

    Discriminator (local/remote):  0x56ff3040 / 0x76d269fb
    State:          up
    rState:         up
    Up Time:        0d 4h 13m 39s 160ms
    Agent DP:       Slot 1 - DP 0
    Errors:         0

SESSION ID: 11
    Interface:      ae1.3
    Logical Router: default (id:1)
    Local IP Address:         fe80::3efa:30ff:fe03:1230
    Neighbor IP Address:      fe80::21e:7aff:fe79:3f10

    Discriminator (local/remote):  0x16c15553 / 0x5
    State:          up
    rState:         up
    Up Time:        0d 4h 13m 39s 410ms
    Agent DP:       Slot 1 - DP 0
    Errors:         0

SESSION ID: 12
    Interface:      ae1.3
    Logical Router: default (id:1)
    Local IP Address:         192.168.3.1
    Neighbor IP Address:      192.168.3.99

    Discriminator (local/remote):  0xbd09e624 / 0x6
    State:          up
    rState:         up
    Up Time:        0d 4h 13m 38s 980ms
    Agent DP:       Slot 1 - DP 0
    Errors:         1

SESSION ID: 14
    Interface:      ae1.3
    Logical Router: default (id:1)
    Local IP Address:         192.168.3.1
    Neighbor IP Address:      192.168.3.2

    Discriminator (local/remote):  0x51cd3a0d / 0x5ec5faee
    State:          up
    rState:         up
    Up Time:        0d 4h 13m 38s 810ms
    Agent DP:       Slot 1 - DP 0
    Errors:         0


weberjoh@pa-home&gt;
weberjoh@pa-home&gt;
weberjoh@pa-home&gt; show advanced-routing bfd details interface ae1.3

BFD Session ID: 10
    Version:        1
    Interface:      ae1.3
    Protocol:       OSPFv3
    Local IP Address:         fe80::3efa:30ff:fe03:1230
    Neighbor IP Address:      fe80::3efa:30ff:fe04:9110

    BFD profile:              default

    State (local/remote):          up / up
    Up Time:        0d 4h 16m 22s 570ms
    Discriminator (local/remote):  0x56ff3040 / 0x76d269fb
    Mode:           Active
    Demand Mode:    Disabled
    Poll Bit:       Disabled
    Multihop:       Disabled
    Multihop TTL:   255
    Local Diag Code:                 0 (No Diagnostic)
    Last Received Remote Diag Code:  0 (No Diagnostic)

    Transmit Hold Time:            0ms
    Desired Min Tx Interval:       1000ms
    Required Min Rx Interval:      1000ms
    Received Min Rx Interval:      1000ms
    Negotiated Transmit Interval:  1000ms
    Detect Multiplier:             3
    Received Multiplier:           3
    Detect time (exceeded):        3000ms (0)
    Tx Control Packets (last):     17576 (44ms ago)
    Rx Control Packets (last):     17587 (843ms ago)
    Agent DP:       Slot 1 - DP 0
    Errors:         0

    Last Recieved Packet:
        Version:        1
        My Discriminator:         0x76d269fb
        Your Discriminator:       0x56ff3040
        Diag Code:      0 (No Diagnostic)
        Length:         24
        Demand bit:     0       Poll bit:       0
        Final bit:      0       Multipoint:     0
        Control Plane Independent:     1
        Authentication Present:        0
        Desired Min Tx Interval:       1000ms
        Required Min Rx Interval:      1000ms
        Detect Multiplier:             3
        Required Min Echo Rx Interval: 0ms

[...]

weberjoh@pa-home&gt;
weberjoh@pa-home&gt;
weberjoh@pa-home&gt; show counter global | match bfd
flow_bfd_accept                      2005679        6 info      flow      bfd       BFD packet acceptted
flow_bfd_error                            20        0 drop      flow      bfd       BFD packet enqueue error
flow_bfd_rx                          2005699        6 info      flow      bfd       BFD packet received
flow_bfd_rx_err                           10        0 drop      flow      bfd       BFD packet receive error
flow_bfd_rx_qos_0                    2005699        6 info      flow      bfd       BFD packet received for qos 0
flow_bfd_tx                          2007301        7 info      flow      bfd       BFD packet transmitted
flow_bfd_tx_err                            1        0 drop      flow      bfd       BFD packet tx error
flow_bfd_tx_fail                           5        0 drop      flow      bfd       BFD packet tx failed
flow_bfd_tx_l2                             1        0 drop      flow      bfd       BFD packet tx layer 2 error
flow_bfd_not_found                        18        0 drop      flow      bfd       BFD packet rx not found
flow_bfd_flow_session                     31        0 info      flow      bfd       BFD packet create Flow session
weberjoh@pa-home&gt;</pre><p>
And for the sake of completeness, this is the view from the Cisco router:</p><pre class="urvanov-syntax-highlighter-plain-tag">R1#show bfd neighbors

NeighAddr                         LD/RD    RH/RS     State     Int
10.23.0.2                          3/1     Up        Up        Fa0/1
192.168.3.1                        6/-1123424732 Up        Up        Fa0/0
192.168.3.2                        2/-1270998408 Up        Up        Fa0/0
FE80::21A:6CFF:FEA1:2B98           4/2     Up        Up        Fa0/1
FE80::3EFA:30FF:FE03:1230          5/381769043 Up        Up        Fa0/0
FE80::3EFA:30FF:FE04:9110          1/316964720 Up        Up        Fa0/0
R1#
R1#
R1#show bfd neighbors details

NeighAddr                         LD/RD    RH/RS     State     Int
192.168.3.1                        6/-1123424732 Up        Up        Fa0/0
Session state is UP and not using echo function.
OurAddr: 192.168.3.99
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 999000, MinRxInt: 999000, Multiplier: 3
Received MinRxInt: 1000000, Received Multiplier: 3
Holddown (hits): 2448(0), Hello (hits): 1000(18082)
Rx Count: 18122, Rx Interval (ms) min/max/avg: 1/1000/873 last: 552 ms ago
Tx Count: 18083, Tx Interval (ms) min/max/avg: 24/1004/879 last: 656 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: OSPF
Uptime: 04:24:37
Last packet: Version: 1                  - Diagnostic: 0
             State bit: Up               - Demand bit: 0
             Poll bit: 0                 - Final bit: 0
             Multiplier: 3               - Length: 24
             My Discr.: -1123424732           - Your Discr.: 6
             Min tx interval: 1000000    - Min rx interval: 1000000
             Min Echo interval: 0

NeighAddr                         LD/RD    RH/RS     State     Int
FE80::3EFA:30FF:FE03:1230          5/381769043 Up        Up        Fa0/0
Session state is UP and not using echo function.
OurAddr: FE80::21E:7AFF:FE79:3F10
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 999000, MinRxInt: 999000, Multiplier: 3
Received MinRxInt: 1000000, Received Multiplier: 3
Holddown (hits): 2760(0), Hello (hits): 1000(18064)
Rx Count: 18120, Rx Interval (ms) min/max/avg: 1/1000/876 last: 244 ms ago
Tx Count: 18066, Tx Interval (ms) min/max/avg: 20/1008/878 last: 788 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: OSPFv3
Uptime: 04:24:38
Last packet: Version: 1                  - Diagnostic: 0
             State bit: Up               - Demand bit: 0
             Poll bit: 0                 - Final bit: 0
             Multiplier: 3               - Length: 24
             My Discr.: 381769043           - Your Discr.: 5
             Min tx interval: 1000000    - Min rx interval: 1000000
             Min Echo interval: 0

[...]</pre><p>
&nbsp;</p>
<h2>Further Reading</h2>
<p><a href="https://weberblog.net/more-capture-details-ii/">Some <strong>Wireshark screenshots</strong> of BFD packets are here</a>. If you want to look at them by yourself, please <a href="https://weberblog.net/the-ultimate-pcap/">download and use the <strong>Ultimate PCAP</strong></a>.</p>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@rosiefoto13?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Rosie Steggles</a> on <a href="https://unsplash.com/photos/a-road-sign-pointing-in-opposite-directions-in-the-desert-h1OhvEIIcxs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/bidirectional-forwarding-detection-bfd-on-a-palo/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14451</post-id>	</item>
		<item>
		<title>Network Encryption with MACsec: Basics &#038; Cases</title>
		<link>https://weberblog.net/network-encryption-with-macsec-basics-cases/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=network-encryption-with-macsec-basics-cases</link>
					<comments>https://weberblog.net/network-encryption-with-macsec-basics-cases/#respond</comments>
		
		<dc:creator><![CDATA[Benjamin Pfister]]></dc:creator>
		<pubDate>Mon, 10 Aug 2026 05:07:43 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Switching]]></category>
		<category><![CDATA[AES]]></category>
		<category><![CDATA[EAPoL]]></category>
		<category><![CDATA[Encryption]]></category>
		<category><![CDATA[Guest Post]]></category>
		<category><![CDATA[Layer 2]]></category>
		<category><![CDATA[MACsec]]></category>
		<category><![CDATA[NAC]]></category>
		<category><![CDATA[RADIUS]]></category>
		<category><![CDATA[Switch]]></category>
		<category><![CDATA[Ultimate PCAP]]></category>
		<category><![CDATA[Wireshark]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14415</guid>

					<description><![CDATA[<img width="300" height="200" src="https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-300x200.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-300x200.jpg 300w, https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-1024x683.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-768x512.jpg 768w, https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-1536x1024.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-2048x1365.jpg 2048w" sizes="auto, (max-width: 300px) 100vw, 300px" />Modern networks are not only threatened by external attacks but are increasingly exposed to internal risks as well. These include unauthorized physical access to network components or manipulated data streams within the LAN. Classic Network Access Control (NAC) based on IEEE 802.1X-2004 often only provides one-time authentication but does not ensure continuous protection of transmitted &#8230; <a href="https://weberblog.net/network-encryption-with-macsec-basics-cases/" class="more-link">Continue reading <span class="screen-reader-text">Network Encryption with MACsec: Basics &#038; Cases</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="200" src="https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-300x200.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-300x200.jpg 300w, https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-1024x683.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-768x512.jpg 768w, https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-1536x1024.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/05/sasun-bughdaryan-fzPusoj22AY-unsplash-2048x1365.jpg 2048w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>Modern networks are not only threatened by external attacks but are increasingly exposed to internal risks as well. These include unauthorized physical access to network components or manipulated data streams within the LAN. Classic Network Access Control (NAC) based on IEEE 802.1X-2004 often only provides one-time authentication but does not ensure continuous protection of transmitted packets. For companies and authorities requiring higher security standards, this gap becomes a risk factor.</p>
<p>This is where <strong>MACsec</strong> (Media Access Control Security) comes into play. The protocol <strong>encrypts and verifies the integrity of data at Layer 2</strong>, directly at the point of entry into the network. Thus, it protects not only against external attacks but also against internal manipulations and unauthorized access to sensitive communication paths.</p>
<p><span id="more-14415"></span></p>
<h2>What is MACsec?</h2>
<p>MACsec secures communication in wired networks, such as between switches, using cryptographic mechanisms. While Network Access Control according to IEEE 802.1X-2004 only enables authentication via the EAP framework and, at most, provides for periodic re-authentication, it does not offer integrity checks or confidentiality at this communication level. <strong>This leads to significant vulnerabilities, especially for network connections in areas accessible to third parties, such as WiFi access points, multifunction devices, or PCs behind screens in public building corridors.</strong> Potential attackers could inject data packets into the network via a man-in-the-middle attack at an authenticated switch port.</p>
<p>Only the combination of IEEE 802.1X-2010 with the MACsec standard (IEEE 802.1AE) closes this gap: it ensures both <strong>data integrity and confidentiality</strong>. Compared to traditional IPsec-based encryption solutions, MACsec stands out due to its higher performance and lower implementation complexity, because it only has 4 cipher suites: AES128-GCM, AES256-GCM, AES128-GCM-XPN and AES256-GCM-XPN. However, it can also be combined with other security protocols such as IPsec or TLS at higher layers if required.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetlion-aggregation-packet-broker" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketLion.1208x232.webp" /></a></div>
<p>Another advantage of MACsec is its transparent transmission of Layer 2 protocols such as LLDP, CDP, LACP, or ARP. Since MACsec is located below IPv4/IPv6 in the OSI reference model, it remains compatible with both IP versions. The <strong>hardware-based implementation enables high performance up to full line rate</strong> and effectively protects against attacks such as session spoofing, replay attacks, or man-in-the-middle attacks.</p>
<h3>MACsec Keywords</h3>

<table id="tablepress-38" class="tablepress tablepress-id-38">
<thead>
<tr class="row-1">
	<th class="column-1">Abbreviation</th><th class="column-2">Term</th><th class="column-3">Description</th>
</tr>
</thead>
<tbody class="row-striping row-hover">
<tr class="row-2">
	<td class="column-1">CA</td><td class="column-2">Connectivity Association</td><td class="column-3">Secured control-plane connection between MACsec peers.</td>
</tr>
<tr class="row-3">
	<td class="column-1">CAK</td><td class="column-2">Connectivity Association Key</td><td class="column-3">Control-plane key from which the session key is derived.</td>
</tr>
<tr class="row-4">
	<td class="column-1">SA</td><td class="column-2">Security Association</td><td class="column-3">Connection between two MACsec peers that guarantees an encrypted connection based on the SAK.</td>
</tr>
<tr class="row-5">
	<td class="column-1">SAK</td><td class="column-2">Security Association Key</td><td class="column-3">Session key derived from the CAK, used for encryption between two MACsec peers.</td>
</tr>
<tr class="row-6">
	<td class="column-1">SC</td><td class="column-2">Secure Channel</td><td class="column-3">Logical channel within which encrypted transmission takes place.</td>
</tr>
<tr class="row-7">
	<td class="column-1">SCI</td><td class="column-2">Secure Channel Identifier</td><td class="column-3">Unique identifier for the secure channel, consisting of the MAC address and port designation.</td>
</tr>
<tr class="row-8">
	<td class="column-1">MKA</td><td class="column-2">MACsec Key Agreement</td><td class="column-3">Key agreement protocol used to locate MACsec peers, generate, renew, and exchange keys.</td>
</tr>
<tr class="row-9">
	<td class="column-1">CKN</td><td class="column-2">Connectivity Association Key Name</td><td class="column-3">Serves as a framework for the CAK. Peers transmit this to each other in plaintext for validation.</td>
</tr>
<tr class="row-10">
	<td class="column-1">Supplicant</td><td class="column-2">Supplicant</td><td class="column-3">Client component for authentication according to IEEE 802.1X.</td>
</tr>
<tr class="row-11">
	<td class="column-1">Authenticator</td><td class="column-2">Authenticator</td><td class="column-3">Component that performs authentication via EAPoL with the supplicant and via the RADIUS protocol with the Authentication Server. The RADIUS server denies or grants access based on authorization.</td>
</tr>
<tr class="row-12">
	<td class="column-1">Authentication Server</td><td class="column-2">Authentication Server</td><td class="column-3">RADIUS server for authentication, authorization, and accounting according to IEEE 802.1X.</td>
</tr>
</tbody>
</table>
<!-- #tablepress-38 from cache -->
<h2>Application Scenarios for MACsec</h2>
<p>MACsec can be deployed in two central scenarios: securing the connection <strong>between a switch and an end device</strong>, or <strong>encrypting switch-to-switch connections</strong>. Both variants provide targeted protection against manipulation and eavesdropping on the network link.</p>
<h3>Scenario: Switch ↔ End Device</h3>
<p>In this scenario, MACsec secures the link between an end device (supplicant) and the switch (authenticator). After the physical link is established, the authentication process begins: The supplicant and authenticator exchange EAPoL frames. The switch forwards the authentication data to the Authentication Server (RADIUS server) as a RADIUS request.</p>
<p>The server verifies the certificate contents for EAP-TLS authentication (mutual certificate authentication). Unlike IEEE 802.1X-2004, the combination with IEEE 802.1X-2010 and 802.1AE enables enhanced authorization after successful authentication. The Authentication Server sends a MACsec policy to the switch in the &#8220;RADIUS Access-Accept&#8221; message. The switch then activates MACsec, provided both sides (supplicant and authenticator) support compatible encryption algorithms (e.g., AES-GCM-128 or AES-GCM-256).</p>
<p>Subsequently, the two communication partners generate a Master Session Key. Using the MACsec Key Agreement (MKA) over EAPoL Frames (Ethertype <code>0x888e</code>), they exchange the required key material, which forms the basis for the subsequent encrypted data transmission.</p>
<p><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14444" src="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-End-Device-1024x336.png" alt="" width="604" height="198" srcset="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-End-Device-1024x336.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-End-Device-300x98.png 300w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-End-Device-768x252.png 768w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-End-Device-1536x504.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-End-Device-2048x672.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packethawk-inline-bypass-network-tap" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketHawk.1208x232.webp" /></a></div>
<h3>Scenario: Switch ↔ Switch</h3>
<p>Here, MACsec is used to encrypt the connection between two switches (point-to-point) or among multiple switches (point-to-multipoint). This is particularly relevant <strong>when third parties have physical access to the cabling or when connections pass through insecure environments</strong>, such as Metro Ethernet networks, dark fiber connections, or optical fibers running through external areas. Without encryption, attackers could intercept and analyze data via bend couplers or TAPs, or even inject malicious data.</p>
<p>MACsec encrypts the payload of MAC frames, making analysis without the key impossible. However, for Metro Ethernet connections over provider networks, it must first be clarified whether the provider allows the transmission of MACsec frames (EtherType <code>0x88e5</code>) in their network.</p>
<p><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14445" src="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-Switch-1024x410.png" alt="" width="604" height="242" srcset="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-Switch-1024x410.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-Switch-300x120.png 300w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-Switch-768x307.png 768w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-Switch-1536x614.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Switch-Switch.png 1920w" sizes="auto, (max-width: 604px) 100vw, 604px" /></p>
<h3>Scenario: Cloud Provider</h3>
<p>If you consider direct peerings to cloud providers like Amazon Web Services (AWS) with Direct Connect, Cloud Interconnect to Google Cloud Platform (GCP) or Express Route to Azure, the link between your on-premises datacenter equipment and cloud datacenter is encrypted by MACsec. Ciphers and link speeds differ by cloud provider. In the end, there should be no possibility to inject packets or capture packets via possible unauthorized TAPs in the link between on-premises and cloud datacenter.</p>
<p><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14446" src="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Cloud-Provider-1024x324.png" alt="" width="604" height="191" srcset="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Cloud-Provider-1024x324.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Cloud-Provider-300x95.png 300w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Cloud-Provider-768x243.png 768w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Cloud-Provider.png 1424w" sizes="auto, (max-width: 604px) 100vw, 604px" /></p>
<h2>How to Decrypt in Wireshark?</h2>
<p>(The following packet captures are part of the <a href="https://weberblog.net/the-ultimate-pcap/">Ultimate PCAP</a>, incl. the session keys in the comments of the first MACsec packets. Have a look at them yourself.)</p>
<p>You have two options for decryption of MACsec in Wireshark depending on the key distribution. If you use so-called „<strong>Static SAK Mode</strong>“ with static session keys, you could decrypt by going to Preferences/Protocols/MACsec/Pre-Shared Key List and enter the static session key into the key column and key number into the info column. Afterwards, Wireshark will decrypt your MACsec frames:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Static-SAK-decrypted-packets-scaled.jpg"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14447" src="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Static-SAK-decrypted-packets-1024x592.jpg" alt="" width="604" height="349" srcset="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Static-SAK-decrypted-packets-1024x592.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Static-SAK-decrypted-packets-300x174.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Static-SAK-decrypted-packets-768x444.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Static-SAK-decrypted-packets-1536x888.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Static-SAK-decrypted-packets-2048x1185.jpg 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>If you use static CAK mode with <strong>dynamically generated SAKs</strong>, you could even decrypt MACsec frames based on CKN and CAK information and enable usage of MKA for decryption. For this, you need to go to Preferences/Protocols/MACsec and set the „Also Use MKA for Decode“ option to „True“. Afterwards, you need to set CKN and CAK under Preferences/Protocols/EAPOL-MKA. In the Info column, you could type in a description for this CKN/CAK value pair. Afterwards, Wireshark will decrypt your MACsec frames as well:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Dynamic-SAKs-scaled.jpg"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14448" src="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Dynamic-SAKs-1024x592.jpg" alt="" width="604" height="349" srcset="https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Dynamic-SAKs-1024x592.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Dynamic-SAKs-300x174.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Dynamic-SAKs-768x444.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Dynamic-SAKs-1536x888.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/MACsec-Wireshark-Dynamic-SAKs-2048x1185.jpg 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@sasun1990?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sasun Bughdaryan</a> on <a href="https://unsplash.com/photos/a-padlock-on-top-of-a-circuit-board-fzPusoj22AY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/network-encryption-with-macsec-basics-cases/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14415</post-id>	</item>
		<item>
		<title>Packet Capture of a Post-Quantum Site-to-Site VPN</title>
		<link>https://weberblog.net/packet-capture-of-a-post-quantum-site-to-site-vpn/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=packet-capture-of-a-post-quantum-site-to-site-vpn</link>
					<comments>https://weberblog.net/packet-capture-of-a-post-quantum-site-to-site-vpn/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Tue, 07 Jul 2026 13:35:22 +0000</pubDate>
				<category><![CDATA[IPsec/VPN]]></category>
		<category><![CDATA[Post-Quantum (PQC)]]></category>
		<category><![CDATA[Allegro Network Multimeter]]></category>
		<category><![CDATA[Diffie-Hellman]]></category>
		<category><![CDATA[FortiGate]]></category>
		<category><![CDATA[ML-KEM]]></category>
		<category><![CDATA[Palo Alto Networks]]></category>
		<category><![CDATA[Post-Quantum Cryptography]]></category>
		<category><![CDATA[PQC]]></category>
		<category><![CDATA[Ultimate PCAP]]></category>
		<category><![CDATA[Wireshark]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14496</guid>

					<description><![CDATA[<img width="300" height="155" src="https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-300x155.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-300x155.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-1024x527.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-768x396.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-1536x791.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />After using several post-quantum secure VPN tunnels (here and there), I was interested in how this key exchange with ML-KEM looks on the wire. Especially in direct comparison to a classical VPN setup with just ECDH (group 21). Spoiler: since it does not fit in a single packet, it has to use a new form &#8230; <a href="https://weberblog.net/packet-capture-of-a-post-quantum-site-to-site-vpn/" class="more-link">Continue reading <span class="screen-reader-text">Packet Capture of a Post-Quantum Site-to-Site VPN</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="155" src="https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-300x155.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-300x155.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-1024x527.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-768x396.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image-1536x791.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/Packet-Capture-of-a-Post-Quantum-Site-to-Site-VPN-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>After using several post-quantum secure VPN tunnels (<a href="https://weberblog.net/pqc-vpn-tunnel-with-palo/">here</a> and <a href="https://weberblog.net/pqc-vpn-tunnel-between-palo-alto-fortigate/">there</a>), I was interested in how this <strong>key exchange with ML-KEM looks on the wire</strong>. Especially in direct comparison to a classical VPN setup with just ECDH (group 21). Spoiler: since it does not fit in a single packet, it has to use a new form of fragmentation. 😳 Here we go:</p>
<p><span id="more-14496"></span></p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">This is one of many VPN tutorials on my blog. &#8211;&gt; <a href="https://weberblog.net/site-to-site-vpn-tutorials/">Have a look at this full list</a>. &lt;&#8211;</div></div>
<h2>Setup</h2>
<p>This was my basic setup. A <strong>Palo Alto PA-440 with PAN-OS 12.1.6</strong> on the left and a <strong>FortiGate FG-70F with FortiOS 7.6.7</strong> on the right. I captured with a <a href="https://allegro-packets.com/en/allegro-network-multimeter" target="_blank" rel="noopener">Network Multimeter &#8220;Allegro 500&#8221; from Allegro Packets</a>.</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Lab-Setup.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14548" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Lab-Setup-1024x565.png" alt="" width="604" height="333" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Lab-Setup-1024x565.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Lab-Setup-300x166.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Lab-Setup-768x424.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Lab-Setup-1536x848.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Lab-Setup.png 1726w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>I captured three runs while I changed the ciphers for both IKE and IPsec (phase 1 and phase 2) in the following way:</p>
<ol>
<li>only classical elliptic curve Diffie-Hellman: group21</li>
<li><strong>group21 + ML-KEM</strong></li>
<li>group21 + ML-KEM + FrodoKEM + Bike (the paranoid way, just for fun)</li>
</ol>

<a href='https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Palo.png'><img loading="lazy" decoding="async" width="300" height="134" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Palo-300x134.png" class="attachment-medium size-medium" alt="" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Palo-300x134.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Palo-1024x456.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Palo-768x342.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Palo-1536x684.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Palo-604x270.png 604w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Palo.png 1600w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Forti.png'><img loading="lazy" decoding="async" width="300" height="234" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Forti-300x234.png" class="attachment-medium size-medium" alt="" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Forti-300x234.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Forti-1024x798.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Forti-768x599.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Forti-1536x1198.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-three-PQC-rounds-Forti.png 1670w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a>

<p>During the VPN sessions, I only did a <strong>ping from one side to the other</strong>. Hence: Not much traffic, but only very few packets. However, note that both firewalls implement some <strong>Dead Peer Detection</strong> (DPD; ISAKMP Informational packets) methods, while the Palo additionally monitors the VPN tunnel itself (tunnel monitor; ESP packets). Hence, there are continuous packets in the trace, even without real payload traffic.</p>
<p>Furthermore, both ends are trying to establish the VPN at the same time. This is why you will see the &#8220;Initiator Request&#8221; and the &#8220;Responder Response&#8221; from both sides at almost the same time. But never mind. ;)</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packethawk-inline-bypass-network-tap" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketHawk.1208x232.webp" /></a></div>
<h2>Analysis</h2>
<p>As always, please download those merged captures to analyse them by yourself. And/or use the <strong><a href="https://weberblog.net/the-ultimate-pcap/">Ultimate PCAP</a></strong>, since those captures are integrated there as well. Note the packet comments to find the Start/End of the appropriate sections. (Tip: Add a custom column to display the <code>frame.comment</code>.)</p>
<p style="text-align: center;">&#8211;&gt; <a href="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-3x-different-cipher-sets.pcapng.gz">PQC VPN Palo-Forti 3x different cipher-sets.pcapng.gz</a> &lt;&#8211;</p>
<p>Here&#8217;s a <strong>basic Wireshark comparison</strong>. Note the new IKEv2 messages for IKEv2 fragmentation (<a href="https://www.rfc-editor.org/info/rfc7383/" target="_blank" rel="noopener">RFC 7383</a>), which are a must for using IKE_INTERMEDIATE (<a href="https://www.rfc-editor.org/info/rfc9242/" target="_blank" rel="noopener">RFC 9242</a>) and enabling multiple key exchanges (<a href="https://www.rfc-editor.org/info/rfc9370/" target="_blank" rel="noopener">RFC 9370</a>).</p>
<h3>Classical: DH group21 only: IKE_SA_INET, IKE_AUTH</h3>
<p><a href="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-01-classical-group21-scaled.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14562" src="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-01-classical-group21-1024x579.png" alt="" width="604" height="342" srcset="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-01-classical-group21-1024x579.png 1024w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-01-classical-group21-300x170.png 300w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-01-classical-group21-768x434.png 768w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-01-classical-group21-1536x868.png 1536w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-01-classical-group21-2048x1157.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<h3>Hybrid: DH group21 + ML-KEM: fragmented IKE_INTERMEDIATE</h3>
<p><a href="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02-hybrid-group21-mlkem-scaled.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14563" src="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02-hybrid-group21-mlkem-1024x579.png" alt="" width="604" height="342" srcset="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02-hybrid-group21-mlkem-1024x579.png 1024w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02-hybrid-group21-mlkem-300x170.png 300w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02-hybrid-group21-mlkem-768x434.png 768w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02-hybrid-group21-mlkem-1536x868.png 1536w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02-hybrid-group21-mlkem-2048x1157.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a> <a href="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02b-hybrid-group21-mlkem-scaled.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14564" src="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02b-hybrid-group21-mlkem-1024x579.png" alt="" width="604" height="342" srcset="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02b-hybrid-group21-mlkem-1024x579.png 1024w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02b-hybrid-group21-mlkem-300x170.png 300w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02b-hybrid-group21-mlkem-768x434.png 768w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02b-hybrid-group21-mlkem-1536x868.png 1536w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-02b-hybrid-group21-mlkem-2048x1157.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<h3>Paranoid way: DH group21 + 3x PQC: MANY fragments :D</h3>
<p><a href="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-03-hybrid-group21-mlkem-frodokem-bike-scaled.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14565" src="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-03-hybrid-group21-mlkem-frodokem-bike-1024x579.png" alt="" width="604" height="342" srcset="https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-03-hybrid-group21-mlkem-frodokem-bike-1024x579.png 1024w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-03-hybrid-group21-mlkem-frodokem-bike-300x170.png 300w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-03-hybrid-group21-mlkem-frodokem-bike-768x434.png 768w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-03-hybrid-group21-mlkem-frodokem-bike-1536x868.png 1536w, https://weberblog.net/wp-content/uploads/2026/07/PQC-VPN-Palo-Forti-03-hybrid-group21-mlkem-frodokem-bike-2048x1157.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/network-traffic-tapping" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRaven.1208x232.webp" /></a></div>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@tobiasamueller?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Tobias A. Müller</a> on <a href="https://unsplash.com/photos/intermodal-containers-on-dock-fusq9KwkSF4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/packet-capture-of-a-post-quantum-site-to-site-vpn/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14496</post-id>	</item>
		<item>
		<title>PQC VPN-Tunnel between Palo Alto  FortiGate</title>
		<link>https://weberblog.net/pqc-vpn-tunnel-between-palo-alto-fortigate/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=pqc-vpn-tunnel-between-palo-alto-fortigate</link>
					<comments>https://weberblog.net/pqc-vpn-tunnel-between-palo-alto-fortigate/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Mon, 22 Jun 2026 05:20:43 +0000</pubDate>
				<category><![CDATA[Fortinet]]></category>
		<category><![CDATA[IPsec/VPN]]></category>
		<category><![CDATA[Palo Alto Networks]]></category>
		<category><![CDATA[Post-Quantum (PQC)]]></category>
		<category><![CDATA[FortiGate]]></category>
		<category><![CDATA[IKEv2]]></category>
		<category><![CDATA[ML-KEM]]></category>
		<category><![CDATA[Post-Quantum Cryptography]]></category>
		<category><![CDATA[PQC]]></category>
		<category><![CDATA[Site-to-Site VPN]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14491</guid>

					<description><![CDATA[<img width="300" height="163" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-300x163.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-300x163.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-1024x557.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-768x418.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-1536x835.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />Since we have learned the basics of post-quantum secure VPN tunnels, let&#8217;s configure a site-to-site VPN between a Palo Alto Networks firewall and a FortiGate with PQC ciphers to verify vendor interoperability. Spoiler: it works like a charm. ;) Palo Alto Networks supports PQC ciphers since PAN-OS 11.2, while 12.1 finally brought the ML-KEM algorithm. &#8230; <a href="https://weberblog.net/pqc-vpn-tunnel-between-palo-alto-fortigate/" class="more-link">Continue reading <span class="screen-reader-text">PQC VPN-Tunnel between Palo Alto <-> FortiGate</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="163" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-300x163.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-300x163.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-1024x557.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-768x418.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image-1536x835.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-between-Palo-Alto-FortiGate-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>Since we have learned the <a href="https://weberblog.net/pqc-vpn-tunnel-with-palo/">basics of post-quantum secure VPN tunnels</a>, let&#8217;s configure a <strong>site-to-site VPN between a Palo Alto Networks firewall and a FortiGate with PQC ciphers to verify vendor interoperability</strong>. Spoiler: it works like a charm. ;)</p>
<p><span id="more-14491"></span></p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">This is one of many VPN articles on my blog. &#8211;&gt; <a href="https://weberblog.net/site-to-site-vpn-tutorials/">Have a look at this full list</a>. &lt;&#8211;</div></div>
<p>Palo Alto Networks <a href="https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/features-introduced-in-pan-os/networking-features" target="_blank" rel="noopener">supports PQC ciphers since PAN-OS 11.2</a>, while 12.1 finally brought the ML-KEM algorithm. FortiGates <a href="https://docs.fortinet.com/document/fortigate/7.6.0/new-features/229631/enhancing-security-with-post-quantum-cryptography-for-ipsec-key-exchange-7-6-1" target="_blank" rel="noopener">support PQC ciphers since FortiOS 7.6</a>. My lab consists of a <strong>PA-440 with PAN-OS 12.1.6</strong> and a <strong>FG-70F with FortiOS 7.6.7</strong>.</p>
<h2>Setup</h2>
<p>(Note that I&#8217;m not showing a complete site-to-site VPN tutorial, but focusing on the PQC part.)</p>
<p>I&#8217;m using the <strong>hybrid approach</strong>. PQC ciphers are used *additionally* to the classical ECDH key agreement. That is: <strong>group21 + mlkem</strong>.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetlion-aggregation-packet-broker" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketLion.1208x232.webp" /></a></div>
<h3>Palo Alto Networks NGFW</h3>
<p>On the <strong>Palo</strong> side, you need to configure the <strong>IKE/IPsec Crypto, the IKE Gateway and the IPsec tunnel</strong> in the following way:</p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-14520 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-01-Palo-IKE-Crypto-1024x602.png" alt="" width="604" height="355" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-01-Palo-IKE-Crypto-1024x602.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-01-Palo-IKE-Crypto-300x176.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-01-Palo-IKE-Crypto-768x451.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-01-Palo-IKE-Crypto-1536x902.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-01-Palo-IKE-Crypto.png 1600w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14521 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-02-Palo-IKE-Crypto-Advanced-1024x675.png" alt="" width="604" height="398" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-02-Palo-IKE-Crypto-Advanced-1024x675.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-02-Palo-IKE-Crypto-Advanced-300x198.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-02-Palo-IKE-Crypto-Advanced-768x506.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-02-Palo-IKE-Crypto-Advanced-1536x1012.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-02-Palo-IKE-Crypto-Advanced.png 1600w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14522 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-03-Palo-IPsec-Crypto-1024x628.png" alt="" width="604" height="370" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-03-Palo-IPsec-Crypto-1024x628.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-03-Palo-IPsec-Crypto-300x184.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-03-Palo-IPsec-Crypto-768x471.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-03-Palo-IPsec-Crypto-1536x943.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-03-Palo-IPsec-Crypto.png 1600w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14523 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-04-Palo-IPsec-Crypto-Advanced-1024x456.png" alt="" width="604" height="269" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-04-Palo-IPsec-Crypto-Advanced-1024x456.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-04-Palo-IPsec-Crypto-Advanced-300x134.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-04-Palo-IPsec-Crypto-Advanced-768x342.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-04-Palo-IPsec-Crypto-Advanced-1536x684.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-04-Palo-IPsec-Crypto-Advanced-604x270.png 604w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-04-Palo-IPsec-Crypto-Advanced.png 1600w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14524 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-05-Palo-IKE-Gateway-1024x835.png" alt="" width="604" height="493" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-05-Palo-IKE-Gateway-1024x835.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-05-Palo-IKE-Gateway-300x245.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-05-Palo-IKE-Gateway-768x626.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-05-Palo-IKE-Gateway.png 1200w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14525 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-06-Palo-IKE-Gateway-Advanced-1024x771.png" alt="" width="604" height="455" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-06-Palo-IKE-Gateway-Advanced-1024x771.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-06-Palo-IKE-Gateway-Advanced-300x226.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-06-Palo-IKE-Gateway-Advanced-768x579.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-06-Palo-IKE-Gateway-Advanced.png 1200w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14526 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-07-Palo-IKE-Gateway-KEM-1024x592.png" alt="" width="604" height="349" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-07-Palo-IKE-Gateway-KEM-1024x592.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-07-Palo-IKE-Gateway-KEM-300x174.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-07-Palo-IKE-Gateway-KEM-768x444.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-07-Palo-IKE-Gateway-KEM.png 1200w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14527 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-08-Palo-IPsec-Tunnel-1024x673.png" alt="" width="604" height="397" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-08-Palo-IPsec-Tunnel-1024x673.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-08-Palo-IPsec-Tunnel-300x197.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-08-Palo-IPsec-Tunnel-768x505.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-08-Palo-IPsec-Tunnel-1536x1010.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-08-Palo-IPsec-Tunnel.png 1600w" sizes="auto, (max-width: 604px) 100vw, 604px" /></p>
<h3>Fortinet FortiGate</h3>
<p>On the Forti, it&#8217;s these steps that are done completely in the VPN Tunnels pane:</p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-14528 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-09-Forti-Custom-VPN-1024x840.png" alt="" width="604" height="495" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-09-Forti-Custom-VPN-1024x840.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-09-Forti-Custom-VPN-300x246.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-09-Forti-Custom-VPN-768x630.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-09-Forti-Custom-VPN-1536x1260.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-09-Forti-Custom-VPN.png 1670w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14529 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-10-Forti-Phase-1-1024x988.png" alt="" width="604" height="583" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-10-Forti-Phase-1-1024x988.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-10-Forti-Phase-1-300x290.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-10-Forti-Phase-1-768x741.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-10-Forti-Phase-1-1536x1483.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-10-Forti-Phase-1.png 1670w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14530 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-11-Forti-Phase-2-Selector-1024x606.png" alt="" width="604" height="357" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-11-Forti-Phase-2-Selector-1024x606.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-11-Forti-Phase-2-Selector-300x177.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-11-Forti-Phase-2-Selector-768x454.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-11-Forti-Phase-2-Selector.png 1474w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14531 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-12-Forti-Phase-2-Encryption-983x1024.png" alt="" width="604" height="629" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-12-Forti-Phase-2-Encryption-983x1024.png 983w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-12-Forti-Phase-2-Encryption-288x300.png 288w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-12-Forti-Phase-2-Encryption-768x800.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-12-Forti-Phase-2-Encryption-1474x1536.png 1474w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-12-Forti-Phase-2-Encryption.png 1668w" sizes="auto, (max-width: 604px) 100vw, 604px" /></p>
<p>On the CLI, it&#8217;s this (excluding the tunnel interface and the static route). Note the <code>set addke1 ml-kem-1024</code> lines.</p><pre class="urvanov-syntax-highlighter-plain-tag">config vpn ipsec phase1-interface
    edit "pa-lab"
        set interface "wan1"
        set ip-version 6
        set ike-version 2
        set peertype any
        set net-device disable
        set proposal aes256gcm-prfsha512
        set dhgrp 21
        set addke1 ml-kem-1024
        set nattraversal disable
        set transport udp
        set remote-gw6 2a00:6020:ad0b:8303::2
        set psksecret ENC Hr6QZodcvtxFwPEt4i1acXEZJIwGCboi1zx4+tA1CAB0zZR9jnIQMcYYpc375bFqulodhZmcN3IIA1JVaDTgK5y3gIG5VuCpkXwsaLQH8Tf4jRJEMTQYg2bBD/QpU8HGJgdEwyBvoRs880zTPoGr6fVsSLgy7smftEQi1NGzMW1M6S7QoEDyjopO6nKKQB0I/+4k6VlmMjY3dkVA
    next
end
config vpn ipsec phase2-interface
    edit "all-ipv6"
        set phase1name "pa-lab"
        set proposal aes256gcm
        set dhgrp 21
        set addke1 ml-kem-1024
        set src-addr-type subnet6
        set dst-addr-type subnet6
        set keylifeseconds 3600
    next
end</pre><p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetroo-data-diode" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRoo.1208x232.webp" /></a></div>
<h2>Verify</h2>
<p>Both firewalls deliver only basic &#8220;it&#8217;s working&#8221; green icons in the GUI:</p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-14533 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-13-Palo-IKE-Info-1024x513.png" alt="" width="604" height="303" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-13-Palo-IKE-Info-1024x513.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-13-Palo-IKE-Info-300x150.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-13-Palo-IKE-Info-768x385.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-13-Palo-IKE-Info-1536x770.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-13-Palo-IKE-Info.png 1600w" sizes="auto, (max-width: 604px) 100vw, 604px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14534 size-large" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-14-Forti-IPsec-Dashboard-1024x396.png" alt="" width="604" height="234" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-14-Forti-IPsec-Dashboard-1024x396.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-14-Forti-IPsec-Dashboard-300x116.png 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-14-Forti-IPsec-Dashboard-768x297.png 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-14-Forti-IPsec-Dashboard-1536x594.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Palo-Forti-14-Forti-IPsec-Dashboard-2048x792.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></p>
<p>If you want to verify whether or not post-quantum ciphers are used, the <strong>CLI</strong> is a must. Note the ML-KEM keywords:</p>
<p><strong>Palo</strong>:</p>
<p><code>show vpn ike-sa detail gateway &lt;name&gt;</code> and</p>
<p><code>show vpn ipsec-sa tunnel &lt;name&gt;</code>:</p><pre class="urvanov-syntax-highlighter-plain-tag">weberjoh@pa-lab&gt; show vpn ike-sa detail gateway fg-lab 

IKE Gateway fg-lab, ID 2 2a00:6020:ad0b:8303::2 =&gt; 2a00:6020:ad0b:8303::9
  Current time: Jun.18 09:28:56

IKE SA:
  SPI:  9835E5BCE743D9A4:8153CAA28008FAA6  Init
        State:      Established
        SN:         11
        Authentication:  PSK, peer PSK
        Proposal:   AES256-GCM16/COMBINED/DH21/ML-KEM-1024/NONE/NONE/NONE/NONE/NONE/NONE
        ID local:   ipaddr:2a00:6020:ad0b:8303::2
           remote:  ipaddr:2a00:6020:ad0b:8303::9
        ID_i:       IPv6_address:2a00:6020:ad0b:8303::9
        ID_r:       IPv6_address:2a00:6020:ad0b:8303::2
        NAT:        Not detected
        Message ID: rx 6, tx 1914
        Liveness check: sending informational packet after idle 5 seconds

        Created:    Jun.18 06:49:24, 2 hours 39 minutes 33 seconds ago
        Expires:    Jun.18 14:49:24, rekey in 4 hours 8 minutes 2 seconds (24455 sec)

  Child SA 29914:
        Tunnel 2    fg-lab
        Type:       ESP       Resp
        State:      Mature
        Message ID: 00000004
        Parent SN:  11
        SPI:        A50203B8 : BEA130B7  &lt;= ESP: BEA130B6
        Algorithm:  AES256-GCM16/COMBINED/DH21/ML-KEM-1024
        TS local:   Proto:any, ::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, Ports:any
        TS remote:  Proto:any, ::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, Ports:any
        Created:    Jun.18 09:08:36, 20 minutes 21 seconds ago
        Expires:    Jun.18 10:08:36, rekey in 33 minutes 2 seconds (3203 sec)



weberjoh@pa-lab&gt; 
weberjoh@pa-lab&gt; 
weberjoh@pa-lab&gt; show vpn ipsec-sa tunnel fg-lab 

GwID/client IP  TnID   Peer-Address                            Tunnel(Gateway)                                                                                                                  Algorithm                                                        SPI(in)  SPI(out) life(Sec/KB)             remain-time(Sec)        
--------------  ----   ------------                            ---------------                                                                                                                  ---------                                                        -------  -------- ------------             ----------------        
2               2      2a00:6020:ad0b:8303::9                  fg-lab(fg-lab)                                                                                                                   ESP/G256/   /DH21/ML-KEM-1024                                    A50203B8 BEA130B7 3600/Unlimited           2357                     

Show IPSec SA: Total 1 tunnels found. 1 ipsec sa found.</pre><p>
&nbsp;</p>
<p><strong>Forti</strong>:</p>
<p>Please note that neither of the following two commands show the key agreement protocol, hence are not usable here: <span class="crayon-c"><code>get vpn ike gateway &lt;name&gt;</code>, <code>get vpn ipsec tunnel name &lt;name&gt;</code>.</span></p>
<p><span class="crayon-c">&#8211;&gt; <strong>This is the one: <code>diagnose vpn ike gateway list name &lt;name&gt;</code></strong>:</span></p><pre class="urvanov-syntax-highlighter-plain-tag">fg-lab # diagnose vpn ike gateway list name pa-lab

vd: root/0
name: pa-lab
version: 2
interface: wan1 5
addr: 2a00:6020:ad0b:8303::9:500 -&gt; 2a00:6020:ad0b:8303::2:500
tun_id: 10.0.0.1/::10.0.0.1
remote_location: 0.0.0.0
network-id: 0
transport: UDP
created: 78734s ago
peer-id: 2a00:6020:ad0b:8303::2
peer-id-auth: no
pending-queue: 0
PPK: no
IKE SA: created 2/5  established 2/5  time 20/4238/21070 ms
IPsec SA: created 1/25  established 1/25  time 0/866/21070 ms

  id/spi: 320 15b515dc59e0a898/cb080b494e28fca3
  direction: responder
  status: established 3212-3212s ago = 20ms
  proposal: aes256gcm
  child: yes
  SK_ei: cfbac895857d9ed8-7954388f85030dc3-f2b0e7bb050f2143-45c69edfa3d5377d-b954a6bc
  SK_er: d062865f3b430a50-795d4be04b81d0a7-5d8cea7d6665c54c-f761ddc81470c232-e64fd33e
  SK_ai: 
  SK_ar: 
  message-id sent/recv: 2/642
  QKD: no
  PQC-KEM (IKE): yes
  PQC-KEM (all IPsec): yes
  lifetime/rekey: 86400/82917
  DPD sent/recv: 00000000/00000000
  peer-id: 2a00:6020:ad0b:8303::2</pre><p>
That&#8217;s it. Happy networking. :)</p>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@huguesdb?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Hugues de BUYER-MIMEURE</a> on <a href="https://unsplash.com/photos/timelapse-photo-of-tunnel-85S5K7GJ9YY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/pqc-vpn-tunnel-between-palo-alto-fortigate/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14491</post-id>	</item>
		<item>
		<title>PQC VPN-Tunnel with Palo</title>
		<link>https://weberblog.net/pqc-vpn-tunnel-with-palo/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=pqc-vpn-tunnel-with-palo</link>
					<comments>https://weberblog.net/pqc-vpn-tunnel-with-palo/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Wed, 10 Jun 2026 10:52:58 +0000</pubDate>
				<category><![CDATA[IPsec/VPN]]></category>
		<category><![CDATA[Palo Alto Networks]]></category>
		<category><![CDATA[Post-Quantum (PQC)]]></category>
		<category><![CDATA[IKEv2]]></category>
		<category><![CDATA[ML-KEM]]></category>
		<category><![CDATA[PAN-OS]]></category>
		<category><![CDATA[Post-Quantum Cryptography]]></category>
		<category><![CDATA[PQC]]></category>
		<category><![CDATA[Site-to-Site VPN]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14472</guid>

					<description><![CDATA[<img width="300" height="150" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-300x150.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-300x150.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-1024x512.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-768x384.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-1536x768.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />As the advent of practical quantum computing draws closer, security vendors are increasingly introducing post-quantum cryptographic (PQC) algorithms to protect existing security architectures against future threats. One important use case is site-to-site VPN connectivity, where organisations must address the &#8220;harvest now, decrypt later&#8221; risk &#8211; the possibility that encrypted traffic captured today could be decrypted &#8230; <a href="https://weberblog.net/pqc-vpn-tunnel-with-palo/" class="more-link">Continue reading <span class="screen-reader-text">PQC VPN-Tunnel with Palo</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="150" src="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-300x150.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-300x150.jpg 300w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-1024x512.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-768x384.jpg 768w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image-1536x768.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/06/PQC-VPN-Tunnel-with-Palo-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>As the advent of practical quantum computing draws closer, security vendors are increasingly introducing <a href="https://en.wikipedia.org/wiki/Post-quantum_cryptography" target="_blank" rel="noopener"><strong>post-quantum cryptographic (PQC)</strong></a><strong> algorithms</strong> to protect existing security architectures against future threats. One important <strong>use case is site-to-site VPN connectivity</strong>, where organisations must address the &#8220;<a href="https://en.wikipedia.org/wiki/Harvest_now,_decrypt_later" target="_blank" rel="noopener">harvest now, decrypt later</a>&#8221; risk &#8211; the possibility that encrypted traffic captured today could be decrypted by quantum computers in the future.</p>
<p>To mitigate this threat, Palo Alto Networks has implemented several approaches for quantum-resistant VPN tunnels, including <strong>Post-Quantum Preshared Keys (PPK)</strong>, <strong>Key Encapsulation Mechanisms (KEM)</strong>, and <strong>Quantum Key Distribution (QKD)</strong>. Each method offers a different balance of security, complexity, and operational requirements.</p>
<p>In this blog post, we will examine these approaches in detail, with a particular focus on KEM-based solutions, which are generally considered the preferred path forward. We will also demonstrate <strong>how to configure a site-to-site VPN tunnel that combines traditional Diffie-Hellman (DH) key exchange with post-quantum algorithms</strong> such as Kyber (standardised by NIST as ML-KEM), providing both classical and quantum-resistant security.</p>
<p><span id="more-14472"></span></p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">This is one of many VPN articles on my blog. &#8211;&gt; <a href="https://weberblog.net/site-to-site-vpn-tutorials/">Have a look at this full list</a>. &lt;&#8211;</div></div>
<div style="margin-bottom:24px"><a href="https://weberblog.net/network-traffic-tapping" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRaven.1208x232.webp" /></a></div>
<h2>Post-Quantum Security for VPN-Tunnels</h2>
<p>The primary challenge posed by quantum computers is their ability to break the asymmetric cryptographic algorithms that are widely used today for key exchange, most notably Diffie-Hellman (DH) and Elliptic Curve Diffie-Hellman (ECDH). As a result, we need new ways to securely establish VPN session keys over an untrusted network, such as the Internet.</p>
<p>Palo Alto Networks currently supports three approaches to address this challenge:</p>
<h3>PPK (Post-Quantum Preshared Key)</h3>
<p>Specified in <a href="https://www.rfc-editor.org/info/rfc8784/" target="_blank" rel="noopener">RFC 8747</a>, PPK is the <strong>simplest approach</strong>. It introduces <strong>an additional secret</strong>, known only to both VPN peers, into the key derivation process. (Do not confuse this with the traditional VPN PSK used for authentication. The PPK serves a different purpose and contributes to key establishment.)</p>
<p>Because the PPK is a randomly generated secret and not derived from a mathematically solvable key exchange, it remains resistant to attacks from both classical and quantum computers. Even if an attacker were able to break the DH exchange in the future, they would still require knowledge of the PPK to derive the session keys.</p>
<p><strong>The downside is scalability.</strong> Every VPN tunnel requires its own securely distributed PPK, creating an additional operational burden. Furthermore, if an attacker records VPN traffic today and later obtains the corresponding PPK, the recorded traffic may become decryptable. In other words, the strong forward secrecy properties (PFS) normally provided by ephemeral key exchanges are reduced.</p>
<h3>KEM (Key Encapsulation Mechanism)</h3>
<p>KEM-based key exchange is expected to become the preferred solution for most deployments. Instead of relying solely on classical DH or ECDH groups, <strong>a post-quantum algorithm is used to establish shared key material</strong>. In many implementations, including current VPN solutions, <strong>the post-quantum mechanism is combined with traditional DH/ECDH in a hybrid approach</strong>, providing protection against both classical and quantum attacks.</p>
<p>Several post-quantum KEM algorithms have been proposed over the years. NIST has standardised CRYSTALS-Kyber as <strong>ML-KEM</strong> (Module-Lattice-Based Key Encapsulation Mechanism), which is currently the leading candidate for widespread deployment. Additional algorithms, such as HQC, may be standardised in the future as alternative options.</p>
<p>When using post-quantum key exchange in IKEv2, the exchange is typically performed in a hybrid manner. <strong>A classical key exchange, such as ECDH Group 21, is combined with at least one additional post-quantum key exchange round (for example, ML-KEM)</strong>. The resulting key material is derived from both exchanges, ensuring that the VPN remains secure as long as at least one of the underlying mechanisms remains uncompromised.</p>
<p>While a single classical and a single post-quantum exchange are sufficient for most deployments, <strong>IKEv2 allows multiple additional key exchange rounds to be performed</strong>. This can further diversify the cryptographic assumptions, although the practical security benefit quickly diminishes. <strong>For most environments, one classical and one post-quantum exchange strike a sensible balance between security and complexity</strong>; configuring multiple post-quantum rounds is generally considered a rather conservative &#8211; or perhaps slightly paranoid &#8211; approach. (The German way. 😂)</p>
<h3>QKD (Quantum Key Distribution)</h3>
<p>This is where things become truly futuristic. :)</p>
<p>QKD uses the <strong>principles of quantum mechanics to exchange cryptographic key material</strong>. Any attempt to observe or intercept the quantum transmission changes its physical properties, allowing eavesdropping attempts to be detected.</p>
<p>In practice, <strong>QKD requires specialised hardware and a dedicated quantum communication channel, typically a fibre-optic connection</strong> between the participating sites. The generated keys are then used by conventional VPN technologies running over normal network links.</p>
<p>While QKD offers fascinating security properties, it also introduces high cost and operational complexity. For this reason, it is currently limited to highly specialised environments. Personally, I do not expect to deploy many QKD-enabled VPNs in the next few years &#8211; at least not in my lab. 🙂</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetfalcon-packet-capture" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketFalcon.1208x232.webp" /></a></div>
<h2>PQ-Variants in PAN-OS Versions</h2>
<p>Note that PANW has implemented those variants sequentially. Depending on your PAN-OS version, you&#8217;ll see none up to all three of them. ;) Links: <a href="https://docs.paloaltonetworks.com/pan-os/11-1/pan-os-release-notes/features-introduced-in-pan-os/networking-features" target="_blank" rel="noopener">PAN-OS 11.1</a>, <a href="https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/features-introduced-in-pan-os/networking-features" target="_blank" rel="noopener">PAN-OS 11.2</a>.</p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-14477 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/PAN-OS-PQ-Variants.png" alt="" width="750" height="568" srcset="https://weberblog.net/wp-content/uploads/2026/06/PAN-OS-PQ-Variants.png 750w, https://weberblog.net/wp-content/uploads/2026/06/PAN-OS-PQ-Variants-300x227.png 300w" sizes="auto, (max-width: 750px) 100vw, 750px" /></p>
<p>Also note that with PAN-OS 11.2 and 12.1, the list of ciphers is different:</p>
<ul>
<li><strong>PAN-OS 11.2</strong> offers various pre-standardised ciphers such as Kyber, Bike, FrodoKEM, HQC, but *not yet* the NIST standard of ML-KEM.</li>
<li><strong>PAN-OS 12.1</strong> offers all of them as well, but additionally the NIST standard <strong>ML-KEM</strong>.</li>
</ul>
<h2>Example: S2S-VPN between 2x Palos</h2>
<p>For this lab, I&#8217;m using 2x PA-440, one with <strong>PAN-OS 11.2.12</strong> &#8220;pa-home&#8221;, the other with <strong>12.1.6</strong> &#8220;pa-lab&#8221;. Hence, I can&#8217;t use ML-KEM (since it was only added with PAN-OS 12.1), but the underlying protocol Kyber. All following screenshots/listings are from PAN-OS 12.1.6.</p>
<p>The first step is to <strong>add the appropriate crypto profiles for IKE as well as for IPsec</strong>: [By the way: For AES-GCM with DH group 21, sha512 is used as the PRF. This is not documented anywhere 🤦 but a logical step since group 19 uses sha256 and group 20 uses sha384, <a href="https://docs.paloaltonetworks.com/network-security/ipsec-vpn/administration/set-up-site-to-site-vpn/define-cryptographic-profiles/define-ike-crypto-profiles" target="_blank" rel="noopener">which is documented here</a>.]
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-14478 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-01-IKE-Crypto-Profile.png" alt="" width="1000" height="588" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-01-IKE-Crypto-Profile.png 1000w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-01-IKE-Crypto-Profile-300x176.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-01-IKE-Crypto-Profile-768x452.png 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14479 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-02-IKE-Crypto-Profile-Advanced-Options.png" alt="" width="1000" height="658" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-02-IKE-Crypto-Profile-Advanced-Options.png 1000w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-02-IKE-Crypto-Profile-Advanced-Options-300x197.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-02-IKE-Crypto-Profile-Advanced-Options-768x505.png 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14480 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-03-IPsec-Crypto-Profile.png" alt="" width="1000" height="613" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-03-IPsec-Crypto-Profile.png 1000w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-03-IPsec-Crypto-Profile-300x184.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-03-IPsec-Crypto-Profile-768x471.png 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14481 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-04-IPsec-Crypto-Profile-Advanced-Options.png" alt="" width="1000" height="444" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-04-IPsec-Crypto-Profile-Advanced-Options.png 1000w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-04-IPsec-Crypto-Profile-Advanced-Options-300x133.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-04-IPsec-Crypto-Profile-Advanced-Options-768x341.png 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></p>
<p>Next is to tune <strong>the IKE Gateway</strong>. Assuming you already have a working site-to-site VPN setup, you need to set the following:</p>
<ul>
<li><strong>IKE Crypto Profile</strong> with PQ ciphers set a minute ago</li>
<li><strong>IKEv2 Fragmentation</strong> (otherwise you&#8217;ll get an operation failed with &#8220;pq-kem constraints failed: IKEv2 fragmentation must be enabled for PQ KEM&#8221;) with a blank line, which then defaults to some values. (There is a bug with PAN-OS 12.1.6 which sets the value to 576 if left blank. Since I&#8217;m using IPv6, I&#8217;ve set it to 1280 manually.)</li>
<li><strong>PQ KEM: Enable Post-Quantum Key Exchange</strong> and &#8220;Block IKEv2 if vulnerable cipher is used&#8221;, whatever this means.</li>
</ul>
<p>as well as the <strong>IPsec Crypto Profile at the IPsec Tunnel</strong>:</p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-14482 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-05-IKE-Gateway.png" alt="" width="750" height="609" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-05-IKE-Gateway.png 750w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-05-IKE-Gateway-300x244.png 300w" sizes="auto, (max-width: 750px) 100vw, 750px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14483 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-06-IKE-Gateway-Advanced-Options.png" alt="" width="750" height="568" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-06-IKE-Gateway-Advanced-Options.png 750w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-06-IKE-Gateway-Advanced-Options-300x227.png 300w" sizes="auto, (max-width: 750px) 100vw, 750px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14484 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-07-IKE-Gateway-Advanced-Options-PQ-KEM.png" alt="" width="750" height="436" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-07-IKE-Gateway-Advanced-Options-PQ-KEM.png 750w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-07-IKE-Gateway-Advanced-Options-PQ-KEM-300x174.png 300w" sizes="auto, (max-width: 750px) 100vw, 750px" /> <img loading="lazy" decoding="async" class="aligncenter wp-image-14485 size-full" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-08-IPsec-Tunnel.png" alt="" width="1000" height="656" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-08-IPsec-Tunnel.png 1000w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-08-IPsec-Tunnel-300x197.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-08-IPsec-Tunnel-768x504.png 768w" sizes="auto, (max-width: 1000px) 100vw, 1000px" /></p>
<p>These are the (a little weird) <strong>system logs</strong> after the tunnel establishment:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-09-System-Log.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14487" src="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-09-System-Log-1024x435.png" alt="" width="604" height="257" srcset="https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-09-System-Log-1024x435.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-09-System-Log-300x127.png 300w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-09-System-Log-768x326.png 768w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-09-System-Log-1536x652.png 1536w, https://weberblog.net/wp-content/uploads/2026/06/Palo-PQ-VPN-09-System-Log.png 1889w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packethawk-inline-bypass-network-tap" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketHawk.1208x232.webp" /></a></div>
<h2>Verify!</h2>
<p>Of course, verification is key. Search for the &#8220;KYBER-1024&#8221; entries, respectively ML-KEM, or whatever algorithm you&#8217;ve chosen.</p>
<ul>
<li><code>show vpn ike-sa detail gateway &lt;name&gt;</code></li>
<li><code>show vpn ipsec-sa tunnel &lt;name&gt;</code></li>
</ul>
<p>Examples:</p><pre class="urvanov-syntax-highlighter-plain-tag">weberjoh@pa-lab&gt; show vpn ike-sa detail gateway pa-home

IKE Gateway pa-home, ID 1 2a00:6020:ad0b:8303::2 =&gt; 2a00:6020:ad0b:8303::1
  Current time: Jun.09 13:18:59

IKE SA:
  SPI:  CB7978FA43B5AD61:68F52ADC2342D6F1  Init
        State:      Established
        SN:         3
        Authentication:  PSK, peer PSK
        Proposal:   AES256-GCM16/COMBINED/DH21/KYBER-1024/NONE/NONE/NONE/NONE/NONE/NONE
        ID local:   ipaddr:2a00:6020:ad0b:8303::2
           remote:  ipaddr:2a00:6020:ad0b:8303::1
        ID_i:       IPv6_address:2a00:6020:ad0b:8303::2
        ID_r:       IPv6_address:2a00:6020:ad0b:8303::1
        NAT:        Not detected
        Message ID: rx 343, tx 344
        Liveness check: sending informational packet after idle 5 seconds

        Created:    Jun.09 12:50:25, 28 minutes 35 seconds ago
        Expires:    Jun.09 20:50:25, rekey in 6 hours 24 minutes 5 seconds (24760 sec)

  Child SA 347:
        Tunnel 1    pa-home
        Type:       ESP       Init
        State:      Mature
        Message ID: 0000005A
        Parent SN:  3
        SPI:        8BA354C8 : F2F00F7D
        Algorithm:  AES256-GCM16/COMBINED/DH21/KYBER-1024
        Created:    Jun.09 12:57:47, 21 minutes 13 seconds ago
        Expires:    Jun.09 13:57:47, rekey in 29 minutes 47 seconds (3060 sec)

  Child SA 600:
        Type:       INFO
        State:      Expired
        Message ID: 00000157
        Parent SN:  3




weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt; show vpn ipsec-sa tunnel pa-home

GwID/client IP  TnID   Peer-Address                            Tunnel(Gateway)                                                                                                                  Algorithm                                                        SPI(in)  SPI(out) life(Sec/KB)             remain-time(Sec)
--------------  ----   ------------                            ---------------                                                                                                                  ---------                                                        -------  -------- ------------             ----------------
1               1      2a00:6020:ad0b:8303::1                  pa-home(pa-home)                                                                                                                 ESP/G256/   /DH21/KYBER-1024                                     8BA354C8 F2F00F7D 3600/Unlimited           2256

Show IPSec SA: Total 1 tunnels found. 1 ipsec sa found.


weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt;</pre><p>
&nbsp;</p>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@dynamicwang?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dynamic Wang</a> on <a href="https://unsplash.com/photos/background-pattern-ERdTJQTtsbE?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/pqc-vpn-tunnel-with-palo/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14472</post-id>	</item>
		<item>
		<title>FortiGate Enables NAT for IPv6 by Default 🤦</title>
		<link>https://weberblog.net/fortigate-enables-nat-for-ipv6-by-default-%f0%9f%a4%a6/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=fortigate-enables-nat-for-ipv6-by-default-%25f0%259f%25a4%25a6</link>
					<comments>https://weberblog.net/fortigate-enables-nat-for-ipv6-by-default-%f0%9f%a4%a6/#comments</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Wed, 27 May 2026 11:33:28 +0000</pubDate>
				<category><![CDATA[Fortinet]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Central NAT]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[FortiGate]]></category>
		<category><![CDATA[IPv4 Thinking]]></category>
		<category><![CDATA[NAT]]></category>
		<category><![CDATA[NAT66]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14233</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />Fortinet has a misstep in its IPv6 settings: NAT66 is enabled by default for every policy. Not only does this make no technical sense and go against established best practices, but in my view, there’s an even bigger issue at play here: Given the widespread use of FortiGate devices and the still limited level of &#8230; <a href="https://weberblog.net/fortigate-enables-nat-for-ipv6-by-default-%f0%9f%a4%a6/" class="more-link">Continue reading <span class="screen-reader-text">FortiGate Enables NAT for IPv6 by Default 🤦</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Enables-NAT-for-IPv6-by-Default-🤦🤦🤦-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>Fortinet has a misstep in its IPv6 settings: <strong>NAT66 is enabled by default for every policy</strong>. Not only does this make no technical sense and go against established best practices, but in my view, there’s an even bigger issue at play here:</p>
<p>Given the widespread use of FortiGate devices and the still limited level of IPv6 expertise among many administrators, this default setting risks creating false knowledge. <strong>Many admins may come away believing that NAT for IPv6 is just as normal as it is for IPv4</strong> &#8211; after all, it’s enabled out of the box. And as with any default, people will quickly get used to it.</p>
<p>In this blog post, I’ll therefore look at a few practical workarounds to move away from this approach as quickly as possible.</p>
<p><span id="more-14233"></span></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetowl-suricata-ids-basiertes-hochleistungs-nsm" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketOwl.1208x232.webp" /></a></div>
<h2>Problem Description</h2>
<p>This default configuration is fundamentally at odds with what IPv6 is meant to be &#8211; essentially the exact opposite of NAT. To recap: <strong>NAT was a workaround for IPv4</strong>, specifically to deal with address exhaustion and allow continued internet connectivity despite limited address space. <strong>The goal of IPv6, in contrast, was to restore true end-to-end connectivity at Layer 3: globally unique, routable IP addresses, with no need for NAT.</strong> (Yes, there are edge cases where NPTv6 &#8211; Network Prefix Translation &#8211; can be used appropriately.)</p>
<div class="su-note"  style="border-color:#d88a59;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#f2a473;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">The use of NAT66, especially in combination with PAT, is completely detached from reality. <strong>Avoiding NAT66 is not a “nice to have.” It is the very purpose of IPv6 to eliminate the need for NAT.</strong></div></div>
<p>A single policy for IPv4 and IPv6 (&#8220;consolidated policy&#8221;) only has a single NAT switch. While this is mandatory for IPv4 to function for almost all outgoing connections, it also enables NAT66 for the same source/destination IPv6 addresses:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Details.png"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14427" src="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Details.png" alt="" width="795" height="945" srcset="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Details.png 795w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Details-252x300.png 252w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Details-768x913.png 768w" sizes="auto, (max-width: 795px) 100vw, 795px" /></a>A forward traffic log then looks like this:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Log.png"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14428" src="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Log.png" alt="" width="621" height="395" srcset="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Log.png 621w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Log-300x191.png 300w" sizes="auto, (max-width: 621px) 100vw, 621px" /></a></p>
<p>From a configuration perspective, the problem lies in the <code>set nat enable</code> CLI command, which does not distinguish between legacy IP and IPv6 (as the CLI *does* distinguish between both IPs when it comes to the src/dst addresses, which is not a good design as well, by the way):</p><pre class="urvanov-syntax-highlighter-plain-tag">config firewall policy
    edit 1
        set name "fg-lab-61 raus"
        set srcintf "fg-lab-61"
        set dstintf "wan1"
        set action accept
        set srcaddr "all"
        set dstaddr "all"
        set srcaddr6 "all"
        set dstaddr6 "all"
        set service "ALL"
        set logtraffic all
        set nat enable
    next
end</pre><p>
Lastly tested with a FortiGate 70F and <strong>FortiOS v7.6.6</strong>. However, this topic has been around for several FortiOS releases. <a href="https://x.com/webernetz/status/836924674646880257" target="_blank" rel="noopener">I first reported it in 2017</a>, almost 10 years ago. Unfortunately, nothing has changed since then.</p>
<h2>Workaround 1: Central NAT</h2>
<p>From an architect&#8217;s perspective, the central NAT is a very good option. Not only for IPv6, but also for IPv4. Why? Because <strong>it separates the network/routing layer (NAT or not) from the security layer (policy allow or deny)</strong>. If you have hundreds of outgoing policies, there&#8217;s no need to have hundreds of &#8220;nat enable&#8221; switches. One NAT policy per direction fits completely, e.g.: internal -&gt; Internet: SNAT.</p>
<p><strong>Since such NAT policies are configured only for IPv4, no IPv6 NAT would be applied within the same rule. 👍🏻</strong></p>
<p>Enabling Central SNAT:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-enabled.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14432" src="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-enabled-1024x558.png" alt="" width="604" height="329" srcset="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-enabled-1024x558.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-enabled-300x164.png 300w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-enabled-768x419.png 768w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-enabled.png 1031w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>Or via CLI:</p><pre class="urvanov-syntax-highlighter-plain-tag">config system settings
    set central-nat enable
end</pre><p>
Building the needed <strong>outgoing SNAT policies for legacy IP</strong> (note the IPv4 selection at the top):</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-Policy.png"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14433" src="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-Policy.png" alt="" width="791" height="835" srcset="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-Policy.png 791w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-Policy-284x300.png 284w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Central-SNAT-Policy-768x811.png 768w" sizes="auto, (max-width: 791px) 100vw, 791px" /></a></p>
<p>Your policies will then show a &#8220;Custom&#8221; in the NAT column:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Dual-Stack-Policy-with-Central-NAT.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14435" src="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Dual-Stack-Policy-with-Central-NAT-1024x210.png" alt="" width="604" height="124" srcset="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Dual-Stack-Policy-with-Central-NAT-1024x210.png 1024w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Dual-Stack-Policy-with-Central-NAT-300x62.png 300w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Dual-Stack-Policy-with-Central-NAT-768x158.png 768w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Dual-Stack-Policy-with-Central-NAT.png 1227w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>Outgoing IPv6 sessions will have no NAT anymore. ✅</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Traffic-Log-without-NAT66.png"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14436" src="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Traffic-Log-without-NAT66.png" alt="" width="571" height="334" srcset="https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Traffic-Log-without-NAT66.png 571w, https://weberblog.net/wp-content/uploads/2026/06/FortiGate-Traffic-Log-without-NAT66-300x175.png 300w" sizes="auto, (max-width: 571px) 100vw, 571px" /></a></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetlion-aggregation-packet-broker" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketLion.1208x232.webp" /></a></div>
<h2>Workaround 2: Independent Policies for IPv4 and IPv6</h2>
<p>As an alternative, you can <strong>split each dual-stack policy into two policies: one for IPv4 (with NAT) and one for IPv6 (without NAT)</strong>. While this will work, it obviously doubles the number of policy entries, which is, unfortunately, a really bad design as well. You&#8217;ll end up with two policy sets &#8211; one covering IPv4, the other one covering IPv6 &#8211; which won&#8217;t be congruent in your daily work. <strong>This eventually leads to more security holes in your overall policy, since you will forget one or the other.</strong></p>
<p>However, technically, you would migrate from this:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14429" src="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-1024x117.png" alt="" width="604" height="69" srcset="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-1024x117.png 1024w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-300x34.png 300w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-768x88.png 768w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT.png 1389w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>to that:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Workaround-two-Policies.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14430" src="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Workaround-two-Policies-1024x128.png" alt="" width="604" height="76" srcset="https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Workaround-two-Policies-1024x128.png 1024w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Workaround-two-Policies-300x38.png 300w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Workaround-two-Policies-768x96.png 768w, https://weberblog.net/wp-content/uploads/2026/05/FortiGate-Dual-Stack-Policy-with-NAT-Workaround-two-Policies.png 1389w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<h2>Workaround 3: Different Device</h2>
<p>I don’t know whether this is a sensible workaround or not. I also don’t want to engage in unnecessary bashing here. Still, <strong>I wonder how much you can trust a product if it already gets the most basic things completely wrong</strong>. To me, it’s more than just a slightly uneasy feeling &#8211; it’s fundamental.</p>
<p>Another concern is the fact that Fortinet has been aware of this issue for years, yet hasn’t made any meaningful changes. And yes, I am fully aware that FortiGate is one of the most widely deployed firewall platforms, and that this topic “only” touches the networking fundamentals rather than the security features themselves.</p>
<p>Even so, it raises serious questions. When customers ask me in my IPv6 workshops today which product they should choose for a new deployment, I simply cannot recommend FortiGate in good conscience. And that’s not solely because of this NAT issue &#8211; there are other IPv6-related shortcomings as well. (E.g., no address groups for v4/v6 addresses at the same time; DNS64 only globally enabled with “always-synthesize-aaaa” enabled by default; NAT64 only possible with &#8220;IP Pool&#8221; and not &#8220;outgoing interface address&#8221;; NAT46 not available with Central NAT; OSPFv3/BGP only through CLI.)</p>
<p>What would you do?</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetlion-aggregation-packet-broker" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketLion.1208x232.webp" /></a></div>
<h2>@Fortinet: Please fix this 🙏</h2>
<p>Fortinet, if you&#8217;re reading this: <strong>Please reconsider this default behaviour.</strong> Please align your IPv6 implementation with the fundamental design principles of the protocol and disable NAT66 by default. This is not a minor detail &#8211; it directly shapes how administrators understand and deploy IPv6 in real-world networks. By correcting this, you would not only improve your product but also help prevent the continued spread of misconceptions around IPv6.</p>
<p>At the same time, <strong>I would encourage everyone reading this to raise awareness of the issue.</strong> If you are working with FortiGate devices or considering them, please reach out to Fortinet &#8211; through your account teams, support channels, or public forums &#8211; and make your voice heard. Vendor defaults matter, and change is far more likely when customers clearly and collectively highlight where improvements are needed.</p>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@silverkblack?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Vitaly Gariev</a> on <a href="https://unsplash.com/photos/man-rubbing-his-face-in-front-of-laptop-bl7h_R-PKpU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/fortigate-enables-nat-for-ipv6-by-default-%f0%9f%a4%a6/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14233</post-id>	</item>
		<item>
		<title>Palo Alto Networks NGFW &#8220;SSL Inbound Inspection&#8221; with different Certificate</title>
		<link>https://weberblog.net/palo-alto-networks-ngfw-ssl-inbound-inspection-with-different-certificate/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=palo-alto-networks-ngfw-ssl-inbound-inspection-with-different-certificate</link>
					<comments>https://weberblog.net/palo-alto-networks-ngfw-ssl-inbound-inspection-with-different-certificate/#comments</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Tue, 05 May 2026 15:42:43 +0000</pubDate>
				<category><![CDATA[Certificate]]></category>
		<category><![CDATA[Palo Alto Networks]]></category>
		<category><![CDATA[SSL Decryption]]></category>
		<category><![CDATA[SSL Inbound Inspection]]></category>
		<category><![CDATA[TLS]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14337</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />I had a use case where I wanted to use the SSL Inbound Inspection on a Palo, but with a different X.509 certificate than the one on the server itself. That is: the backend server has its self-signed (or internal PKI-signed) certificate along with its hostname, while the decryption policy on the Palo uses a &#8230; <a href="https://weberblog.net/palo-alto-networks-ngfw-ssl-inbound-inspection-with-different-certificate/" class="more-link">Continue reading <span class="screen-reader-text">Palo Alto Networks NGFW &#8220;SSL Inbound Inspection&#8221; with different Certificate</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/05/Palo-Alto-Networks-NGFW-SSL-Inbound-Inspection-with-different-Certificate-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>I had a use case where I wanted to use the SSL Inbound Inspection on a Palo, <strong>but with a different X.509 certificate than the one on the server itself</strong>. That is: the backend server has its self-signed (or internal PKI-signed) certificate along with its hostname, while the decryption policy on the Palo uses a publicly trusted signed certificate for the same hostname. Just like a reverse proxy / load balancer / WAF.</p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">TL;DR: While it would be technically feasible, <strong>this configuration is not working</strong>. :(</div></div>
<p><span id="more-14337"></span></p>
<p>To be more precise about the use case: An internal server has one certificate, signed by the internal PKI, but with various DNS hostnames &#8211; internal ones, such as <code>foobar.internal</code>, and external ones, such as <code>myserver.company.com</code>.</p>
<p>Now, <strong>external visitors shall see a publicly trusted certificate</strong> for <code>myserver.company.com</code>, which is different from the one installed on the server itself. This is exactly what a reverse proxy is meant for. But to avoid another component (and since the Palo can do the security part by looking into the TLS session), I wanted to use the SSL Inbound Inspection &#8211; but with a different certificate.</p>
<p>By the way: Why is it still called &#8220;SSL&#8221; and not &#8220;TLS&#8221;? This really triggers me. 😂</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetroo-data-diode" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRoo.1208x232.webp" /></a></div>
<p>My lab consisted of the following:</p>
<ul>
<li>PA-440, <strong>PAN-OS 11.2.11</strong></li>
<li>Raspi with a self-signed certificate with CN/SAN of <code>pi10-test5.weberlab.de</code></li>
<li>A Let&#8217;s Encrypt certificate with the same name, <code>pi10-test5.weberlab.de</code></li>
<li>This Let&#8217;s Encrypt certificate, including its private key, was uploaded to the Palo and used in the decryption policy.</li>
</ul>
<p>But, as already noted, this setup is working.</p>
<p>The decryption log showed some &#8220;<strong>certificate verify failed</strong>&#8221; errors:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-01-Decryption-Log.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14345" src="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-01-Decryption-Log-1024x216.png" alt="" width="604" height="127" srcset="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-01-Decryption-Log-1024x216.png 1024w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-01-Decryption-Log-300x63.png 300w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-01-Decryption-Log-768x162.png 768w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-01-Decryption-Log-1536x323.png 1536w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-01-Decryption-Log.png 1952w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>while the traffic log listed those sessions as &#8220;policy-deny&#8221;, which is not accurate from my point of view: (and those lines were not highlighted in red, though the checkbox was hit)</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-02-Traffic-Log.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14346" src="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-02-Traffic-Log-1024x196.png" alt="" width="604" height="116" srcset="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-02-Traffic-Log-1024x196.png 1024w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-02-Traffic-Log-300x57.png 300w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-02-Traffic-Log-768x147.png 768w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-02-Traffic-Log-1536x294.png 1536w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-02-Traffic-Log-2048x392.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>The <code>show counter global</code> revealed some <code>ssl_inbound_cert_mismatch</code> hits:</p><pre class="urvanov-syntax-highlighter-plain-tag">ssl_inbound_cert_mismatch                 70        0 error     ssl       pktproc   No matching server certificate found in config</pre><p>
which exactly aligns with the hit count on the decryption policy:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-03-Decryption-Policy.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14349" src="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-03-Decryption-Policy-1024x194.png" alt="" width="604" height="114" srcset="https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-03-Decryption-Policy-1024x194.png 1024w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-03-Decryption-Policy-300x57.png 300w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-03-Decryption-Policy-768x146.png 768w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-03-Decryption-Policy-1536x291.png 1536w, https://weberblog.net/wp-content/uploads/2026/05/PANW-SSL-Inbound-Inspection-with-different-Certificate-03-Decryption-Policy-2048x388.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p><a href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA1Ki000000sY1zKAE" target="_blank" rel="noopener">This KB article from PANW</a> gives some details about that behaviour:</p>
<div class="su-quote su-quote-style-default"><div class="su-quote-inner su-u-clearfix su-u-trim">When a server sends a ServerHello message, the firewall captures the certificate&#8217;s MD5 fingerprint.</p>
<p>It compares this fingerprint against the one stored in your local SSL Inbound Inspection rule.</p>
<p>If the fingerprints do not match, the firewall immediately kills the session and logs the error: Server and Firewall&#8217;s certificate mismatch.</div></div>
<p>For whatever reason, I&#8217;m seeing a different error message. Anyway, that&#8217;s the root cause here. <strong>AFAIK, it should be possible to do this TLS interception regardless of the exact certificate being present. Hence, I suppose that it&#8217;s a limit by design.</strong></p>
<p>Any comments? ;)</p>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@robert_clark?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Robert Clark</a> on <a href="https://unsplash.com/photos/a-large-group-of-purple-and-yellow-bullet-caps-bw8iOoOzjc0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/palo-alto-networks-ngfw-ssl-inbound-inspection-with-different-certificate/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14337</post-id>	</item>
		<item>
		<title>Basic IPv6 Messages (v2): Wireshark Captures</title>
		<link>https://weberblog.net/basic-ipv6-messages-v2-wireshark-captures/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=basic-ipv6-messages-v2-wireshark-captures</link>
					<comments>https://weberblog.net/basic-ipv6-messages-v2-wireshark-captures/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Thu, 23 Apr 2026 19:49:02 +0000</pubDate>
				<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Memorandum]]></category>
		<category><![CDATA[Coloring Rules]]></category>
		<category><![CDATA[DHCPv6]]></category>
		<category><![CDATA[Dual-Stack]]></category>
		<category><![CDATA[IPv6 Duplicate Address Detection]]></category>
		<category><![CDATA[Neighbor Discovery]]></category>
		<category><![CDATA[pcap]]></category>
		<category><![CDATA[ProfiShark]]></category>
		<category><![CDATA[Router Advertisement]]></category>
		<category><![CDATA[Ultimate PCAP]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Wireshark]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=12509</guid>

					<description><![CDATA[<img width="300" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-300x150.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-300x150.jpg 300w, https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-1024x513.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-768x384.jpg 768w, https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-1536x769.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />In my IPv6 classes, I always teach the basic IPv6 messages as seen on the wire. There&#8217;s so much new stuff, such as Router Advertisements, Duplicate Address Detections, Neighbour Solicitations, and so on. Therefore, I&#8217;m using a rather simple packet capture showing the starting process of a client getting its addresses. For the last 10 years, &#8230; <a href="https://weberblog.net/basic-ipv6-messages-v2-wireshark-captures/" class="more-link">Continue reading <span class="screen-reader-text">Basic IPv6 Messages (v2): Wireshark Captures</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-300x150.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-300x150.jpg 300w, https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-1024x513.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-768x384.jpg 768w, https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image-1536x769.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Wireshark-Capture-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>In my IPv6 classes, I always teach<strong> the basic IPv6 messages as seen on the wire</strong>. There&#8217;s so much new stuff, such as Router Advertisements, Duplicate Address Detections, Neighbour Solicitations, and so on. Therefore, I&#8217;m using a rather <strong>simple packet capture showing the starting process of a client getting its addresses</strong>.</p>
<p>For the last 10 years, I used <a href="https://weberblog.net/basic-ipv6-messages-wireshark-capture/">this capture</a>, which I took on a Knoppix Linux along with a German Speedport router, in which SLAAC was used for getting the addresses. However, it turned out that in enterprise-grade networks, <strong>stateful DHCPv6</strong> is used more commonly. Hence, I did it again and captured the very first IPv6 messages as seen on an IPv6 node, but this time on a Windows 11 PC and a Debian 13, along with stateful DHCPv6.</p>
<p><span id="more-12509"></span></p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">Note that this post is one of many related to IPv6. <a href="https://weberblog.net/ipv6/">Click here for a structured list</a>.</div></div>
<h2>The Packet Captures</h2>
<p>My testbed consists of the following components:</p>
<ul>
<li><strong>Windows 11 Version 25H2</strong> (Build 26200.7462)</li>
<li>Raspberry Pi 3 with <strong>Debian GNU/Linux 13 (trixie)</strong>, <strong>Kernel 6.12.62</strong>+rpt-rpi-v8</li>
<li>Palo Alto Networks firewall PA-440 with PAN-OS 11.1.10-h10 as the layer 3 gateway and <strong>DHCPv6 relay</strong></li>
<li>Infoblox Grid with NIOS 9.0.7, acting as the DHCPv6 server to which the Palo relays. The GUA addresses <code>2a00:6020:ad0b:83::/48</code> are out of a residential ISP connection (<a href="https://weberblog.net/verbindungsaufbau-deutsche-glasfaser/">Deutsche Glasfaser</a>) here in Germany. RFC 1918 for legacy IP. (<a href="https://weberblog.net/stateful-dhcpv6-capture-along-with-relaying/">Details about DHCPv6 relaying are here.</a>)</li>
</ul>
<p>To avoid unnecessary packets, only those clients were present on this VLAN. I <strong>captured with a real TAP</strong>, the <a href="https://weberblog.net/my-network-companion-the-profishark/"><strong>ProfiShark</strong></a>, in between the switch (port A) and the clients (port B), starting *before* the LAN cables were plugged in.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/network-traffic-tapping" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRaven.1208x232.webp" /></a></div>
<p>I did those captures with the <strong>Windows</strong> machine (was powered up, but I plugged in and out the network cable), and then with the the <strong>Ubuntu</strong> machine, which I booted up and shut down. In both cases, I also did the following simple tasks to have some upper-layer packets in there.:</p>
<ul>
<li><code>ping -c 4 -6 weberblog.net</code></li>
<li><code>ping -c 4 -4 weberblog.net</code></li>
<li><code>nslookup/host securityasapodcast.de</code></li>
<li><code>firefox/lynx http://ip.webernetz.net</code></li>
<li><code>firefox/lynx https://ip-only.webernetz.net</code></li>
</ul>
<p>Here are the capture files. <strong>Feel free to download and use them for whatever you need</strong>. (Please link back to this post if used. Thanks.) Those *.pcapng.gz files can be opened directly in Wireshark. And, of course, those packets are part of the <a href="https://weberblog.net/the-ultimate-pcap/">Ultimate PCAP</a>.</p>
<p style="text-align: center;"><a href="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-DHCPv6-Windows.pcapng.gz">&#8211;&gt; IPv6 Address Assignment <strong>DHCPv6 Windows</strong>.pcapng.gz &lt;&#8211;</a><br />
<a href="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-DHCPv6-Linux.pcapng.gz">&#8211;&gt; IPv6 Address Assignment <strong>DHCPv6 Linux</strong>.pcapng.gz &lt;&#8211;</a></p>
<p>And since I was on it anyway, I did some new captures for the classical <strong>SLAAC address assignment</strong>, too. That is: RA with prefix information along with the RDNSS option:</p>
<p style="text-align: center;"><a href="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-SLAAC-Windows.pcapng.gz">&#8211;&gt; IPv6 Address Assignment <strong>SLAAC Windows</strong>.pcapng.gz &lt;&#8211;</a><br />
<a href="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-SLAAC-Linux.pcapng.gz">&#8211;&gt; IPv6 Address Assignment <strong>SLAAC Linux</strong>.pcapng.gz &lt;&#8211;</a></p>
<p>Packets you can find within those trace files:</p>
<ul>
<li><strong>Router Solicitations</strong> aka ICMPv6 type 133</li>
<li><strong>Router Advertisements</strong> aka ICMPv6 type 134 (M-flag set, no prefix; respectively prefix information and A-flag)</li>
<li><strong>Duplicate Address Detection (DAD)</strong> aka ICMPv6 type 135, sent from the unspecified address <code>::</code></li>
<li>Neighbour Solicitation &amp; Advertisement, types 135 and 136</li>
<li>Multicast Listener stuff</li>
<li><strong>Stateful DHCPv6</strong> (via relay on the Palo, only on the DHCPv6 captures)</li>
<li>DNS queries</li>
<li>Ping aka ICMP/ICMPv6 echo-request and echo-reply</li>
<li>DHCP for legacy IP</li>
<li>ARP for legacy IP</li>
</ul>
<h2>Wiresharking IPv6 &#8211;&gt; Coloring Rules</h2>
<p>Please note that I&#8217;m heavily relying on <strong>colouring rules in order to distinguish all those ICMPv6-based neighbour discovery protocol (NDP) messages, which are: RS/RA, NS/NA, and DAD</strong>. Furthermore, the MLD messages, which are not really of interest, are kind of hidden, since I am using a rule of green foreground with white background for them. Refer to these first four lines:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6.png"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-14383" src="https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6.png" alt="" width="873" height="470" srcset="https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6.png 873w, https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-300x162.png 300w, https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-768x413.png 768w" sizes="auto, (max-width: 873px) 100vw, 873px" /></a></p>
<p>Here&#8217;s a side-by-side comparison of the *same* packets without (left) and with (right) my colouring rules:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-side-by-side-comparison.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14384" src="https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-side-by-side-comparison-1024x365.png" alt="" width="604" height="215" srcset="https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-side-by-side-comparison-1024x365.png 1024w, https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-side-by-side-comparison-300x107.png 300w, https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-side-by-side-comparison-768x274.png 768w, https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-side-by-side-comparison-1536x547.png 1536w, https://weberblog.net/wp-content/uploads/2026/05/Wireshark-Coloring-Rules-for-IPv6-ICMPv6-side-by-side-comparison-2048x730.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<h2>Looking at the Startup Process</h2>
<p>Since a picture is worth a thousand words, here are some of the bootup process from Windows with DHCPv6:</p>

<a href='https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-1-Router-Solicitation.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-1-Router-Solicitation-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-2-Router-Advertisement.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-2-Router-Advertisement-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-3-DHCPv6.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-3-DHCPv6-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-4-DHCPv6-Advertise.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-4-DHCPv6-Advertise-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-5-Duplicate-Address-Detection.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-5-Duplicate-Address-Detection-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-6-Neighbor-Solicitations-and-Advertisements.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-6-Neighbor-Solicitations-and-Advertisements-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-7-Upper-Layer-Traffic.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/Basic-IPv6-Messages-v2-Windows-DHCPv6-7-Upper-Layer-Traffic-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>

<div style="margin-bottom:24px"><a href="https://weberblog.net/packetowl-suricata-ids-basiertes-hochleistungs-nsm" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketOwl.1208x232.webp" /></a></div>
<h2>Some Notes</h2>
<ul>
<li><strong>Neither operating system sends Duplicate Address Detection messages for its link-local addresses</strong>, but only for their GUAs. Even though I plugged in the network cable again and again, that is, the capture process always started at the very beginning of the NIC being live on the network. Is this a current best practice I&#8217;m not aware of?</li>
<li><strong>Windows *always* sends DHCPv6 SOLICIT messages</strong>, even if the RA does not have the M-flag set, or even if no RA was received at all. Be careful in situations where both SLAAC and M-flag are used! (Not recommended anyway.)</li>
<li>Quite interesting is the <strong>Internet Protocol that Windows/Linux are using for querying the recursive DNS server</strong>:
<ul>
<li>SLAAC with RDNSS: Windows IPv4 🟡, Linux IPv4 🟡</li>
<li>Stateful DHCPv6: Windows IPv6 ✅, Linux still IPv4 ❌ (WHY?!?!?)</li>
<li>That is: Within Dual-Stack environments, IPv6 is not used for reaching the recursive DNS server in many situations. I would have expected it to behave differently. At least for the stateful DHCPv6 part, IPv6 should be used to reach the RDNS. Maybe the stub resolver on my Linux machine behaves differently? Or is it related to latency?</li>
</ul>
</li>
<li>Windows does not send any Multicast Listener Reports at all. Linux does. (I don&#8217;t see any advantages of those MLDs anyway, since almost all layer 2 switches I know don&#8217;t leverage multicast snooping by default.)</li>
<li>When you move a Windows PC into a new Layer 3 network, it initially assumes it is still in the previous one. You can see this as it requests the old IPv4 address via DHCP or tries to use the old IPv6 addresses via NDP. To make matters more complicated, in my two test VLANs, the Palo Alto Networks firewall (default gateway) always uses the exact same IPv6 link-local address, <code>fe80::3efa:30ff:fe04:9114</code>.</li>
<li>I omitted many other chatty packets that were sent during the first seconds of a connected network, e.g.: NTP, LLMNR, NBNS, MDNS, IGMP, SSDP. Those are all sent for various reasons (that I don&#8217;t know) from Windows. That is: While my proposed PCAPs show all packets relevant to IPv6 and legacy IP address assignment, it does NOT show all possible name resolution and network reconnaissance attempts from Windows itself.</li>
</ul>
<p>For the sake of completeness, here are some screenshots of how I set up the layer 3 interfaces on the Palo. (Note that I initially configured a third testbed with &#8220;stateless DHCPv6&#8221;, hence the O-flag. But since this is not a relevant scenario anymore, as all major operating systems have RDNSS implemented, I did not follow up on those captures.)</p>

<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-01-Interfaces.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-01-Interfaces-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-02-SLAAC.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-02-SLAAC-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-03-SLAAC.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-03-SLAAC-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-04-SLAAC.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-04-SLAAC-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-05-SLAAC.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-05-SLAAC-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-06-DHCPv6.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-06-DHCPv6-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-07-DHCPv6.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-07-DHCPv6-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-08-DHCPv6.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-08-DHCPv6-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-09-DHCP-Relay.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2026/05/IPv6-Address-Assignment-Palo-09-DHCP-Relay-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>

<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@dtopkin1?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dayne Topkin</a> on <a href="https://unsplash.com/photos/macbook-pro-on-white-table-y5_mFlLMwJk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/basic-ipv6-messages-v2-wireshark-captures/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">12509</post-id>	</item>
		<item>
		<title>Decrypting TLS with Wireshark</title>
		<link>https://weberblog.net/decrypting-tls-with-wireshark/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=decrypting-tls-with-wireshark</link>
					<comments>https://weberblog.net/decrypting-tls-with-wireshark/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Mon, 13 Apr 2026 11:09:15 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[TLS]]></category>
		<category><![CDATA[Tutorial/Howto]]></category>
		<category><![CDATA[Wireshark]]></category>
		<category><![CDATA[Decrypted]]></category>
		<category><![CDATA[Follow HTTP Stream]]></category>
		<category><![CDATA[Follow TCP Stream]]></category>
		<category><![CDATA[Follow TLS Stream]]></category>
		<category><![CDATA[HTTPS]]></category>
		<category><![CDATA[Ultimate PCAP]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14278</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />Did you know that you can easily decrypt TLS (mostly HTTPS) traffic with Wireshark? Well, only if you have the keys. ;) This really is a game-changer if you&#8217;re stuck with troubleshooting encrypted data. Let&#8217;s do an example: The server&#8217;s private key (certificate) is no longer of interest, since all modern ciphers use (EC)DHE, in &#8230; <a href="https://weberblog.net/decrypting-tls-with-wireshark/" class="more-link">Continue reading <span class="screen-reader-text">Decrypting TLS with Wireshark</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>Did you know that you can easily <strong>decrypt TLS (mostly HTTPS) traffic with Wireshark</strong>? Well, only if you have the keys. ;) This really is a game-changer if you&#8217;re stuck with troubleshooting encrypted data. Let&#8217;s do an example:</p>
<p><span id="more-14278"></span></p>
<div class="su-note"  style="border-color:#69adc8;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;"><div class="su-note-inner su-u-clearfix su-u-trim" style="background-color:#83c7e2;border-color:#ffffff;color:#333333;border-radius:3px;-moz-border-radius:3px;-webkit-border-radius:3px;">TL;DR: You can decrypt TLS traffic with Wireshark, but only <strong>if you have the session keys</strong>! Those can be exported by browsers if you set the SSLKEYLOGFILE environment variable *before* using the browser.</div></div>
<p>The server&#8217;s private key (certificate) is no longer of interest, since all modern ciphers use (EC)DHE, in which the session keys are derived by both parties. With TLS 1.3, RSA key exchange is gone completely. All ciphers use forward secrecy.</p>
<h2>Getting the Session Keys</h2>
<p>In this example, I&#8217;m using a browser with HTTPS. Of course, you can decrypt any other TLS traffic with Wireshark, as long as you have the session keys. However, in most of my daily business scenarios, decrypting HTTPS is the most relevant.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetroo-data-diode" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRoo.1208x232.webp" /></a></div>
<p><strong>You have to set the SSLKEYLOGFILE variable, which then creates a file with the session keys.</strong> No admin privileges are needed for this step. After that, open your browser of choice and start surfing. In my example, I opened my fairly simple website at<a href="https://ip.webernetz.net" target="_blank" rel="noopener"> https://ip.webernetz.ne</a>t.</p><pre class="urvanov-syntax-highlighter-plain-tag">set SSLKEYLOGFILE=%USERPROFILE%\sslkeys.log
start firefox</pre><p>
(For some reason, various variables/fields are still named &#8220;SSL&#8221; rather than &#8220;TLS&#8221;.)</p>
<p>At the start of the browser, many different HTTPS sessions are already initiated by the browser itself. That is: The sslkeys.log is kind of crowded. Be aware that it contains any session keys since your start. Keep them to yourself!</p>
<p>In my sample, I copied only the relevant session keys for my single session. Those can be <strong>correlated by the &#8220;Random&#8221; value within the client TLS hello</strong>, field 
			<span id="urvanov-syntax-highlighter-6af179c33165f582191082" class="urvanov-syntax-highlighter-syntax urvanov-syntax-highlighter-syntax-inline  crayon-theme-classic crayon-theme-classic-inline urvanov-syntax-highlighter-font-monaco" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important;"><span class="crayon-pre urvanov-syntax-highlighter-code" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important; -moz-tab-size:4; -o-tab-size:4; -webkit-tab-size:4; tab-size:4;">tls.handshake.random</span></span> in Wireshark. Different lines are present in the file, such as CLIENT_HANDSHAKE_TRAFFIC_SECRET, SERVER_HANDSHAKE_TRAFFIC_SECRET, CLIENT_TRAFFIC_SECRET_0, SERVER_TRAFFIC_SECRET_0, EXPORTER_SECRET. My sample keys are:</p><pre class="urvanov-syntax-highlighter-plain-tag">CLIENT_HANDSHAKE_TRAFFIC_SECRET 24a0ba3ed6a030ec8e3dfaaf467fedf990caa19957f92d05a2a424a8a7ec0373 afd7382d4e2250b87110fea5381e69e557d4203aab16992d4b79c2b3a54bb6a4
SERVER_HANDSHAKE_TRAFFIC_SECRET 24a0ba3ed6a030ec8e3dfaaf467fedf990caa19957f92d05a2a424a8a7ec0373 7d4920ba247e0ce9eb43bd5f2bede6e015711131fc2a943e578a8ce260f38579
CLIENT_TRAFFIC_SECRET_0 24a0ba3ed6a030ec8e3dfaaf467fedf990caa19957f92d05a2a424a8a7ec0373 68b953f99d56afffb8bcdfbe8e14fa00a7da5a3df0fee6c6ed6efd20317acf9b
SERVER_TRAFFIC_SECRET_0 24a0ba3ed6a030ec8e3dfaaf467fedf990caa19957f92d05a2a424a8a7ec0373 9833238deb0bc979f8d2384da9c318297ae89b95cd88cfed1cf6dd27ba3f3873
EXPORTER_SECRET 24a0ba3ed6a030ec8e3dfaaf467fedf990caa19957f92d05a2a424a8a7ec0373 7b95217e262cb72a82241da2785d647ea4336215f9573b9a4fc657d05e91ee84</pre><p>
<h2>Decryption, Please!</h2>
<p>Now, within Wireshark, go to Edit -&gt; Preferences -&gt; Protocols -&gt; TLS and select your sslkey.log file at the &#8220;(Pre)-Master-Secret log filename&#8221;:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-01-Protocols-TLS-sslkeys.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14289" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-01-Protocols-TLS-sslkeys-1024x754.png" alt="" width="604" height="445" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-01-Protocols-TLS-sslkeys-1024x754.png 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-01-Protocols-TLS-sslkeys-300x221.png 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-01-Protocols-TLS-sslkeys-768x566.png 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-01-Protocols-TLS-sslkeys-1536x1131.png 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-01-Protocols-TLS-sslkeys.png 1955w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>After hitting OK, <strong>Wireshark will decrypt all applicable TLS sessions directly</strong>. The following screenshot shows the original (encrypted) PCAP on the left-hand side, while the decrypted traffic on the right-hand side. While the original TLS traffic shows only &#8220;Application Data&#8221;, which is de facto random data, the decrypted part shows the actual protocol, an HTTP GET in this scenario:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-02-Decrypted-Traffic-scaled.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14290" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-02-Decrypted-Traffic-1024x609.png" alt="" width="604" height="359" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-02-Decrypted-Traffic-1024x609.png 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-02-Decrypted-Traffic-300x178.png 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-02-Decrypted-Traffic-768x457.png 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-02-Decrypted-Traffic-1536x913.png 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-02-Decrypted-Traffic-2048x1218.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>On the Packet Bytes section (bottom right), you can switch between the original Packet vs. the Decrypted TLS view:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-03-switch-between-Packet-or-Decrypted-TLS-scaled.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14291" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-03-switch-between-Packet-or-Decrypted-TLS-1024x609.png" alt="" width="604" height="359" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-03-switch-between-Packet-or-Decrypted-TLS-1024x609.png 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-03-switch-between-Packet-or-Decrypted-TLS-300x178.png 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-03-switch-between-Packet-or-Decrypted-TLS-768x457.png 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-03-switch-between-Packet-or-Decrypted-TLS-1536x913.png 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-03-switch-between-Packet-or-Decrypted-TLS-2048x1218.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>If you want to distribute the PCAP *with* the session keys, you can <strong>inject them into the capture file</strong>, which then turns into a *.pcapng file format: Edit -&gt; Inject TLS Secrets:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-04-Inject-TLS-Secrets.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14292" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-04-Inject-TLS-Secrets-1024x818.png" alt="" width="604" height="482" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-04-Inject-TLS-Secrets-1024x818.png 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-04-Inject-TLS-Secrets-300x240.png 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-04-Inject-TLS-Secrets-768x613.png 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-04-Inject-TLS-Secrets-1536x1226.png 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-04-Inject-TLS-Secrets.png 2000w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<h2>Sample in the Ultimate PCAP</h2>
<p>The sample of HTTPS traffic shown here, including the injected TLS keys, is part of the <a href="https://weberblog.net/the-ultimate-pcap/">Ultimate PCAP</a>. Please download and analyse it by yourself &#8211; the display filter to find those packets could be: 
			<span id="urvanov-syntax-highlighter-6af179c331663713007747" class="urvanov-syntax-highlighter-syntax urvanov-syntax-highlighter-syntax-inline  crayon-theme-classic crayon-theme-classic-inline urvanov-syntax-highlighter-font-monaco" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important;"><span class="crayon-pre urvanov-syntax-highlighter-code" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important; -moz-tab-size:4; -o-tab-size:4; -webkit-tab-size:4; tab-size:4;">http and tcp.port eq 443</span></span>.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetroo-data-diode" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRoo.1208x232.webp" /></a></div>
<h2>Follow {HTTP|TCP|TLS} Stream</h2>
<p>Note the differences between the three &#8220;Follow &#8230;&#8221; methods. The well-known &#8220;<strong>Follow TCP Stream</strong>&#8221; will still show the encrypted data:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-05-Follow-TCP-Stream.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14294" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-05-Follow-TCP-Stream-1024x736.png" alt="" width="604" height="434" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-05-Follow-TCP-Stream-1024x736.png 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-05-Follow-TCP-Stream-300x216.png 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-05-Follow-TCP-Stream-768x552.png 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-05-Follow-TCP-Stream-1536x1103.png 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-05-Follow-TCP-Stream-2048x1471.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>while the &#8220;<strong>Follow TLS Stream</strong>&#8221; shows the <strong>DEcrypted data</strong>, but still with the HTTP Content-Encoding such as gzip. Hence: still not completely readable (though decrypted):</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-06-Follow-TLS-Stream.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14295" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-06-Follow-TLS-Stream-1024x735.png" alt="" width="604" height="434" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-06-Follow-TLS-Stream-1024x735.png 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-06-Follow-TLS-Stream-300x215.png 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-06-Follow-TLS-Stream-768x551.png 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-06-Follow-TLS-Stream-1536x1103.png 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-06-Follow-TLS-Stream-2048x1471.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>Finally, the &#8220;<strong>Follow HTTP Stream</strong>&#8220;, when clicked on an HTTP packet (rather than on a mere TCP packet), brings us readable plain-text HTTP completely:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-07-Follow-HTTP-Stream.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14296" src="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-07-Follow-HTTP-Stream-1024x735.png" alt="" width="604" height="434" srcset="https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-07-Follow-HTTP-Stream-1024x735.png 1024w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-07-Follow-HTTP-Stream-300x215.png 300w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-07-Follow-HTTP-Stream-768x551.png 768w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-07-Follow-HTTP-Stream-1536x1103.png 1536w, https://weberblog.net/wp-content/uploads/2026/03/Decrypting-TLS-with-Wireshark-07-Follow-HTTP-Stream-2048x1471.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>That&#8217;s it. Happy decrypting. ;)</p>
<h2>Further Reading/Watching</h2>
<ul>
<li>YouTube David Bombal &amp; Chris Greer: <a href="https://www.youtube.com/watch?v=yodDbgoCnLM" target="_blank" rel="noopener">Decrypting TLS, HTTP/2 and QUIC with Wireshark</a></li>
<li>&#8220;<a href="https://lekensteyn.nl/files/wireshark-ssl-tls-decryption-secrets-sharkfest18eu.pdf" target="_blank" rel="noopener">SSL/TLS decryption: uncovering secrets</a>&#8221; presentation by Peter Wu, at <a href="https://sharkfest.wireshark.org/retrospective/sfeu/sf18eu/" target="_blank" rel="noopener">SharkFest’18 EUROPE</a>, the Wireshark Developer and User Conference</li>
<li>Palo Alto Networks: <a href="https://unit42.paloaltonetworks.com/wireshark-tutorial-decrypting-https-traffic/" target="_blank" rel="noopener">Wireshark Tutorial: Decrypting HTTPS Traffic</a></li>
<li>Netresec: <a href="https://www.netresec.com/?page=Blog&amp;month=2024-08&amp;post=How-to-Inspect-TLS-Encrypted-Traffic" target="_blank" rel="noopener">How to Inspect TLS Encrypted Traffic</a> (please note the table that lists various types of keys and configurations needed)</li>
</ul>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@markusspiske?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/photos/matrix-movie-still-iar-afB0QQw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/decrypting-tls-with-wireshark/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14278</post-id>	</item>
		<item>
		<title>Introducing FortiNite: Fortinet’s Low‑Latency Power‑Up for Fortnite</title>
		<link>https://weberblog.net/introducing-fortinite-fortinets-low-latency-power-up-for-fortnite/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=introducing-fortinite-fortinets-low-latency-power-up-for-fortnite</link>
					<comments>https://weberblog.net/introducing-fortinite-fortinets-low-latency-power-up-for-fortnite/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Wed, 01 Apr 2026 07:11:36 +0000</pubDate>
				<category><![CDATA[Bandwidth/Delay]]></category>
		<category><![CDATA[Fortinet]]></category>
		<category><![CDATA[Acceleration]]></category>
		<category><![CDATA[April 1st]]></category>
		<category><![CDATA[Fortnite]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[Latency]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14300</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />After years of customers confusing Fortinet with Fortnite, the two companies finally decided to lean into the chaos. The result: FortiNite — a joint innovation designed to deliver “next‑gen latency acceleration” for Fortnite players worldwide, a groundbreaking collaboration with Epic Games’ Fortnite. For years, support teams across the globe have endured phrases like “I can’t &#8230; <a href="https://weberblog.net/introducing-fortinite-fortinets-low-latency-power-up-for-fortnite/" class="more-link">Continue reading <span class="screen-reader-text">Introducing FortiNite: Fortinet’s Low‑Latency Power‑Up for Fortnite</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2026/03/Introducing-FortiNite-Fortinets-Low‑Latency-Power‑Up-for-Fortnite-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>After years of customers confusing Fortinet with Fortnite, the two companies finally decided to lean into the chaos. The result: <strong>FortiNite</strong> — a joint innovation designed to deliver <strong>“next‑gen latency acceleration” for Fortnite players</strong> worldwide, a groundbreaking collaboration with Epic Games’ Fortnite.</p>
<p><span id="more-14300"></span></p>
<p>For years, support teams across the globe have endured phrases like “I can’t reach my Fortnite firewall” or “Is the Fortinet battle pass included?” Eventually, both companies realised:</p>
<div class="su-quote su-quote-style-default"><div class="su-quote-inner su-u-clearfix su-u-trim">“If people keep mixing us up anyway… why not build something together?”</div></div>
<h2>What is FortiNite?</h2>
<p>FortiNite is marketed as a “<em>next‑generation, AI‑enhanced, cloud‑based latency reduction infrastructure accelerator</em>”.</p>
<p>In plain English: <strong>FortiNite makes Fortnite faster. Much faster.</strong></p>
<p>Leveraging Fortinet’s global Security Fabric and Epic’s galaxy of servers full of excited players, FortiNite promises:</p>
<p><strong>🚀 Sub‑millisecond latency boosts</strong><br />
<strong>🔐 Ultra‑secure, accelerated gameplay tunnels</strong><br />
<strong>🎯 Skill‑based match acceleration mode</strong><br />
<strong>⚡ Adaptive Lag Prevention (ALP™)</strong><br />
<strong>🛡️ Anti‑Tilt Protection — because lag is the #1 cause of dramatic headset slams</strong></p>
<p>Early internal benchmarks claim that FortiNite grants players “the equivalent of three additional shotgun reaction windows.”</p>
<p>Scientific? No.<br />
Convenient? Absolutely.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetowl-suricata-ids-basiertes-hochleistungs-nsm" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketOwl.1208x232.webp" /></a></div>
<h2>Now with Full IPv6 Turbo Mode</h2>
<p>One of FortiNite’s most celebrated features is its <strong>exclusive IPv6 Performance Pipeline</strong>.</p>
<p>Because while many ISPs still treat IPv6 like an optional DLC, FortiNite elevates it to its rightful place: the <strong>ultimate low‑latency gaming protocol (ULLGP)</strong>.</p>
<p>FortiNite takes advantage of:</p>
<p>✨ <strong>Direct end‑to‑end IPv6 paths</strong> with fewer NAT dragons to slay<br />
🚫 <strong>Zero NAT traversal</strong> — because NAT clearly stands for “Not Actually Tactical”<br />
📈 <strong>Reduced congestion</strong>, thanks to IPv6 lanes that nobody else uses<br />
💡 <strong>SmartFlow6™</strong> — an AI engine that automatically reroutes packets away from congested IPv4 players (also known as “the lagging mortals”)</p>
<p>Fortinet humorously noted in their launch statement:</p>
<div class="su-quote su-quote-style-default"><div class="su-quote-inner su-u-clearfix su-u-trim">“IPv4 players will still see improvements, but FortiNite truly shines on IPv6 — like switching from a shopping cart to a sports car.”</div></div>
<p>Epic Games added:</p>
<div class="su-quote su-quote-style-default"><div class="su-quote-inner su-u-clearfix su-u-trim">“We didn’t know IPv6 could be fun until now.”</div></div>
<h2>Integration with Existing Fortinet Products</h2>
<p>True to the Forti‑ecosystem approach, FortiNite integrates seamlessly:</p>
<ul>
<li><strong>FortiGate</strong>: Lights up in a “Victory Royale” pattern when latency dips below 5 ms</li>
<li><strong>FortiAnalyzer</strong>: Offers dashboards correlating your K/D ratio with packet‑loss spikes</li>
<li><strong>FortiManager</strong>: Lets admins distribute “No‑Build Mode” across entire VLANs</li>
<li><strong>FortiAP</strong>: Features a stealth SSID named <em>SweatyLobby_5Ghz</em> for peak tactical advantage</li>
</ul>
<p>These features are, of course, “in beta” — a phrase which here means “completely fictional”.</p>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@elladon?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">ELLA DON</a> on <a href="https://unsplash.com/photos/a-person-working-on-a-computer-in-a-dark-room-pjhYzDw0HWM?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/introducing-fortinite-fortinets-low-latency-power-up-for-fortnite/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14300</post-id>	</item>
		<item>
		<title>Protocol Independent Multicast (PIM) Capture</title>
		<link>https://weberblog.net/protocol-independent-multicast-pim-capture/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=protocol-independent-multicast-pim-capture</link>
					<comments>https://weberblog.net/protocol-independent-multicast-pim-capture/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Wed, 18 Mar 2026 11:55:47 +0000</pubDate>
				<category><![CDATA[Routing]]></category>
		<category><![CDATA[Cisco Router]]></category>
		<category><![CDATA[ffmpeg]]></category>
		<category><![CDATA[IGMP]]></category>
		<category><![CDATA[IPv6]]></category>
		<category><![CDATA[MLD]]></category>
		<category><![CDATA[Multicast]]></category>
		<category><![CDATA[PIM]]></category>
		<category><![CDATA[ProfiShark]]></category>
		<category><![CDATA[Raspberry Pi]]></category>
		<category><![CDATA[Ultimate PCAP]]></category>
		<category><![CDATA[VLC]]></category>
		<category><![CDATA[Wireshark]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14023</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />You never stop learning. One topic that hadn’t crossed my path in the past decade is: Multicast. Whew. Alongside all the technical literature, online presentations, and various blog posts, I decided to approach it the classic way &#8211; through packet captures. ;) So here’s a new part of the #UltimatePCAP, which contains quite a bit &#8230; <a href="https://weberblog.net/protocol-independent-multicast-pim-capture/" class="more-link">Continue reading <span class="screen-reader-text">Protocol Independent Multicast (PIM) Capture</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2025/11/Protocol-Independent-Multicast-PIM-Capture-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>You never stop learning. One topic that hadn’t crossed my path in the past decade is: <strong>Multicast</strong>. Whew. Alongside all the technical literature, online presentations, and various blog posts, I decided to approach it the classic way &#8211; through packet captures. ;)</p>
<p>So here’s a new part of the <a href="https://weberblog.net/the-ultimate-pcap/">#UltimatePCAP</a>, which contains quite a bit of <strong>PIM traffic</strong>, including Hello, Join/Prune, Register (via unicast!), and more. Of course, for IPv6 and legacy IP (IPv4). Let&#8217;s have a look:</p>
<p><span id="more-14023"></span></p>
<p>Please note that I&#8217;m *not* a multicast expert. Luckily, there are many good resources out there. I recommend this Cisco Live presentation from Aleksandar Sofranic (YouTube): <a href="https://www.youtube.com/watch?v=UEmmEMzPn6Q" target="_blank" rel="noopener">IP Multicast Introduction and Troubleshooting</a>, or this (partially free) <a href="https://networklessons.com/multicast" target="_blank" rel="noopener">multicast course on NetworkLessons.com</a>, or <a href="https://blog.golle.org/posts/Multicast/Intro" target="_blank" rel="noopener">this blog post series from Emil Boklund</a>.</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetroo-data-diode" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRoo.1208x232.webp" /></a></div>
<h2>Lab Setup</h2>
<p>This is my lab, consisting of <strong>2x Cisco router 2811</strong> with <strong>IOS version 15.1(4)M12a</strong> and <strong>1x Palo Alto Networks firewall PA-440</strong> with <strong>PAN-OS 11.1.10-h1</strong> (which only supports legacy IP for multicast, not IPv6). Everything is routed via OSPF/OSPFv3, while PIM is used for multicast traffic. The rendezvous point (RP) is statically configured on R1&#8217;s loopback address. A Raspberry Pi on the right-hand side is offering a multicast stream. Three clients are placed in the lab to receive the streams. The capture point was between the routers R1 and R2, leveraging a real TAP, namely the <a href="https://weberblog.net/my-network-companion-the-profishark/">ProfiShark</a> from Profitap.</p>
<p><a href="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Lab.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14045" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Lab-1024x616.png" alt="" width="604" height="363" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Lab-1024x616.png 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Lab-300x181.png 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Lab-768x462.png 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Lab-1536x924.png 1536w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Lab-2048x1232.png 2048w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>Raspberry Pi ffmpeg stream (thanks to <a href="https://www.reddit.com/r/networking/comments/1jppn6y/which_multicast_stream_for_testing_purposes/" target="_blank" rel="noopener">this Reddit posting</a>):</p><pre class="urvanov-syntax-highlighter-plain-tag">ffmpeg -f lavfi -re -i "testsrc=size=640x360:rate=30:decimals=2" -c:v libx264 -f mpegts "udp://239.23.11.10:1234?pkt_size=1316"</pre><p>
Similar for IPv6:</p><pre class="urvanov-syntax-highlighter-plain-tag">ffmpeg -f lavfi -re -i "testsrc=size=640x360:rate=25:decimals=2" -c:v libx264 -f mpegts "udp://[ff05::2311]:1234?pkt_size=1316"</pre><p>
The clients/receivers used VLC to play the streams via 
			<span id="urvanov-syntax-highlighter-6af179c331925234238529" class="urvanov-syntax-highlighter-syntax urvanov-syntax-highlighter-syntax-inline  crayon-theme-classic crayon-theme-classic-inline urvanov-syntax-highlighter-font-monaco" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important;"><span class="crayon-pre urvanov-syntax-highlighter-code" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important; -moz-tab-size:4; -o-tab-size:4; -webkit-tab-size:4; tab-size:4;">udp://@239.23.11.10:1234</span></span>, respectively 
			<span id="urvanov-syntax-highlighter-6af179c331927620998330" class="urvanov-syntax-highlighter-syntax urvanov-syntax-highlighter-syntax-inline  crayon-theme-classic crayon-theme-classic-inline urvanov-syntax-highlighter-font-monaco" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important;"><span class="crayon-pre urvanov-syntax-highlighter-code" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important; -moz-tab-size:4; -o-tab-size:4; -webkit-tab-size:4; tab-size:4;">udp://@[ff05::2311]:1234</span></span>.</p>
<h2>It&#8217;s Capturing Time!</h2>
<p>This was the sequence of events that I captured for <strong>IPv4</strong> on 2025-11-26. All times in UTC:</p>
<ul>
<li>15:27 &#8211; cable between R1 and R2 was plugged into/through the TAP</li>
<li>15:31 &#8211; start of ffmpeg on the Raspberry Pi, sending to 239.23.11.10 on port 1234
<ul>
<li>15:34 &#8211; client 1 starts listening to the multicast stream via VLC</li>
<li>15:36 &#8211; client 1 stopped viewing (stream is cropped in the PCAP)</li>
</ul>
</li>
<li>15:42 &#8211; stop of ffmpeg on the Raspberry Pi
<ul>
<li>15:49 &#8211; client 1 starts again, though the stream is not present anymore</li>
<li>15:50 &#8211; client 1 stops</li>
</ul>
</li>
<li>15:51 &#8211; client 2 starts VLC, though the stream is not present</li>
<li>15:53 &#8211; client 2 stops</li>
</ul>
<p>For <strong>IPv6</strong>, the following sequence was captured on 2025-12-03, all times are in UTC as well:</p>
<ul>
<li>11:07 &#8211; cable between R1 and R2 was plugged into/through the TAP</li>
<li>11:10 &#8211; start of ffmpeg on Raspi, sending to [ff05::2311]:1234
<ul>
<li>11:12 &#8211; client 3 starts listening to the multicast stream via VLC</li>
<li>11:14 &#8211; client 3 stops</li>
</ul>
</li>
<li>11:16 &#8211; stop of ffmpeg on the Raspi
<ul>
<li>11:22 &#8211; client 3 starts again, though stream not running</li>
<li>11:23 &#8211; client 3 stops</li>
</ul>
</li>
</ul>
<p>Some notes concerning the capture:</p>
<ul>
<li>I left only the beginning of the actual H.264 streams in there to keep the file as small as possible. (Can you decode them? ;))</li>
<li>Neither IGMP (for IPv4) nor MLD (for IPv6) is interesting in this capture, as I captured between the two routers R1 and R2 rather than on the source or destination subnet of the multicast stream. Hence, we&#8217;re merely looking at PIM here.</li>
<li>I don&#8217;t know why there&#8217;s PIMv1 traffic in there, since PIMv2 is the default at all.</li>
<li>For IPv4, there are some unrelated PIM joins in there, as the clients requested some other multicast groups as well.</li>
<li>Concerning IPv6, there&#8217;s a lot of ICMPv6 traffic in the capture, which relates to RS/RA, NS/NA, and MLD. I left them within the trace, as I left ARP for IPv4 there as well.</li>
</ul>
<h2>Wiresharking</h2>
<p><strong>Please download the <a href="https://weberblog.net/the-ultimate-pcap/">UltimatePCAP</a> by yourself in order to have a closer look at all those packets and sessions.</strong> The following screenshots give a rough overview, though.</p>
<p>5x for legacy IP, 5x for IPv6:</p>

<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-01-Hello.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-01-Hello-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-02-Register.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-02-Register-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-03-Register-stop.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-03-Register-stop-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-04-Join.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-04-Join-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-05-Prune.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-05-Prune-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-01-Hello.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-01-Hello-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-02-Register.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-02-Register-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-03-Register-stop.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-03-Register-stop-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-04-Join.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-04-Join-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-05-Prune.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Wireshark-PIM-IPv6-05-Prune-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>

<div style="margin-bottom:24px"><a href="https://weberblog.net/packethawk-inline-bypass-network-tap" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketHawk.1208x232.webp" /></a></div>
<h2>Shows &amp; Configurations</h2>
<p>Here are some <strong>multicast routing table outputs during the tests</strong>, all taken from <strong>R1</strong>:</p>
<p>As the stream started, but nobody was listening yet:</p><pre class="urvanov-syntax-highlighter-plain-tag">R1#show ip mroute

(*, 239.23.11.10), 00:00:25/stopped, RP 10.0.0.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(192.168.124.12, 239.23.11.10), 00:00:25/00:02:34, flags: P
Incoming interface: FastEthernet0/1, RPF nbr 10.23.0.2
Outgoing interface list: Null</pre><p>
Client 1 listens to the stream:</p><pre class="urvanov-syntax-highlighter-plain-tag">R1#show ip mroute

(*, 239.23.11.10), 00:03:46/00:03:17, RP 10.0.0.1, flags: S
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:00:16/00:03:17

(192.168.124.12, 239.23.11.10), 00:03:46/00:01:13, flags: T
  Incoming interface: FastEthernet0/1, RPF nbr 10.23.0.2
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:00:16/00:03:17</pre><p>
Stream was not present anymore, client 2 requested it:</p><pre class="urvanov-syntax-highlighter-plain-tag">R1#show ip mroute

(*, 239.23.11.10), 00:00:38/00:03:27, RP 10.0.0.1, flags: S
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    FastEthernet0/0, Forward/Sparse, 00:00:38/00:03:27</pre><p>
Same for <strong>IPv6</strong>: Stream started, no one listening yet:</p><pre class="urvanov-syntax-highlighter-plain-tag">R1#show ipv6 mroute

(2A00:6020:AD0B:83C1:E37:DC1D:6FB8:B0DC, FF05::2311), 00:00:09/00:03:20, flags: SP
  Incoming interface: FastEthernet0/1
  RPF nbr: FE80::21A:6CFF:FEA1:2B98
  Outgoing interface list: Null</pre><p>
Client 3 listens to the stream:</p><pre class="urvanov-syntax-highlighter-plain-tag">R1#show ipv6 mroute

(*, FF05::2311), 00:00:37/never, RP 2A00:6020:AD0B:8399::1, flags: SCJ
  Incoming interface: Tunnel1
  RPF nbr: 2A00:6020:AD0B:8399::1
  Immediate Outgoing interface list:
    FastEthernet0/0, Forward, 00:00:37/never

(2A00:6020:AD0B:83C1:E37:DC1D:6FB8:B0DC, FF05::2311), 00:03:14/00:03:01, flags: SJT
  Incoming interface: FastEthernet0/1
  RPF nbr: FE80::21A:6CFF:FEA1:2B98
  Inherited Outgoing interface list:
    FastEthernet0/0, Forward, 00:00:37/never</pre><p>
Stream not present anymore, client 3 requesting it nevertheless:</p><pre class="urvanov-syntax-highlighter-plain-tag">R1#show ipv6 mroute

(*, FF05::2311), 00:00:02/never, RP 2A00:6020:AD0B:8399::1, flags: SCJ
  Incoming interface: Tunnel1
  RPF nbr: 2A00:6020:AD0B:8399::1
  Immediate Outgoing interface list:
    FastEthernet0/0, Forward, 00:00:02/never</pre><p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetlion-aggregation-packet-broker" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketLion.1208x232.webp" /></a></div>
<p>For the sake of completeness, here are the configuration commands related to IP routing and multicast for both routers:</p><pre class="urvanov-syntax-highlighter-plain-tag">############
R1
############
ip cef
ip multicast-routing
ipv6 unicast-routing
ipv6 cef
ipv6 multicast-routing
!
interface Loopback0
 ip address 10.0.0.1 255.255.255.255
 ipv6 address 2A00:6020:AD0B:8399::1/128
!
interface FastEthernet0/0
 description Switch-gi1/0/39
 ip address 192.168.3.99 255.255.255.0
 ip pim sparse-mode
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 7 0331783E321E13567A053D170D175C3837
 ipv6 address 2A00:6020:AD0B:8303::99/64
 ipv6 ospf 6 area 0.0.0.0
 ipv6 ospf authentication ipsec spi 305419896 sha1 7 0327785F572B711B6B51415C35472F5A557A0D050D646D074B5F335B59750C0D0A715A563C47090A06
 bfd interval 999 min_rx 999 multiplier 3
!
interface FastEthernet0/1
 description Switch-gi1/0/40
 ip address 10.23.0.1 255.255.255.0
 ip pim sparse-mode
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 7 1422313E38151831102417273816502230
 ipv6 address 2A00:6020:AD0B:83C0::1/64
 ipv6 ospf 6 area 0.0.0.0
 bfd interval 999 min_rx 999 multiplier 3
!
router ospf 1
 router-id 10.0.0.1
 redistribute connected subnets
 network 10.23.0.0 0.0.0.255 area 0.0.0.0
 network 192.168.3.0 0.0.0.255 area 0.0.0.0
 bfd all-interfaces
!
ip pim rp-address 10.0.0.1
!
ipv6 pim rp-address 2A00:6020:AD0B:8399::1
ipv6 router ospf 6
 router-id 10.0.0.1
 bfd all-interfaces
 redistribute connected
!

############
R2
############
ip cef
ip multicast-routing
ipv6 unicast-routing
ipv6 cef
ipv6 multicast-routing
!
interface Loopback0
 ip address 10.0.0.2 255.255.255.255
 ipv6 address 2A00:6020:AD0B:8399::2/128
!
interface FastEthernet0/0
 description Switch-gi1/0/41
 ip address 10.23.0.2 255.255.255.0
 ip pim sparse-mode
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 7 133034273F1D36301F280C212F27443325
 ipv6 address 2A00:6020:AD0B:83C0::2/64
 ipv6 nd ra suppress all
 ipv6 ospf 6 area 0.0.0.0
 bfd interval 999 min_rx 999 multiplier 3
!
interface FastEthernet0/1
 description Switch-gi1/0/42
 no ip address
!
interface FastEthernet0/1.124
 description R2-Netz1
 encapsulation dot1Q 124
 ip address 192.168.124.1 255.255.255.0
 ip pim sparse-mode
 ipv6 address 2A00:6020:AD0B:83C1::1/64
!
interface FastEthernet0/1.125
 description R2-Netz2
 encapsulation dot1Q 125
 ip address 192.168.125.1 255.255.255.0
 ip pim sparse-mode
 ipv6 address 2A00:6020:AD0B:83C2::1/64
!
router ospf 1
 router-id 10.0.0.2
 redistribute connected subnets
 network 10.23.0.0 0.0.0.255 area 0.0.0.0
 bfd all-interfaces
!
ip pim rp-address 10.0.0.1
!
ipv6 pim rp-address 2A00:6020:AD0B:8399::1
ipv6 router ospf 6
 router-id 10.0.0.2
 bfd all-interfaces
 redistribute connected
!</pre><p>
&nbsp;</p>
<p>Soli Deo Gloria!</p>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@cdd20?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">愚木混株 Yumu</a> on <a href="https://unsplash.com/photos/a-group-of-red-arrows-on-a-black-surface-HQH-GOZ6K2c?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/protocol-independent-multicast-pim-capture/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14023</post-id>	</item>
		<item>
		<title>Multicast Routing w/ Palo</title>
		<link>https://weberblog.net/multicast-routing-w-palo/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=multicast-routing-w-palo</link>
					<comments>https://weberblog.net/multicast-routing-w-palo/#respond</comments>
		
		<dc:creator><![CDATA[Johannes Weber]]></dc:creator>
		<pubDate>Thu, 05 Mar 2026 14:47:19 +0000</pubDate>
				<category><![CDATA[Palo Alto Networks]]></category>
		<category><![CDATA[Routing]]></category>
		<category><![CDATA[IGMP]]></category>
		<category><![CDATA[Multicast]]></category>
		<category><![CDATA[PIM]]></category>
		<guid isPermaLink="false">https://weberblog.net/?p=14037</guid>

					<description><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" />A rare use case on a Palo (at least from my point of view): Multicast Routing. And it can become as complex as you want. Fortunately, the basics are relatively easy to configure, at least if you have a rough understanding of multicast and routing with PIM and IGMP. (Recommended YouTube session here.) Let&#8217;s have &#8230; <a href="https://weberblog.net/multicast-routing-w-palo/" class="more-link">Continue reading <span class="screen-reader-text">Multicast Routing w/ Palo</span> <span class="meta-nav">&#8594;</span></a>]]></description>
										<content:encoded><![CDATA[<img width="300" height="169" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-300x169.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="" style="display: block; margin: auto; margin-bottom: 5px;max-width: 100%;" link_thumbnail="" decoding="async" loading="lazy" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-300x169.jpg 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-1024x576.jpg 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-768x432.jpg 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image-1536x864.jpg 1536w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-featured-image.jpg 1920w" sizes="auto, (max-width: 300px) 100vw, 300px" /><p>A rare use case on a Palo (at least from my point of view): <strong>Multicast Routing</strong>. And it can become as complex as you want. Fortunately, the basics are relatively easy to configure, at least if you have a rough understanding of multicast and routing with PIM and IGMP. (<a href="https://www.youtube.com/watch?v=UEmmEMzPn6Q" target="_blank" rel="noopener">Recommended YouTube session here.</a>) Let&#8217;s have a look at the <strong>common configuration</strong> steps on PAN-OS, the needed <strong>security policies</strong> to the special destination zone type of &#8220;multicast&#8221;, as well as some <strong>&#8220;show&#8221; outputs</strong> that can be used for troubleshooting:</p>
<p><span id="more-14037"></span></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/network-traffic-tapping" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRaven.1208x232.webp" /></a></div>
<h2>The Lab</h2>
<ul>
<li>My lab consists of 3x Cisco routers (2811, IOS Version 15.1(4)M12a) and 1x PA-440 &#8220;pa-lab&#8221; with <strong>PAN-OS 11.1.10-h1</strong>, ARE enabled, hence: logical routers.</li>
<li>(Note that with <a href="https://docs.paloaltonetworks.com/pan-os/11-2/pan-os-release-notes/limitations/limitations-in-pan-os-11-2" target="_blank" rel="noopener">PAN-OS 11.2 and ARE, multicast routing is not supported at all</a>.)</li>
<li><strong>PIM-SM (sparse-mode)</strong> is used all over the lab. The rendezvous point (RP) is statically configured on R1&#8217;s loopback interface.</li>
<li>Since Palo only supports legacy IP (IPv4) with multicast, IPv6 is not of interest in this setup. 😢</li>
<li>A Raspberry Pi on the right-hand side offers a multicast stream at 239.23.11.10:1234. Accomplished by: 
			<span id="urvanov-syntax-highlighter-6af179c331c3a266049796" class="urvanov-syntax-highlighter-syntax urvanov-syntax-highlighter-syntax-inline  crayon-theme-classic crayon-theme-classic-inline urvanov-syntax-highlighter-font-monaco" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important;"><span class="crayon-pre urvanov-syntax-highlighter-code" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important; -moz-tab-size:4; -o-tab-size:4; -webkit-tab-size:4; tab-size:4;">ffmpeg -f lavfi -re -i "testsrc=size=640x360:rate=25:decimals=2" -c:v libx264 -f mpegts "udp://239.23.11.10:1234?pkt_size=1316"</span></span>.</li>
<li>The Palo serves a client subnet directly (VLAN 51, client 1 aka receiver, <strong>IGMP</strong>), and is additionally connected to another &#8220;internal&#8221; router (R3, <strong>PIM</strong>), in which another receiver (client 2) resides.</li>
</ul>
<p><a href="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-Lab-70.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14073" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-Lab-70-1024x549.png" alt="" width="604" height="324" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-Lab-70-1024x549.png 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-Lab-70-300x161.png 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-Lab-70-768x412.png 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-w-Palo-Lab-70-1536x823.png 1536w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<h2>The Config</h2>
<p>The following screenshots provide an overview of the multicast settings needed for this kind of setup. Almost all settings were left at their defaults.</p>

<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-01-enable-multicast-protocol.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-01-enable-multicast-protocol-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-02-PIM.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-02-PIM-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-03-PIM-Interfaces.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-03-PIM-Interfaces-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-04-PIM-Rendezvous-Point.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-04-PIM-Rendezvous-Point-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-05-IGMP.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-05-IGMP-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>

<p>Special attention needs to be paid to the <strong>security policies</strong>:</p>
<ul>
<li>Allowing &#8220;<strong>pim</strong>&#8221; is only necessary if another router must communicate with the RP *through* the Palo, or if the Palo itself provides the RP. If the Palo is only terminating receivers (IGMP), there&#8217;s no PIM policy needed. (I&#8217;m not fully sure why, since for other routing protocols such as OSPF or BGP, those allow rules are a must. Yes, I&#8217;ve checked an explicit intrazone-deny rule as well. Still no hits.)</li>
<li><strong>IGMP</strong> must be allowed from the receiver&#8217;s zone to the special &#8220;<strong>multicast</strong>&#8221; destination zone. Of course, destination address objects can be used to further restrict the traffic.</li>
<li>For the actual <strong>multicast traffic</strong>, in my case, a video stream on UDP port 1234, a policy has to allow this type of traffic <strong>from the multicast source</strong> (in my case: zone &#8220;transfer&#8221;) <strong>to the special &#8220;multicast&#8221; destination zone</strong>.</li>
</ul>
<p><a href="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Policies-Palo-Alto-1x.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14201" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Policies-Palo-Alto-1x-1024x443.png" alt="" width="604" height="261" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Policies-Palo-Alto-1x-1024x443.png 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Policies-Palo-Alto-1x-300x130.png 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Policies-Palo-Alto-1x-768x333.png 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Policies-Palo-Alto-1x.png 1307w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p><a href="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-06-Security-Policies.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14081" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-06-Security-Policies-1024x245.png" alt="" width="604" height="145" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-06-Security-Policies-1024x245.png 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-06-Security-Policies-300x72.png 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-06-Security-Policies-768x184.png 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-06-Security-Policies-1536x368.png 1536w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-06-Security-Policies.png 1862w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p><a href="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-07-Security-Policies-multicast-destination-zone.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14082" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-07-Security-Policies-multicast-destination-zone-1024x394.png" alt="" width="604" height="232" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-07-Security-Policies-multicast-destination-zone-1024x394.png 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-07-Security-Policies-multicast-destination-zone-300x116.png 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-07-Security-Policies-multicast-destination-zone-768x296.png 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-07-Security-Policies-multicast-destination-zone.png 1353w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/packetroo-data-diode" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRoo.1208x232.webp" /></a></div>
<h2>The Show</h2>
<p>The following screenshots and CLI outputs were taken while both receivers were consuming the stream. (Using the VLC media player with 
			<span id="urvanov-syntax-highlighter-6af179c331c3e122928212" class="urvanov-syntax-highlighter-syntax urvanov-syntax-highlighter-syntax-inline  crayon-theme-classic crayon-theme-classic-inline urvanov-syntax-highlighter-font-monaco" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important;"><span class="crayon-pre urvanov-syntax-highlighter-code" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important; -moz-tab-size:4; -o-tab-size:4; -webkit-tab-size:4; tab-size:4;">udp://@239.23.11.10:1234</span></span>.)</p>

<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-08-Multicast-FIB.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-08-Multicast-FIB-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-09-Multicast-IGMP-Interface.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-09-Multicast-IGMP-Interface-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-10-Multicast-IGMP-Membership.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-10-Multicast-IGMP-Membership-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-11-Multicast-PIM-Group-Mapping.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-11-Multicast-PIM-Group-Mapping-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-12-Multicast-PIM-Interface.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-12-Multicast-PIM-Interface-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>
<a href='https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-13-Multicast-PIM-Neighbour.png'><img loading="lazy" decoding="async" width="150" height="150" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-13-Multicast-PIM-Neighbour-150x150.png" class="attachment-thumbnail size-thumbnail" alt="" /></a>

<p><strong>Session Browser</strong> during the stream: (the IGMP session was already gone)</p>
<p><a href="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-14-Session-Browser.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14090" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-14-Session-Browser-1024x184.png" alt="" width="604" height="109" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-14-Session-Browser-1024x184.png 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-14-Session-Browser-300x54.png 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-14-Session-Browser-768x138.png 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-14-Session-Browser-1536x275.png 1536w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-14-Session-Browser.png 2014w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p><strong>Traffic Log</strong> *after* the receivers stopped consuming the stream:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-15-Traffic-Log.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14091" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-15-Traffic-Log-1024x147.png" alt="" width="604" height="87" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-15-Traffic-Log-1024x147.png 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-15-Traffic-Log-300x43.png 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-15-Traffic-Log-768x110.png 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-15-Traffic-Log-1536x221.png 1536w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-15-Traffic-Log.png 1782w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>Traffic Log for &#8220;pim&#8221;, in which router R3 contacted the RP:</p>
<p><a href="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-16-Traffic-Log-PIM.png"><img loading="lazy" decoding="async" class="aligncenter size-large wp-image-14098" src="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-16-Traffic-Log-PIM-1024x243.png" alt="" width="604" height="143" srcset="https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-16-Traffic-Log-PIM-1024x243.png 1024w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-16-Traffic-Log-PIM-300x71.png 300w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-16-Traffic-Log-PIM-768x183.png 768w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-16-Traffic-Log-PIM-1536x365.png 1536w, https://weberblog.net/wp-content/uploads/2025/12/Multicast-Routing-Palo-16-Traffic-Log-PIM.png 1939w" sizes="auto, (max-width: 604px) 100vw, 604px" /></a></p>
<p>Almost the same via the CLI show commands. One note, though: <strong>The 
			<span id="urvanov-syntax-highlighter-6af179c331c41525019459" class="urvanov-syntax-highlighter-syntax urvanov-syntax-highlighter-syntax-inline  crayon-theme-classic crayon-theme-classic-inline urvanov-syntax-highlighter-font-monaco" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important;"><span class="crayon-pre urvanov-syntax-highlighter-code" style="font-size: 12px !important; line-height: 15px !important;font-size: 12px !important; -moz-tab-size:4; -o-tab-size:4; -webkit-tab-size:4; tab-size:4;">show advanced-routing multicast pim state</span></span> command is the only one that gives an output comparable to that from the Cisco world. E.g., only this one lists the Rendezvous Point for the (*,G) groups.</strong></p><pre class="urvanov-syntax-highlighter-plain-tag">weberjoh@pa-lab&gt; show advanced-routing multicast pim neighbor

Logical router: default

Interface                               Neighbor                 Uptime    Holdtime  Generation ID       DR Pri
ethernet1/1                             192.168.3.99             44:59:56  00:01:26  1170265741          1
ethernet1/5.131                         10.23.1.2                44:59:56  00:01:44  3086112133          1


weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt; show advanced-routing multicast igmp membership group 239.23.11.10

Logical router: default

Interface                               Address             Group               Source              Mode      Timer          Src  V    Uptime    Static
ethernet1/5.51                          192.168.51.1        239.23.11.10        *                   EXCLUDE   00:02:15       1    3    00:10:35  False
Total (Interface, Groups): 1


weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt; show advanced-routing multicast route group 239.23.11.10

Flags: S - Sparse, C - Connected, P - Pruned, M - SSM, R - SGRpt Pruned, F - FHR flag, T - SPT-bit set

Logical router: default

group          source              flags     Proto     incoming            outgoing            TTL  Uptime
239.23.11.10   *                   SC        IGMP      ethernet1/1         ethernet1/5.51      1    00:11:04
                                             PIM                           ethernet1/5.131     1    00:09:16
239.23.11.10   192.168.124.12      ST        IGMP      ethernet1/1         ethernet1/5.51      1    00:11:04
                                             PIM                           ethernet1/5.131     1    00:09:16
total route shown: 2


weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt; show advanced-routing multicast fib group 239.23.11.10

Logical Router:  default

maximum of mfib entries for this mfib:  275
number of mfib entries for this mfib:   3
number of mfib entries shown:           2

group            source           flags  incoming             outgoing
-----            ------           -----  --------             --------
239.23.11.10     0.0.0.0          1      ethernet1/1          ethernet1/5.131
                                                              ethernet1/5.51
239.23.11.10     192.168.124.12   2      ethernet1/1          ethernet1/5.131
                                                              ethernet1/5.51


weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt;
weberjoh@pa-lab&gt; show advanced-routing multicast pim state group 239.23.11.10

Logical router: default

(*, G):

group               RP                  up time   upstream join  join timer     RPF interface                           RPF next hop

239.23.11.10        10.0.0.1            00:11:41  Joined         00:00:20       ethernet1/1                             192.168.3.99/32

    oil interface                           local membership    join/prune          join expire timer   prune pending timer assert st           assert timer        assert winner addr  assert winner metric
    ethernet1/5.51      LOCAL               NOINFO              --:--               --:--               NOINFO              --:--               0.0.0.0             infinity

    ethernet1/5.131     NOINFO              JOIN                02:42               --:--               NOINFO              --:--               0.0.0.0             infinity

    pimreg              N/A                 JOIN                02:42               --:--               NOINFO              --:--               0.0.0.0             infinity

(S, G):

group               source              up time   upstream nbr        upstream join  join timer     RPF next hop        DR reg    DR reg stop timer   SPT

239.23.11.10        192.168.124.12      00:11:41  192.168.3.99        Joined         00:00:20       192.168.3.99/32     RegNoInfo --:--:--            False

    oil interface                           local membership    join/prune          join expire timer   prune pending timer assert st           assert timer        assert winner addr  assert winner metric
    ethernet1/5.131     NOINFO              JOIN                02:41               --:--               NOINFO              --:--               0.0.0.0             infinity


weberjoh@pa-lab&gt;</pre><p>
Finally, this is how R3 looked like during the session:</p><pre class="urvanov-syntax-highlighter-plain-tag">R3#show ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
      P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor          Interface                Uptime/Expires    Ver   DR
Address                                                            Prio/Mode
10.23.1.1         FastEthernet0/0          1d21h/00:01:39    v2    1 / G
R3#
R3#
R3#show ip mroute 239.23.11.10
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group,
       V - RD &amp; Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.23.11.10), 01:19:52/stopped, RP 10.0.0.1, flags: SJC
  Incoming interface: FastEthernet0/0, RPF nbr 10.23.1.1
  Outgoing interface list:
    FastEthernet0/1.132, Forward/Sparse, 00:10:13/00:01:56

(192.168.124.12, 239.23.11.10), 01:19:51/00:02:34, flags: JT
  Incoming interface: FastEthernet0/0, RPF nbr 10.23.1.1
  Outgoing interface list:
    FastEthernet0/1.132, Forward/Sparse, 00:10:13/00:01:56

R3#
R3#
R3#show ip igmp groups 239.23.11.10
IGMP Connected Group Membership
Group Address    Interface                Uptime    Expires   Last Reporter   Group Accounted
239.23.11.10     FastEthernet0/1.132      00:10:33  00:02:42  192.168.132.11
R3#</pre><p>
<h2>The End</h2>
<p>Uff. ;) That&#8217;s it for now. Of course, you can configure other scenarios, such as setting the Rendezvous Point on the Palo itself or using filters for various settings. But not for me this time.</p>
<p>Soli Deo Gloria!</p>
<div style="margin-bottom:24px"><a href="https://weberblog.net/network-traffic-tapping" target="_blank" rel="noopener"><img decoding="async" class="aligncenter size-full" src="https://weberblog.net/wp-content/uploads/2026/05/Banner_PacketRaven.1208x232.webp" /></a></div>
<p><span class="text-Kvkr6N truncate-Pc_c1s textS-BC51wP">Photo by <a href="https://unsplash.com/@junscythe?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jeanson Wong</a> on <a href="https://unsplash.com/photos/lights-on-road-YRn96vHg5b8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></span>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://weberblog.net/multicast-routing-w-palo/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">14037</post-id>	</item>
	</channel>
</rss>
