My first OpenBSD

Links to insidesocial.com all give a 403 Forbidden "You don't have permission to access /click/2007/11/my_first_openbsd.html on this server" error. Is that a page that needs an account for viewing or is access limited to specific countries? IE only?

Hmm, the link seems to be working for me and I am using Iceweasel.

Incinerator's IP address is probably being blocked. If you send an email to Steven and he can probably take care of it.

I have e-mailed him about this issue, hopefully it will be resolved soon.

The boneheads who run the server have chosen to block THE ENTIRE EUROPEAN CONTINENT in their efforts to fight a DNS attack.

I have had some luck with requests to unblock individual IPs, so if anybody is blocked and wishes to be unblocked, please send me your IP. If you don't know it, the Web site http://whatismyip.com will tell you. I don't know how this works with dynamic IPs.

In any event, our upgrade from Movable Type 3.2 to 4.0 for the blogging software has been stalled for about a month due to the usual issues, but now that my No. 1 IT guy is back from vacation, hopefully they will get the upgrade done and then REMOVE ALL IP BLOCK.

We can only hope.

Thanks to everybody for your interest, and again, I apologize for the boneheaded system administration with a chain saw instead of the more-targeted scalpel approach.

Good news, I just visited the site and all was OK! Till the previous week I was blocked.

Quoting:The boneheads who run the server have chosen to block THE ENTIRE EUROPEAN CONTINENT in their efforts to fight a DNS attack

OK, that might as well explain why I wasn't able to visit your site the past two months or so. Really explains a lot.

I'm still locked-out.

This whole thing remains disturbing. I tried to put the entire text of my OpenBSD followup on LXer so anybody can read it. ...

And I'm pressing further on the IP blocking problem.

Quoting:I tried to put the entire text of my OpenBSD followup on LXer so anybody can read it. ...

I inserted some HTML tags to make it look better for you Steven. Did you get my e-mail?

If I try to click on the home page of LXer on the OpenBSD story of insidesocal http://lxer.com/module/newswire/ext_link.php?rid=95137

then I am redirected to the insidesocal page http://www.insidesocal.com/click/2007/11/openbsd_the_proverb...

where I get : Forbidden You don't have permission to access /click/2007/11/openbsd_the_proverbial_thrill.html on this server.

Apache/1.3.33 Server at http://www.insidesocal.com Port 80

Okay, at the top of this thread there is this link: http://lxer.com/module/newswire/view/94996/index.html

Under this link I come to a page where I can see a summary of the story. To see full story I have to click on this: http://lxer.com/module/newswire/ext_link.php?rid=94996

This last link again puts me on the insidesocal page where I again see the above mentioned "Forbidden" error.

I am in the European region - I mention this because it was said in this thread that the errors are because of a firewall -. AND I see these Forbidden errors for several weeks now on the insidesocal page.

I'm PLEADING with them to STOP BLOCKING THE ENTIRE EUROPEAN CONTINENT. What a way to deal with spam ...

I put the entire text of my longer OpenBSD followup directly on LXer, so anybody can see it.

Click on the "read more" link while in LXer, or just go here:

http://lxer.com/module/newswire/view/95137/index.html

Hi Everyone,

I am working with Steven to see if we can't circumnavigate this link blocking issue altogether.

LXer values its European readers as it does all its readers, LXer will not post articles that do not allow readers to access content based on where someone lives. I also want to say that Steven is in no way responsible for the hosting company's 'stop-gap' measure, he has been doing his best to reason with Click's hosting company to no avail so far.

I have moved the link from the header to the body of the article on LXer. Everyone should be able to access the article directly on LXer now.

I want to apologize to everyone who has been blocked from accessing Steven's articles, I did not move to rectify this issue as quickly as I should have. I am sorry.