BrazilFW 2.27.3 is available to download.
SERIOUS BUG - Subnetting examples should be disabled
Bug - Missing ebtables lib
Bug - Missing ebtables file etherstype
Bug - Typo at PPTPD package: PPTPD_REMOTEIP_LAST
Bug - Missing cr2br functions requested by some add-ons
Bug - Bad definitions for some l7-filter protocols.
Bug - ppp.dial error due changes to rc.pppoe
Bug - Wrong broadcast address for subnetting
Bug - Load velox.tgz after tinyproxy.tgz but first to set system clock.
Bug - Simplified firewall rules should be applied before the dial-up.
Webadmin - Removed priority info when using subnetting.
Webadmin - Fixed header color
Webadmin - Dial e Hangup misplaced when using pppoe.
Improvement - Blocked used should not access system services.
Improvement - Simplified firewall logic enhancement. (Bobbb)
Improvement - Added -v to active firewall rules (Bobbb).
Wizard - Fixed "Error copying modules file"
Wizard - Warning for not empty floppies
Wizard - Save the options for the next round.
Wizard - Add the BrazilFW logo
Wizard - Driver de4x5 is pci instead isa.
Wizard - Driver smc9194 is pci instead isa.
Wizard - Added options to install pptpd.
Wizard - NIC lists improved.
Wizard - Added new driver sc92031
Wizard - Added new experimental usb modem driver.
Languages - BRZ - Typo "configurações do Firewall"
Wizard for Linux - Do do demand dns addresses for pppoe.
Installer - Typo: remove this instalations disk
Installer - Do not keep language files when upgrading.
Note for who is upgrading from 2.27.x:
Our previous versions (2.27.0, 2.27.1 and 2.27.2) introduces the new subnetting feature, however the examples provided should come DISABLED by default and I released them enabled.
If you install a fresh new BrazilFW 2.27.3 you should not be affected by this problem. But if you upgrade from a previous bugged version you must access the Webadmin go to the Subnetting page and disable ou remove the 3 examples provided.
Note: New behavior for simplified firewall
Since this versions, blocked used can not access any system service (webadmin, ssh, proxies, etc).
If you changed the default policy from "Allow access to all internal users" to "Deny access to all internal users", be sure to add your own IP address to the white list before to reload firewall, or you will be locked out the system.