https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162021-03-04T07:58:30ZpfSense bugtrackerpfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=519252021-03-04T07:58:30ZJim Pingle
<ul><li><strong>Subject</strong> changed from <i>vpn_wg_edit.php: Interface created with incorrect inet6 prefixlen</i> to <i>WireGuard using incorrect IPv6 tunnel address prefix length</i></li><li><strong>Target version</strong> set to <i>CE-Next</i></li></ul> pfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=521112021-03-09T13:52:21ZJim Pingle
<ul><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li><li><strong>Target version</strong> changed from <i>CE-Next</i> to <i>2.5.1</i></li></ul> pfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=521452021-03-10T09:16:46ZJim Pingle
<ul></ul><p>That's easy enough to reproduce and check:</p>
<ul>
<li>Set WG instance tunnel address to include <code>2001:db8:1:ee71::1/64</code> and confirm <code>ifconfig wg0</code> shows <code>2001:db8:1:ee71::1/64</code></li>
<li>Change tunnel address to <code>2001:db8:1:ee71::1/128</code> and <code>ifconfig wg0</code> incorrectly shows <code>2001:db8:1:ee71::1/64</code></li>
<li>Apply fix</li>
<li>Save the tunnel again with the tunnel address set to <code>2001:db8:1:ee71::1/128</code>, <code>ifconfig wg0</code> correctly shows <code>2001:db8:1:ee71::1/128</code></li>
<li>Set WG instance tunnel address back to <code>2001:db8:1:ee71::1/64</code> and confirm <code>ifconfig wg0</code> correctly shows <code>2001:db8:1:ee71::1/64</code></li>
</ul>
<p>Fix committed, will show up shortly.</p> pfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=521462021-03-10T09:20:07ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</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 commit:8579d26bfb0dea0386c61008ade222c0ea29aa98.</p> pfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=521472021-03-10T09:21:11ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Waiting on Merge</i></li></ul> pfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=521872021-03-10T13:00:24ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Waiting on Merge</i> to <i>Feedback</i></li></ul><p>Cherry-picked to RELENG_2_5_1</p> pfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=525912021-03-19T10:59:55ZJim Pingle
<ul><li><strong>Target version</strong> changed from <i>2.5.1</i> to <i>Future</i></li></ul> pfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=537972021-05-15T21:59:46ZKris Phillips
<ul></ul><p>If still relevant, should be moved to the package support for the WG package in 2.6.0. This is no longer relevant for core pfSense and pfSense Plus with WG removal.</p> pfSense Packages - Bug #11618: WireGuard using incorrect IPv6 tunnel address prefix lengthhttps://redmine.pfsense.org/issues/11618?journal_id=538072021-05-17T07:37:54ZJim Pingle
<ul><li><strong>Project</strong> changed from <i>pfSense</i> to <i>pfSense Packages</i></li><li><strong>Category</strong> changed from <i>WireGuard</i> to <i>WireGuard</i></li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li><li><strong>Assignee</strong> deleted (<del><i>Jim Pingle</i></del>)</li><li><strong>Target version</strong> deleted (<del><i>Future</i></del>)</li><li><strong>Release Notes</strong> deleted (<del><i>Default</i></del>)</li></ul><p>Can be reopened if it still applies to the package.</p>