pfSense bugtracker: Issueshttps://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162023-07-18T15:14:08ZpfSense bugtracker
Redmine pfSense - Bug #14587 (New): Firewall Log Sort By Timehttps://redmine.pfsense.org/issues/145872023-07-18T15:14:08ZBrian Shell
<p>When viewing the System Logs > Firewall, and trying to sort by Time with newest first, it appears the sort is working alphabetically instead of chronologically. For example, this is the order I see when attempting to sort. Don't be concerned about the gaps of time between as this is simply due to to events being logged during those times and that is expected based on the logging I have enabled. Jun 30, Jun 28, Jun 27, Jun 26, Jun 25, Jun 24, Jun 23, Jun 22, Jun 21, Jul 6, Jul 4, Jul 18, Jul 13, Jul 10. Hopefully this will be something reproducible so a developer can see it because it is hard to explain in words. Attaching part of a screenshot so you can see the sorting. You won't see the issue from my screenshot I would have to scroll down and send many pages of screens.</p> pfSense - Bug #13565 (New): LOR on Boot for Static Routes Startup Item in KVM environmenthttps://redmine.pfsense.org/issues/135652022-10-15T18:44:53ZKris Phillips
<p>When booting the following message is present in the boot list:</p>
<p>Setting up static routes...Invoking IPv6 network device address event may sleep with the following non-sleepable locks held:<br />exclusive sleep mutex vtnet0-rx0 (vtnet0-rx0) r = 0 (0xfffff80005927480) locked <code> /var/jenkins/workspace/pfSense-CE-snapshots-master-main/sources/FreeBSD-src-devel-main/sys/dev/virtio/network/if_vtnet.c:2195<br />stack backtrace:<br />#0 0xffffffff80debac5 at witness_debugger+0x65<br />#1 0xffffffff80decc2a at witness_warn+0x3fa<br />#2 0xffffffff80fe02da at in6_update_ifa+0xbda<br />#3 0xffffffff8100fb85 at in6_ifadd+0x1d5<br />#4 0xffffffff8100c38c at nd6_ra_input+0xfbc<br />#5 0xffffffff80fdac0e at icmp6_input+0x77e<br />#6 0xffffffff80ff4ab3 at ip6_input+0xbc3<br />#7 0xffffffff80ee90a0 at netisr_dispatch_src+0x220<br />#8 0xffffffff80ec39ec at ether_demux+0x17c<br />#9 0xffffffff80ec5066 at ether_nh_input+0x3f6<br />#10 0xffffffff80ee8f2f at netisr_dispatch_src+0xaf<br />#11 0xffffffff80ec3ea9 at ether_input+0x99<br />#12 0xffffffff80b863e1 at vtnet_rxq_eof+0x791<br />#13 0xffffffff80b85ba7 at vtnet_rx_vq_process+0x97<br />#14 0xffffffff80d34b39 at ithread_loop+0x279<br />#15 0xffffffff80d30fd0 at fork_exit+0x80<br />#16 0xffffffff8130e3de at fork_trampoline+0xe<br />lock order reversal: (sleepable after non-sleepable)<br /> 1st 0xfffff80005927480 vtnet0-rx0 (vtnet0-rx0, sleep mutex) </code> /var/jenkins/workspace/pfSense-CE-snapshots-master-main/sources/FreeBSD-src-devel-main/sys/dev/virtio/network/if_vtnet.c:2195<br /> 2nd 0xffffffff8366fbd0 in6_multi_sx (in6_multi_sx, sx) @ /var/jenkins/workspace/pfSense-CE-snapshots-master-main/sources/FreeBSD-src-devel-main/sys/netinet6/in6_mcast.c:1193<br />lock order vtnet0-rx0 -> in6_multi_sx attempted at:<br />#0 0xffffffff80deb68d at witness_checkorder+0xbfd<br />#1 0xffffffff80d84783 at _sx_xlock+0x63<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed parent" title="Bug: Gateway not added when switching from DHCP to static (Resolved)" href="https://redmine.pfsense.org/issues/2">#2</a> 0xffffffff80fe8a31 at in6_joingroup+0x31<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: VPN negation rules not added in 2.0 (Resolved)" href="https://redmine.pfsense.org/issues/3">#3</a> 0xffffffff80fe0682 at in6_update_ifa+0xf82<br /><a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: Remove hard coded VLAN supported interfaces list (Resolved)" href="https://redmine.pfsense.org/issues/4">#4</a> 0xffffffff8100fb85 at in6_ifadd+0x1d5<br /><a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Todo: Don't sync on every filter reload (Resolved)" href="https://redmine.pfsense.org/issues/5">#5</a> 0xffffffff8100c38c at nd6_ra_input+0xfbc<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Status -> Wireless display bugs (Resolved)" href="https://redmine.pfsense.org/issues/6">#6</a> 0xffffffff80fdac0e at icmp6_input+0x77e<br /><a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Todo: [ Fit123 ] Captive Portal (Closed)" href="https://redmine.pfsense.org/issues/7">#7</a> 0xffffffff80ff4ab3 at ip6_input+0xbc3<br /><a class="issue tracker-2 status-3 priority-5 priority-high4 closed" title="Feature: Clear states after failover (Resolved)" href="https://redmine.pfsense.org/issues/8">#8</a> 0xffffffff80ee90a0 at netisr_dispatch_src+0x220<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: route-to forwards broadcast and multicast frames in some scenarios (Resolved)" href="https://redmine.pfsense.org/issues/9">#9</a> 0xffffffff80ec39ec at ether_demux+0x17c<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Enable SSH console menu doesn't work on embedded (Resolved)" href="https://redmine.pfsense.org/issues/10">#10</a> 0xffffffff80ec5066 at ether_nh_input+0x3f6<br /><a class="issue tracker-2 status-3 priority-4 priority-default closed" title="Feature: Allow multiple syslog servers (Resolved)" href="https://redmine.pfsense.org/issues/11">#11</a> 0xffffffff80ee8f2f at netisr_dispatch_src+0xaf<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Editing DNS forwarder overrides does not trigger sync to secondary (Resolved)" href="https://redmine.pfsense.org/issues/12">#12</a> 0xffffffff80ec3ea9 at ether_input+0x99<br /><a class="issue tracker-2 status-3 priority-4 priority-default closed" title="Feature: wireless page to have option to select transmit and receive antennas (Resolved)" href="https://redmine.pfsense.org/issues/13">#13</a> 0xffffffff80b863e1 at vtnet_rxq_eof+0x791<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: reply-to should not be added when bridging (Resolved)" href="https://redmine.pfsense.org/issues/14">#14</a> 0xffffffff80b85ba7 at vtnet_rx_vq_process+0x97<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Package reinstall on configuration restore doesn't work (Resolved)" href="https://redmine.pfsense.org/issues/15">#15</a> 0xffffffff80d34b39 at ithread_loop+0x279<br /><a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: Deleting multiple OPT interfaces results in an invalid configuration (Resolved)" href="https://redmine.pfsense.org/issues/16">#16</a> 0xffffffff80d30fd0 at fork_exit+0x80<br /><a class="issue tracker-2 status-5 priority-10 priority-lowest closed" title="Feature: LED support on ALIX, WRAP, etc. (Closed)" href="https://redmine.pfsense.org/issues/17">#17</a> 0xffffffff8130e3de at fork_trampoline+0xe<br />done.</p> pfSense - Bug #13144 (New): Firewall rule entries can get out of sync when entries are deleted wh...https://redmine.pfsense.org/issues/131442022-05-10T01:27:57ZSilvan Ehemann
<p>tested versions:<br />2.4.5<br />2.6.0</p>
<p>Prereqs<br />Admin A logs in to Firewall<br />Admin B logs in to same Firewall</p>
<p>Intention<br />Admin A would like to create a firewall rule<br />Admin B would like to create a separator</p>
<p>Issue<br />If the two admins execute the changes at the same time, under certain conditions existing firewall rules will be deleted!</p>
<p>Steps to reproduce<br />- Admin A creates one additional firewall rule. (Admin A does NOT yet click on apply.) The rule is now visible at the top of the list.<br />- Admin B creates one separator. The separator is now visible at the bottom of the list.<br />- Admin B clicks "save" on his separator.<br />- Result: The firewall rule in the bottom position is deleted and is replaced by the new firewall rule.</p>
<p>Notice:<br />I have already created a forum post on <a class="external" href="https://forum.netgate.com/topic/171774/rule-disappears-when-multiple-admins-edit-rules-and-separators">https://forum.netgate.com/topic/171774/rule-disappears-when-multiple-admins-edit-rules-and-separators</a>. We think it is worth mentioning and improving</p>
<p>with regards</p>
<p>Emasi</p> pfSense - Bug #12067 (New): DHCP Monitoring Statistics Errorhttps://redmine.pfsense.org/issues/120672021-06-21T08:39:05ZEvgeny Korostelev
<p>I have 2 DHCP pool (51 + 51 IP address) in one network (see attachments screen)<br />But monitoring DHCP show maximum dhcprange - 51 IP address</p> pfSense - Bug #11777 (New): Input validation prevents DNS Resolver from being disabledhttps://redmine.pfsense.org/issues/117772021-04-03T17:51:02ZMartin Thygesen
<p>When trying to disable unbound, the following error prevents the service from being turned off.</p>
<p>-----------------<br />The following input errors were detected:</p>
<pre><code>The generated config file cannot be parsed by unbound. Please correct the following errors:<br /> [1617488979] unbound-checkconf[18250:0] fatal error: outgoing-interface: fe80::20c:29ff:fec7:63f1%em0 present twice, cannot bind same ports twice.<br />-----------------</code></pre>
<p>taxonomy<br />user was operating with unbound dns resolver normally<br />system was setup for network interfaces LAN & DMZ & LOOPBACK (v4 & v6)<br />system was setup for outbound network interfaces WAN (v4 & v6)<br />user installed bind package to replace unbound but did not activate it.<br />user tried to disable unbound and was presented with this error message.<br />user stopped the unbound service from the dashboard and retried to disable the configuration, outcome failed</p>
<p>Workaround:<br />user adjusted the network interfaces to loopback<br />user adjusted the outbound network interface setting to loopback<br />user saved the config<br />user disabled unbound, and was successful in disabling the service.</p>
<p>Recommendation:<br />remove some of the check conditions that prevent the service config from being disabled<br />the service can clearly be stopped without the configuration process being impacted.<br />the parse of the configuration is too restrictive in this case.</p> pfSense Packages - Bug #11650 (New): FRR configuration broken on restore of manually edited FRR c...https://redmine.pfsense.org/issues/116502021-03-10T06:51:58ZAndrew Green
<p>SG-3100<br />21.02-RELEASE-p1 (arm)<br />built on Mon Feb 22 09:38:52 EST 2021</p>
<p>FRR package version 1.1.0_8</p>
<p>I could not find any instructions to remove all of a package's configuration so I did this:</p>
<p>- Made a config backup<br />- Edited the config xml and remove the FRR config references but left the package sections in place with empty <config></config> sections inside.<br />- Restored the config<br />- Router rebooted and reinstalled packages<br />- Went to reconfigure FRR and it broke sometimes when saving the settings.<br />- I managed to make the error go away after adding and deleting a prefix list.<br />- Here is the PHP error:<br /><pre>
arm
12.2-STABLE
FreeBSD 12.2-STABLE 0e42b7d7eac(HEAD) pfSense-SG-3100
Crash report details:
PHP Errors:
[09-Mar-2021 21:46:49 America/St_Johns] PHP Fatal error: Uncaught Error: Only variables can be passed by reference in /usr/local/pkg/frr/inc/frr_zebra.inc:295
Stack trace:
#0 /usr/local/pkg/frr/inc/frr_zebra.inc(758): frr_zebra_generate_prefixlists(true, false)
#1 /usr/local/pkg/frr.inc(683): frr_generate_config_zebra()
#2 /usr/local/www/pkg_edit.php(245) : eval()'d code(1): frr_generate_config()
#3 /usr/local/www/pkg_edit.php(245): eval()
#4 {main}
thrown in /usr/local/pkg/frr/inc/frr_zebra.inc on line 295
[09-Mar-2021 21:47:15 America/St_Johns] PHP Fatal error: Uncaught Error: Only variables can be passed by reference in /usr/local/pkg/frr/inc/frr_zebra.inc:295
Stack trace:
#0 /usr/local/pkg/frr/inc/frr_zebra.inc(758): frr_zebra_generate_prefixlists(true, false)
#1 /usr/local/pkg/frr.inc(683): frr_generate_config_zebra()
#2 /usr/local/www/pkg_edit.php(245) : eval()'d code(1): frr_generate_config()
#3 /usr/local/www/pkg_edit.php(245): eval()
#4 {main}
thrown in /usr/local/pkg/frr/inc/frr_zebra.inc on line 295
[09-Mar-2021 21:47:30 America/St_Johns] PHP Fatal error: Uncaught Error: Only variables can be passed by reference in /usr/local/pkg/frr/inc/frr_zebra.inc:295
Stack trace:
#0 /usr/local/pkg/frr/inc/frr_zebra.inc(758): frr_zebra_generate_prefixlists(true, false)
#1 /usr/local/pkg/frr.inc(683): frr_generate_config_zebra()
#2 /usr/local/www/pkg_edit.php(245) : eval()'d code(1): frr_generate_config()
#3 /usr/local/www/pkg_edit.php(245): eval()
#4 {main}
thrown in /usr/local/pkg/frr/inc/frr_zebra.inc on line 295
[09-Mar-2021 21:47:36 America/St_Johns] PHP Fatal error: Uncaught Error: Only variables can be passed by reference in /usr/local/pkg/frr/inc/frr_zebra.inc:295
Stack trace:
#0 /usr/local/pkg/frr/inc/frr_zebra.inc(758): frr_zebra_generate_prefixlists(true, false)
#1 /usr/local/pkg/frr.inc(683): frr_generate_config_zebra()
#2 /usr/local/www/pkg_edit.php(245) : eval()'d code(1): frr_generate_config()
#3 /usr/local/www/pkg_edit.php(245): eval()
#4 {main}
thrown in /usr/local/pkg/frr/inc/frr_zebra.inc on line 295
[09-Mar-2021 21:49:51 America/St_Johns] PHP Fatal error: Uncaught Error: Only variables can be passed by reference in /usr/local/pkg/frr/inc/frr_zebra.inc:262
Stack trace:
#0 /usr/local/pkg/frr/inc/frr_zebra.inc(764): frr_zebra_generate_aspaths()
#1 /usr/local/pkg/frr.inc(683): frr_generate_config_zebra()
#2 /usr/local/www/pkg_edit.php(245) : eval()'d code(1): frr_generate_config()
#3 /usr/local/www/pkg_edit.php(245): eval()
#4 {main}
thrown in /usr/local/pkg/frr/inc/frr_zebra.inc on line 262
[09-Mar-2021 21:49:55 America/St_Johns] PHP Fatal error: Uncaught Error: Only variables can be passed by reference in /usr/local/pkg/frr/inc/frr_zebra.inc:262
Stack trace:
#0 /usr/local/pkg/frr/inc/frr_zebra.inc(764): frr_zebra_generate_aspaths()
#1 /usr/local/pkg/frr.inc(683): frr_generate_config_zebra()
#2 /usr/local/www/pkg_edit.php(245) : eval()'d code(1): frr_generate_config()
#3 /usr/local/www/pkg_edit.php(245): eval()
#4 {main}
thrown in /usr/local/pkg/frr/inc/frr_zebra.inc on line 262
[09-Mar-2021 21:50:03 America/St_Johns] PHP Fatal error: Uncaught Error: Only variables can be passed by reference in /usr/local/pkg/frr/inc/frr_zebra.inc:262
Stack trace:
#0 /usr/local/pkg/frr/inc/frr_zebra.inc(764): frr_zebra_generate_aspaths()
#1 /usr/local/pkg/frr.inc(683): frr_generate_config_zebra()
#2 /usr/local/www/pkg.php(140) : eval()'d code(1): frr_generate_config()
#3 /usr/local/www/pkg.php(140): eval()
#4 {main}
thrown in /usr/local/pkg/frr/inc/frr_zebra.inc on line 262
No FreeBSD crash data found.
</pre></p> pfSense Packages - Bug #11493 (New): After upgrade zabbix proxy wont starthttps://redmine.pfsense.org/issues/114932021-02-21T05:31:00ZPim Janssen
<p>Due to database changes between zabbix-proxy versions. The proxy database needs to be removed after upgrading else the proxy service won't start.</p>
<p>Workaround <br />manual remove database /var/db/zabbix-proxy/proxy.db</p> pfSense - Bug #10701 (New): Firewall Log too wide with Rule Description Columnhttps://redmine.pfsense.org/issues/107012020-06-25T05:41:01ZLouis B
<p>Hello,</p>
<p>I just noticed that at least with systemlog firewall the layout does not fit inside the page any more. May be there are layout issues at other places as well. I did not check.</p>
<p>I noticed it with version </p>
<pre><code>2.5.0-DEVELOPMENT (amd64)<br />built on Tue Jun 23 01:04:03 EDT 2020<br />FreeBSD 12.1-STABLE</code></pre>
<p>And I tried with multiple browsers (all the same)</p>
<p>Louis</p> pfSense Packages - Bug #10265 (New): Adding a Note with malformed title will force system restorehttps://redmine.pfsense.org/issues/102652020-02-17T14:27:22ZYuri Weinstein
<p>This is related to using Notes package.</p>
<p>Add a new note with title</p>
<p>"Add/Change/Set the custom resolution of your display using xrandr on Ubuntu 18.04 — {In a minute}"</p>
<p>(I am not sure why this particular string causes a problem, but it does) and anything in the notes body</p>
<p>Click on Save => notice that the note was not added and pfSense System Notices show a new warning:</p>
<p>"pfSenseConfigurator<br />pfSense is restoring the configuration /cf/conf/backup/config-1581970855.xml @ 2020-02-17 12:21:23"</p> pfSense Packages - Bug #9012 (New): Captive Portal authentication in Squid Proxy Server does not ...https://redmine.pfsense.org/issues/90122018-10-05T11:25:32ZKevin Chou
<p>Version pfsense 2.4.4-RELEASE (amd64)<br />I have configured Authentication Method to "Captive Portal" in Squid Proxy Server -> Authentication<br />But it does not work, squid cannot get current user and deny access.</p> pfSense Packages - Bug #8454 (New): Arpwatch package break email notifications from other sourceshttps://redmine.pfsense.org/issues/84542018-04-12T07:18:20ZYehuda Katz
<p>Arpwatch replaces /usr/sbin/sendmail with a symlink to a PHP script that specifically mentioned Arpwatch in the message subject:<br /><a class="external" href="https://github.com/pfsense/FreeBSD-ports/blob/015971be238550a1f9aa060fe5ed93849c01572e/net-mgmt/pfSense-pkg-arpwatch/files/usr/local/pkg/arpwatch.inc#L217">https://github.com/pfsense/FreeBSD-ports/blob/015971be238550a1f9aa060fe5ed93849c01572e/net-mgmt/pfSense-pkg-arpwatch/files/usr/local/pkg/arpwatch.inc#L217</a></p>
<p>This causes notifications from ACME (run by CRON) to come with subjects like this:</p>
<blockquote>
<p>wall.example.com - Arpwatch Notification : Cron <root@wall> /usr/local/pkg/acme/acme_command.sh "renewall"</p>
</blockquote> pfSense - Bug #8233 (New): NAT reflection back to originating host broken when using FQDN-based I...https://redmine.pfsense.org/issues/82332017-12-22T12:46:33ZChaos215 Bar2
<p>It appears NAT reflection is slightly broken when targeted at an IP alias which is defined via FQDN (rather than IP address). In this case, reflection works from hosts on subnets other than the one that the NAT target is on, but not from the same subnet. Within the same subnet, it appears traffic it redirected to the target host, but the originating IP is not translated.</p>
<p>To put this in context, let's say I have a host ns.example.com at IP 10.0.0.10, and I want to redirect traffic sent to 1.2.3.4 to this host. Let's say I create an alias "NameServer", and create a NAT rule to translate traffic arriving on the WAN interface destined for the address 1.2.3.4, port 53 to "NameServer" port 53, and enable reflection. ("Enable NAT Reflection for 1:1 NAT" and "Enable automatic outbound NAT for Reflection" are enabled and 1.2.3.4 is an IP alias with an outbound NAT rule mapping traffic from "NameServer" to the NAT address 1.2.3.4, FWIW.)</p>
<p>If the alias "NameServer" points at the FQDN ns.example.com (which resolved internally to 10.0.0.10), then I run into this problem. If I make a DNS request to 1.2.3.4 from outside the server's subnet (let's say outside 10.0.0.0/24), everything is fine (even from interfaces other than WAN, so reflection is working… sort of). If I make a request from within the same subnet, I do see a response, but it comes directly from 10.0.0.10, not 1.2.3.4. (i.e. The request packet was clearly redirected to 1.2.3.4, but it doesn't actually seem to have gone through NAT.)</p>
<p>If the alias "NameServer" points at the IP 10.0.0.10, then everything works, and I see several <em>additional</em> translation rules:<br /><pre>
no nat on lagg0 inet proto tcp from 10.0.0.1 to <NameServer> port = domain
no nat on lagg0 inet proto udp from 10.0.0.1 to <NameServer> port = domain
nat on lagg0 inet proto tcp from 10.0.0.0/24 to <NameServer> port = domain -> 10.0.0.1 port 1024:65535
nat on lagg0 inet proto udp from 10.0.0.0/24 to <NameServer> port = domain -> 10.0.0.1 port 1024:65535
</pre></p>
<p>These are in addition to rules of the following form, that exist either way:<br /><pre>
nat on igb1 inet from <NameServer> to any -> 1.2.3.4 static-port
no rdr proto carp all
rdr-anchor "relayd/*" all
rdr-anchor "tftp-proxy/*" all
<Above rules here>
rdr on igb1 inet proto tcp from any to 1.2.3.4 port = domain -> <NameServer> round-robin
rdr on igb1 inet proto udp from any to 1.2.3.4 port = domain -> <NameServer> round-robin
rdr on igb0 inet proto tcp from any to 1.2.3.4 port = domain -> <NameServer> round-robin
rdr on igb0 inet proto udp from any to 1.2.3.4 port = domain -> <NameServer> round-robin
rdr on lagg0 inet proto tcp from any to 1.2.3.4 port = domain -> <NameServer> round-robin
rdr on lagg0 inet proto udp from any to 1.2.3.4 port = domain -> <NameServer> round-robin
</pre></p>
<p>(The DNS server is located on lagg0, on which the router has the IP 10.0.0.1. igb1 is WAN, and igb0 is the regular LAN interface.)</p>
<p>It appears the problem is that pfSense can't resolve the interface the host pointed to by "NameServer" will lie on at the time of rule creation, so is unable to create the necessary NAT rules to allow reflection to work within the same subnet. Perhaps either a new kind of "rdr" style rule that performs NAT when reflecting back out to the same subnet is necessary, or an option to specify an interface in addition to (perhaps connected to) a host alias is needed, to enable creation of these rules.</p> pfSense - Bug #7857 (New): Interfaces Widget U/I fails to wrap IPV6 addresses when the string is ...https://redmine.pfsense.org/issues/78572017-09-13T03:43:10ZBryan Stenson
<p>Strictly a U/I issue, the widget fails to wrap when the browser window is set small enough to make the string too wide for the box.</p> pfSense - Bug #5091 (Confirmed): In rule creation destination ports fields (from and to) are too...https://redmine.pfsense.org/issues/50912015-09-03T10:43:16ZPierre DOUCETpierre.doucet@sib.fr
<p>Refer to screenshot in attachement.</p>
<p>This could be solved by adding width tag in all.css files for all themes.</p>
<pre>
.formfldalias {
background-color: #990000;
color: #FFFFFF;
width: 300px;
}
</pre> pfSense - Bug #4298 (Assigned): Excessive errors from snmpdhttps://redmine.pfsense.org/issues/42982015-01-26T04:32:43ZHolger Hampel
<p>When accessing snmp from a montitoring system I get many, many errors (logged in the central syslog):</p>
<p>snmpd<sup><a href="#fn95772">95772</a></sup>: could not encode error response</p>
<p>I tried to disable some mibs, but there is no change.</p>
<p>Same monitoring worked in 2.1.5</p>