![]() |
yes i upload files from package ... see anything extra there but nothing in my admin cp ...no extra menu item...
reg macc |
Is your account the superadmin account? If not, make sure your account has the extra admin permission assigned to it to allow for ip banning.
Also, refresh the menu frame of the admin cp. If you still can't see it, rebuild the bitfields. and refresh the menu again. |
yes my account is superadmin ..i put permissions and can not see ...uploaded files again ...no resuls ...
reg macc |
Ok, I found the problem... at some point i managed to loose a file from the archive. (the file that defines the menu...) New archive with missing file included now attached.
|
have updated but no results ...
reg macc |
I've added some code to the installer which should fix the issue you are having.
Incidentally, is anyone else having issues with the menu not showing? (it should appear under the users menu) |
So the CIDR (never heard of it before) of 32 means that if you enter an IP to ban it will ban all the IPs in the 0-31,32-63 etc range that the IP falls in? Or what?
What if I want to ban just the single IP as per the original vB IP banning system? Cos that's all that I will ever need to do. |
thanks ...now works
regards macc |
This will come in very useful, installed. :)
|
Quote:
imagine the ip address as a big binary number. each of the . seperated parts equates to 8 bits so an ip address as a number would look like this: 00000000 . 00000000 . 00000000 . 00000000 32 binary bits in total. The cidr range is specifying how meny of those bits must match before the ip is considered banned. specifying a cidr range of 32 means that ALL 32 bits must match and is thus the same as banning a single ip. The real power comes in when you want to ban larger ranges for people who have dynamic ip addresses. a cidr range of 24, for example matches only the most significant 24 bits of the ip so for the following ip, if all the 0's match it wouldn't matter what the x was set to 00000000.00000000.00000000.xxxxxxxx this is equivilant to banning an ip with only three segments to it. Currently the cidr is hard coded at 16, mostly because i didn't want admins on my own forums accidentilly banning the entire board cause they didnt know what it did. This will probably become an option at some point in the future (eg setting the max allowed cidr range) There is a note saying to leave the cidr at 32 if you dont know what it does :p Edit: just to clearly answer your question, If you just want to ban a single ip address, leave the cidr set to 32. |
All times are GMT. The time now is 01:48 PM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|