pfSense

Update bogons update routine

Update etc/rc.update_bogons.sh

The used version of sh does not support the fallthrough operator and function keyword.

Avoid 'Cannot allocate memory' errors

Add support for compressed bogon files

Add back end support for custom bogon urls

Add label to each pfctl logged result line, not just the first one.

With this, log filtering can find both the addresses added and deleted bogon records.

pfctrl is comment aware (#).

Leave comments in place so last update info can be retrieved by diagnostics tables.
Instead ensure private space is not included.

switch to using the fullbogons-ipv4.txt from Cymru, and standardize paths to /lists/

Ensure conf_mount_rw and conf_mount_ro are matched

On nanobsd, running /etc/rc.update_bogons.sh gives:
[2.1-BETA0][admin@test02.homedomain]/tmp(12): /etc/rc.update_bogons.sh 1
/etc/rc.update_bogons.sh: cannot create /etc/bogonsv6: Read-only file system
The code does 1 conf_mount_rw but 2 conf_mount_ro...

Fix syntax error in bogons update

Bail out without a valid IPv6 address so we don't generate a invalid dhcpv6 server config

rm the right file when working with v6 bogons.
Reported-by: http://forum.pfsense.org/index.php?topic=43334.new;topicseen#new

Add the bogonsv6 table for the IPv6 bogons

Do not remount ro twice

Download and verify the bogons md5 with the bogons files Ticket #141

Fix bogons update in GUI without duplicating logic

Move sleep to correct location

Do not sleep if /var/run/donotsleep_bogons exists. For some reason the first argument is not being passed when ran from webConfigurator

Only echo out when we are sleeping

Do not sleep if an argument is passed

Skip sleep if argument is specified, and update bogons at end of setup wizard.

Add missng `

Simplify (and really) sleep correctly to avoid hammering files.pfsense.org

Echo out to system logs exactly what is going on during bogons update

• Increase random window *4
• Relaunch the update bogons script again if it fails

correct bogons file location

Switch to a more random number between 1-2,000. that'd be somewhere between
immediately and 33 minutes. If people are setting their time zone
properly that also helps distribute the load, since it runs at 1:01 AM
local time.

Use files.pfsense.org

Requested-by: CMB

Use files.pfsense.org

Requested-by: CMB

Log how many changes are made to bogons file.

Throw an error when we cannot download bogons file instead of blindly assuming it succeedded.

Actually generate a random number

• Download bogons entries from pfsense.com
• Do not update on every minute on the 1st of the month
• Sleep for a random period before updating to avoid killing the server

Match on the beginning of the string so that the 110 network is included

Submitted-by: XAI via IRC

MFC 9473
Update bogons to latest from cymru Strip out RFC1918 since we have a seperate filter for that (and we tell people that we don't block them in this filter, doh)

Make uniform by renaming update_bogons.sh to rc.update_bogons.sh