pfSense bugtracker: Issueshttps://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162024-02-29T06:58:23ZpfSense bugtracker
Redmine pfSense Packages - Bug #15296 (New): WAN Interface cannot added to ntopng if offline-packet loss https://redmine.pfsense.org/issues/152962024-02-29T06:58:23ZSergei Shablovsky
<p>Brilliant pfSense DevTeam !</p>
<p>In multi-WAN pfSense configuration WAN interfaces that pfSense decide in “Offline, Packet loss” state CANNOT BE ADDED into ntopng config.</p>
<p>(to adding certain WAN connection (for example if WAN interface come from “Offline, packet loss” state to “Online” state), ntopng need to be disabled, service stopped, ntopng pkg uninstalled (with all data and configs deleted), than hardware rebooting, install ntopng pkg again, and only after that new WAN with “Online” status becomes visible as Interface in ntopng”).</p>
<p>But LAN interfaces ALL would be ADDED as well even some of them are not connected physically. So this bug related only WAN interfaces.</p>
<p>P.S.<br />This is related for WAN DHCP, do not know about WAN STATIC.</p> pfSense - Bug #15083 (New): Installing to ZFS mirror does not format or populate EFI partition on...https://redmine.pfsense.org/issues/150832023-12-11T16:28:54ZJim Pingle
<p>Installing Plus 23.09.1 or CE 2.7.2 to a ZFS mirror does not format or populate the EFI partition on the additional disks of the mirror. Only the first disk in the mirror has a populated EFI filesystem with the expected loader files.</p>
<p>The EFI Partition for the second disk (or later) is created and labeled as <code>/dev/gpt/efiboot1</code> (and so on) but there is no filesystem on that partition (and thus, no files).</p>
<p>Should the first disk in the mirror fail, this would leave the system unbootable.</p>
<p>Can be worked around by manually creating and populating the additional EFI partition(s) post-install</p>
<p>For example, to format and populate the EFI filesystem on the second disk of the mirror:</p>
<pre><code class="shell syntaxhl"><span class="c"># newfs_msdos -F 32 -c 1 -L EFISYS1 /dev/gpt/efiboot1</span>
<span class="c"># mount_msdosfs /dev/gpt/efiboot1 /mnt</span>
<span class="c"># cp -R /boot/efi/ /mnt</span>
<span class="c"># umount /mnt</span>
</code></pre> 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 Packages - Bug #15048 (New): Snort large memory consumption when updatinghttps://redmine.pfsense.org/issues/150482023-11-29T09:47:49ZRicardo ot
<p>Snort since the last updates uses a lot of memory when updating and it has a big impact. Can this be improved?</p>
<p>Thanks,</p>
<p>I have these configurations active for 2 interfaces:<br />Resolve Flowbits. checked.<br />Use IPS Policy. Checked.<br />IPS Policy Selection. Connectivity.<br />All the rulesets (Categories). Checked all</p>
<p>I already changed the PfBlokerng configuration to use "Unbound python mode" and changed the time so that the update is not done at the same time. This has improved PfblockerNg's memory usage.</p>
<p>System log Logs:</p>
<blockquote>
<p>Nov 29 00:48:16 php 46952 [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload<br />Nov 29 00:45:00 php 46952 [pfBlockerNG] Starting cron process.<br />Nov 29 00:25:57 php 85398 [Snort] The Rules update has finished.<br />Nov 29 00:25:57 php 85398 [Snort] Snort has restarted on WANONT with your new set of rules...<br />Nov 29 00:25:45 php 85398 [Snort] Snort START for <abbr title="vmx3">WANONT</abbr>...<br />Nov 29 00:25:44 kernel pid 31736 (snort), jid 0, uid 0: exited on signal 11 (core dumped)<br />Nov 29 00:25:44 snort 31736 * * * Caught Term-Signal<br />Nov 29 00:25:43 php 85398 [Snort] Snort STOP for <abbr title="vmx3">WANONT</abbr>...<br />Nov 29 00:25:42 php 85398 [Snort] Building new sid-msg.map file for WANONT...<br />Nov 29 00:25:42 php 85398 [Snort] Enabling any flowbit-required rules for: WANONT...<br />Nov 29 00:25:42 php 85398 [Snort] Enabling any flowbit-required rules for: WANONT...<br />Nov 29 00:25:41 php 85398 [Snort] Updating rules configuration for: WANONT ...<br />Nov 29 00:25:41 php 85398 [Snort] Snort has restarted on LAN with your new set of rules...<br />Nov 29 00:25:29 kernel pid 29090 (snort), jid 0, uid 0: exited on signal 11 (core dumped)<br />Nov 29 00:25:29 php 85398 [Snort] Snort START for <abbr title="vmx1">LAN</abbr>...<br />Nov 29 00:25:28 snort 29090 *** Caught Term-Signal<br />Nov 29 00:25:27 php 85398 [Snort] Snort STOP for <abbr title="vmx1">LAN</abbr>...<br />Nov 29 00:25:27 php 85398 [Snort] Building new sid-msg.map file for LAN...<br />Nov 29 00:25:27 php 85398 [Snort] Enabling any flowbit-required rules for: LAN...<br />Nov 29 00:25:26 php 85398 [Snort] Enabling any flowbit-required rules for: LAN...<br />Nov 29 00:25:26 php 85398 [Snort] Updating rules configuration for: LAN ...<br />Nov 29 00:25:25 php 85398 [Snort] Building new sid-msg.map file for WAN...<br />Nov 29 00:25:25 php 85398 [Snort] Enabling any flowbit-required rules for: WAN...<br />Nov 29 00:25:25 php 85398 [Snort] Enabling any flowbit-required rules for: WAN...<br />Nov 29 00:25:24 php 85398 [Snort] Updating rules configuration for: WAN ...<br />Nov 29 00:25:24 php 85398 [Snort] Removed 49 obsoleted rules category files.<br />Nov 29 00:25:24 php 85398 [Snort] Hide Deprecated Rules is enabled. Removing obsoleted rules categories.<br />Nov 29 00:25:17 php 85398 [Snort] Feodo Tracker Botnet C2 IP rules were updated...<br />Nov 29 00:25:17 php 85398 [Snort] Feodo Tracker Botnet C2 IP rules file update downloaded successfully.<br />Nov 29 00:25:17 php 85398 [Snort] Emerging Threats Open rules file update downloaded successfully<br />Nov 29 00:25:15 php 85398 [Snort] There is a new set of Emerging Threats Open rules posted. Downloading emerging.rules.tar.gz...<br />Nov 29 00:25:15 php 85398 [Snort] Snort GPLv2 Community Rules file update downloaded successfully<br />Nov 29 00:25:13 php 85398 [Snort] There is a new set of Snort GPLv2 Community Rules posted. Downloading community-rules.tar.gz...<br />Nov 29 00:25:13 php 85398 [Snort] Snort Subscriber rules file update downloaded successfully<br />Nov 29 00:25:04 php 85398 [Snort] There is a new set of Snort Subscriber rules posted. Downloading snortrules-snapshot-29200.tar.gz...</p>
</blockquote> 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 - Bug #14906 (New): DHCPv4 server self-assigning address to own DHCP client-enabled inter...https://redmine.pfsense.org/issues/149062023-10-22T15:24:26ZLuca Piccirillo
<p>Assume three NICs: igc0, igc1, igc2<br />Assume a single bridge: bridge0 (OPT2, OPT3)<br />And a VLAN: igc0.1036</p>
<p>Interfaces assignment as follows:<br />WAN -> igc0.1036 -> IPv4 (DHCP): 1.2.3.4/30<br />LAN -> bridge0 -> IPv4 (static): 192.168.1.1/24<br />OPT1 -> igc0 -> IPv4 (static): 192.168.100.2/24<br />OPT2 -> igc1<br />OPT3 -> igc2</p>
<p>DHCP & RA enabled for LAN only.</p>
<p>The problem: switching OPT1 IPv4 settings from static to DHCP makes pfSense to assign itself an address from the LAN pool, also creating a wrong on-link route for its LAN subnet over the igc0 port, which is the underlying IF of WAN.</p>
<p>Of course this is easily noticeable when no other DHCP serve is active on that igc0 port broadcast domain.</p> pfSense - Bug #14891 (New): High CPU usage when interface get down and up due to proces check_rel...https://redmine.pfsense.org/issues/148912023-10-18T10:40:27ZThijs K
<p>Today I noticed that the cpu usage was high on my pfSense appliance (N5105, I226). <br />After looking in top I see that check_reload_status is fully taxing one core. <br />This process seems to be triggered when the wan interface comes down and up. <br />The process keeps running and taxing the CPU until it is manually stopped.</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 #14734 (New): Alias FQDN resolving issue results in incomplete tableshttps://redmine.pfsense.org/issues/147342023-08-31T13:59:20ZRobert Gijsen
<p>In CE 2.7.0, there are still issues when FQDN are used in aliasses. Vonsider an alias with 3 entries, 2 static IP's and one FQDN, pointing to one of those IP's as well. When the FQDN changes to the other IP, the IP it had initially is gone from the table.</p>
<p>Steps to reproduce:</p>
Create an alias
<ul>
<li>add 1.1.1.1</li>
<li>add 8.8.8.8</li>
<li>add a (public) dns entry you created, pointing to 1.1.1.1, ie pfsensetest.domain.com</li>
<li>monitor the table-entry for the alias, all will be ok</li>
<li>now change the DNS entry for pfsensetest.domain.com from 1.1.1.1 to 8.8.8.8 and wait for it to be replicated and pfSense to pick it up</li>
<li>in my setups, 1.1.1.1 got deleted from the table. So while 8.8.8.8 is in there 'twice' now, and 1.1.1.1 only once statically, it's not there anymore</li>
<li>killing filterdns and reloading filters repopulates the tables correctly it seems.</li>
</ul>
<p>It looks like when the FQDN is resolved, it overrules the static entry if one with the same value exists, and when the FQDN changes, the static entry is not put back in to the table. I tailed resolver.log while reproducing the issue, but it made no notion at all of resolving the FQDN to another IP. So I don't know what log to add, or which log to enable verbose logging for.</p>
<p>I consider this high priority, as it has high potential of actually functionally breaking an environment.</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>