User manual BARRACUDA NG FIREWALL 4.2.13 RELEASE AND MIGRATION NOTES REV 1.2

[. . . ] 14 Updating a CC and its Managed Systems . 18 1 2 General The Barracuda NG Firewall may reboot after patch installation. If not, Barracuda Networks recommends performing a manual reboot. Maintenance Calendar Upcoming patch release dates will be announced by Barracuda Networks at www. barracudanetworks. com. Known Issues If the setup is performed using a PAR file, the WiFi service requires, after the network activation, a dummy change of the WiFi module followed by Activate in order to make WiFi work. Advice about known issues is available through the Barracuda Networks support. 3 Migration and Release Notes 4. 2. 13 Updates with Barracuda NG Firewall Patch 13 Software Modules and Components Affected by this Patch Table 1­1 Software Modules and Components Affected by Patch 13 Patch 11 13 Firewall VPN Service Access Control Service HTTP Proxy Secure Web Proxy URL Filter Software Modules Other Mail Gateway Spam Filter Virus Scanner DHCP Service DHCP Relay DNS FW Audit Log Service FTP Gateway OSPF/RIP Service SNMP Service SSH Proxy Barracuda OS Control Center Network NG Admin NG Installer NG Network Access Client VPN Client R8 for Mac 4 Updates with Barracuda NG Firewall Patch 13 Bugfixes Included with Barracuda NG Firewall Patch 13 Barracuda NG Firewall Table 1­2 Barracuda NG Firewall Module Network Patch 4. 2. 13 Description An issue concerning the dial-in process via PPPOE DSL has been fixed. A problem occurred in patch 11 that prevented preauthentication from functioning. [. . . ] In rare cases it happened that proxy service died if ACL entries of URL filter categories type were present in conjunction with long URLs, generating the following error message: Too few URLFILTERACLCLASS<ACL-Name> processes are running This issue has been fixed. Under certain circumstances it was possible that the proxy service crashed in Normal mode, generating the error message assertion failed. Due to an error in the proxy statistics module, FTP statistics were logged in an erroneous format, generating the following error messages into Box > Statistics > cstatd: Severity / Probability low / low Request No. Control Center 4. 2. 13 low / low Control Center 4. 2. 13 low / low DHCP Service 4. 2. 13 low / low DHCP Service 4. 2. 13 low / low FTP Gateway 4. 2. 13 low / low 1506576 HTTP-Proxy 4. 2. 13 low / low 1506038 HTTP Proxy 4. 2. 13 low / low HTTP Proxy 4. 2. 13 low / low 1506568 HTTP Proxy 4. 2. 13 low / low 1506520 HTTP Proxy 4. 2. 13 low / low 1506704 HTTP Proxy 4. 2. 13 low / low 1506571 Unspecified error. file I/O error Network 4. 2. 13 If the OSPF service was blocked, it was automatically started after a network restart although it shouldn't. The Huawei E870 modem was provoking USB storage problems. Packets with an MTU size bigger than 1500 bytes could crash a box when sent over a bridged network. This issue has been fixed. low / low Network 4. 2. 13 low / low 1506273 Network 4. 2. 13 low / low 1505052 6 Bugfixes Included with Barracuda NG Firewall Patch 13 Table 1­2 Barracuda NG Firewall Module Network Patch 4. 2. 13 Description If PPTP was configured as a DSL link, the MTU field was not editable until the configuration dialog was closed and then reopened. It was not possible to re-establish VPN connections via L2TP that existed before and broke up due to some reason. This issue has been fixed. Severity / Probability low / low Request No. 1506238 VPN Service 4. 2. 13 low / low 1506194 VPN Client for Mac Table 1­3 Barracuda NG Admin Module VPN Client for Mac Patch 2. 0 SP2 Description Mac OSX 10. 6. 3 was in a VPN connection erroneously not using the VPN DNS Server. This issue has been fixed. Severity / Probability low / medium Request No. 1506440 7 Migration and Release Notes 4. 2. 13 Migrating to Barracuda NG Firewall 4. 2. 13 Read this document before updating your system. After the first reboot following the update, the version information may show a dirty release. It will automatically change to a clean release after approximately three minutes. This is a normal behaviour as execution of the validation function takes time. Hardware based on i386 compatible CPUs does not provide the functions required for Traffic Shaping. Because of that, Traffic Shaping does not work on i386 kernels. Type rpm -q kernel --qf %{ARCH}\\n within the shell to find out which kernel is present. For USB memory stick based installation, a 1GB memory stick is required. The ISO image does not fit on a 512 MB memory stick. Support for Token Ring and FDDI cards is not available. Minimum System Requirements Table 1­1 Minimum system requirements for Barracuda NG Firewall Operation systems Disk space included (Barracuda OS) 4 GB for gateway installation on harddisks 2 GB for gateway installation on CF RAM 20 GB for Barracuda NG Control Center installation 256 MB 400 MHz 1 network interface required RAM Processor Networking Table 1­2 Minimum system requirements for Barracuda NG Admin / Barracuda NG Installer Windows 2000, Windows XP, Windows Vista (32-bit, 64-bit), Windows 7 (32-bit) Operation systems Note: Barracuda NG Admin additionally supports Windows 7 64-bit. 30 MB 512 MB 1. 3 GHz Disk space RAM Processor 9 Migration and Release Notes 4. 2. 13 Version Compatibility Kickstart files required for installation must be created with the Barracuda NG Installer version delivered with your Barracuda NG Firewall product package. They are available on the USB stick. · · When upgrading to 4. 2. 13, ensure that at least 300 MB of free storage space is available for the root partition. If this minimum amount of space is not available, Barracuda Networks highly recommends to re-install the system with a larger root partition instead of upgrading. This is due to blocked services instead of a complete shutdown of the Barracuda subsystem. Barracuda Networks recommends the following procedure to update HA systems. Step 1: Log-On to the Secondary HA Box Log into the respective box. Step 2: Update the Secondary HA Box · · Enter the Control > Licenses tab and import <filename>. tgz by clicking the Software Update. . . button, with File Type set to TGZ file (*. tgz). Click OK to start the update sequence. During the update sequence, Barracuda NG Admin loses connection to the box due to a service shutdown. [. . . ] button, with the File Type set to TGZ file (*. tgz). Click OK to start the update sequence. · · During the update sequence, Barracuda NG Admin loses its connection to the box due to a service shutdown. This has no influence on the update process itself, however, it requires manual closing of the Barracuda NG Admin configuration session on this box. 15 Migration and Release Notes 4. 2. 13 As soon as the update sequence was completed, the primary HA box will reboot automatically after approximately 2 minutes. Step 4: Unblock All Servers on Primary HA Box Unblock all servers by clicking Stop Server (Control > Server). Step 5: Log-On to the Secondary HA Box Log into the respective box. Step 6: Block All Servers on Secondary HA Box Block all he servers there. Step 7: Verify Functionality of Primary Box Proceed to the next step after having assured that the primary box is fully functional. Step 8: Unblock All Servers on Secondary HA Box Unblock all servers on the respective box. Step 9: Unblock the Configuration Updates Do this using the Control > Configuration Updates > Unblock Update button. Step 10: Update Completed The update process is finished. 16 Updating a CC and its Managed Systems Update a Single CC Before starting the update procedure, block all servers as well as the configuration update using Control > Configuration Updates > Block Update on the CC. Otherwise the update process may fail. Step 1: Log-On to the Control Center Enter the Control > Licenses tab and import <filename>. tgz by clicking the Software Update. . . [. . . ]