Administrative and Maintenance Tools - Advanced Ipban Manager

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
  • Fixed product help and version check urls
• 4.0-0.4 a2
  • Fixed bug with admincp menu not showing
• 4.0-0.4 a1
  • initial release

Notes

• See https://vborg.vbsupport.ru/showthread.php?t=186342 this thread for 3.6+ version and some guides on usage.

[Carnage]

I'm unable to reproduce so i'm going to have to look at this closer

[Mrquarter2]

I still can't get this to work :/

[Carnage]

ok, i've got an alpha 2 release ready with updated xml files which should fix the issue. As I can't reproduce the issue, someone else will have to confirm that its fixed.

[Sador]

Just installed. It doesn't show up anywhere in the admin panel. When I go to /admincp/ipbans.php it shows the following (check the attachment)

I've got full admin permissions, so unless I need to change permissions to be able to use this mod it should be fine.

Hope you can find out what's wrong, it seems like a nice mod.

[Mrquarter2]

It works now

[Carnage]

Just installed. It doesn't show up anywhere in the admin panel. When I go to /admincp/ipbans.php it shows the following (check the attachment)

I've got full admin permissions, so unless I need to change permissions to be able to use this mod it should be fine.

Hope you can find out what's wrong, it seems like a nice mod.

Did you install the latest alpha 2 release?

If so, check your admin permissions - this mod adds a new one. If its still not working, i'll need to come up with some more ideas for you to try to debug the issue so i can fix it.

As an aside, the reason that the alpha 1 release was broken was because i /tried/ to change the productid from the vb 3.7+ version of the mod (so that it wouldn't show as an update to users using that version) and didn't realise that it needed changing in a couple of extra places.

[Sador]

Yeah, I installed the alpha 2.

"Administer Ipbans" [x] yes"

It still doesn't show up anywhere and when going to /admincp/ipbans.php it only shows the empty thing from the attachment.

[Carnage]

ok, go into plugins and products.

Click edit by the product; if the product id is anything other than imhotek_ipbans you need to uninstall the product and reinstall it.

If it is imhotek_ipbans, go into includes/xml and open cpnav_ipbans.xml. check that the product field in all of the items (where present) is imhotek_ipbans. If it isn't change it to that.

Go back to the admincp, disable and then enable the product and refresh your admin cp.

[Sador]

Just reinstalled it completely, now it seems to work. Don't know what went wrong the first time, but it works now. Thanks.

[Carnage]

Beta 1 released.

New features added:

Range to CIDR calculator.
-Input two ip addresses and it'll calculate a set of bans required to cover the range given; this may not work in all instances and may not give the best set of bans.

Working product help and version check urls.
-Limitation on vbulletin.org meant that version urls weren't being checked correctly.
-Product was missing help url.