https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162022-10-11T14:41:04ZpfSense bugtrackerpfSense - Bug #13473: No IPv6 address acquired after reboot/dhcp6c not startinghttps://redmine.pfsense.org/issues/13473?journal_id=632172022-10-11T14:41:04ZJim Pingle
<ul><li><strong>Plus Target Version</strong> changed from <i>22.11</i> to <i>23.01</i></li></ul> pfSense - Bug #13473: No IPv6 address acquired after reboot/dhcp6c not startinghttps://redmine.pfsense.org/issues/13473?journal_id=640142022-11-22T11:35:10ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Incomplete</i></li><li><strong>Target version</strong> deleted (<del><i>2.7.0</i></del>)</li><li><strong>Plus Target Version</strong> deleted (<del><i>23.01</i></del>)</li></ul><p>I can't reproduce anything like this with LAGG and DHCP6 on current snapshots, it's all working happily here and none of those errors are present in the logs across multiple reboots. My LAGG-based WANs obtain DHCP addresses as expected and LAGG-based LANs get their tracked delegated prefixes OK as well.</p>
<p>If there is a problem here we're going to need more info about how to reproduce it. It's possible it was corrected already in dev snapshots and that's why it's working for me, or it may be specific to your DHCP6 settings/environment.</p> pfSense - Bug #13473: No IPv6 address acquired after reboot/dhcp6c not startinghttps://redmine.pfsense.org/issues/13473?journal_id=640632022-11-27T18:43:54ZFlole Systems
<ul></ul><p>Have you tested with multiple client interfaces? As described the issue happens due to the new "single dhcpv6 client for all interfaces"-function which attempts to configure all interfaces when only the first interface is ready. So are you really using a single lagg with multiple vlans that are running dhcpv6 clients?</p> pfSense - Bug #13473: No IPv6 address acquired after reboot/dhcp6c not startinghttps://redmine.pfsense.org/issues/13473?journal_id=640642022-11-27T18:45:27ZFlole Systems
<ul></ul><p>Probably similar to <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: DHCP client can fail permanently if an interface is down at boot (Resolved)" href="https://redmine.pfsense.org/issues/13671">#13671</a></p> pfSense - Bug #13473: No IPv6 address acquired after reboot/dhcp6c not startinghttps://redmine.pfsense.org/issues/13473?journal_id=649372023-01-01T20:36:02ZFlole Systems
<ul></ul><p>Further information was provided, so this is not incomplete.</p> pfSense - Bug #13473: No IPv6 address acquired after reboot/dhcp6c not startinghttps://redmine.pfsense.org/issues/13473?journal_id=715262023-12-24T17:14:04ZMarcos M
<ul><li><strong>Status</strong> changed from <i>Incomplete</i> to <i>Duplicate</i></li></ul> pfSense - Bug #13473: No IPv6 address acquired after reboot/dhcp6c not startinghttps://redmine.pfsense.org/issues/13473?journal_id=715272023-12-24T17:14:16ZMarcos M
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-1 status-4 priority-4 priority-default" href="/issues/9453">Bug #9453</a>: Reconfiguring a parent LAGG interface breaks its VLANs</i> added</li></ul>