pfSense

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.

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.

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.

If you update to the latest snapshot then you can try patch ID: cdb6c8ac8e65f98a2ac0fa469c963c055a5c522d

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.

Try it and post back your results please.

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.

Luke Hamburg wrote:

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.

PR has been merged, but there were a couple of minor problems there, fixed in 31677494e659768a12d134641bbd4453d2c0a03c

Luke Hamburg wrote:

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.

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.

Daniel Helgenberger wrote:

Luke Hamburg wrote:

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.

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.

This is not fixed. I just posted about it in the community forum (https://forum.netgate.com/topic/133538/with-multiple-ipv6-wan-connections-dhcp6c-broken) and then found this report.

Renato, do you have an update on this? Any way I can help get this fixed?

In a similar vein, but a bit different: it's also important to be able to have multiple id-assoc pd n 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.

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)

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;
        };
};

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.

I have the same issue.
Is there still some work on this bug?
Thanks!

What's the status here? I'm waiting for the fix, too.

Jim Pingle wrote:

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 #4881 are implemented. Therefore, at the moment having a second DHCPv6 WAN is of little use.

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.

I have the same problem with 2.4.5-p1. Still no fix?

Confirmation that issue is still present in 2.4.5p1.

Log messages:
dhcp6c 4633 Sending Solicit
dhcp6c 38399 unexpected interface (1)

I'm running into the same issue

Just ran into this and #4881 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.

We too see this issue. Two upstream DHCP6 lines. The confusing thing is, this works somehow, but with intermittent problems. The order in which the pppoe connection and the cable line are started seem to make a difference.

Yes, still there :(

This issue still isn't fixed with 2.5.0.

Issue is getting worse with 2.5.1-RC. This is unacceptable!

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):

--- /etc/inc/interfaces.inc
+++ /etc/inc/interfaces.inc
@@ -3904,8 +3904,8 @@
 function find_dhcp6c_process($interface) {
        global $g;

-       if ($interface && isvalidpid("{$g['varrun_path']}/dhcp6c_{$interface}.pid")) {
-               $pid = trim(file_get_contents("{$g['varrun_path']}/dhcp6c_{$interface}.pid"), " \n");
+       if ($interface && isvalidpid("{$g['varrun_path']}/dhcp6c.pid")) {
+               $pid = trim(file_get_contents("{$g['varrun_path']}/dhcp6c.pid"), " \n");
        } else {
                return(false);
        }
@@ -3966,8 +3966,8 @@
                $i++;
        }
        /* Clear the RTSOLD script created lock & tidy up */
-       unlink_if_exists("/tmp/dhcp6c_{$interface}_lock");
-       unlink_if_exists("{$g['varrun_path']}/dhcp6c_{$interface}.pid"); // just in case!
+       unlink_if_exists("/tmp/dhcp6c_lock");
+       unlink_if_exists("{$g['varrun_path']}/dhcp6c.pid"); // just in case!
 }
 function reset_dhcp6client_process($interface) {

@@ -3993,15 +3993,15 @@
         * lock deleted.
         */

-       if (!file_exists("/tmp/dhcp6c_{$interface}_lock")) {
+       if (!file_exists("/tmp/dhcp6c_lock")) {
                kill_dhcp6client_process($interface, true);
                /* Lock it to avoid multiple runs */
-               touch("/tmp/dhcp6c_{$interface}_lock");
+               touch("/tmp/dhcp6c_lock");
                mwexec("/usr/local/sbin/dhcp6c {$debugOption} " .
                    "{$noreleaseOption} " .
                    "-c {$g['varetc_path']}/dhcp6c_{$interface_name}.conf " .
-                   "-p {$g['varrun_path']}/dhcp6c_{$interface}.pid " .
-                   $interface);
+                   "-p {$g['varrun_path']}/dhcp6c.pid " .
+                   "eth10 eth11");
                log_error(sprintf(gettext(
                    "Starting dhcp6 client for interface wan %s in DHCP6 without RA mode"),
                    $interface));
@@ -5021,7 +5021,6 @@
        $dhcp6cscriptwithoutra .= "echo \$dreason > /tmp/{$wanif}_reason\n";
        $dhcp6cscriptwithoutra .= "case \$REASON in\n";
        $dhcp6cscriptwithoutra .= "REQUEST)\n";
-       $dhcp6cscriptwithoutra .= "/bin/sleep 2\n";
        $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";
@@ -5188,7 +5187,7 @@
                 *
                 * Taking the interface down or releasing will kill the client.
                 */
-               if (!file_exists("/tmp/dhcp6c_{$wanif}_lock"))
+               if (!file_exists("/tmp/dhcp6c_lock"))
                {
                        /*
                         * If the interface is being brought up, wait for the

This may not work for everyone but for me it work's and that's whats important to me.

fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/336

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?