<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[How to deal with duplicate link local when testing]]></title><description><![CDATA[<p dir="auto">Hey all,</p>
<p dir="auto">I'm trying to troubleshoot my Comcast Business setup and finally have the time. To test, I've created a VM with a 2.1.2 release assigned to the IPV6 modem and the internal LAN. On my production firewall, I've turned off IPV6.</p>
<p dir="auto">I'm getting the following on the test pfSense VM:</p>
<pre><code>kernel: em0: DAD complete for fe80:1::1:1 - duplicate found
</code></pre>
<p dir="auto">Which makes sense, since both firewalls have rewritten the link-local address to this same value.</p>
<p dir="auto">From the production firewall, where the LAN PHY is VLANed out:</p>
<pre><code>fe80::1:1%em0_vlan10
</code></pre>
<p dir="auto">And then on the test VM (just using access mode, no trunking):</p>
<pre><code>fe80::1:1%em0
</code></pre>
<p dir="auto">My guess is that pfSense rewrites the address w/o EUI-64 to make it easier to troubleshoot/test. But I'd like to know why the value is changed, as here is an example on my prod setup where I haven't attempted to "track interface":</p>
<pre><code>fe80::200:24ff:fed0:38a4%em0_vlan600
</code></pre>
<p dir="auto">So, the questions are:</p>
<ul>
<li>
<p dir="auto">Understanding why the value is written that way in the first place?</p>
</li>
<li>
<p dir="auto">Is there a way to change that value per-firewall? that way I can have both up w/o the duplicate error?</p>
</li>
<li>
<p dir="auto">Why doesn't link local get reset back to the EUI-64 value once IPv6 is removed from an interface?</p>
</li>
</ul>
<p dir="auto">Once I get past that point I'll attempt, again, to get Comcast BIS with my /56 operational. Thanks all!</p>
]]></description><link>https://forum.netgate.com/topic/67906/how-to-deal-with-duplicate-link-local-when-testing</link><generator>RSS for Node</generator><lastBuildDate>Mon, 07 Sep 2026 15:12:18 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/67906.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 13 Apr 2014 02:18:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How to deal with duplicate link local when testing on Fri, 18 Apr 2014 00:30:45 GMT]]></title><description><![CDATA[<p dir="auto">Bumping to see where I can resolve this issue. As a lark I install m0n0wall and setup IPv6 there. PD allocation worked, yet still no LAN traffic passing the local netgear modem.</p>
<p dir="auto">But when I did enabled IPv6 on the LAN interface, the link-local always stayed in EUI64 format. So just trying to figure out what portion of pfSense code is changing the link-local addresses to fe80:1::1:1, and how to revert back to SLAAC-style addresses.</p>
]]></description><link>https://forum.netgate.com/post/456128</link><guid isPermaLink="true">https://forum.netgate.com/post/456128</guid><dc:creator><![CDATA[gadams999]]></dc:creator><pubDate>Fri, 18 Apr 2014 00:30:45 GMT</pubDate></item></channel></rss>