pfSense bugtracker: Issueshttps://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162023-12-01T20:31:37ZpfSense bugtracker
Redmine pfSense Packages - Feature #15056 (New): Feature Request: Donate to Package Maintainer Button https://redmine.pfsense.org/issues/150562023-12-01T20:31:37ZJonathan Lee
<p>Maybe the packages, should have a button so donate button to send some money to maintainers. I recently learned that Snort was built with donated time. I was really confused about this. It kind of confused me.</p> pfSense - Bug #15015 (New): Static routes not workinghttps://redmine.pfsense.org/issues/150152023-11-20T17:53:07ZSilviu Bajenaru
<p>Hello,</p>
<p>This morning I updated to PFSense 2.7.1 from 2.7.0. Now, I just tried to add a dynamic gateway and a static route. Unfortunately, the static route is not being added to the routing table. I restored the VM backup from this morning, before I updated, added the same gateway and static route and it was added to the routing table, and everything works fine.<br />I've set the priority to Urgent since this is quite bad for a router...?</p>
More info about my setup: I've got three sites, let's call them A, B and C. There is an IPSec tunnel between A and B, and one between B and C. Both tunnels are set with Mode VTI. I've assigned the ipsec interfaces and set the gateways and routes:<br />Site A has a gateway set on the IPSec interface and a route for site C that uses that gateway.<br />Site B has two gateways (one for each IPSec tunnel) and the following routes:
<ul>
<li>route to site A via the IPSec interface - gateway - going to site A</li>
<li>route to site B via the IPSec interface - gateway - going to site B<br />Site C has a gateway set on the IPSec interface and a route for site A that uses that gateway.<br />Site A was updated this morning to PFSense 2.7.1, while Site C is running 2.7.0.<br />Site A DOES NOT have the static routes added to the routing table.<br />Site C does have the static routes added to the routing table.</li>
</ul>
<p>Once I reverted Site A to 2.7.0, I did the same config again and the routes were added to the routing table.</p>
<p>Thank you.</p> pfSense Packages - Feature #14941 (New): add directdomains list in GUIhttps://redmine.pfsense.org/issues/149412023-11-03T09:46:08ZClaude-Axel Piller
<p>Is it possible to add directly in the GUI a directdomains category like whitelist or blacklist ...<br />this directdomains won't use the proxy and can access directly to internet.<br />Some apps like vrchat don't work with proxy.<br />thanks</p> pfSense Packages - Feature #14838 (New): Full support for AdBlock-style listshttps://redmine.pfsense.org/issues/148382023-10-04T21:57:19ZAndre Braitandrebrait@gmail.com
<p>The AdBlock syntax allows for both blacklisting and whitelisting, as well as using wildcards and sometimes plain regular expressions. Many popular lists make use of such features. Currently, pfBlockerNG only supports parsing simple non-wildcard blacklist entries, as long as they obey the format `^[|]{2}.*[^]$`.</p>
<p>Support can be improved, especially for the Python mode.</p>
<ul>
<li>Unbound mode:
<ul>
<li>Whitelist entries with wildcards (limited)
<ul>
<li>Using grep with regexes to rule out entries from the blacklists</li>
</ul>
</li>
</ul>
</li>
<li>Python mode
<ul>
<li>Blacklist entries with wildcard support
<ul>
<li>Requires filtering 100% inside Python</li>
</ul>
</li>
<li>Whitelist entries with wildcard support
<ul>
<li>Probably better and easier if done 100% inside Python</li>
<li>Default "re" engine might be too slow, better to import "regex"</li>
</ul></li>
</ul></li>
</ul>
<p>References: <br />1. <a class="external" href="https://help.adblockplus.org/hc/en-us/articles/360062733293-How-to-write-filters">https://help.adblockplus.org/hc/en-us/articles/360062733293-How-to-write-filters</a><br />2. <a class="external" href="https://adguard.com/kb/general/ad-filtering/create-own-filters/">https://adguard.com/kb/general/ad-filtering/create-own-filters/</a></p>
<p>Some of it is already implemented in this PR: <a class="external" href="https://github.com/pfsense/FreeBSD-ports/pull/1302">https://github.com/pfsense/FreeBSD-ports/pull/1302</a></p> pfSense Packages - Regression #14764 (New): HAProxy local syslog not workinghttps://redmine.pfsense.org/issues/147642023-09-09T19:08:28ZMichael Vincent
<p>HAProxy package v0.63_1</p>
<p>Setting the syslog host to <code>/var/run/log</code> in the HAProxy settings doesn't produce any entries in the pfSense system logs.</p>
<p>Following the suggestion in <a href="https://serverfault.com/a/1141223" class="external">this post</a> fixes the issue by making syslogd listen to a UDP socket:</p>
<ol>
<li>Edit <code>/etc/defaults/rc.conf</code> (Diagnostics -> Edit File).</li>
<li>Change <code>syslogd_flags="-s"</code> to <code>syslogd_flags="-s -b localhost -C"</code></li>
<li>Restart the syslogd service (Status -> Services).</li>
</ol>
<p>They also reference this forum post with more details:<br /><a class="external" href="https://forums.freebsd.org/threads/haproxy-not-logging.76876/#post-477067">https://forums.freebsd.org/threads/haproxy-not-logging.76876/#post-477067</a></p> pfSense - Bug #14741 (New): PHP error in DNS Forwarder host overrides when the language is set to...https://redmine.pfsense.org/issues/147412023-09-02T10:26:29ZNicolas PISTER
<p>A PHP error occur when a user try to add or modify Host Override in DNS Forwarder module</p>
<pre>
amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT #1 RELENG_2_7_0-n255866-686c8d3c1f0: Wed Jun 28 04:21:19 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-CE-snapshots-2_7_0-main/obj/amd64/LwYAddCr/var/jenkins/workspace/pfSense-CE-snapshots-2_7_0-main/sources/FreeBSD-src-REL
Crash report details:
PHP Errors:
[02-Sep-2023 11:55:24 Europe/Paris] PHP Fatal error: Uncaught ValueError: Unknown format specifier "p" in /usr/local/www/classes/Form/Input.class.php:127
Stack trace:
#0 /usr/local/www/classes/Form/Input.class.php(127): sprintf('Nom de domaine ...', '<br />')
#1 /usr/local/www/services_dnsmasq_edit.php(85): Form_Input->setHelp('Domain of the h...', '<br />')
#2 {main}
thrown in /usr/local/www/classes/Form/Input.class.php on line 127
[02-Sep-2023 11:58:37 Europe/Paris] PHP Fatal error: Uncaught ValueError: Unknown format specifier "p" in /usr/local/www/classes/Form/Input.class.php:127
Stack trace:
#0 /usr/local/www/classes/Form/Input.class.php(127): sprintf('Nom de domaine ...', '<br />')
#1 /usr/local/www/services_dnsmasq_edit.php(85): Form_Input->setHelp('Domain of the h...', '<br />')
#2 {main}
thrown in /usr/local/www/classes/Form/Input.class.php on line 127
[02-Sep-2023 11:58:46 Europe/Paris] PHP Fatal error: Uncaught ValueError: Unknown format specifier "p" in /usr/local/www/classes/Form/Input.class.php:127
Stack trace:
#0 /usr/local/www/classes/Form/Input.class.php(127): sprintf('Nom de domaine ...', '<br />')
#1 /usr/local/www/services_dnsmasq_edit.php(85): Form_Input->setHelp('Domain of the h...', '<br />')
#2 {main}
thrown in /usr/local/www/classes/Form/Input.class.php on line 127
</pre>
<p>I think it come from a french translation file because when i use original language, everithing works.</p> pfSense - Bug #14397 (New): DHCPv4 client (dhclient) does not use 802.1p Priority tagging on DHCP...https://redmine.pfsense.org/issues/143972023-05-19T14:52:52ZTue Madsen
<p>Some ISPs using VLANs for service, require DHCPv4/v6 Frames to be 802.1p priority tagged. <br />pfSense has the option to do this by either:<br />- Setting VLAN priority tagging in the Interface DHCP options (if you are not using Advanced configuration or a predefined configuration file)<br />- If using advanced configuration: By adding “vlan-pcp x” in the advanced modifier options.</p>
<p>BUG:<br />This priority setting in only used in DISCOVER and RELEASE frames sent by dhclient - NOT in RENEW or REBIND.</p>
<p>This is now causing major problems in France where Orange (Major ISP) has upgraded to also requiring the RENEW frames to be properly VLAN Priority tagged.<br />This causes the uplink to stop working when a renew is due. (About once a day)</p>
<p>I don’t know if the issue is the same in DHCPv6</p>
<p>The issue was patched in OPNsense about a month ago, and they decided to drop the advanced options overwrite of the VLAN priority setting in interface DHCP options. <br />Instead they let the user choose if VLAN priority should be used via the interface DHCP VLAN Priority setting already available. <br />If selected it would - apart from adding “vlan-pcp x” to the dhclient config - also set the priority tag in the builtin pffilter rule that passes Interface DHCP client traffic. This adds the tag to RENEW and REBIND frames.</p>
<p>The issue occurs because dhclient uses a bfg interface for DISCOVER and RELEASE - thus respecting the vlan-pcp settings. But for RENEW it uses a simple socket, and that causes it not to be tagged correctly. In pfSense you cannot create a floating match rule to manually tag the traffic that has higher priority than the builtin pass quick rule for the interface DHCP client.</p> pfSense Packages - Bug #13544 (New): SquidGuard either denying everything or proxying everythinghttps://redmine.pfsense.org/issues/135442022-10-05T01:40:03ZJimmy Michaelson
<p>Hey,</p>
<p>I truly doubt this is a configuration issue as I've tried all the possible combinations.</p>
<p>Relevant images and config:</p>
<p><a class="external" href="https://forum.netgate.com/topic/175057/10-btc-bounty-squid-proxy-whitelist-per-source-ip/6">https://forum.netgate.com/topic/175057/10-btc-bounty-squid-proxy-whitelist-per-source-ip/6</a></p>
<p>FYI: The bounty has been bumped to $20 and is also valid here.</p> pfSense - Bug #9295 (New): IPv6 PD does not work with PPPOE (Server & Client)https://redmine.pfsense.org/issues/92952019-01-29T11:51:01ZDirk Steingäßer
<p>Hi,</p>
<p>as encountering DHCPv6 with Prefix delegation does not work together with PPPOE Server vice versa it is not possible to get a prefix with an interface where the IPv4 Uplink is PPPOE.</p> pfSense - Bug #8089 (New): VLAN page breaks after config restore to new hardware.https://redmine.pfsense.org/issues/80892017-11-13T11:09:13ZBridgetowermedia IT
<p>The VLAN interface page breaks after restoring a backup from devices using emX interfaces to devices using igbX interfaces.<br />This is rather problemmatic as after the page is broken the only way to fix is to re-image.<br />The work around is to remove all VLAN interfaces from the configuration before backing up and restoring.</p>
<p>When the page breaks this is the error received:<br />Fatal error: Cannot redeclare vlan_inuse() (previously declared in /usr/local/www/interfaces_vlan.php:42) in /etc/inc/interfaces.inc on line 272 Call Stack: 0.0026 231112 1. {main}() /usr/local/www/interfaces_vlan.php:0 0.0027 231616 2. require_once('/usr/local/www/guiconfig.inc') /usr/local/www/interfaces_vlan.php:33 0.0029 254168 3. require_once('/etc/inc/authgui.inc') /usr/local/www/guiconfig.inc:51 0.0029 254800 4. include_once('/etc/inc/auth.inc') /etc/inc/authgui.inc:25 0.0029 255232 5. require_once('/etc/inc/config.gui.inc') /etc/inc/auth.inc:31 0.0061 279224 6. require_once('/etc/inc/notices.inc') /etc/inc/config.gui.inc:37 0.0061 279600 7. require_once('/etc/inc/functions.inc') /etc/inc/notices.inc:24 PHP ERROR: Type: 1, File: /etc/inc/interfaces.inc, Line: 272, Message: Cannot redeclare vlan_inuse() (previously declared in /usr/local/www/interfaces_vl an.php:42)</p>
<p>You can reproduce by:</p>
<p>add vlan to 8860 interface<br />backup config<br />restore config to vmware device<br />reassign interfaces as normal.<br />backup config<br />restore to 8860<br />then try and reassign interfaces,<br />get errors about non existing vlans<br />attempt to resolve vlan issue on vlan interfaces page.</p> pfSense - Bug #7730 (New): 2.3.4_1 greX: loop detected when hit save on filter rules or interfaceshttps://redmine.pfsense.org/issues/77302017-07-27T07:16:59ZRichie M
<p>upgraded from 2.2.6<br />anytime we hit save in the GUI for interface or filter rules, even if no change was made, we start getting Jul 25 14:50:02 <histname> kernel: greX: loop detected spam in dmesg/system.log. Our GRE tunnel goes down.</p>
<p>Any cluster sync activity from the Primary to Secondary also causes this issue.</p>
<p>We have to do a save on the GRE interface in the web GUI (this downs/ups the interface) and the tunnel starts working again.</p>
<p><code><br />Jul 25 14:50:01 hostname kernel: gre0: loop detected<br />Jul 25 14:50:02 hostname kernel: gre1: loop detected<br />Jul 25 14:50:02 hostname kernel: gre0: loop detected<br />Jul 25 14:50:02 hostname kernel: gre1: loop detected<br />Jul 25 14:50:02 hostname kernel: gre0: loop detected<br />Jul 25 14:50:03 hostname kernel: gre1: loop detected<br />Jul 25 14:50:03 hostname kernel: gre0: loop detected<br />Jul 25 14:50:03 hostname kernel: gre1: loop detected<br /></code></p>
<p>Original Forum Thread: <a class="external" href="https://forum.pfsense.org/index.php?topic=134258.0">https://forum.pfsense.org/index.php?topic=134258.0</a></p> pfSense - Feature #7521 (New): Package Updates via Mirrorhttps://redmine.pfsense.org/issues/75212017-05-04T20:21:52ZMark Olliver
<p>Since the upgrade to 2.3 systems that no longer can connect to the internet directly or via a proxy can not get updates manually.</p>
<p>This is leaving internal firewalls vulnerable to potential threats, can we please have an option to mirror the Pfsense repo and thus conversely an option in the system updates menu to enter a local mirror as an override.</p>
<p>By doing this we can reinstate updates for offline systems and keep them secure.</p>
<p>Thanks</p>
<p>Mark</p> pfSense Packages - Bug #7388 (New): Suricata does not property recognize MTU for PPPOE interfaceshttps://redmine.pfsense.org/issues/73882017-03-14T21:11:57ZKristopher Kolpin
<p>Due to path MTU discovery (via ICMPv6) issues with some IPv6 TCP traffic I have to manually set MSS to 1452 in the WAN interface.</p>
<p>The Suricata detects the MTU as 1500 in this situaion. However, when MTU and MSS are left blank (i.e. pfSense auto-establishes MTU and MSS) Suricata detects MTU properly as 1492. See logs below:</p>
<p>#Manually set MTU of 1492 and MSS of 1452.<br />14/3/2017 -- 21:50:29 - <Info> -- Found an MTU of 1500 for 'pppoe0'<br />14/3/2017 -- 21:50:29 - <Info> -- Set snaplen to 1524 for 'pppoe0'</p>
<p>#MTU and MSS left blank (auto).<br />14/3/2017 -- 21:58:41 - <Info> -- Found an MTU of 1492 for 'pppoe0'<br />14/3/2017 -- 21:58:41 - <Info> -- Set snaplen to 1516 for 'pppoe0'</p> pfSense Packages - Bug #6988 (New): SNORT Package PHP memory errorhttps://redmine.pfsense.org/issues/69882016-12-06T01:57:22ZZeev Zalessky
<p>Crash report begins. Anonymous machine information:</p>
<p>amd64<br />10.3-RELEASE-p9<br />FreeBSD 10.3-RELEASE-p9 #1 5fc1b19(RELENG_2_3_2): Tue Sep 27 12:26:06 CDT 2016 root@ce23-amd64-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense</p>
<p>Crash report details:</p>
<p>PHP Errors:<br />[05-Dec-2016 11:14:18 Asia/Jerusalem] PHP Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 155312128 bytes) in /usr/local/www/snort/snort_interface_logs.php on line 84<br />[05-Dec-2016 11:14:18 Asia/Jerusalem] PHP Stack trace:<br />[05-Dec-2016 11:14:18 Asia/Jerusalem] PHP 1. {main}() /usr/local/www/snort/snort_interface_logs.php:0</p>
<p>Filename: /var/crash/minfree<br />2048</p> pfSense - Bug #5355 (New): on Dynamic WAN IP (DHCP Client) it takes 10 minutes before Phase1 reco...https://redmine.pfsense.org/issues/53552015-10-29T03:37:18ZVitali Karivitali.kari@gmail.com
<p>2.2.4-RELEASE (i386)<br />built on Sat Jul 25 19:56:41 CDT 2015<br />FreeBSD 10.1-RELEASE-p15</p>
<p>It seems that charon do not care or is being not informed after WAN IP address changes</p>
<p>it try still use the old IP address and cannot bind this.</p>
<p>i see this messages after IP adress is changed: (the XXX.XXX.180.28 is an old IP address)<br />Logs are in reverse order!</p>
<p>...<br />Oct 26 09:43:49 charon: 09[IKE] <con1000|2> sending DPD request<br />Oct 26 09:43:49 charon: 09[IKE] <con1000|2> sending DPD request<br />Oct 26 09:43:48 charon: 05[NET] error writing to socket: Can't assign requested address<br />Oct 26 09:43:48 charon: 09[NET] <con1000|3> sending packet: from XXX.XXX.180.28<sup><a href="#fn500">500</a></sup> to XXX.XXX.183.110<sup><a href="#fn500">500</a></sup> (391 bytes)<br />Oct 26 09:43:48 charon: 09[IKE] <con1000|3> sending retransmit 4 of request message ID 0, seq 1<br />Oct 26 09:43:48 charon: 09[IKE] <con1000|3> sending retransmit 4 of request message ID 0, seq 1<br />Oct 26 09:43:39 charon: 09[IKE] <con1000|2> sending DPD request<br />Oct 26 09:43:39 charon: 09[IKE] <con1000|2> sending DPD request<br />Oct 26 09:43:29 charon: 09[IKE] <con1000|2> sending DPD request<br />Oct 26 09:43:29 charon: 09[IKE] <con1000|2> sending DPD request<br />Oct 26 09:43:24 charon: 05[NET] error writing to socket: Can't assign requested address<br />Oct 26 09:43:24 charon: 09[NET] <con1000|3> sending packet: from XXX.XXX.180.28<sup><a href="#fn500">500</a></sup> to XXX.XXX.183.110<sup><a href="#fn500">500</a></sup> (391 bytes)<br />Oct 26 09:43:24 charon: 09[IKE] <con1000|3> sending retransmit 3 of request message ID 0, seq 1<br />Oct 26 09:43:24 charon: 09[IKE] <con1000|3> sending retransmit 3 of request message ID 0, seq 1<br />Oct 26 09:43:19 charon: 09[IKE] <con1000|2> sending DPD request<br />Oct 26 09:43:19 charon: 09[IKE] <con1000|2> sending DPD request<br />...</p>
<p>after i while (10 - 15 minutes) IPsec realizes that the WAN address is changed and reconnects successfully:</p>
<p>...<br />Oct 26 09:53:32 charon: 12[IKE] <con1000|4> IKE_SA con1000<sup><a href="#fn4">4</a></sup> established between XXX.XXX.180.42[XXX]...XXX.XXX.183.110[XXX.XXX.183.110]<br />Oct 26 09:53:32 charon: 12[ENC] <con1000|4> received unknown vendor ID: 69:93:69:22:87:41:c6:d4:ca:09:4c:93:e2:42:c9:de:19:e7:b7:c6:00:00:00:05:00:00:05:00<br />Oct 26 09:53:32 charon: 12[IKE] <con1000|4> received NAT-T (RFC 3947) vendor ID<br />Oct 26 09:53:32 charon: 12[IKE] <con1000|4> received NAT-T (RFC 3947) vendor ID<br />Oct 26 09:53:32 charon: 12[IKE] <con1000|4> received DPD vendor ID<br />Oct 26 09:53:32 charon: 12[IKE] <con1000|4> received DPD vendor ID<br />Oct 26 09:53:32 charon: 12[ENC] <con1000|4> parsed AGGRESSIVE response 0 [ SA KE No ID HASH V V V NAT-D NAT-D ]<br />Oct 26 09:53:32 charon: 12[NET] <con1000|4> received packet: from XXX.XXX.183.110<sup><a href="#fn500">500</a></sup> to XXX.XXX.180.42<sup><a href="#fn500">500</a></sup> (388 bytes)<br />Oct 26 09:53:32 charon: 12[NET] <con1000|4> sending packet: from XXX.XXX.180.42<sup><a href="#fn500">500</a></sup> to XXX.XXX.183.110<sup><a href="#fn500">500</a></sup> (391 bytes)<br />Oct 26 09:53:32 charon: 12[ENC] <con1000|4> generating AGGRESSIVE request 0 [ SA KE No ID V V V V V V ]<br />Oct 26 09:53:32 charon: 12[IKE] <con1000|4> initiating Aggressive Mode IKE_SA con1000<sup><a href="#fn4">4</a></sup> to XXX.XXX.183.110<br />Oct 26 09:53:32 charon: 12[IKE] <con1000|4> initiating Aggressive Mode IKE_SA con1000<sup><a href="#fn4">4</a></sup> to XXX.XXX.183.110<br />Oct 26 09:53:32 charon: 16[KNL] creating acquire job for policy XXX.XXX.180.42/32|/0 === XXX.XXX.183.110/32|/0 with reqid {2}<br />Oct 26 09:51:15 charon: 16[IKE] <con1000|3> establishing IKE_SA failed, peer not responding<br />Oct 26 09:51:15 charon: 16[IKE] <con1000|3> establishing IKE_SA failed, peer not responding<br />Oct 26 09:51:15 charon: 16[IKE] <con1000|3> giving up after 5 retransmits<br />Oct 26 09:51:15 charon: 16[IKE] <con1000|3> giving up after 5 retransmits<br />Oct 26 09:50:00 charon: 05[NET] error writing to socket: Can't assign requested address<br />...</p>
<p>If more debug information is needed, I can provide this.</p>