Version: 4.0-0.4 rc, by Carnage
Developer Last Online: Sep 2014
Category: Administrative and Maintenance Tools -
Version: 4.0.0
Rating:
Released: 10-28-2009
Last Update: 01-17-2010
Installs: 170
DB Changes Uses Plugins
Additional Files
No support by the author.
What does this do?
This is intended as a replacement for the ip bans under vbulletin options. It allows for timed ip bans, cidr ranges and attatching reasons to bans.
It also features registration only ip bans allowing members who may be effected by an ip ban to continue using the forums, but blocking registrations and ip ban exempts so that you can ban a large range of ips and let through a smaller subset of them.
What can I use it for?
This is a much better tool for managing ip bans on your forums. As it has its own permissions, you can grant admins access to it without needing them to have full access to the vbulletin settings. For more details see the features list.
Features
A new interface, separate to the options for adding and removing ip bans.
Set expiry dates and reasons for ip bans
See who set which ip bans
Set ip bans by cidr range.
Set registration only ip bans (great for stopping spam bots without affecting existing forum users)
Set exempt ip bans (ban a large range of ips and only allow select ips through the ban)
Define unbannable ips in config.php
A range of tools for assisting usage including:
Cidr to range calculator (see what range a certain ban will affect)
Range to cidr calculator (creates a set of bans to cover any arbitrary range [experimental]
Test an ip (enter an ip to see if its banned or not and which if any bans affect it)
Whois an ip (get information on who owns (eg which isp) an ip and the cidr range of ips that they own (simplifying blocking users on dynamic ips)) [Dependant on host and server OS]
Check if a user is banned (enter a username/userid to see if they are banned or not)
Planned features
Ban a user (some sort of integration and automation to ip ban users from their admincp profile)
Integration with delete as spam feature to allow automatically ip banning spammers
Inport/Export ip bans to share with others and amongst other sites you own
Os independent whois and results parsing (eg give novice admins a hand in picking out the important bits)
Automatic conversion from old bans into new ones.
Phrases for admincp areas (that are currently lacking them)
Integrated Admin help
Installation
1. Backup db.
2. Upload files from zip.
3. Import product file.
4. Setup admin permissions for your staff.
Upgrading from 3.6+ version of this mod
1. Backup db
2. Use the uninstall option for the 3.6 version of this product. (this will leave your ip bans in tact)
3. Upload the new files from the zip, overwriting the old ones
4. Import the new product file.
5. Check admin permissions for your staff members.
Upgrading from previous versions of this mod
1. Upload files in upload directory
2. Import product (allowing override)
Uninstallation
1. Backup db.
2. Uninstall the product file.
3. Manually delete the ipbans table from your database (unless you want to keep it)
4. Delete the files that were included with this release.
Changelog
4.0-0.4 rc1
Changed min cidr range from 16 to 8.
Added md5 sums file, ipban manger will no longer come up as suspect files in diagnostics (unless someone has tampered with the files)
Added feature to check if a user is banned
4.0-0.4 b2 (unreleased)
Fixed a couple of minor bugs
Redirecting to the wrong place after adding an ip ban
Short php tag at top of admincp file
4.0-0.4 b1
Added tool to calculate cidrs from an arbitary range
Makes the $ip a string with a max value of 2147483647*2. Then when PHP needs to do arithmetic on the string it implicitly casts it to a float if it is larger then 2147483647 (for 32-bit systems) otherwise an int. On 64-bit systems PHP expands integers to 2^64.
Right, I had already figured out the problem. I removed the sprintf and allowed the AND to be done with the integers then printed it as an unsigned int in the query.
I didn't realize that php would automatically convert back till I consulted the documentation following your issue the fix for 32 bit systems will be in the next release.
Thats in the uploads folder for a reason :P upload it don't import it, it stops vbulletin from seeing the mods files as being 'not a part of vbulletin' in the diagnostic tools, it also makes sure that the files that come with this mod have not become currupt.
Would it be too much to ask for specific instructions for setting permissions to make this feature available for a user account, or for the administrators group?
In order to make this avaliable for a user, they must be an administrator. Then you need to edit their admin permissions and give them the can admin ipbans permission.
Does this work for vb 3.8.5?
Does this modification allow us to prevent blocking collective proxy IPs like AOL has? (blocking one AOL IP will block a mass of different AOL IPs)