ArticlesArticles Most Popular ArticlesMost Popular Articles Most Helpful ArticlesMost Helpful Articles
RSS Feeds
DrillDown Icon Table of Contents Back
 . . . . . . . . . . . . .
DrillDown Icon Home
DrillDown Icon Cyberoam Security Appliances (UTM and NGFW)
DrillDown Icon Common Criteria (EAL4+) Compliant CyberoamOS
DrillDown Icon Version 10.X
DrillDown Icon Version 9.x
DrillDown Icon Release Notes
DrillDown Icon V 9.6
DrillDown Icon V 9.5.8 build 68 - For CR15i only
DrillDown Icon V 9.5.8 build 60 - For CR15i only
DrillDown Icon V 9.5.8
DrillDown Icon V 9.5.4
DrillDown Icon Release Notes
DrillDown Icon Known Issues
DrillDown Icon V 9.5.3 build 22
DrillDown Icon V 9.5.3 build 18
DrillDown Icon V 9.5.3 build 14
DrillDown Icon Archives
DrillDown Icon Guides
DrillDown Icon Getting Started Guide
DrillDown Icon IPS Release Notes
DrillDown Icon Application Filter Release Notes
DrillDown Icon Cyberoam Migration Assistant Guide
DrillDown Icon Cyberoam Virtual Appliances
DrillDown Icon Cyberoam Central Console
DrillDown Icon Cyberoam's On-Cloud Management Service
DrillDown Icon Cyberoam iView – Logging & Reporting
DrillDown Icon Clients
  Email This ArticlePrint PreviewPrint Current Article and All Sub-Articles
Rate Icon Rate Icon Rate Icon Rate Icon Rate Icon
 
Release Notes
Release Information
Compatible versions: 9.5.3 build 14 onwards  
Version 9.5.4 Build 92 - 7th November, 2008
Version 9.5.4 Build 86 - 4th September, 2008
Version 9.5.4 Build 80 – 6th August, 2008
Version 9.5.4 Build 74 – 22nd July, 2008
Version 9.5.4 Build 72 – 15th July, 2008
Version 9.5.4 Build 66 – 17th June, 2008

Upgrade Information
Upgrade type: Manual upgrade

Upgrade procedure
Download upgrade from http://downloads.cyberoam.com
Log on to Cyberoam Web Admin console and go to Help> Upload Upgrade and upload the file downloaded in step 1
Once the file is uploaded successfully, log on to CLI console and go to option 6 Upgrade Version and follow the on-screen instructions.
Compatibility Issues: None 

Introduction

This document contains the Release Notes for Cyberoam version 9.5.4 with the five builds - Build 66, Build 72, Build 74, Build 80 and Build 86.

It is a performance and maintenance release which includes new features, enhancements and several bugs solved in response to bug reports and beta version feedback that improves quality, reliability, and performance.

The following sections describe the release information in detail and provide other information that supplements the main documentation.

 

Features

1. Filter HTTPS traffic based on Domain names[1]

Cyberoam now filters HTTPS traffic based on Domain names using site Certificates.

Most of the content filtering solutions can detect and block the websites accessed over the HTTP protocol. To bypass these kinds of solutions, users use URL Translation or HTTP proxy websites hosted on HTTPS to access blocked sites. With this development, Cyberoam would be able to block these kinds of attempts to bypass the web content filter and sites hosted on SSL.

Protocols supported - SSLv2, SSLv3 and TLS

Certificate supported – X.509

By default, this option is enabled and can be disabled from Internet Access policy (IAP). Access denied message will not be displayed when access is denied.
 
2. Multiple Syslog server support[2]

Cyberoam now supports multiple syslog servers for remote logging. One needs to configure the facility, severity and log file format for syslog servers and logging location if multiple syslog servers are configured.

Maximum 5 syslog servers can be defined from Logs Configuration page of Web Admin Console.

Apart from firewall and Intrusion Detection and Prevention (IDP) logs, Cyberoam now also supports logging of following activities on syslog server:  AntiVirus,   AntiSpam, Content Filtering

Except for Traffic discovery logs, all the logs can be stored on the syslog server also.

Logging of various activities to syslog server can be enabled or disabled from the Logs Configuration page of Web Admin Console.
 
3. Support BGP protocol for Dynamic Routing[3]

Cyberoam now supports Border Gateway Protocol (BGP) for dynamic routing.

BGP is a path vector protocol that is used to carry routing between routers that are in the different administrative domains (Autonomous Systems) e.g. BGP is typically used by ISPs to exchange routing information between different ISP networks.

Cyberoam has implemented BGP version 4 as described in RFC 1771. Additionally, RFC 1997 (Communities Attribute), RFC 2796 (Route Reflection), RFC 2858 (Multiprotocol extensions) and RFC 2842 (Capabilities Advertisement) are also supported.

CLI Console provides the Cisco compliant CLI for routing configuration. Additionally, a firewall rule is to be configured for the zone for which the BGP traffic is to be allowed i.e. LAN to LOCAL or WAN to LOCAL.
 
4. HTTP upload report
Cyberoam Web Surfing report now provides details of HTTP upload activity carried out by each user. The following information will be available from the report: User name / IP address, URL, File name and size
 

Enhancements

Build 92

1.      Streaming media bypass

Cyberoam now has an ability to disable HTTP scanning of video and audio streams in order to avoid delays caused by scanning and downloading the entire stream prior to playing.  

By default, Cyberoam will scan video and audio files and one can disable from Antivirus, HTTP Configuration page of Web Admin Console. 

2.      Searchable Intrusion Prevention System (IPS) reports

IPS reports can now be searched by Source IP address, destination IP address, severity and signature name.


Build 86

Cyberoam has introduced a smooth method of tying two Administrative consoles - Web Admin Console and CLI, by embedding CLI link in Web Admin Console. Link to CLI can be clicked for the immediate access to CLI.
 
It initiates a telnet connection with CLI without closing Web Admin console, which avoids toggling between consoles especially when management service is to be restarted (RMS).
 
Console link is provided in the button bar in the top right most corner on each page of Web Admin Console.  
 
Behavior:
  • Cyberoam will not display any message like “RMS complete…” once management services are restarted. 
  •  After restarting management services, one will have to open a new session as existing session will automatically expire after restarting management services
  • After executing following commands from CLI: cyberoam check_disk data_partition, cyberoam check_disk system_partition, cyberoam repair_disk data_partition, cyberoam repair_disk system_partition, one will have to restart Cyberoam
Cyberoam from this version onwards provides the facility to monitor (capture) the dropped packets from Web Admin Console also. Till previous versions, it was possible to monitor from CLI only.
 
Report will provide packet header information and details on which module is dropping packets e.g. firewall, IDP along with information like firewall rule number, user and user group, Internet Access policy number etc.  This will help Cyberoam administrators to troubleshoot errant firewall rule.
 
Captured dropped packets can be exported or searched by the following parameters: source and destination host, port, protocol and interface.
 
Utility can be accessed from Diagnostic tool.
 
For searching and using the doclet information, Dashboard Doclet Information can now be copied. For example, Signature name displayed in the “Recent IDP Alerts” doclet can be copied and used as a searching criteria in Search IDP Signature to get the signature details.
 

Build 80

1.      VPN policy Templates

To make VPN connection configuration an easy task, following four default VPN policies are included for frequently used VPN deployment scenarios:
  • Road warrior
  • L2TP
  • Head office connectivity
  • Branch office connectivity

 2.      Block access of restricted sites through Google and Yahoo language translation services

Cyberoam can now block web access through the language translation services of yahoo and google which is used as a proxy to access the restricted sites. A language translation service instantly translates text and web pages.

For example,
If the access to www.monster.com is blocked by blocking JobsSearch category, then user will not be able to access the site using google and yahoo translation services.

 3.      Configurable action for invalid HTTP traffic

Cyberoam can now be configured to accept invalid traffic through HTTP port i.e. allow traffic not following HTTP protocol. 

The configuration can be done via the “set http_proxy relay_http_invalid_traffic” command from the CLI Console. 

By default, Cyberoam is configured to not to relay such traffic. 

4.      Web Admin Console change

From this version onwards, one has to configure trusted ports only once. Prior to this previous version, one had to configure HTTPS and HTTP trusted ports separately. 

  

Build 72

  1. Dashboard System Status Doclet includes secure scanning status (enabled or disabled) configured on CLI console.
  2. Two additional file types - Flash Video File (.flv) and Shockwave Flash Format File (.swf) are included in default File type category.
  3. VPN logs are included in debug file generated from CLI console.

Build 66

1. Optimization of Startup time

Startup time is reduced by approximate 35% to 45% across various models. This was achieved by performing some maintenance tasks like re-arranging booting sequence, removing obsolete files. But Cyberoam may take time to startup if it goes down abruptly e.g. after power failure.
2. Support Asymmetric routing environment[4]

Cyberoam being a stateful firewall, tracks the traffic connection state. Due to this, Cyberoam drops the packets if both the outbound and return packets do not traverse through Cyberoam.

In asymmetric routing environments, either outbound or return packets are seen by Cyberoam. Up till previous versions, it was not possible to deploy Cyberoam in such environments.

Administrator can now configure source and destination host or network tuple from which such traffic is to be allowed from CLI console.  

By default, Cyberoam will drop the packets if both the outbound and return packets do not traverse through Cyberoam. Use set advanced-firewall-bypass-stateful-firewal-config command to set such networks.
 
3. Multiple Active directory support
Cyberoam now supports configuration of multiple Active Directory servers for user authentication. Cyberoam can be configured to authenticate users via HTTP client or Single Sign on Client. To logon using HTTP Client, users are required to specify user name along with the domain name.
 
4. Configurable action for Mid-stream TCP connections[5]

Cyberoam can now be configured to pick up TCP connections in mid stream. Enabling midstream pickup of TCP connections will help while plugging in the Cyberoam appliance as a bridge in a live network without any loss of service. It can also be used for handling network behavior due to peculiar network design and configuration. E.g. atypical routing configurations leading to ICMP redirect messages.

The configuration can be done via the “set advanced-firewall midstream_connection_pickup” command option in the CLI Console.

By default, Cyberoam is configured to drop all untracked (mid-stream session) TCP connections in both the deployment modes.
 
5. VLAN tags preservation in bridge mode for scanned traffic

From this version onwards, VLAN (Virtual LAN) tags will be preserved even when antivirus scanning, spam filtering and web filtering using Internet Access Policy (IAP) are applied to VLAN tagged traffic in Bridge mode.

In the earlier versions, VLAN tags were not preserved when scanning or Internet Access Policy was applied on the traffic.
6. Spam detection performance improvements
  • Enhanced image-spam detection algorithms
  • Optimized operation by fine-tuning parameters to improve performance and to save bandwidth
  • Improved detection of spam and malware in nested messages
  • Added HTTP connection pooling between the Anti Spam Engine and the Anti Spam Center
    Improved local caching and classification performance

 

Support multiple Host Group membership

Cyberoam now supports membership of single host in multiple host groups.

8.      Dependency of restarting management services removed

It is now not required to restart management services (RMS) for the following actions: 

  • defining Network in Auth Network[6]
  • subscribing any of the modules
  • enabling or disabling any of the System modules

9.      Ability to switch on/off traffic discovery history log[7]

Traffic discovery history log can now be turned off from the Configure Autopurge Utility page of Web Admin Console.

If logging is enabled, then one can also specify number of days up to which logs should be retained. For example, if you specify 5 days, on the 6th day, the logs of the first day will be removed.

By default, logs are retained for 7 days.

10. Utility to monitor dropped packets[8]

A packet capture command is added on the CLI console to help Administrators view dropped packets. It will provide connection details and details on which module is dropping packets e.g. firewall, IDP along with information like firewall rule number, user, Internet Access policy number etc. This will help Cyberoam administrators to troubleshoot errant firewall rules.

Use CLI command “packet-capture” to generate the packet dump.

11. Visibility to Spyware infected computers on Dashboard[9]

“Recent Spyware Alerts” - doclet is added on the Dashboard to provide an instant visibility to spyware infected hosts. Alert provides username to help identify the spyware infected computer and take the immediate corrective action.

Cyberoam constantly monitors and provides alert on the Dashboard on detecting spyware and also blocks Spyware “phone-home” traffic and other related backdoor traffic. Dashboard alert will be provided if any applications, laptops or desktops are secretly phoning home.

Cyberoam detects “phone-home” traffic with IDP signature.

12. CLI console improvements

  • Show network interface will now display interface information as per the Cyberoam nomenclature e.g. Port A, Port B instead of eth0, eth1
  • MTU can now also be configured when Cyberoam appliance is configured in transparent mode
  • MTU and MSS values can now be configured from the Cyberoam Console option (set network command) and Cyberoam will now automatically configure MSS value on enabling PPPoE on the WAN interface. MTU and MSS configuration option from Network Configuration menu has been removed.
  • Cyberoam Console option – “set network interface” command now allows configuration for the physical interfaces only. In case Cyberoam is deployed in transparent mode, only one interface would be available for configuration. In the earlier versions, Cyberoam displayed all the Ethernet interfaces including alias, ipsec and lo. 
  • Following HTTP proxy commands[10] are added

Command

Description

Default value

set http_proxy av_session

No. of files scanned simultaneously

20

Allowed range:1 to 64

set http_proxy dns_threads

No. of simultaneous DNS requests that can be handled by Proxy server

5

Allowed range: 1 to 128

One may need to increase when Cyberoam is used as Proxy server or DNS response time is high (when DNS server is responding slowly)

set http_proxy client_session

No. of simultaneous client session

1024

Allowed range: 1024 to 8192

One may need to increase when DNS server is responding slowly or number of simultaneous requests are high

set http_proxy rw_buffer_size

Size of read/write buffer

4 Kbytes

Allows range: 1 to 16 Kbytes

One can increase in-case of high speed WAN link.  

set http_proxy X-Forwarded-For

Include/Exclude X-Forwarded-For header information from outbound HTTP requests

OFF

Applicable only in transparent mode.

set http_proxy deny_unknown_proto

Allow/deny traffic not following HTTPS protocol i.e. invalid traffic through HTTPS port

YES

set http_proxy debug

Run proxy in debug mode

OFF

set http_proxy core_dump

Generate dump

OFF

13. Dashboard Alert message on failure to apply Firewall rule

Cyberoam will now display Alert messages on Dashboard incase Cyberoam fails to apply any of the firewall rule on RMS (Restart Management Service), appliance reboot, or after adding, deleting or updating firewall rule. Message will prompt to “Rebuild Firewall state” from CLI console.

14. Configurable action for ICMP error message tracking[11]

In the earlier versions, in-case of ICMP error, by default, Cyberoam deleted existing connection from its internal connection state.

This option can now be disabled from the “set advanced-firewall” command from CLI Console.
 
Behavior information

Build 92

Following logs can be retained for maximum 90 days: Mail Virus log, Mail Spam log, IPS log, FTP log and Appliance Audit log. Previous versions allowed to retain logs for 60 days.

Build 86

Alert message on failure to apply Firewall rule will be logged as Firewall rule log and can be from CLI console. One can use the command “show firewall-rule-log” to view the alerts.

From this build onwards, they will not be displayed on Dashboard.

Build 80

From this build onwards, default LAN to WAN (Any Host to Any Host) firewall rule will allow traffic to flow between the virtual host and the network. Prior to this version, one had to create firewall rule for the Virtual host to function, and to allow traffic to flow between the virtual host and the network.

Build 66

  • Web Surfing logs can be retained for 365 days instead of 60 days
  • HA failover timeout is reduced to 3 seconds. In earlier versions, failover was instant. After failover, all the Auxiliary sessions will timeout after 5 minutes if there is no traffic flow on the connection.
  • When Cyberoam is deployed in transparent mode and is used as a direct proxy, LAN to WAN or WAN to LAN firewall rule is to be defined.
  • For PPPoE connections, LCP echo request and reply can be disabled by setting LCP Interval and LCP Failure as zero from the Manage Interface page of Web Admin Console.
  • After disabling HA, network configuration will be preserved on Auxiliary appliance. Till previous versions, factory defaults were restored on Auxiliary appliance on disabling HA. After disabling HA, to remove Auxiliary appliance from the cluster and use independently, reset HA from Auxiliary appliance and change IP schema through Network Configuration Wizard.
  • Report are not synchronized when HA is configured.
  • Cyberoam will now automatically reboot on kernel crash. Till previous versions, Administrator had to manually restart the system.
  • Host name can include only alphanumeric characters and special character “.” Till previous versions, special characters “_” and white space were also allowed.
  • DHCP service cannot be configured on Interface alias or virtual sub interface. Till previous versions, it was possible to configure.
  • By default, IDP logs are not archived. One needs to enable from Configure Autopurge Utility.

Discontinued Feature

Bugs solved

The purpose of this list is to give an overview of the bugs fixed in the various builds current release. The ID denotes the internal Cyberoam bug tracking ID and the description explains problem.
 

Build 92

Command Line Interface (CLI) over Web Admin Console

Bug ID - 6321
Description - High CPU usage is triggered when system date is updated from CLI through Web Admin Console.  

Firewall

Bug ID – 5470
Description – When multiple administrators are performing any operation a firewall rule simultaneously, firewall configuration error occurs. Due to this, sometimes a firewall rule is created without the host group hence Dashboard flashes the message to rebuild firewall state.  

HTTP Proxy

Bug ID – 6157
Description –  When WAN to LOCAL firewall rule with Pharming or virus scanning is enabled, there is an potential vulnerability of  Cyberoam acting as an open proxy  

Internet Access policy

Bug ID – 6382
Description – One needs to restart management services to apply custom Internet access policy.

Intrusion Detection and Prevention (IDP)
Bug ID – 6395
Description – Even when the IDP module is not subscribed, signatures included in "cyberoam signatures" category were working. By default, only custom signatures should work when IDP module is not subscribed.


Logs & Reports

Bug ID – 6323
Description – “Google search keywords” proactive report is sometimes mailed without username or IP address.

System

Bug ID – 5466
Description – On clicking “Preview” button on System>Configure>Customize Denied Message page, instead of displaying preview of custom access denied message, blank page is displayed. 
 
Bug ID – 5620
Description – On restarting management services, error “Restarting Management Service .........Failed : Route to destination already exists”. This error occurs when duplicate route entry exists in the routing table. 
 
Bug ID – 5913
Description – Traceroute functionality does not work with URL but works with IP address. For example, when one tries to determine the route for newwebmail.elitecore.com, result is not displayed but when one tries with 203.88.138.194, result is displayed. 
 
Bug ID – 5957
Description – Ping functionality used to check gateway reachability does not work when one tries to ping a URL but works when the IP address of the same URL is pinged. For example, when one pings for newwebmail.elitecore.com, ping result is not displayed while when 203.88.138.194 is pinged, result is displayed. 
 
Bug ID – 6143
Description – Virtual host stops working under certain circumstances.
Bug ID – 6378
Description – At the time of configuring custom denied message for any custom category, Cyberoam does not allow selecting the required category but randomly selects a category from the list.
Bug ID – 5773
Description – When multiple links are terminated on Cyberoam and Net-to-Net IPSec connection and Road Warrior connection are configured on two different links, instead of serving requests through different gateways, all the requests are served by only one gateway. 

Bug ID – 6184
Description – When high numbers of VPN tunnel are configured, on doing an RMS, the VPN tunnels get deactivated.

Web Admin Console

Bug ID – 6065
Description – If one tries to re-position the Dashboard Doclets by dragging and dropping when IDP Engine has stopped, Dashboard Doclet alignment is lost.

Workaround – Restart IDP Engine from Manage IDP page and then reset the Dashboard.

Bug ID – 6112
Description – “Recent IDP Alerts” doclet on Dashboard displays on additional column. 
 

Build 86

Bandwidth policy

Bug ID – 5791
Description – When HTTP virus scanning and content filtering is enabled (Internet Access policy is configured), file downloading speed reduces drastically. 

CLI console

Bug ID – 5909
Description – Word “cyberoam” is incorrectly spelled in the tcpdump command help. Help reads as “filedump   Dump packets in a file. Download file from http://<cyberooam_ip>/documents/tcpdump.out” but it should read as “filedump   Dump packets in a file. Download file from http://<cyberoam_ip>/documents/tcpdump.out”

HTTP Proxy

Bug ID – 5209
Description – When Upstream Proxy (Parent proxy) IP address is configured same as Cyberoam WAN interface IP address, Cyberoam is not able to establish connectivity with Cyberoam Registration server as a result it is not possible to register Cyberoam appliance.

Logs & Reports

Bug ID - 5715
Description - Data field sequence mismatch in tabular and CSV format of Top 10 users by Data transfer report(Internet Usage > Organization-Wide).

Bug ID - 5855
Description – Cyberoam does not forward Firewall logs to the remote logging server.

System

Bug ID – 5104
Description – Cyberoam incorrectly allows to configure Gateway IP address in a non-standard IP address format from Network Configuration Wizard and Manage Gateway Page of Web Admin Console.

Bug ID – 5692
Description – Ping and Traceroute functionality used to check gateway reachability is not working.

Bug ID – 5516
Description – When ZoneEdit is configured as Dynamic DNS, it does not update its database whenever Cyberoam’s External Interface IP address changes. Manage Dynamic DNS page displays “Could not connect to www.zoneedit.com

Bug ID – 5788
Description – When Shutdown button is clicked on Manage Server page, Cyberoam restarts instead of shutting down. This behavior is observed only in Cyberoam Appliance CR 250i.

Bug ID – 5772
Description – Customize Client Preference does not support URLs ending with “.local”    as home page

VPN

Bug ID – 5693
Description – Cyberoam incorrectly allows to delete PPTP and L2TP users from Manage Active page. But, deleted users are displayed on PPTP and L2TP Configuration page.
Bug ID - 5278
Description – At the time of adding PPTP and L2TP users even when group is not selected, Error message is not displayed. Cyberoam should display message as “Select at least one Group”.

Same behavior is observed at the time of deleting users.

Bug ID - 5908
Description – Cyberoam incorrectly retains and displays the Dashboard “Rebuild Firewall state” Alert even after upgrading Cyberoam if Cyberoam has failed to apply any of the firewall rule before upgrading Cyberoam.

Build 80

Categorization

Bug ID – 5564
Description – Default Web category name is spelled incorrectly as “PesonalAndBiographySites’. It should be spelled as “PersonalAndBiographySites’

Data transfer policy

Bug ID – 5439
Description – Monthly Data transfer policy does not work as per the configuration. For example, 5 GB per month data transfer quota is configured for the user but user is able transfer only up to 1.

Firewall

Bug ID – 5523
Description – Even when Web and Application Filter module has expired, Cyberoam blocks all the HTTPS traffic.

Bug ID – 5637
Description – After adding a new LAN zone, default LAN to WAN firewall rules are not added automatically.

Groups

Bug ID – 5116
Description – Incomplete Add Group page is displayed when not a single data transfer policy is configured. As a result it is not possible to add a new user group. In other words, one needs to configure at-least one data transfer policy to add a group.

Intrusion Detection & Prevention (IDP)

Bug ID – 5582
Description – IDP module triggers high CPU usage when IDP engine restarts frequently. This happens because, Cyberoam generates an alert every time IDP engine restarts and when IDP engine restarts frequently, more number of alerts are generated which results into high CPU usage.

Logs & Reports

Bug ID – 5530
Description – Data fields sequence mismatch in the tabular format and CSV format of IDP reports.

Bug ID – 5552
Description – There is mismatch in URLs listed in User wise blocked attempts report and its drill down report

Bug ID – 5614
Description – By default, HTTP and FTP logs are enabled and stored on Cyberoam Appliance itself and Cyberoam does not provide any provision to disable them. But, after updating the logging configuration, Web Admin Console incorrectly displays them as disabled.

Bug ID – 5634
Description – When Cyberoam is configured as Proxy, one cannot access secure sites if content filtering log is disabled from Web Admin Console

System

Bug ID – 3755
Description – Under the testing environment it is found that when multiple gateways are defined on Cyberoam, gateway parameters are not defined uniquely for each gateway. The exact configuration parameters that trigger this situation are not known. If you face this problem, you are requested to contact at support@cyberoam.com with the scenario details.

Bug ID – 4995
Description – When Cyberoam is configured as a Browser proxy, users are not able to access the sites like www.scdl.net which are hosted on the server on which DNS-based load balancing is implemented. This is because; Cyberoam receives a different IP address for the same site from DNS.

Bug ID – 5258
Description – After restoring backup of version 9.5.4 build 27 on version 9.5.4 build 55, mail ID in Backup schedule is not preserved. Due to this, one does not receive the backup mails.

Bug ID – 5414
Description – Applications like Gtalk, Skype using port 443 but not following SSL standard are not accessible i.e. when Certificate based Categorization (HTTPS) is enabled from Internet Access policy.

Bug ID – 5465
Description – Cyberoam incorrectly allows Inactive user with Administrator privilege to logon to Web Admin Console.

Bug ID – 5675
Description – After restoring backup of version 9.5.3 build 22 on version 9.5.4 build 78, incomplete Logs Configuration page is displayed in Web Admin console.

Bug ID – 5670
Description – While changing the Cyberoam deployment mode from transparent to route through Network Configuration Wizard, Cyberoam allows to configures additional port with the duplicate Gateway name.

Bug ID – 5480
Description – User Migration Utility imports users from Active Directory without domain name. Due to this, users cannot be authenticated and hence they cannot establish PPTP or L2TP connection.  

Virtual host

Bug ID – 5638
Description – IP based Virtual host does not work as per the configuration after restarting management services. 

Virtual Private Network (VPN)

Bug ID – 5445
Description – When VPN policy is configured with different PFS (Perfect Forward Secrecy) value at both the peers, VPN service frequently restarts i.e. PFS is configured for one peer but not configured for another peer. 

Bug ID – 5480
Description – User Migration Utility imports users from Active Directory without domain name. Due to this, users cannot be authenticated and hence they cannot establish PPTP or L2TP connection.
 

Build 74

Categorization

Bug ID – 5609
Description – Certain default categories were not included in CIPA Internet Access policy.

Firewall

Bug ID – 5599
Description - After upgrading to version 9.5.4 build 72, Cyberoam does not preserve any WAN to LOCAL firewall rules configured with DNAT policy. Due to this, Internal servers became inaccessible from the WAN side.

By default, they should be preserved but after upgrading to version 9.5.4 build 72 one has to create virtual host for the servers to forward the request.

Bug ID – 5621
Description – When specific outgoing gateway is configured through Firewall rule, Cyberoam did not route the traffic through the configured gateway.

 

Build 72

Antivirus

Bug ID – 5392
Description – When mail attachments are blocked, Disclaimer or signatures are not added to the mails.

Bug ID – 5408
Description – HTTP proxy restarts when one tries to search URL category (Categories>Web Category>Search URL) or add/delete keyword and domains in Custom Web category.

Bug ID – 5448
Description – After configuring special character hash (#) in URL Regex for HTTP scanning rule, blank page is served instead of HTTP configuration page.

Firewall
Bug ID – 4575
Description – LAN to LAN Virtual host rules gets executed automatically at midnight.

Bug ID – 5397
Description – Instead of replacing the modified default rules, Cyberoam Central Console (CCC) pushes modified default firewall rules as a new set of default rules and adds them at the top of the list in Cyberoam.

Bug ID – 5454
Description – Dashboard Alert "System failed to apply firewall rule(s)" is displayed when virtual host with UDP port forwarding is configured as destination host in firewall rule.

Bug ID – 5455
Description – After changing the addressing mode of the WAN interface from PPPoE to Static, proxy ARP entry for the Virtual host is not updated. Due to this, Internet users were not able to access the internal servers.

Bug ID – 5471
Description – Cyberoam should not be accessible from WAN side when access is denied from Local ACL. But, it is possible to access Cyberoam when virtual host for WAN interface with traffic port forwarded to LAN IP is configured as a destination host for WAN to LAN drop firewall.

Bug ID – 5536
Description – Host name cannot include special characters space or underscore but when one tries to include them incorrect error message appears. The message reads “Enter valid Host name. Only alphanumeric characters, space, dot and ‘_’ allowed“ but should read as “Enter valid Host name. Only alphanumeric characters and dot allowed.”

Bug ID – 2385
Description – Incorrect Access Deny message is displayed when access to “All Web Traffic” category is not allowed.
 

Intrusion Detection and Prevention

Bug ID - 5315
Description – After upgrading to Signature Database version 2.4.7, IDP Engine uses high CPU. Due to this unpredictable traffic behavior is observed in the traffic on which IDP policy is applied.

Bug ID - 5559
Description - High number of IDP alerts triggers high CPU usage

Logs & Reports

Bug ID – 4515
Description – Google Search keywords report included URL encoding characters e.g. + or %

SNMP

Bug ID – 5123
Description – Cyberoam hangs every 5 minutes after starting SNMP server.

Bug ID – 5417
Description – When user gives incorrect username or password at the time to logon to MyAccount, incorrect error message appears. The message reads “Error in Authenticating, contact the administrator if problem persists” but should read as “Wrong username or password”

Bug ID – 5432
Description – At the time of changing user password, Cyberoam displays “You must enter valid email ID” message when email ID is left empty. As email ID is not a mandatory field, Cyberoam should not give this error message.

Bug ID – 5447
Description – After upgrading Cyberoam from version 9.5.3 build 22 to version 9.5.4 build 66 one needs to restart management services manually to access Cyberoam Web Admin Console.

Bug ID – 5460
Description – Cyberoam does not support special character underscore in group name but when one tries to include incorrect error message appears. The message reads “Enter valid Group name. Only alphanumeric characters, space and ‘_’ are allowed.” but should read as “Enter valid Group name. Only alphanumeric characters and space are allowed.”

Bug ID – 5507
Description – After upgrading Cyberoam from version 9.5.3 build 22 to version 9.5.4 build 66 Syslog configuration is not retained.

Bug ID – 5509
Description – On resetting Cyberoam to factory defaults, DHCP client configuration is not retained if Cyberoam WAN interface is configured as DHCP client.
 

Traffic Discovery

Bug ID – 5418
Description – Download and upload data transfer column are transposed in Traffic discovery reports.

Web Admin Console

Bug ID – 5419
Description – ”HateAndRacism” category is included multiple times in CIPA Internet Access policy.

Bug ID – 5420
Description – Font size is not consistent on all the configuration pages of Network Configuration Wizard.

Bug ID – 5478
Description – One can configure username and password without enabling “Authentication Required” from Configure Mail Settings page of Network Configuration Wizard.

Bug ID – 5519
Description – Even when by default, HTTP and FTP Antivirus logs are enabled, HTTP and FTP Antivirus log checkboxes are unchecked and “greyed out” 

Build 66 

Anti Spam

Bug ID – 3549
Description – Cyberoam does not detect spam mails if parent proxy is configured.
 
Bug ID – 4510
Description – Quarantine area is rotated only when the area is full. Due to this, there is mismatch in percentage utilization of Quarantine area and actual mails displayed in the area. For example, total area utilized is 10% but repository does not display any mails.
 
Bug ID - 4634
Description – "From Email Address" field accepts invalid email address in the Spam policy
 
Bug ID - 4635
Description – When action defined for spam mail is “Prefix Subject” and MIME header filter contains a comma (,), Cyberoam forwards scanned mails without adding prefix to the original subject. 
 
Bug ID - 4761
Description - Users are not able to open the Quarantined (Spam and Virus) mails in any of the mail clients.  Users are required to save the mails in EML format to open the mails in Outlook Express as Cyberoam downloads’ mails in HTML format.
 
Bug ID – 4814
Description – Anti Spam General Configuration page displays incorrect status of Cyberoam Anti Spam Center.
 
Bug ID – 4984
Description – Quarantine Spam mails are not displayed in User My Account.
 
Bug ID – 5293
Description – Only last 7 days quarantined mails were displayed in Quarantine report as well as in Self Service Quarantine area (User My Account). Due to this, there is data mismatch in Quarantine report and Quarantine utilization area.

Anti Virus

Bug ID - 4159   
Description - Mismatch in AV scan time displayed on Captured Connection page and "Search Captured Sessions" page of HTTP Statistics when AV scanning disabled.
 
Bug ID - 4519
Description – Cyberoam allows to configure file size threshold as zero for HTTP scanning. Cyberoam does not scan files when file size threshold is configured as zero.

Bug ID - 4522
Description – Incomplete virus name is displayed in "Recent FTP Viruses detected" section of Dashboard

Bug ID - 4633
Description – SMTP Email scanning rule names can include special characters like !@#$
 
Bug ID – 4665
Description – When HTTP scanning is enabled in Real mode, browser hangs while accessing following sites: http://tw.movie.yahoo.com, http://www.ipower.com/support, http://ctworld.org.tw

Bug ID – 4667
Description – Cyberoam failed to display virus alerts on Dashboard and generate Syslog report in high traffic environment.

Bug ID – 4790
Description – When “Video” file type attachment is blocked, Cyberoam blocks both “Video” and “Image” file type attachments. 
 
Bug ID – 5065
Description - When virus scanning is enabled, Rediffmail website does not open.
 
Bug ID – 5227
Description – Anti-virus engine does not start after upgrading to version 9.5.4 build 55

Bug ID - 5290
Description - User My Account Quarantine Mail reports incorrectly displays Spam mails detected by POP/IMAP proxy as Quarantine mails.

Bug ID – 5297
Description – When HTTP scanning is enabled and Internet Access policy is configured, Yahoo mail attachment can not be send. This behavior is observed only with Internet Explorer 6.

Bandwidth policy

Bug ID - 4345
Description - Priority level 4 is not displayed in Bandwidth policy

Categorization

Bug ID – 3476
Description – When no matching URL is found as per the search criteria, the “Search URL” option of Web category displays incorrect message.
 
Bug ID – 4904
Description – It is possible to create Custom File Type category with multiple file extensions specified on multiple rows using <Enter>

Bug ID – 5083
Description – When multiple File type Extensions are specified using “Enter” button while creating custom web category, the category does not work as expected.

Command Line Interface (CLI)

Bug ID - 4644           
Description – CLI Console command "cyberoam service status" gives following error and does not generate a Debug log file. This situation occurs only if log file generation command is executed when Cyberoam is writing log records to a log file.
Error:
tar: cyberoam_tomcat.log: file changed as we read it
tar: Error exit delayed from previous errors

Bug ID – 5233
Description – Latency observed when one tries to log on to CLI console due to reverse IP address lookup.

Bug ID - 5366
Description – ARP entry for Virtual host can not be deleted from CLI console.

Bug ID – 5367
Description – When Cyberoam is configured in transparent mode, Interface speed can not be configured.

Firewall

Bug ID - 4880
Description – Changes in grouped Services are not reflected in Service Group.

Bug ID – 5384
Description – Firewall rules based on Custom Application Protocol category does not work as expected.

Group

Bug ID - 4645   
D
escription – Manage Group page displayed "Data Transfer Policy Bean" (incorrect spelling) instead of "Data Transfer Policy Name"
 
Bug ID – 4703
Description – Save operation does not ask for confirmation before saving the Login restriction changes from the Change Group IP restriction page (Web Admin Console).
 
Bug ID – 4704
Description – When user is allowed login from specific nodes, Edit Group page does not display login nodes details.

Bug ID – 4705
Description – After adding IP address for login restriction, Change Group IP Restriction page is displayed without header

Bug ID – 5074
Description – At the time of creating or updating group, if "%" is included in group name, a Java error is displayed.
 

High Availability

Bug ID - 4414           
Description – HA synchronization process does not synchronize BGP configuration
 
Bug ID - 4415           
Description – Cyberoam allows to configure (add and delete) BGP routes from the Auxiliary appliance of HA cluster.
 
Bug ID - 4430           
Description – If SSH communication on the dedicated link fails, synchronization process remains incomplete. Due to this, Configure HA page displays primary appliance as Active and auxiliary as a stand-alone appliance even when HA is enabled.
 
Bug ID - 4441           
Description – It is possible to configure static routes from Auxiliary appliance of HA cluster.
 
Bug ID - 4455           
Description – Incorrect message "Applicable for primary node only when both nodes are UP" is displayed when HA load balancing is disabled from Auxiliary appliance (CLI console).
 
Bug ID - 4567           
Description – In Active-Passive HA cluster, if HA is disabled while synchronization process is going on, cluster becomes unstable.
 
Bug ID - 4625           
Description – In an Active-Passive HA cluster, deleting VPN connection on the Primary appliance does not delete connection from the Auxiliary appliance.
 
Bug ID - 4643           
Description – After failover in Active-Passive HA Cluster, it is not possible to establish Certificate based Net-to-Net VPN connections.

Bug ID - 4651
Description - In Active-Passive HA cluster, after changing any network configuration from CLI console (Option 1 Network Configuration), all the logged in users on Primary appliance do not get logged in automatically on Auxiliary appliance.   

Bug ID – 4694
Description – In Active-Passive cluster, cluster becomes unstable when multiple events occur simultaneously e.g. dedicated link status changes during the failover process.
 
Bug ID – 4758
Description - When an Appliance configured with VLAN and Alias, is configured as an Auxiliary appliance in Active-Passive HA cluster, Cyberoam does not remove VLAN and Alias configuration.
 
Bug ID - 4901
Description – After restarting management services from Primary appliance of Active-Passive cluster, Auxiliary appliance can not be accessed with Auxiliary Administration IP.
 
Bug ID - 4972
Description – If an Appliance configured with DHCP is configured as an Auxiliary appliance in Active-Passive HA cluster, Cyberoam does not remove DHCP configuration from the appliance.
 
Bug ID – 5219
Description – HA could not be configured due to improper configuration of HA service.
 
Bug ID - 5264
Description – HA synchronization process does not synchronize Local ACL
 
Bug ID – 5375
Description – At the time of enabling HA, sometimes both the Appliances in HA cluster respond to the ARP request.
 
Bug ID – 5376
Description – After HA failover, IP address added in Proxy ARP does not work as expected.
 
Bug ID – 5377
Description – Proxy ARP does not work after restoring backup on a different appliance, but works if backup is restored on same appliance.

Internet Access Policy

Bug ID – 4907
Description – It is possible to create Internet Access policy with the name including all the special character like @ # $%. Now Cyberoam will allow only alphanumeric characters, space and underscore (_) in the Internet Access policy name. 

Intrusion Detection and Prevention (IDP)

Bug ID – 4697
Description – Warning or Update successful confirmation message is not displayed when IDP engine status changes or signature database is updated successfully.
 
Bug ID – 4773
Description – Administrator receives “root partition full” error mail when an IDP alert file becomes full and the update or delete operation is not completed.
 
Bug ID - 5365
Description – After updating IDP category, one needs to restart IDP daemon manually from Web Admin console.

Logs and Reports

Bug ID - 4616
Description – Sometimes "NULL" is displayed as Category name in "Top 10 Categories (by Hits)" web surfing report when Cyberoam is configured in transparent mode.

Bug ID – 4618
Description – User wise Web Surfing report displays junk characters in IP address column

Bug ID - 4678
Description – Cyberoam does not preserve Syslog configuration on upgrading from V 9.3.0 build 09 to V 9.5.3 build 18. Hence, one has to re-configure Syslog after upgrading.

Bug ID – 4682
Description – An invalid IP address can be configured for Syslog server from Manage Syslog page of Web Admin console.

Bug ID – 4688
Description – Syslog configuration is not included in backup.

Bug ID – 4689
Description – Update successful confirmation message is not displayed after updating log configuration from Logs Configuration page.

Bug ID – 4700
Description – No validation is performed on email addresses configured in Bypass Email Ids page for Reports.
 
Bug ID - 4730           
Description – When the report END DATE is selected as current date for Appliance Audit log and Event log Cyberoam does not generate logs nor displays the Error message. 
 
Bug ID – 4748
Description – Title bar displays incorrect title for all the Compliance reports.
 
Bug ID - 4966
Description – Cyberoam does not preserve Syslog configuration on upgrading from V 9.3.0 build 22 to V 9.5.4 build 43. Hence, one has to re-configure Syslog after upgrading.
 
Bug ID – 4986
Description – Pie-chart for Daily and weekly proactive reports is not generated when there is no data to populate the graph. Due to this, Proactive reports are mailed without any proper message.

Bug ID – 5005
Description – HTTP File Upload report provides option of viewing report in graphically format even when it is not possible.

Bug ID – 5006
Description - Incase of Password Change event, action column of Audit log displays “Null” instead of the action description.

Bug ID – 5008
Description – When data for Data Transfer Report by User (Internet Usage>By User) spans over multiple pages, “Next” button is displayed but does not work.

Bug ID – 5164
Description – Certain events are not logged in IDP logs due to segmentation fault.  

Multiple Gateway

Bug ID – 5055
Description – In-case of multiple gateways, Cyberoam sends multiple email alerts of gateway status even when gateway status is not changed. 

PPPoE

Bug ID – 4784
Description – It is not possible to remove PPPoE interface using Network Configuration Wizard.

Bug ID - 4785
Description – Cyberoam incorrectly allowed to update the gateway IP address of PPPoE-enabled interface from Web Admin Console.
 
Bug ID – 4925
Description – It is not possible to update the weight of the PPPoE gateway.

Bug ID – 5274
Description – Cyberoam supported only 25 characters for PPPoE username. Now it supports 60 characters.

Bug ID - 5369
Description - On restarting management services (RMS), PPPoE client is killed.

Proxy

Bug ID – 2336
Description - Allowing Application categories or file type categories in “Deny All” Internet Access policy does not work. From the current version onwards, support to allow Application category in “Deny All”, Internet Access policy is removed.
 
Bug ID - 3942
Description - If “Restrict HTTP Upload” category is denied, users are not able to send mails using Gmail. Instead of blocking the messages with attachment, user is denied the access to Gmail itself.
 
Bug ID – 4171
Description – As Cyberoam does not support Active FTP, when FTP scanning is enabled, attempts to connect to an active mode FTP server gives “451 Proxy unable to comply” error.

Bug ID - 4276
Description – Web Surfing reports display User name as "Unknown" if user is not logged in and tries to download virus when Cyberoam is configured as HTTP Proxy.
 
Bug ID – 4325
Description – After changing default HTTP proxy port, Audit log are not generated for the event.
 
Bug ID – 4490 
Description – Due to incorrect HTTP header parsing, certain sites like www.cada.fr were not accessible.
 
Bug ID – 4525
Description – HTTP downloads fail with AV scanning and transfer-encoding is set to chunk. Due to this, websites like http://www.anindakapinda.com failed to open.

Bug ID - 4526           
Description – Custom Web category cannot be created if HTTP Proxy is not running.
 
Bug ID - 4604
Description – When HTTPS Categorization (from Internet Access policy) is enabled in transparent mode, users are not able to access secure (HTTPS) sites.
 
Bug ID – 4988
Description – HTTP Proxy sends multiple IP Address information when IP lookup sites/tools e.g.www.whatismyipaddress.com, returns multiple IP Addresses.
 
Bug ID - 5113
Description - FTP proxy restarts due to assertion failure.

With Windows FTP client, Cyberoam now will give “Proxy unable to comply” message instead of restarting proxy, if server closes the connection before the process is complete.

Bug ID – 5213
Description - Parent proxy configuration is retained even after disabling the parent proxy setting from Configure HTTP Proxy page of Web Admin Console.

Bug ID – 5278
Description – POP, IMAP and FTP proxy restarts frequently under heavy traffic.

Bug ID - 5282
Description - FTP Proxy hangs if session is terminated by FTP Client before file transfer process is complete.
 
Bug ID - 5295
Description – FTP client hangs after it receives negative response from FTP server. This behavior is observed only when the initial response of FTP server is positive. For example, when client is uploading a 500 MB file and available space on server is only 200 MB, server will initially send positive response and later when no space is available it will send negative response.
 
Bug ID – 5309
Description – Due to header parsing problem, HTTP Proxy restarts.
 
Bug ID – 5368
Description – After changing the default port of HTTP proxy, BGP and HA cannot be configured.

Bug ID – 5371
Description – When HTTP proxy is configured on non-standard port, HTTP proxy does not work after restoring backup.

System
Bug ID – 2237
Description – Backup of Cyberoam Appliance models CR50i, CR 100i, CR250i, and CR500i can not be restored on CR1000i or CR1500i

Bug ID - 2437
When Cyberoam is deployed in transparent mode, Manage Gateway page on the Web Admin Console displays incorrect Ethernet Port IP address.
 
Bug ID – 3315
Description – DHCP server does not lease IP address from the secondary interface when two LAN interfaces are configured.

Bug ID – 3934
Description – If a DHCP service is configured on the Interface Alias, DHCP server is not able to lease IP address. From the current version onwards, one will not be able to enable DHCP server on Alias IP Interface
 
Bug ID – 4179
Description – Even when custom login and logoff messages are configured, instead of custom login and logoff messages, Cyberoam displays default messages.

Bug ID - 4493
Description - Yahoo messenger disconnects frequently when parent proxy is configured.

Bug ID - 4494
Description – Even when gateway is not reachable, Dashboard displays gateway status as reachable.

Bug ID - 4536
Description – Cross model appliance backup cannot be restored.

Bug ID - 4553
Description - When Cyberoam is configured as a DHCP client on the WAN interface, Cyberoam Gateway becomes unreachable at times. This happens because; when Cyberoam DHCP client on the WAN interfaces failed to fetch the IP address from the ISP DHCP server it does not retry again leading to loss of Internet connectivity. It was necessary to restart management services (RMS) for Cyberoam DHCP client to request again. Cyberoam DHCP client is now updated and will keep on retrying until it receives IP address from the ISP DHCP server.

Bug ID - 4572           
Description – Backup of v 7.4.2.x cannot be restored on v 9.5.4.xx

Bug ID - 4605
Description – When Cyberoam is deployed in transparent mode, after changing the default HTTP port one could not access Web Admin Console.

Bug ID - 4655        
Description – When Cyberoam upgrade is applied after System date is updated to the current date, Web UI upgrades are not applied. This situation occurs only when system date was by mistake configured to some future date.
 
Bug ID - 4664
Description - When Cyberoam is configured as DHCP Client, Cyberoam does not forward the IP lease request to DHCP server if not leased on the initial request.

Bug ID – 4681
Description – An invalid URL can be configured as a Home page from Custom Client Preferences page of Web Admin console.
 
Bug ID – 4701
Description – If port number 2812 is not free, java does not load.

Bug ID – 4732
Description - When both Parent proxy and DDNS are configured, it is not possible to access the Cyberoam appliance using FQDN (hostname). This is because; proxy IP address is forwarded to DDNS instead of WAN IP address of Cyberoam.
 
Bug ID - 4786
Description – Cyberoam incorrectly allowed to update the gateway IP address of DHCP-enabled WAN interface from Web Admin Console.
 
Bug ID – 4793
Description – Cyberoam allows white space in the “Timeout session after” field while creating Group.

Bug ID – 4794
Description – Cyberoam allows to specify Web Admin console port value as a decimal number. Due to this, Web Admin console becomes inaccessible.
 
Bug ID – 4807
Description – After customizing contents of the HTTP client page, it is not possible to save the user password.
 
Bug ID - 4813
Description – Special character Hyphen is not accepted as a part of Dynamic DNS host name.
 
Bug ID – 4821
Description – User session timeout does not work as expected.
 
Bug ID – 4822
Description – Explicitly added route for DHCP-enabled interface is removed after running Network Configuration Wizard.
 
Bug ID - 4831
Description - When the contents of customized HTTP client page do not fit on a single page, scroll bar is not displayed and as a result users are not able to view the entire contents.
 
Bug ID – 4833
Description – When WAN port is configured as DHCP client, Gateway failover condition does not work.
 
Bug ID - 4853
Description – After restarting management services or rebooting Cyberoam, VPN service does not start if DHCP server is not able to lease IP address to the WAN Interface.
 
Bug ID - 4899
Description – When Cyberoam is configured in transparent mode, the Gateway IP address cannot be changed.
 
Bug ID - 4906
Description – When HTTP port is configured on any of the reserved port like 3128, 8007, 8384, 8088, 8090, 9001, Web Admin console becomes inaccessible.
 
Bug ID – 4944
Description – Tip for configuring minimum and maximum days for log retention is not displayed on the Configure Auto Purge Utility page.

Bug ID - 5035
Description – When Cyberoam is configured as a DNS server, users are not able to access the Internet as Cyberoam is not able to resolve the name.
 
Bug ID – 5246
Description – Cyberoam does not detect ICMP flood as per the configuration.
 
Bug ID – 5286
Description – As DNS server could not resolve the cached name query, users were not able to access the Internet.
 
Bug ID – 5363
Description – “Disable Autostart” button does not work for DHCP server and Domain Name server.
 
Bug ID – 5378
Description – When Cyberoam DHCP client on the WAN interfaces fails to fetch the IP address from the ISP DHCP server, Interface based Virtual host does not work.

Bug ID - 5373
Description – MSS value is not retained after running Network Configuration Wizard.
 
Virtual host
Bug ID – 4820
Description – When any of the Cyberoam interface is configured as Virtual host, IP address of the Virtual host does not change automatically if changed through Network Configuration wizard.

Bug ID – 4991
Description – Port forward rule for Virtual host fails when more than 30 ports are included in the port range.

Virtual Private Network (VPN)

Bug ID – 2322
Description – When same network is specified as local and remote network in Connection, VPN tunnel is not establish.
 
Bug ID - 4457
Description - L2TP tunnel gets disconnected while copying file.
 
Bug ID - 4735
Description - VPN Client always disables NAT-T parameter irrespective of the configuration imported from Cyberoam.
 
Bug ID – 4816
Description – VPN connection running on static IP Address fails to get activated
 
Bug ID – 5372
Description – Cyberoam crashes due to race condition in VPN services.
 
Bug ID – 5374
Description – VPN connections can not be deleted after the VPN module is disabled from System Modules page of Web Admin console. 

Traffic Discovery

Bug ID – 4921
Description – Traffic discovery module cannot handle packet size greater than 2048 bytes. Due to this, packets were dropped.
 
Bug ID – 5370
Description – Cyberoam will not classify traffic pattern even after enabling Traffic Discovery module if Traffic discovery module is disabled at the time of upgrading Cyberoam. This behavior is observed when Cyberoam is upgraded to version 9.5.4 build 55

Web Admin Console

Bug ID – 5260
Description – Help option is removed from the Main page as it opened an obsolete page. 


[1] Refer User Guide (Document version – 95466-1.1-24/06/2008, page 81)

[2] Refer User Guide (Document version – 95466-1.1-24/06/2008, page 212)

[3] Refer Cyberoam Console Guide(Document version – 95466-1.0 -24/06/2008, page 30)

[4] Refer Cyberoam Console Guide(Document version – 95466-1.0 -24/06/2008, page 59)

[5] Refer Cyberoam Console Guide(Document version – 95466-1.0 -24/06/2008, page 59)

[6] RMS is required after adding a superset range for an existing subnet range

[7] Refer User Guide (Document version – 95466-1.1-24/06/2008, page 212)

[8] Refer Cyberoam Console Guide(Document version – 95466-1.0 -24/06/2008, page 56)

[9] Refer User Guide (Document version – 95466-1.1-24/06/2008, page 16)

[10] Refer Cyberoam Console Guide(Document version – 95466-1.0 -24/06/2008, page 56)

[11] Refer Cyberoam Console Guide(Document version – 95466-1.0 -24/06/2008, page 56)

Attachments
Article ID: 156