Project

General

Profile

Actions

Bug #1297

closed

/etc/bogons out-of-date

Added by don mkumba almost 15 years ago. Updated almost 15 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/20/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

I'm running version 1.2.3, and have noticed my IP belonging 2.120.0.0/15 is being blocked as bogons. Digging around I found /etc/bogons out-of-date. Tried to run /etc/rc.update_bogons.sh but it just hangs forever. Found this in the logs:
Feb 21 00:50:24 root: rc.update_bogons.sh is starting up.
Feb 21 00:50:24 root: rc.update_bogons.sh is sleeping for 62747

Actions #1

Updated by Chris Buechler almost 15 years ago

  • Status changed from New to Rejected

not a bug. fix your DNS so it can update, and run "/etc/rc.update_bogons.sh now" so it doesn't sleep.

Actions #2

Updated by don mkumba almost 15 years ago

and it's fairly out-of-date, comparing to the current http://files.pfsense.org/bogon-bn-nonagg.txt

Actions #3

Updated by don mkumba almost 15 years ago

nothing wrong with dns, it's just this code, which causes the script to sleep, if run with no arguments:

  1. Sleep for that time.
    if [ ! $1 ]; then # Grab a random value
    value=`od -A n -d -N2 /dev/random | awk '{ print $1 }'`

    echo "rc.update_bogons.sh is sleeping for $value" | logger
    sleep $value
    fi

I can see the point, but does /etc/bogons get updated automatically??

Actions #4

Updated by Chris Buechler almost 15 years ago

yes it's updated automatically, yours is failing for some reason (lacking DNS is most commonly the reason). It isn't a bug, so please post further discussion to the forum or mailing list.

Actions #5

Updated by don mkumba almost 15 years ago

ignore, all ok, /etc/crontab:
1 3 1 * * root /usr/bin/nice -n20 /etc/rc.update_bogons.sh

Actions

Also available in: Atom PDF