pfSense bugtracker: Issueshttps://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162017-12-12T02:51:54ZpfSense bugtracker
Redmine pfSense - Bug #8201 (Duplicate): 502 gateway issues Increase FPM process availability in high ram...https://redmine.pfsense.org/issues/82012017-12-12T02:51:54ZMartin Wasley
<p>To reduce chance of nginx gateway error when interacting with FPM backend, this patch does the following, starts up extra FOM server processes at startup, allows more to stay running on standby, increases automatic shutdown time from 5 seconds to one hour. On systems with a gig or more of ram.</p>
<p>PR <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: Issue building pfPort "voucher" (Rejected)" href="https://redmine.pfsense.org/issues/3881">#3881</a></p> pfSense - Bug #8200 (Resolved): Set VLAN priority on on dhcp6c packetshttps://redmine.pfsense.org/issues/82002017-12-12T02:41:58ZMartin Wasley
<p>dhcp6c packets are not being tagged with VLAN priority.</p>
<p>Pull request issued:</p>
<p>PR 3862</p> pfSense - Feature #8173 (New): dhcp6c - RAW Optionshttps://redmine.pfsense.org/issues/81732017-12-09T05:38:14ZMartin Wasley
<p>The lack of available options in dhcp6c prevents pfSense from being used with certain ISPs.</p>
<p>For example, Orange France require three options to be sent that are not currently supported in dhcp6c.</p>
<p>I have now issued a PR upstream at hrs-allbsd/wide-dhcpv6 that allows the use of the Keyword RAW as an option. Here is an example of a part of the config file when using the RAW options.</p>
<ol>
<li>User class "+FSVDSL_livebox.Internet.softathome.Livebox3";<br />send raw-option 15 00:2b:46:53:56:44:53:4c:5f:6c:69:76:65:62:6f:78:2e:49:6e:74:65:72:6e:65:74:2e:73:6f:66:74:61:74:68:6f:6d:65:2e:6c:69:76:65:62:6f:78:33;</li>
<li>Vendor class "sagem" <br />send raw-option 16 00:00:04:0e:00:05:73:61:67:65:6d;</li>
<li>Authentication<br />send raw-option 11 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:65:78:61:6d:70:6c:65;</li>
<li>IA-PD<br />send ia-pd 0;</li>
<li>Requests : authentication, domain-name, domain-name-servers;<br />send raw-option 6 00:0b:00:11:00:17:00:18;</li>
</ol>
<p>Several users have been using the modified version of dhcp6c for several months with no issues, but obliviously it would be better if the version of dhcp6c that ships with pfSense supported this 'out of the box'.</p> pfSense - Bug #8042 (Closed): VLAN Priority on dhcpc6c packets is not set. REF #7973https://redmine.pfsense.org/issues/80422017-11-01T02:40:04ZMartin Wasley
<p>Although VLAN tagging now works, it does not work for dhcp6c. <a class="user active" href="https://redmine.pfsense.org/users/10">Jim Pingle</a> suggested to @kwillers that adding a new floating rule would work, this appears not to work as a rule has already been created which takes priority over any new rule. The rule in question is as shown, created in filter inc:</p>
<p>pass out {$log['pass']} quick on \${$oc['descr']} proto udp from any port = 546 to any port = 547 tracker {$increment_tracker($tracker)} label "{$fix_rule_label("allow dhcpv6 client out {$oc['descr']}")}"</p>
<p>This is where the vlan prio must be added as this rule takes precedence. @kwillers has got it to work by modding filter.inc to add the priority on the rule shown above.</p>
<p>I have now added an entry into interfaces.php to allow the setting of a vlan priority on the above rule.</p>
<p>Before I post a PR with the changes, where do we want to put this setting? Currently I have it sat at the bottom of the dhcp6c settings in WAN, where you just enter the numeric value of the VLAN, is this way acceptable or should it done as s done in the VLAN Prio set as per the firewall rules?</p>
<p>The changes to this will still only partially fix the issues with dhcp6c and ORANGE France. In August I sent Renato an email containing patches that are required for the client to accept RAW options, this also needs to be up-streamed</p> pfSense - Bug #7920 (Not a Bug): Logos Missing and wrong sizehttps://redmine.pfsense.org/issues/79202017-10-10T02:42:28ZMartin Wasley
<p>pfSense logo is the wrong size on the login screen, appears far too large. It's missing completely from the other pages.</p> pfSense - Feature #7598 (Resolved): Static IPv6 using IPv4 PPPoE as parent interfacehttps://redmine.pfsense.org/issues/75982017-05-23T11:46:38ZMartin Wasley
<p>A strange requirement has come up. When selecting to use Static IPV6 it's not possible to specify using the PPPoE interface. There are manual methods of adding routes and adding addresses to interfaces and although this works, dpinger will not pick up the correct interface.</p>
<p>I have now got this working by adding an option in interfaces.php when selecting a static IPv6 to select to use the IPv4 connectivity link ( PPPoE ); an little code in interfaces.inc then correctly sets the interface and dpinger then works fine; I just need to add a new function to update the gateway in case that changes and it's done and dusted.</p>
<p>Would this be a useful addition to 2.4 or is it a hold off until a later version or of no use to anyone else but users of my ISP?</p> pfSense - Bug #7425 (Resolved): dhclient not sending option 77https://redmine.pfsense.org/issues/74252017-03-24T10:41:47ZMartin Wasley
<p>Not sure it's a bug, more of something missing. As reported on the forum 2.4 dhclient does not send option 77. This particularly affects customers of Orange France who need to send this optiom. I have re-applied the patches that were done to the 2.3 client, where it works, to the 2.4 client; the user on the forum reported it's working correctly.</p>
<p>Should I do a PR to the main FreeBSD repo ir PR it to pfSense/FreeBSD-Src?</p> pfSense - Bug #7202 (Resolved): "Warning: sprintf(): Too few arguments in /usr/local/www/classes/...https://redmine.pfsense.org/issues/72022017-02-03T08:10:32ZMartin Wasley
<p>Problem with changes to the setHelp function or calls to it.</p> pfSense - Bug #7185 (Resolved): DHCP6c SIGTERM, SIGKILLhttps://redmine.pfsense.org/issues/71852017-02-01T04:51:16ZMartin Wasley
<p>I have found that when issuing a SIGTERM to dhcp6c that it immediately deletes the pid file, however, if the WAN interface is down then it will continue to send release signals for at least thirty seconds. The issue here is that the call to kill the process checks to see if the process is still alive before issuing a final sigkill, as the pid has been deleted that sigkill does not get sent as dhcp6c continues on.</p>
<p>I have issued an UPSTREAM PR to correct this along with some additions.</p> pfSense - Bug #7023 (Rejected): dhclienthttps://redmine.pfsense.org/issues/70232016-12-20T06:20:56ZMartin Wasley
<p>One of my testers has a site in France, the dhclient needs to send extra options ( Orange France ). Apparently there was a dhclient someone in France compiled that worked with 2.3.2. I have said I would look at making it work in 2.4 but I cannot find the correct source. It lives in /sbin/ as far as I can tell.</p>
<p>I pulled the FreeBSD source but that compiles to a much larger size than the version currently in 2.4.</p>
<p>Can someone kindly point me in the right direction.</p> pfSense - Todo #6944 (Closed): dhcp6c releasing allocationhttps://redmine.pfsense.org/issues/69442016-11-19T12:38:35ZMartin Wasley
<p>There is a problem some users are having with dhcp6c sending a release on exit, in 99% of cases this is not an issue as the BNG will look at the DUID on the next request and give the same allocation. However, there is at least one ISP in the UK that is using a 'sticky' dynamic and the release causes the BNG to do exactly that and next time around and new range is given.</p>
<p>I have written a fix for this by adding a a no release option to the dhcp6c client, it works and has resolved the issue, Merlin has a similar fix for Asus routers.</p>
<p>For the life of me I cannot work out how to do a pull request on the FreeBSD ports to get this to be included in the main pfSense/FreeBSD-ports code.</p>
<p>I have also added an option to interfaces.inc and interfaces.php to control the 'no release' and I know how to do pull requests for those, and I will do so once the dhcp6c client has been updated.</p>
<p>Any help much appreciated...</p>