https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162016-11-06T00:43:53ZpfSense bugtrackerpfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=292922016-11-06T00:43:53ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li></ul> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=293232016-11-07T14:57:09ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Confirmed</i></li><li><strong>Assignee</strong> deleted (<del><i>Jim Pingle</i></del>)</li><li><strong>Target version</strong> set to <i>Future</i></li></ul><p>Confirmed. The daemon is binding to all interfaces, which prevents the second one from operating properly.</p>
<p>Changing the dhcp6c process to use a single config and instance will require significant work to implement for little gain. At this time, a single LAN cannot utilize prefixes from both WANs until other features such as <a class="issue tracker-2 status-3 priority-4 priority-default closed" title="Feature: Allow NPt to use dynamic IPv6 networks (Resolved)" href="https://redmine.pfsense.org/issues/4881">#4881</a> are implemented. Therefore, at the moment having a second DHCPv6 WAN is of little use.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=296282016-11-28T09:04:01ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Renato Botelho</i></li></ul> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=308792017-01-25T11:08:59Z→ luckman212luke.hamburg@gmail.com
<ul></ul><p>I have a dual WAN 2.3.2-p1 system with only one of the WANs configured for DHCP6 (not PPPoE, just Ethernet) and I am hitting this issue too. Not sure if it's quite the same bug, but the end result of winding up with multiple instances of dhcp6c running (and losing v6 connectivity as a result) is the same.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=308812017-01-25T13:17:48ZMartin Wasley
<ul></ul><p>Its not, it's a problem that appears from time to time and is quite intermittent. In 2.4b changes have been made which hopefully nai!s this issue of multiple fhcp6c clients.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=308822017-01-25T13:20:08Z→ luckman212luke.hamburg@gmail.com
<ul></ul><p>Ok great, I will definitely try 2.4b then. If you happen to know which commits are relevant to that fix I'd love to look at them.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=309042017-01-26T07:46:02ZMartin Wasley
<ul></ul><p>If you update to the latest snapshot then you can try patch ID: cdb6c8ac8e65f98a2ac0fa469c963c055a5c522d</p>
<p>There are a couple of subsequent minor commits to that, but they are cosmetic and/or minor function call changes that do not affect the overall operation.</p>
<p>Try it and post back your results please.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=309052017-01-26T08:08:50Z→ luckman212luke.hamburg@gmail.com
<ul></ul><p>Thanks. I first checked out master and didn't find that commit... then drank some coffee & realized it's a PR still under review by Renato. Looks like it is ready to be merged. Will test shortly.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=309072017-01-26T10:25:33ZRenato Botelhorenato@netgate.com
<ul></ul><p>Luke Hamburg wrote:</p>
<blockquote>
<p>Thanks. I first checked out master and didn't find that commit... then drank some coffee & realized it's a PR still under review by Renato. Looks like it is ready to be merged. Will test shortly.</p>
</blockquote>
<p>PR has been merged, but there were a couple of minor problems there, fixed in <a class="changeset" title="Escape $ to avoid replacing it by PHP variables" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/31677494e659768a12d134641bbd4453d2c0a03c">31677494e659768a12d134641bbd4453d2c0a03c</a></p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=364432018-04-30T05:27:15ZDaniel Helgenberger
<ul></ul><p>Luke Hamburg wrote:</p>
<blockquote>
<p>Thanks. I first checked out master and didn't find that commit... then drank some coffee & realized it's a PR still under review by Renato. Looks like it is ready to be merged. Will test shortly.</p>
</blockquote>
<p>The comments about this commit are a little bit confusing. This is issue is still not fixed, right? (Issue is open and I am facing the same issue). I'd like to open a pull request for this one if it is not already in the works.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=375352018-08-06T14:05:10ZTony Martino
<ul></ul><p>Daniel Helgenberger wrote:</p>
<blockquote>
<p>Luke Hamburg wrote:</p>
<blockquote>
<p>Thanks. I first checked out master and didn't find that commit... then drank some coffee & realized it's a PR still under review by Renato. Looks like it is ready to be merged. Will test shortly.</p>
</blockquote>
<p>The comments about this commit are a little bit confusing. This is issue is still not fixed, right? (Issue is open and I am facing the same issue). I'd like to open a pull request for this one if it is not already in the works.</p>
</blockquote>
<p>This is not fixed. I just posted about it in the community forum (<a class="external" href="https://forum.netgate.com/topic/133538/with-multiple-ipv6-wan-connections-dhcp6c-broken">https://forum.netgate.com/topic/133538/with-multiple-ipv6-wan-connections-dhcp6c-broken</a>) and then found this report.</p>
<p>Renato, do you have an update on this? Any way I can help get this fixed?</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=379152018-08-21T08:29:42ZZachary Hill
<ul></ul><p>In a similar vein, but a bit different: it's also important to be able to have multiple <code>id-assoc pd n</code> stanzas for even a single interface. I'm aware it's a bit unorthodox, but it's supported by the daemon, and it's necessary in my network as I have AT&T UVerse residential ISP with an NVG589 router/gateway that doesn't properly support me requesting my whole /60 (or anything larger than /64) in one go, I have to separately send multiple /64 PD requests.</p>
<p>A working config for me looks like this: (generated by a functional setup on my EdgeRouter X, though I've been unsuccessful in adapting it on pfSense, something about being unable to apply the address to the desired interface)</p>
<pre><code class="text syntaxhl">interface eth0 {
send ia-na 0;
request domain-name-servers, domain-name;
send rapid-commit;
send ia-pd 0;
send ia-pd 1;
script "/opt/vyatta/sbin/ubnt-dhcp6c-script";
};
id-assoc na 0 {};
id-assoc pd 0 {
prefix ::/64 infinity;
prefix-interface eth1 {
sla-id 0;
sla-len 0;
};
};
id-assoc pd 1 {
prefix ::/64 infinity;
prefix-interface eth2 {
sla-id 0;
sla-len 0;
};
};
</code></pre>
<p>I'm not sure the currently planned fix will also cover my use-case (which I assume isn't unique) but I just wanted to add a bit of info to the conversation. I can open up another issue if this would be considered separate or unrelated.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=393732018-11-22T07:53:17ZMoritz Hartwigmori@heldenhaft.de
<ul></ul><p>I have the same issue.<br />Is there still some work on this bug?<br />Thanks!</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=402882019-03-24T12:31:48ZHolger Glemser
<ul></ul><p>What's the status here? I'm waiting for the fix, too.</p>
<p>Jim Pingle wrote:</p>
<blockquote>
<p>Changing the dhcp6c process to use a single config and instance will require significant work to implement for little gain. At this time, a single LAN cannot utilize prefixes from both WANs until other features such as <a class="issue tracker-2 status-3 priority-4 priority-default closed" title="Feature: Allow NPt to use dynamic IPv6 networks (Resolved)" href="https://redmine.pfsense.org/issues/4881">#4881</a> are implemented. Therefore, at the moment having a second DHCPv6 WAN is of little use.</p>
</blockquote>
<p>I cannot agree with the "of little use" part. I have multiple (V)LANs and want to distribute them between my two WANs, i.e. have some configured to track WAN1 and some to track WAN2 which is easily configurable in the UI in the "Track IPv6 Interface" section of the interface configuration. However, this bug causes this not to work.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=468882020-06-20T13:35:05ZCar F
<ul></ul><p>I have the same problem with 2.4.5-p1. Still no fix?</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=492982020-11-07T17:08:06ZKris Phillips
<ul></ul><p>Confirmation that issue is still present in 2.4.5p1.</p>
<p>Log messages:<br />dhcp6c 4633 Sending Solicit<br />dhcp6c 38399 unexpected interface (1)</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=495002020-11-15T17:07:00ZRandy Cross
<ul></ul><p>I'm running into the same issue</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=495442020-11-16T20:27:42ZCaleb Cargescaleb@calebcarges.info
<ul></ul><p>Just ran into this and <a class="issue tracker-2 status-3 priority-4 priority-default closed" title="Feature: Allow NPt to use dynamic IPv6 networks (Resolved)" href="https://redmine.pfsense.org/issues/4881">#4881</a> now that our backup ISP also has native v6. Looks like I'll have to work around it by hand for now when in a pinch, by setting that interface to DHCPv6 and configuring NPt specifically when the backup is needed.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=495452020-11-17T04:41:03ZTobias Meyer
<ul></ul><p>We too see this issue. Two upstream DHCP6 lines. The confusing thing is, this works <strong>somehow</strong>, but with intermittent problems. The order in which the pppoe connection and the cable line are started seem to make a difference.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=505312021-01-25T11:44:46ZTobias H
<ul></ul><p>Yes, still there :(</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=518772021-03-03T02:57:04ZCar F
<ul></ul><p>This issue still isn't fixed with 2.5.0.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=526782021-03-25T02:53:54ZCar F
<ul></ul><p>Issue is getting worse with 2.5.1-RC. This is unacceptable!</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=539292021-05-21T15:12:03ZFlole Systems
<ul></ul><p>I am using this dirty fix (plus a manually generated config file specified for both interfaces in the Webinterfaces), my interfaces are hardcoded in the patch (eth10 and eth11):</p>
<pre><code class="diff syntaxhl"><span class="gd">--- /etc/inc/interfaces.inc
</span><span class="gi">+++ /etc/inc/interfaces.inc
</span><span class="p">@@ -3904,8 +3904,8 @@</span>
function find_dhcp6c_process($interface) {
global $g;
- if ($interface && isvalidpid("{$g['varrun_path']}/dhcp6c_{$interface}.pid")) {
<span class="gd">- $pid = trim(file_get_contents("{$g['varrun_path']}/dhcp6c_{$interface}.pid"), " \n");
</span><span class="gi">+ if ($interface && isvalidpid("{$g['varrun_path']}/dhcp6c.pid")) {
+ $pid = trim(file_get_contents("{$g['varrun_path']}/dhcp6c.pid"), " \n");
</span> } else {
return(false);
}
<span class="p">@@ -3966,8 +3966,8 @@</span>
$i++;
}
/* Clear the RTSOLD script created lock & tidy up */
<span class="gd">- unlink_if_exists("/tmp/dhcp6c_{$interface}_lock");
- unlink_if_exists("{$g['varrun_path']}/dhcp6c_{$interface}.pid"); // just in case!
</span><span class="gi">+ unlink_if_exists("/tmp/dhcp6c_lock");
+ unlink_if_exists("{$g['varrun_path']}/dhcp6c.pid"); // just in case!
</span> }
function reset_dhcp6client_process($interface) {
@@ -3993,15 +3993,15 @@
* lock deleted.
*/
- if (!file_exists("/tmp/dhcp6c_{$interface}_lock")) {
<span class="gi">+ if (!file_exists("/tmp/dhcp6c_lock")) {
</span> kill_dhcp6client_process($interface, true);
/* Lock it to avoid multiple runs */
<span class="gd">- touch("/tmp/dhcp6c_{$interface}_lock");
</span><span class="gi">+ touch("/tmp/dhcp6c_lock");
</span> mwexec("/usr/local/sbin/dhcp6c {$debugOption} " .
"{$noreleaseOption} " .
"-c {$g['varetc_path']}/dhcp6c_{$interface_name}.conf " .
<span class="gd">- "-p {$g['varrun_path']}/dhcp6c_{$interface}.pid " .
- $interface);
</span><span class="gi">+ "-p {$g['varrun_path']}/dhcp6c.pid " .
+ "eth10 eth11");
</span> log_error(sprintf(gettext(
"Starting dhcp6 client for interface wan %s in DHCP6 without RA mode"),
$interface));
<span class="p">@@ -5021,7 +5021,6 @@</span>
$dhcp6cscriptwithoutra .= "echo \$dreason > /tmp/{$wanif}_reason\n";
$dhcp6cscriptwithoutra .= "case \$REASON in\n";
$dhcp6cscriptwithoutra .= "REQUEST)\n";
<span class="gd">- $dhcp6cscriptwithoutra .= "/bin/sleep 2\n";
</span> $dhcp6cscriptwithoutra .= "/usr/sbin/rtsold -1 -p {$g['varrun_path']}/rtsold_{$wanif}.pid -M {$g['varetc_path']}/rtsold_{$wanif}_script.sh -O {$g['varetc_path']}/rtsold_{$wanif}_script.sh {$wanif}\n";
if ($debugOption == '-D') {
$dhcp6cscriptwithoutra .= "/usr/bin/logger -t dhcp6c \"dhcp6c REQUEST on {$wanif} - running rtsold\"\n";
<span class="p">@@ -5188,7 +5187,7 @@</span>
*
* Taking the interface down or releasing will kill the client.
*/
<span class="gd">- if (!file_exists("/tmp/dhcp6c_{$wanif}_lock"))
</span><span class="gi">+ if (!file_exists("/tmp/dhcp6c_lock"))
</span> {
/*
* If the interface is being brought up, wait for the
</code></pre>
<p>This may not work for everyone but for me it work's and that's whats important to me.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=556482021-08-11T11:33:56ZViktor Gurov
<ul></ul><p>fix:<br /><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/336">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/336</a></p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=569432021-10-25T18:21:02ZFlole Systems
<ul></ul><p>Has the fix been merged yet? What's the current status? Can we set the target version appropriately as there is now a PR pending so it should be merged soon-ish?</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=579292021-12-21T07:15:03ZJim Pingle
<ul><li><strong>Target version</strong> changed from <i>Future</i> to <i>CE-Next</i></li><li><strong>Plus Target Version</strong> set to <i>22.05</i></li></ul> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=579302021-12-21T07:15:09ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Confirmed</i> to <i>Pull Request Review</i></li></ul> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=579362021-12-21T08:47:14ZRenato Botelhorenato@netgate.com
<ul><li><strong>Assignee</strong> changed from <i>Renato Botelho</i> to <i>Viktor Gurov</i></li></ul> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=591012022-02-17T11:15:09ZViktor Gurov
<ul><li><strong>Status</strong> changed from <i>Pull Request Review</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Multiple DHCP6 WAN connections. Fixes #6880" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/dd3d48af87c892a070210f0064e589157868e7c2">dd3d48af87c892a070210f0064e589157868e7c2</a>.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=591232022-02-18T05:39:16ZViktor Gurov
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-4 priority-default" href="/issues/12823">Bug #12823</a>: Multiple DHCP6 WAN connections PPPoE interface 'defached' status</i> added</li></ul> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=593232022-02-24T12:26:28ZJim Pingle
<ul><li><strong>Target version</strong> changed from <i>CE-Next</i> to <i>2.7.0</i></li></ul> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=616512022-06-02T20:02:14ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>This looks excellent on the latest snapshot.</p>
<p>On 22.01 each interface has a separate configuration and only one of the interfaces obtains an address.</p>
<p>On 22.05 there is a single combined configuration file, both interfaces get an address, both have online/working gateways, I can ping upstream on both from the firewall itself and from delegated prefixes from both WANs.</p>
<p>Renato mentioned there may still be a lingering issue if both WANs are PPPoE but that can be handled in a separate Redmine issue for a future release. The multiple DHCP6 case appears to be working perfectly now.</p> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=617202022-06-06T14:58:44ZJim Pingle
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-3 priority-4 priority-default closed" href="/issues/13253">Bug #13253</a>: ``dhcp6c`` is not restarted when applying settings when multiple WANs are configured for DHCP6</i> added</li></ul> pfSense - Bug #6880: Multiple DHCP6 WAN connections leads to multiple dhcp6c clientshttps://redmine.pfsense.org/issues/6880?journal_id=621612022-07-11T18:34:09ZJim Pingle
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-1 status-11 priority-4 priority-default closed" href="/issues/13353">Bug #13353</a>: DHCPv6 (still) doesn't work properly with multiple interfaces</i> added</li></ul>