Download - D-Link

NetDefend Firewall Firmware Release Notes
the HTTP ALG together with Anti-Virus scanning.
108. In certain rare scenarios, the H323 ALG could make the firewall reboot
unexpectedly.
109. The system would advertise the wrong IPv6 address when going active in a
high availability scenario.
110. In rare cases when a heavy load of IPsec traffic was sent through the firewall
there could be logs about hardware acceleration failure with performance
degradation as a result. Affected models were DFL-260E and DFL-860E.
111. When listing VLANs in the CLI and the same VLAN ID was available on more
than one physical interface, the listing was incorrect.
112. Fragmented packets coming from a VLAN going into an L2TPv3 tunnel would
be erroneously dropped in some situations.
113. The internal SSH Server could in rare circumstances use an increasing
amount of memory.
114. Enabling Router Advertisement on an interface with an unnamed
IPv6Network would produce a configuration error.
115. The properties for local_peer and remote_peer in the IPsec logs were
sometimes truncated.
116. The system sometimes restarted unexpectedly during a reconfiguration.
117. The firewall would always perform automatic updates of IDP and AV
databases on startup and HA activation. Automatic updates will now only
occur at the configured time.
118. The log events "too_many_flows_aged" and "failed_to_select_policy_rule"
both used the same log ID 01803001. Now the former uses ID 01803005
and the latter ID 01803001.
119. Syslog messages sent from the firewall did not follow the standard specified
in RFC5424. A setting that enables sending Syslog messages according to
RFC5424 has been added to the ' LogReceiverSyslog ' configuration object.
120. LDAP queries against OpenLDAP servers did not work as expected. It is now
possible, via the new setting; 'Combined Username' and 'Optional
Attribute', on the LDAP Server, to specify how LDAP queries towards an
OpenLDAP server should be sent.
121. Certain web pages were not possible to reach or load when using the HTTPS
ALG.
122. POP3 ALG log messages would sometimes contain incorrect e-mail
addresses.
123. On rare occasions, the SMTP and POP3 ALGs could not read fields from the
DataHeader correctly.
25