Actions
Feature #1299
closedupdate /etc/bogons
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/21/2011
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Description
This is follow-up from http://redmine.pfsense.org/issues/1297
Basically the default /etc/bogons is fairly out-of-date, so when you have built and boot up your first firewall, you might me scratching your head for a good few hours, wondering why some networks are being blocked. Then out of the sudden, they will be allowed, that's when /etc/rc.update_bogons.sh kicks in from cron. I have learnt in the hard way.
I would like to propose the following changes:
1. most recent "bogons" to be included in next and every new release
2. /etc/bogons to be updated at boot time
3. the update script to fall back to hardcoded IP, if DNS is not available
Actions