FireBrick Model: FB6000 | FB2500 | FB2700 | FB2900 | FB9000 | SoHo/Plus | FB105
Software Versions: Older versions | Factory releases | Factory and Beta | Factory, Beta & Alpha
Release notes from Beta release 2.02.645 to Alpha release 2.02.647
ICMP error packets generated by the FB and sent out on a tunnel have source IP set to tunnel NAT IP (if set).
New tunnel port option is now available on bricks without bonding feature.
Release notes from Factory release 2.02.644 to Beta release 2.02.645
DHCP: Fixed problem where FB could incorrectly consider itself a backup server, and reply after a delay to some requests. Minor improvements/fixes to some DHCP log messages.
UI: Setup Log/Filter Options page did not redisplay after performing an email test.
Profiles: Ping profile now has an option to set the data length to be used in the ping packet - default is zero (as before).
Tunnels: Tunnels have a new option to set the UDP port number to be used for the tunnel envelope packets - default is 1 (as before). This enables tunnels to be used over some links with deep packet inspection which do not support UDP port 1.
Release notes from Factory release 2.02.643 to Factory release 2.02.644
UI: Fix problem with clearing all Event actions in Log/Filter options.
Release notes from Factory release 2.02.638 to Factory release 2.02.643
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.
Fix poor performance and lockup problems following reception of invalid length ether packets.Release notes from Factory release 2.02.638 to Beta release 2.02.641
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.
Release notes from Factory release 2.02.637 to Factory release 2.02.638
Internal fix for compatibility with production labeller.Release notes from Factory release 2.02.604 to Factory release 2.02.637
Introduction of new tunnel retiming code, which will be replacing the current tunnel reordering mechanism. The tunneling protocol version has been changed from V2 to V3 to include extra retiming information. If both ends of a tunnel are V3-capable, the Firebrick will automatically switch to V3 tunneling, and if tunnel bonding is in use, will retime the packets using the new information.Release notes from Beta release 2.02.635 to Beta release 2.02.636
The handling of packet fragments has been improved - they now participate fully in session tracking. This means they will be treated in the same way as unfragmented packets when filter, routing, mapping rules etc. are processed, so can be NATed or address mapped. This should improve performance, and also avoid problems with configurations using NATing where fragmentation cannot be avoided - eg VPNs. The distribution of traffic across bonded tunnel sets should also improve where there is significant fragmented data.Release notes from Beta release 2.02.634 to Beta release 2.02.635
Fixed minor problem preventing deletion of filter table entries.Release notes from Beta release 2.02.628 to Beta release 2.02.634
UI:Release notes from Beta release 2.02.626 to Beta release 2.02.628
Bug fixes:Release notes from Beta release 2.02.626 to Beta release 2.02.627
Bug fixes:Release notes from Beta release 2.02.625 to Beta release 2.02.626
Further UI improvements:Release notes from Beta release 2.02.606 to Beta release 2.02.625
Release notes from Beta release 2.02.605 to Beta release 2.02.606
The UI web pages have been extensively reviewed for this release. A few improvements to the UI have been incorporated, and several minor bugs fixed.Release notes from Factory release 2.02.604 to Beta release 2.02.605
Introduction of new tunnel retiming code, which will be replacing the current tunnel reordering mechanism. The tunneling protocol version has been changed from V2 to V3 to include extra retiming information. If both ends of a tunnel are V3-capable, the Firebrick will automatically switch to V3 tunneling, and if tunnel bonding is in use, will retime the packets using the new information.Release notes from Factory release 2.02.594 to Factory release 2.02.604
Fixed a problem where changes to setup security settings for the filters, users, tunnels, profiles and routes entries were ineffective. Improved checking of uploaded software and config files. Fixed problem preventing ports connected to certain makes of switch from re-establishing after parameter changes or a line test. Port Throttle and B/Limit options now work as intended. Corrected tunnel status checking, which was causing tunnels to appear to be up before keepalives had been exchanged in both directions. Added Date header to email messages. New "local information" feature allowing user-specifiable text and links to be displayed on the main menu page, configurable from setup page. Note that this is an experimental feature which may be changed or removed before the next factory release. Comments and suggestions are welcome.Release notes from Beta release 2.02.602 to Beta release 2.02.603
Fix spurious debug log message when viewing route table.Release notes from Beta release 2.02.601 to Beta release 2.02.602
Avoid log corruption if FireBrick reboots while writing to the log.Release notes from Beta release 2.02.600 to Beta release 2.02.601
Fixed portgroup edit page, which was showing new port ranges preset to start at 1 when using Internet Explorer.Older versions | Factory releases | Factory and Beta | Factory, Beta & Alpha