It works like it's supposed, although a little tweaking so it doesn't lock you out if no IP mentioned would probably help improve it (from the comments I've read since it didn't happen to me) still worth 5 stars for me

I does what i says, nice module thanks.

the others rewiews (advises) diddent explain i so clear for me so here is some more info.

1.) find your ip. eg C:\links\WhatIsMyIP_com.htm
copy it.
2.) yuo must have atleast 1 bad ip. i took someone that had spammed my cookbook.
(i coud see it in the component joomlastats.

3. install the module go to administrator modules.
click on it and set the good and bad ip.
Publish it log out and log in.

NOTE. this is for a system with a permanet IP
and a computer without a router.

This module does work, but required a little detective work to figure out why it didn't at first.

In as much as the author support is entirely in Russian, and no real support is available in English. I hope the moderator will make exception for a little support suggestion here because this module can be made to behave even in those cases where it initially locks the user out of the administration backend. It should either be supported for the user community or removed from listing as unsupported/undocumented, but it is not as erratic as it appears to be for usability. It is very very simple and requires exact format requirement for the IP address or range.

It is a valuable addition, with a few caveats. Undertanding why it may not behave should be better stated. I'd hate to see this unique tool removed simply because it is poorly documented, but one can't RTFM if you don't read Russian.

I originally entered the allowed IP range in wildcard notation. Access failed on relog.

I momentarily renamed the .php and .xml files long enough to log back into the back end after it failed. I changed the names of the files back. I changed the entry to the exact IP rather than a wildcard range and I logged out and then back in and it worked fine.

On examination of the php file it will also accept ranges in Netblock Notation (Cisco). It will not accept IP Mask Notation. It will not accept wildcard notation (192.168.*.*) It has a very simple but effective RegExp filter built into the input stage and it will accept ONLY valid netblock notation.

192.168.128.0/17 etc... will define a valid range format for people who access their server remotely from dynamic IP lease addresses... Non-overlapping ranges can be added, seperated by commas.

I would be certain to add any ranges your ISP is likely to use especially if they are upgrading hardware regularly. At the very least keep a note of this problem in your notes. Your IP lease could change in several months and leave you scratching your head as to why you can't get back in. Fixing it takes about 1-2 minutes.

As the name implies, this extension blocks access to unauthorized access to joomlaroot/administration/index2.php by IP.
It is not a backend tool for blocking frontend access.

For those of us who cant read russian.

http://www.google.co.uk/translate?u=http%3A%2F%2Fjoomlaportal.ru%2Fcontent%2Fview%2F1110%2F70%2F&langpair=ru%7Cen&hl=en&ie=UTF8

Translation by Google.

I tried this out and it worked for me on Joomla! 1.0.12 Stable [ Sunfire ].

How to install:
1. Install as any normal module
2. Goto Modules > Administrator Modules > BackendIPBlocker
3. Publish It to the 'Header' position. Now set the parameter's (ip's).
4. Save it. Logout, then log back in, if you can then it has worked, if you cant then Login to your server (shell or ftp). Locate and remove mod_backendipblocker.xml and mod_backendipblocker.php.
5. Done, if it worked.

I installed and didn't put any ips into any allow or deny field. I published the module in the header position as instructed. I was immediately logged out of the admin area. Additionally, after login attempt, I am redirected to the public homepage.

To REMOVE:

Login to your server (shell or ftp). Locate and remove mod_backendipblocker.xml and mod_backendipblocker.php.

Login to your joomla admin page as normal. Go to your admin modules. First Unpublish. Next, uninstall the nasty little bugger. It will give you a warning that removal failed.. but it really didn't. The entry for mod_backendipblocker will be gone and you'll be back to the state you were before you installed this mess.

Works, but works so well I locked myself out. I added my office IP as a good IP address and sure enough, I coldn't log in from home. I then added my hope IP on the next line and now I am locked out from both locations. I went to the developers webpage, but it isn't in English.... Help!