sevo: can you post the 'script language' it comes up with.

angeldevil: can you try with a different cidr; say 31 ?

TY Carnage i can ban that IP while change CIDR to 31

So if ive understood this correct if i use the CIDR range /24 to ban IP: 9.10.166.9/24 that will ban the [256 ips] from 9.10.166.0 through to 9.10.166.255.

Btw thats a Example IP :)

I can't get this to work either. I ban a single ip address using this mod and the same address is used just minutes after.....Hmmmmm.

I'm using (vBulletin 3.7.2 Patch Level 2)

I have just installed on 2 forums and nothing shows in the menu of either

thanks will test this ;)

i wonder... the banning of a single ip address works perfectly fine on my forums. I'm thinking it may be an issue in the under lying programs - php and mysql.

Can the people having problems with banning single ips (via pm if you wish) tell me what version of php and mysql you are using and if its 64 or 32 bit.

For now, ban using a cidr of 31.

Requests:

• Add more than one IP at a time (I have a lot of spam bots
• Some sort of comment system so we can organize our IP bans (Something like have categories like Spam Bot IPs and stuff)

Why when I enter some IP addresses it works, then when I enter certain other ones it comes up as 0.0.0.0 ( I tried CIDR 32 and 31 )?

That is the only glitch I see.....oh would be nice to have multiple fields to enter multiple IP addresses as well as having the script loop back tot he add IP page rather than the main page of admin.

Requests

* Enter more than one IP address
* Ability to update current entries
* Fix error of 0.0.0.0 showing up when IP address entered
* Loop either to entry screen of list of banned IP addresses after submit is hit

just waiting the full version :Peace:

Definately can?t wait for this to be final. Any ETA on when that will be ? ;)
Thanks for this Mod, I am sure its great once its final.

Wolfseye

is this working for vB 3.8.0 ?

Could I please have an example on how to use this ? I know how to ban IP Ranges in PLESK etc. so there its simple. For an example below I would like to know what to enter. I hope you can help me with that so I understand it correctly.

That is the IP range that I would like to Ban.
Now the CIDR would be:
So what would I would have to enter exactly in the IP Ban options of this Mod ? Thank you in advance. ;)

Wolfseye

Request:

- interfaces it with the IP-to-Country http://ip-to-country.webhosting.info...ountry.csv.zip

Hm, the registration thing doesnt seem to be working. No matter what I put under that field it bans the IP for everything, not just registration.

jesus: what vb version are you using?

kfiasche81: what integration would you like? All that is is a list of what ips come from what country...

tlwwolfseye: ban for 94.0.0.0 cidr set to 12 however the code (for safety reasons) is set to block ip bans over too large a range; so you will need to edit ipbans.php and change the 16 on lines 85 and 87 to 12.

caltek: what ips caused errors, which ones worked?

I don't seem to be able to find the option on where to access the mod.

Where would it be?

Ok, got that resolved, but am now getting the following error:

That seems like a print out of the code... well; some of it anyway - my suggestion is to upload a fresh copy of ipbans.php to your admincp dir.

If you wait an hour or so before doing that - i'm putting the finishing touches to V 0.3

Edit:

V0.3 is out now, i suggest you upgrade to that and see if that solves the problem

Installed v 0.3 and get this error when I try to add an IP:

Parse error: syntax error, unexpected '(', expecting '}' in ipbans.php on line 121


Also note that when I try to add an IP that starts with '1' I get 0.0.0.0 showing up. ( i.e. 192.1.243.1 shows up as 0.0.0.0 )

I got the same error but quickly figuered out the problem.
The author has used the short hand <? instead of <?php in the beginning of the PHP files.

This mode is not supported by many installations, and one should always use <?php when programming in PHP.

So, to fix your problem. Go in to all PHP-files in this modification and change the first line to read
<?php
instead of
<?

It seems like the author has ommited the ?> at the end of the files as well. This is poor practise.

Otherwise, top ace! :)

This is debatable. There are a good number of reasons for omitting it:
- Prevents excess white space at end of file; this can interfere with sending headers etc and cause xhtml validation errors.
- php.net dosn't use closing delimiters in its code eg http://www.php.net/source.php?url=/include/prepend.inc
- The closing tag is in fact optional.

Anyway, fixed file uploaded for those that dont have short tags enabled.

@caltek: what versions of php/mysql are you running? 32bit or 64 bit os?

thanks for the update. This does indeed enhance the IP banning functionality in vbulletin and could be useful to have as default. I have many banned IPs over the years, now I have no clue why any of them were banned.

Thats pretty much why i wrote this mod. It also allows me to give all admins ip ban privilages without them having access to the other options.

For anyone who was wondering; this does seem to work fine on vb 3.8.2 as i've just updated my own board to that version.

installed on 3.82

when I add an ip, it says added successfully, & the row is saved to the DB

BUT when I list banned ips, the list is blank.

not sure what is wrong

You checked the db and the ip is in there?

did you install the list of ip bans provided with the mod?

This is all I did

-------
Installation
Backup db.
Upload files from zip.
Import product.
Refresh admincp.
-------

yes, the ips are in the DB. I have 3 rows in the ipban table. I've attached an example. image 1 shows the row int he DB. image 2 is what I get when I click List "IP Bans"

Does this work on 3.8.2

When I ban a IP with an CIDR, it shows as 0.0.0.0 and /8 for example, instead of what I entered... In the case shown in the attached zip file, I was banning 194.8.0.0/8 which is spammer trying to spam my site... However, it all shows as 0.0.0.0 as you will see in the attachment...

What can I do about it, or is there a reason it wouldn't show the IP info?

Thanks,
kapii

I uploaded to my FTP and everything. But how do i access it?

It's in the left side of your ACP probably between the users and users groups...

re: ip ban against 194.8.0.0/8

I testeed this on my own board and it went through ok. (displaying a ban against 194.0.0.0 which is correct for /8)

can you tell me what versions of php/mysql you are running and if you are using 64 bit or 32 bit versions. I'm having issues tracking down the apparent random occurance of 0.0.0.0 bans...

Not Working
Mod Inutil

The same problem with 0.0.0.0

Please try
array('ip'=>'194.158.64.0','cidr'=>'19','descripti on'=>'Country'),
array('ip'=>'217.147.112.0','cidr'=>'20','descript ion'=>'Country'),

You will see 0 in 'ip' column in "ipban"-table

'ip'-column has attribute 'UNSIGNED'
I've changed attribute. Set it empty. Now in db:
194.158.64.0 -> -1029816320
217.147.112.0 -> -644648960

But in admin panel "List IP Bans" this ip-addresses are not shown.

Same problem here.. mad numbers for the duration, and new bans appear as 0.0.0.0 in the list.. this is new behaviour, there are bans in the list made on the .2a revision that are coherent..

this is ver 3.7.2, on a (shared) linux server..

edit: i should mention, this problem started BEFORE i upgraded from ver .2a, i imagined the upgrade would fix it, but it did not.

hmm. I will definitely hurt. thanks

Mine is not random... It happens every time I try to ban anything from 190 and up on the prefix number...

I'm using :
MySQL Version 5.0.77-community
PHP 5.2.5
Web Server Apache v1.3.41 (cgi)

I hope there is a way to fix this as the spammers and hackers are driving me nuts...

Thanks,
kapii
:eek:

Hello!
I just remove UNSIGNED attribute in table and now everything is OK

Thanks for this information, its very useful.

An ip address should be an unsigned int, however it would seem that some versions of php return a signed int instead hence the problem. I'll see if theres a better fix for this tommorow, however if not, changing the mysql field to signed will probably solve it.