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

[. . . ] If ath based WLAN devices were used within a bridging group, the system froze on activation of the WLAN devices. XDSL, DHCP, ISDN or UMTS links configured using Own Routing Table while Clone Routes was set to No prevented the configured routes or the configured default route of being introduced into the policy table. This issue has been fixed. Note: If a box was updated from patch 11 and did not have hotfix 359 applied but had Clone Routes set to No, a manual reboot must be performed after updating to patch 13 in order to introduce correct route handling. Severity / Probability high / high Request No. 1506880 VPN Service 4. 2. 13 high / low 1506896 Network 4. 2. 13 medium / medium Barracuda OS 4. 2. 13 medium / low Firewall 4. 2. 13 medium / low Network 4. 2. 13 medium / low 1506290 Network 4. 2. 13 In rare cases it happened that a scripted restart of an XDSL link would not work. An issue concerning the formatting of USB sticks under Windows 7 during the install process has been fixed. [. . . ] 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. 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. 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. . . Click OK to start the update sequence. During the update sequence, Barracuda NG Admin loses connection to the box due to a service shutdown. This has no influence on the update process itself, but it requires manual closing of the Barracuda NG Admin configuration session on this box. As soon as the update sequence has completed, the secondary HA box may reboot automatically after approximately 2 minutes. · After having assured that the secondary box is fully functional proceed to . Step 3: Log-On to the Primary HA Box · Switch all servers from the primary to the secondary box and verify for correct operability. You may leave the primary box in standby mode until correct operability has been verified. [. . . ] Enter the Control > Licenses tab and import <filename>. tgz by clicking the Software Update. . . 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. . . [. . . ]