pfSense

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