well, THAT didn't take long

176.123.0.0/19: from bogon to blocked in one easy step

[lucy24]

While doing some housekeeping I found a flurry of recent visits from

176.123.0.57

Most were blocked due to forging the wrong referer; some got through. Quick glance at existing notes say they're coming from a bogon range. Hmm. Detour to whois for update.

176.123.0.0/19 now belongs to Moldova. (Its neighbor 176.123.32.0/20 got scooped up by Romania around the same time. Unfortunately the rest of the quadrant, ..48.0/20, is chopped into 23s and 24s, including some, ahem, respectable countries.)

Don't think I'll get a lot of legitimate visitors from Moldova. Nor indeed any illegitimate ones, thanks to a speedy

Deny from 176.123.0.0/19

:: heh, heh ::

[dstiles]

176.123.0.0/19 (or at least part of it) seems to be a cloud server. That's the only range I have blocked within 176.123/16, and that only since 17th Oct.

[wilderness]

Just think of all the fun I'm missing ;)

RewriteCond %{REMOTE_ADDR} ^17[5-9]\. [OR]
RewriteCond %{REMOTE_ADDR} ^18[0-35-9]\. [OR]

[lucy24]

Gosh. There's a full-blown

176.0.0.0/5

in there. Most folks stop at 8. I guess you could say

224.0.0.0/3

but it would only be for the entertainment value, since nobody lives there anyway.