As a matter of policy, FireBrick software upgrades are free to download for all FireBrick customers.
SOFTWARE UPGRADES ARE BEST DONE USING THE WEB CONTROL PAGES ON THE FIREBRICK ITSELF
If you are loading new software from this web page, please read the instructions first.
There are three categories of software releases available - Factory, Beta and Alpha.
These categories reflect the amount of testing done - releases normally start life as an alpha, then after initial alpha testing are converted to a beta. As a beta they are subjected to further testing, both by ourselves and by customers in the field. If, after beta testing, a release is stable, we will promote it to a factory release. If during testing we find a problem, we may choose to withdraw that release, or promote a later release.
Factory releases have been tested extensively, both by us and by test users, and have been stable for some time as a beta release. We recommend upgrading all FireBricks to the latest factory release when convenient. FB2500 and FB2700 models will automatically upgrade to the latest factory release, unless you change the default "sw-update" setting in the config.
Beta releases have been through alpha testing to eliminate obvious bugs, and are generally stable. They are available to all users, should you wish to try a new feature or bug-fix before it is available as a factory release, and are willing to take the risk. FireBrick dealer technical support may also ask you to try a new beta to fix a problem. However, when running a beta, we suggest you keep an eye on our software downloads page, in case the beta you are using is withdrawn, or a subsequent beta release with relevant bug fixes is made available. When a beta release has had sufficient testing, it is normally promoted to factory release, or withdrawn if any serious problems are found. Your FireBrick's upgrade page will normally offer the latest beta release, or you can manually download it from our website and upload it onto your FireBrick.
Alpha releases are only for use by designated alpha testers, who are members of staff or customers closely involved in developing and debugging new features. Alpha releases may have had little or no testing, so there is a significant risk of bugs. If you would like to get involved in alpha testing, please contact your dealer. To load an alpha release, your FireBrick must first have alpha upgrades enabled by us. Your FireBrick's upgrade page will then offer the latest alpha release, or you can manually download it from our website and upload it onto your FireBrick.
Remember that if any upgrade causes repeated crashes, your FireBrick automatically reverts to older code.
To install new software you need to load two files:
Log in to your FireBrick administration pages, select Setup and then Upload/Restore, and select the FireBrick software file you downloaded. This will take up to a minute to load, after which you are prompted to load the user interface. Select the user interface file requested. This will take up to a minute, and then your FireBrick will be ready to use again.
FireBrick Model: FB6000 | FB2500 | FB2700 | SoHo/Plus | FB105
Software Versions: Older versions | Factory releases | Factory and Beta | Factory, Beta & Alpha
UI: Fix problem with clearing all Event actions in Log/Filter options.
UI: The time at which the page was generated is now displayed on each page. Default filename for config save now includes Firebrick name and date/time. Setup Log/Filter options now correctly displays the default filter setting. Wizard should only display when user has enough access to make suggested change. Fix UI misbehaviour when clicking on Save Config after login has timed out.
Tunnels: Incorrect source IP could be used in some cases, causing a tunnel to fail to establish.
DHCP: Client was incorrectly setting an SNMP server in config on Firebrick without reporting feature. Server running as a backup was incorrectly adding "Offered" entries to DHCP table. Host name in "Offered" entries was sometimes incorrect. DHCP traffic to FireBrick is now allowed through the default filter, so no explicit filters are required for operation of DHCP.
ARP:ARP responses using ethernet 802 frame format are now accepted.
Routing: Session tracking of ICMP sessions (eg PING) improved.
Older versions | Factory releases | Factory and Beta | Factory, Beta & Alpha