pfSense

Setup Wizard can result in invalid LAN DHCP pool calculation

1) consider where the LAN IP is in the subnet range and then put the
DHCP pool in the biggest remaining segment, either above or below.
2) Check the size of the available segment. If it is reasonably big then...

A number of things block waiting for file download timeouts, sometimes multiple times across multiple files (many URL Table aliases, for instance). The long timeout causes very long boot times (10-20+ minutes) on many configs with pfblocker if booted disconnected from the Internet. This is strictly the timeout for the HTTP/HTTPS connection attempt. Once connected, it can run past that. 5 seconds should be more than enough for any properly-functioning network. Part of Ticket #4442.

device_type isn't used here

Don't call growl if the configured address isn't an IP or resolvable
hostname. Avoids 1 minute timeout delay in fsockopen in growl.class. Cuts
that down to about a 20 second timeout. Ticket #4739

trigger a reboot after restoration of full backup. Ticket #4107

Deprecate /usr/local/bin/3gstat

Use CARP IPs that are configured. Ticket #4370

set the serial port appropriately for RCC-VE platforms. sync from factory
repo. Ticket #4720

Return IP correctly in get_interface_ip for gateway groups specifying a
VIP. Ticket #4661

Use 'host!' flag when setting CURLOPT_INTERFACE, as recommended by CURL docs