Filter
Top Products
5
SonicOS 5.8.1.2 Release Notes for the NSA 220/250M Series Appliances
P/N 232-000648-00 Rev A
Bandwidth Management
Symptom
Condition / Workaround
Issue
Traffic is dropped when the ingress or egress
values for an interface are modified and traffic is
passing through that interface.
Occurs when modifying the ingress or egress
interface values while the interface is passing
traffic.
Workaround: Stop traffic on the interface, and
then modify the values.
101286
Bandwidth management application rules are
sometimes mapped to the wrong global BWM
priority queue.
Occurs when creating a bandwidth management
rule on the App Flow Monitor page and setting
the priority to High. The App Flow Monitor page
displays the created rule with a Medium priority
setting, even though
High
was selected.
100116
Firmware
Symptom
Condition / Workaround
Issue
The Botnet Service is incorrectly listed on the
Security Services > Summary page and the
System > Status page of the SonicWALL TZ
200 wireless appliance, even though the service
is not supported on this platform.
Botnet Command & Control Filtering is not
supported on the SonicWALL TZ 100 and TZ 200
series appliances (as also reflected in the
Supported Features by Appliance Model table of
the Release Notes). The Botnet service listing
indicating 'Not Licensed' on the System > Status
page should be ignored.
108038
An iPad client fails to connect to the L2TP
server if MSCHAPv2 authentication is set as the
first order authentication method.
Occurs when GroupVPN is enabled and
configured for an L2TP. The iPad can successfully
connect if PAP authentication is set as the first
order authentication method, but fails if
MSCHAPv2 is prefered. A Windows XP client can
succesfully connect using MSCHAPv2.
Workaround: Move MSCHAPv2 to the bottom of
the authentication protocol list (by clicking on the
Down Arrow button).
106801
The error message “This request is blocked by
the sonicwall gateway botnet service. Botnet
Responder IP: 125.39.127.25" is displayed.
Occurs when navigating to the Security Services
> Geo-IP & Botnet Filter page and enabling the
“Block connections to/from Botnet Command and
Control Systems” option. For example, when
trying to view the qq.com web site, the site is
blocked even though it is not considered a Botnet
server.
105889
The Geo-IP and Botnet Exclusion Objects do
not take effect, causing DNS query packets to
be incorrectly dropped.
Occurs when enabling the checkbox for Block All
Connections to/from Following Countries,
selecting all countries, and entering DNS Servers
into the Exclusion Object. When a web page is
accessed and the packet monitor is used to
capture packets, you can see that all DNS query
packets are dropped by the Geo-IP filter.
100010