https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162016-08-16T12:50:22ZpfSense bugtrackerpfSense Packages - Bug #6721: Incorrect OpenBGPd package scripts prevent use of both IPv4 and IPv6https://redmine.pfsense.org/issues/6721?journal_id=286252016-08-16T12:50:22ZLuzemario Dantas
<ul></ul><p>Please read the title as: Incorrect OpenBGPd package scripts prevent use of both IPv4 and IPv6 - at the same time.</p> pfSense Packages - Bug #6721: Incorrect OpenBGPd package scripts prevent use of both IPv4 and IPv6https://redmine.pfsense.org/issues/6721?journal_id=286262016-08-16T13:18:06ZLuzemario Dantas
<ul></ul><p>Steps to reproduce:</p>
<p>1. Install the latest OpenBGPd package;<br />2. Enter the needed settings, adding both IPv4 and IPv6 prefixes;<br />3. Fill the other tabs with neighbor info and other settings as usual;<br />4. Save all settings;<br />5. Watch on "Raw config" the "listen-on-ip" for IPv6 settings. There is a IPv4 address there;<br />6. Click on "status" tab. The PID for BGPd is missing, indicating BGPd did not start;<br />7. On command shell, try "bgpd -d". An error message is thrown and the service does not start.</p> pfSense Packages - Bug #6721: Incorrect OpenBGPd package scripts prevent use of both IPv4 and IPv6https://redmine.pfsense.org/issues/6721?journal_id=290642016-10-12T15:22:15ZJim Pingle
<ul><li><strong>Target version</strong> deleted (<del><i>2.4.0</i></del>)</li></ul> pfSense Packages - Bug #6721: Incorrect OpenBGPd package scripts prevent use of both IPv4 and IPv6https://redmine.pfsense.org/issues/6721?journal_id=292842016-11-06T00:29:40ZJim Thompsonjim@netgate.com
<ul><li><strong>Assignee</strong> set to <i>Jim Pingle</i></li></ul> pfSense Packages - Bug #6721: Incorrect OpenBGPd package scripts prevent use of both IPv4 and IPv6https://redmine.pfsense.org/issues/6721?journal_id=293152016-11-07T11:14:46ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Patch</i></li><li><strong>Assignee</strong> changed from <i>Jim Pingle</i> to <i>Luzemario Dantas</i></li></ul><p>Unless there is a compelling need to set it to listen on two specific addresses manually, leave "Listen on IP" blank and it should listen on both IPv4 and IPv6.</p>
<p>If someone wants to test and submit a patch to do separate IPv4 and IPv6 "Listen on IP" address boxes, it wouldn't be tough to do, but it doesn't appear to be strictly necessary at this point. Using the raw config tab can easily work around it as well.</p> pfSense Packages - Bug #6721: Incorrect OpenBGPd package scripts prevent use of both IPv4 and IPv6https://redmine.pfsense.org/issues/6721?journal_id=293212016-11-07T14:21:37ZLuzemario Dantas
<ul></ul><p>Hi Jim,</p>
<p>Leaving "Listen on IP" blank makes the default IPv4 address "0.0.0.0" to be put on both IPv4 <strong>and IPv6</strong> "local-address" directives of raw config when using groups. This still prevents bgpd daemon from starting because "0.0.0.0" is a IPv4 dot-formatted address (and the daemon expects a colon formatted address when IPv6 family is used on that group).</p>
<p>A workaround for this is setting the "Local address X" extra parameter to a valid IPv6 colon-formatted address for each neighbor, so the default "local-address" for IPv6 will get this address instead of an IPv4 dot-formatted address copied from "listen on" clause.</p>
<p>We applied this here because we have several WAN links with both IPv4 and IPv6 BGP sessions established, so it was necessary to have specific "local-address" directives defined.</p>