pfSense bugtracker: Issueshttps://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162016-09-28T02:59:11ZpfSense bugtracker
Redmine pfSense - Bug #6820 (Resolved): Configure WAN Interface Boot Delayhttps://redmine.pfsense.org/issues/68202016-09-28T02:59:11ZNOYB NOYBJunkYardMail1@Frontier.com
<p>DHCP server responds within just a few milliseconds, but boot up hangs on configure WAN interface for 20+ seconds. The interface is active and responding to traffic during this time of delay with no firewall rules activated. Totally open system.</p>
<p>Same config on 2.3.3 i386 continues right on through without delay.</p>
<p>Forum Thread:<br /><a class="external" href="https://forum.pfsense.org/index.php?topic=118150.0">https://forum.pfsense.org/index.php?topic=118150.0</a></p> pfSense - Bug #6403 (Resolved): Alias type URL (IP) not available for firewall ruleshttps://redmine.pfsense.org/issues/64032016-05-24T22:08:07ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Aliases of the URL (IP) type are not available for selection in firewall rules.</p>
<p>This should fix it.<br /><a class="external" href="https://github.com/pfsense/pfsense/pull/2985">https://github.com/pfsense/pfsense/pull/2985</a></p> pfSense - Bug #6399 (Resolved): Alias type not available from config during alias url table creationhttps://redmine.pfsense.org/issues/63992016-05-24T15:46:25ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Need to pass alias type to process_alias_urltable() function when creating a new url table alias because it is not yet set in config. So the alias_get_type function can't be successfully used yet.</p>
<p>This should fix it.<br /><a class="external" href="https://github.com/pfsense/pfsense/pull/2983">https://github.com/pfsense/pfsense/pull/2983</a></p> pfSense - Bug #6333 (Confirmed): Bootup starts/restarts dpinger multiple timeshttps://redmine.pfsense.org/issues/63332016-05-08T00:22:39ZNOYB NOYBJunkYardMail1@Frontier.com
<p>The setup_gateways_monitor function is called multiple times during boot up by rc.boot, rc.newwanip, and rc.newwanipv6.</p>
<p>Each time stopping and restarting dpinger.</p> pfSense - Bug #6189 (Resolved): Boot up troubles with ramdisk and alias tableshttps://redmine.pfsense.org/issues/61892016-04-17T02:27:54ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Enabling ramdisk does not save/backup/restore the alias tables (/var/db/aliastables/).<br />Thus they have to be re-downloaded at every boot up. Because of this they may not be available when the firewall rules are loaded, which can result in errors and unpredictable behavior.</p>
<p>Some symptoms may include, sluggishness, high CPU utilization, and network connectivity issues, until all the tables are downloaded and get applied.</p> pfSense - Bug #6031 (Closed): Anti-Lockoug Rule Not Effective Against Canned Interface Block Ruleshttps://redmine.pfsense.org/issues/60312016-03-26T19:38:23ZNOYB NOYBJunkYardMail1@Frontier.com
<p>The anti-lockout rule appears to be to low in the processing order to be effective against inadvertently enabling the canned rules of the interface.</p>
<p>For instance. Inadvertent enabling of the block private networks rule on the LAN interface (if it in using a private network address) will override the anti-lockout rule due to their order.</p>
<p>Although the displayed order on firewall rules in places anti-lockout at the top this is not the actual order of processing.</p> pfSense - Bug #5901 (Resolved): Available Widgets and Save Icons Gone Missinghttps://redmine.pfsense.org/issues/59012016-02-17T03:24:07ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Available widgets icon, the plus symbol (+), has gone missing from the dashboard title bar.</p> pfSense - Bug #5804 (Resolved): Alias Auto Suggest Box Entries Display white on white when dark t...https://redmine.pfsense.org/issues/58042016-01-23T05:58:38ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Alias auto suggest box is empty in firewall rules edit (and other locations too).</p>
<p>The box looks about the right size for the list of aliases and the size changes while entering an alias name. But all it's entries display as blank. Can scroll through them with up/down arrow and they show in the entry field. But entries in the list are all displayed blank.</p>
<p>2.3-BETA (i386)<br />built on Sat Jan 23 03:02:05 CST 2016</p> pfSense - Bug #5792 (Resolved): Can't Delete Crash Report - Non English Languagehttps://redmine.pfsense.org/issues/57922016-01-21T21:36:53ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Cannot delete crash report in non English language.</p>
<p>It just won't go away unless language switched to English.</p>
<p><a class="external" href="https://forum.pfsense.org/index.php?topic=105690.0">https://forum.pfsense.org/index.php?topic=105690.0</a></p> pfSense - Bug #5551 (Resolved): DNS Resolver Listen Port Not Savedhttps://redmine.pfsense.org/issues/55512015-11-28T01:38:03ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Specified listen port is not saved. Remains default 53.</p> pfSense - Bug #3728 (Resolved): Cancel Button Doesn't Work - Firewall Aliases Edithttps://redmine.pfsense.org/issues/37282014-07-01T12:20:41ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Cancel button in Firewall Aliases Edit does not work.</p> pfSense Packages - Feature #2487 (Needs Patch): DNS Servers Query Seqentially / Parallelhttps://redmine.pfsense.org/issues/24872012-06-11T00:18:59ZNOYB NOYBJunkYardMail1@Frontier.com
<p>System: General Setup<br />DNS Servers</p>
<p>Option for querying each server sequentially with a specified delay, rather than all at once in parallel.</p> pfSense - Bug #1819 (New): DNS Resolver Not Registering DHCP Server Specified Domain Namehttps://redmine.pfsense.org/issues/18192011-08-29T15:37:36ZNOYB NOYBJunkYardMail1@Frontier.com
<p>DHCP Server specified Domain Name not being registered in DNS Forwarder.</p>
<p>Hosts are resolvable by System General specified domain name instead.</p>
<p>Is this expected mode of opperation? Seem like they should be registered with the domain name they are being assigned.</p>
<p>2.0-RC3 (i386) <br />built on Sun Aug 28 15:02:45 EDT 2011</p> pfSense - Bug #1818 (Closed): DNS Forwarder Not Registering DHCP Server Specified Domain Namehttps://redmine.pfsense.org/issues/18182011-08-29T15:25:22ZNOYB NOYBJunkYardMail1@Frontier.com
<p>DHCP Server specified Domain Name not being registered in DNS Forwarder.</p>
<p>Hosts are resolvable by System General specified domain name instead.</p>
<p>Is this expected mode of opperation? Seem like they should be registered with the domain name they are being assigned.</p>
<p>2.0-RC3 (i386) <br />built on Sun Aug 28 15:02:45 EDT 2011</p> pfSense - Feature #1215 (Resolved): DHCP Bootp Flagshttps://redmine.pfsense.org/issues/12152011-01-20T13:18:09ZNOYB NOYBJunkYardMail1@Frontier.com
<p>Need support for DHCP Bootp flags on WAN interface. Specifically 0x8000 (Broadcast).</p>
<p>Some ISP's do not set dhcp server broadcast flag by default. Therefore dhcp client requests without the broadcast flag set fail.</p>
<p>We cannot control how ISP's chose to configure and run their dhcp systems but, we certainly should be able to control and configure our dhcp clients behavior. Especially a router dhcp client.</p>