vb.org Archive - Block User Ip From Your (.htaccess)

Quote:

Originally Posted by Terminatoronly (Post 1160499)

Ok The Finman thanks for your reply i think that this thread is not good maybe i will report it

No problem as I am actually quite happy you brought this topic up. :)

As Forza stated, this really is a subject that needs discussion, since I believe the majority of web admins & owners (at least the ones I know) are running Apache.

The links I provided show the various ways that .htaccess can be applied.

Maybe a good place to start is the discussion of what does what and where, as my .htaccess code is slightly different, yet both work. :)

To block IPs and IP ranges, Terminatoronly uses...

Code:

<Limit GET HEAD POST> 

order allow,deny 

deny from 188.156.187.*** 

deny from 188.155.187.*** 

allow from all 

</LIMIT>

It appears that he is blocking not just an IP, but an IP range of 188.156.187.0 through 188.156.187.255.

If an IP is static (meaning the user's IP does not change - such as most cable & DSL) then one should simply use the specific IP address such as 188.156.187.244. Most "dial up" ISPs use dynamic IPs. Basically meaning that the user is assigned an IP from a block range available from that ISP while logged in. Upon log out, that user relinquishes that IP to the ISP and then it can be assigned to another user within that ISP's range.

I know I am probably covering well known knowledge, but sometimes I find that people don't realize just how much banning a block range can effect them and their guests.

Banning IP ranges can not only restrict users that may not have done anything to you, but you may also inadvertently knock out search engine spiders, crawlers, good bots, good users, Etc.

I really advise against banning IP ranges unless the problem is really that serious, and you have a reasonable idea of just how many other users you may knock out in the process...especially AOL users since AOL routes them through their own proxy servers, and banning even one range of AOL users you can take out a HUGE chunk of other visitors you may wish to have.

I use a variation of Terminatoronly's .htaccess file for banning IPs at the server base.

For example...

Quote:

Options +FollowSymlinks
RewriteEngine On
RewriteCond %{REMOTE_HOST} ^4\.245\.40\.88
RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R]
RewriteCond %{REMOTE_HOST} ^86\.131\.16\.92
RewriteRule ^.*$ http://www.send_them_somewhere_else.com/ [L,R]
RewriteCond %{REMOTE_HOST} ^68\.48\.
RewriteRule ^.*$ http://www.yahoo.com/ [L,R]
RewriteCond %{REMOTE_HOST} ^71\.253\.249\.
RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R]
RewriteCond %{REMOTE_HOST} ^68\.114\.48\.210
RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R]

I have divert my immediate time to another project at the moment, but I will try and hop back in and explain the differences when I get a chance.

If someone else wants to hop in and list additional variations (other than mine or Terminatoronly), then please jump on in...as there is ALOT more variations than why are listed so far. :)

Also, here is another variation you might want to try, as it shows how two different uses for .htaccess files can be combined.

From my other post I showed you how to block (actually completely redirect ;) ) people linking to your board or site that are not friendly.

Code:

Options +FollowSymlinks 

RewriteEngine On

RewriteCond %{HTTP_REFERER} ^http://www.troll_bulletin_board.com 

RewriteRule /* http://www.malicious_website.org [R,L]

RewriteCond %{HTTP_REFERER} ^http://troll_bulletin_board.com 

RewriteRule /* http://www.malicious_website.org [R,L]

Let's combine them real quick! :D

Code:

Options +FollowSymlinks 

RewriteEngine On

RewriteCond %{REMOTE_HOST} ^4\.245\.40\.88

RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R]

RewriteCond %{REMOTE_HOST} ^86\.131\.16\.92

RewriteRule ^.*$ http://www.send_them_somewhere_else.com/ [L,R]

RewriteCond %{REMOTE_HOST} ^68\.48\.

RewriteRule ^.*$ http://www.yahoo.com/   [L,R]

RewriteCond %{REMOTE_HOST} ^71\.253\.249\.

RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R]

RewriteCond %{REMOTE_HOST} ^68\.114\.48\.210

RewriteRule ^.*$ http://www.send_them_somewhere_else.net/ [L,R]

RewriteCond %{HTTP_REFERER} ^http://www.troll_bulletin_board.com 

RewriteRule /* http://www.malicious_website.org/ [R,L]

RewriteCond %{HTTP_REFERER} ^http://troll_bulletin_board.com 

RewriteRule /* http://www.malicious_website.org/ [R,L]

RewriteCond %{HTTP_REFERER} ^http://www.another_troll_bulletin_board.com 

RewriteRule /* www.another_bad_place.com/ [R,L]

RewriteCond %{HTTP_REFERER} ^http://another_troll_bulletin_board.com 

RewriteRule /* http://www.another_bad_place.com/ [R,L]

The above code actually combines the IPs and Referral Links .htaccess code variations, and then sends the trolls (via their IPs), and users/trolls/whatever (clicking through links to your board) to wherever you want to bounce them to. :D

First, before someone jumps in ans says I should have included "this" or excluded "that" in my .htaccess code above...I am not using the above (or attached) .htaccess file as the "be all and end all" of how to accomplish blocking IPs, IP Ranges, Referral Links, Etc.

I am simply showing you one possibility, just as Terminatoronly showed you his variation.

I've included a real good beginner's tutorial...

http://www.javascriptkit.com/howto/htaccess.shtml

as some of the Apache tutorials are about as much fun as watching paint dry. :rolleyes:

http://httpd.apache.org/docs/1.3/howto/htaccess.html

Anyway, I'm sure a lot of Apache users already have a good grounding of what can be done with .htaccess, but maybe some may not be.

Also, there are a good deal of variations that can be used for different effects, and I would really encourage Apache users who already use .htaccess to list the way they use them and why. ;)

I'll try and pop back in later...but yeah, I think it would be great if people would post their own uses and variations of htaccess files. :)

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01227 seconds Memory Usage 1,748KB Queries Executed 10 (?)
More Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (3)bbcode_code_printable (5)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)pagenav (1)pagenav_curpage (1)pagenav_pagelink (1)post_thanks_navbar_search (1)printthread (5)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start pagenav_page pagenav_complete bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages: