Topic: Banning based on hostname

Well I happen to notice punBB dosnt support banning of hosts (ex. pool-52-234-324-32.sttlwa.dsl-w.verizon.net). I happen to use punBB and SMF for a number of high traffic sites but when users act up on my forums I end up having to ban users based on Host/ISP masks to prevent them from disconnecting there cable modem and obtaining a new ip. I use wild cards (since there supported in SMF) where the ip would be listed (ex. pool-*-*-*-*.sttlwa.dsl-w.verizon.net) I add more wild cards if that didnt work but the chances of that are slim to none.

Anyway, getting to the point, PunBB does not support banning of hosts and it kind makes me sad since punBB is a really nice forum software. Banning IPs and usernames isnt enough to stop users from disconnecting and reconnecting to get a new IP then making a new forum name just to spam. So my feature request is banning by Hostnames, e-mail addresses, IP, Username and support of wild cards (if not supported yest).

Much thanks.

^)^ DeathfireD ^)^

2

Re: Banning based on hostname

you can always ban host in .htaccess .....    host.net etc....

Re: Banning based on hostname

Thats not what I was asking for though. Id like it to be in the forum software thus the feature request.....

^)^ DeathfireD ^)^

4

Re: Banning based on hostname

Banning hosts !  Well that feature is really not so needed since pubb is meant to be small and every byte is important wink  I do not support the feature because it is easily done in other ways. It is matter of couple of seconds to do that IMO

Re: Banning based on hostname

I don't think this would make it into PunBB, since you would need to use gethostbyaddr each time the user visits a page, which can slow down the page load a lot for people who have IPs that don't resolve.
However, doing it should be easy enough: add a column to the bans table, edit admin_bans.php to allow you to add bans with hostnames, and change the check_bans function so that it gets the user's hostname and checks it against the bans

Re: Banning based on hostname

Smartys, wouldnt it be easyer to check host by log in and register? Doing it by page I can see your point but doing it by log in and register would be much less stressfull on the pages. Only issue would be sessions that havent expired yet (IE. Keep me logged in everytime I visit). Thats somthing I guess could be handled with the already made ban system that checks the username or IP or e-mail.

So in simple form. If I ban a user with the hostname  pool-*-*-*-*.sttlwa.dsl-w.verizon.net I ban his username "Noob" then I ban his IP 23.24.234.243 and finaly I ban his e-mail noob@verizon.net.

Then when the user visits the site again the forum goes by its default system "Username check, IP, e-mail" Since his name is banned and his IP is banned he gets the banned message. So now he disconnects his cable modem, gets a new IP from his host (assuming he can) and clicks on register. The forum now checks his host with banned hosts. It finds his host banned so it gives him the banned message screen.

Simple and effective. I know I could simple do this other ways but that kinda limits the audience of PunBB. Its just a request but I guess if its never added I or someone else could make a mod for it.

^)^ DeathfireD ^)^

Re: Banning based on hostname

Smartys, wouldnt it be easyer to check host by log in and register? Doing it by page I can see your point but doing it by log in and register would be much less stressfull on the pages

Except that bans on IPs are done on every forum page
And just moving it to two pages would simply make only those two pages slow (and you'd have to integrate the fact that you're only checking on 2 pages into check_bans) tongue

8 (edited by DeathfireD 2006-05-04 04:12)

Re: Banning based on hostname

Smartys wrote:

Smartys, wouldnt it be easyer to check host by log in and register? Doing it by page I can see your point but doing it by log in and register would be much less stressfull on the pages

Except that bans on IPs are done on every forum page
And just moving it to two pages would simply make only those two pages slow (and you'd have to integrate the fact that you're only checking on 2 pages into check_bans) tongue

Whats wrong with having it on just 2 pages over all? You only log in or register once. If you did it on every page then every page would load slow. Giving up 2 pages isn't that much of a sacrifice I think since its only checking the host when they trigger the register button or the log in button and not checking before they click register or log in. This would load the page fine the only slow time would happen after they click register or log in because thats when it would look over there host info and output the sorry your banned message.

Integrating it would not be that hard. But this was just a request to the forum scripters. I didn't have any intent of doing this on my own. Much thanks for your fast replys.

^)^ DeathfireD ^)^

9 (edited by Smartys 2006-05-04 10:36)

Re: Banning based on hostname

Whats wrong with having it on just 2 pages over all? You only log in or register once. If you did it on every page then every page would load slow. Giving up 2 pages isn't that much of a sacrifice I think since its only checking the host when they trigger the register button or the log in button and not checking before they click register or log in.

It can still make those pages go much more slowly smile
It doesn't matter that it's "just" two pages, it matters that it happens tongue
And you're forgetting people who choose "Remember my login" and thus normally don't login again. Those people would be unbannable. Thus, it does need to be checked on every pageview (otherwise you can stay unbanned just by never letting your login expire).

Re: Banning based on hostname

Not to be rude but did you read my other posts fully? If a user has the "Remember my login" and I ban there IP, Username, e-mail and hostname. The next time they view the page the normal ban system would take effect (IE. IP, username, e-mail). They would then get the banned page message saying sorry you are banned. So assuming the person disconnects there cable modem, DSL router to obtain a new IP from there host they now have access to the board again. BUT since I also banned there host if they tryed to register a new account they would be pointed to a nice "You are Banned" page. Now that I think of it You wouldnt even need it on the log in page since the username would be banned anyway.

So to brake it down have the banning host code just on the register page. I honestly dont see why you dont like this feature. It wouldnt take long to add as a MOD or a feature. The load time wouldnt be that effected if you did it right heck its in the majority of the forum software on the internet already.

I guess what im trying to get at is, the host banning would only prevent users from registering but they could still view the pages.

^)^ DeathfireD ^)^

11 (edited by Smartys 2006-05-04 19:35)

Re: Banning based on hostname

Not to be rude but did you read my other posts fully? If a user has the "Remember my login" and I ban there IP, Username, e-mail and hostname. The next time they view the page the normal ban system would take effect (IE. IP, username, e-mail).

What's to say they don't routinely disconnect/reconnect?
And yes, I read your other posts: I just believe that host banning is not a necessary feature and would be better off as a mod smile

Re: Banning based on hostname

What do you mean routinely? Like dialup? then they would still of course get the banned page because there username is banned along with their last used ip and e-mail address. So assuming they think there smart and try to register a new account their host is then checked before their register forum is processed and then get confronted with a nice banned page.

Ya I can see how this would be a better MOD but I don't understand why PunBB is being limited just to the audience of "small community's". I find it to be a very nice script and with some new features such as host banning it would work out for major community's. I suppose its something that will have to wait untill more users request it I guess.

Thanks for your input I hope to see a mod someday. If not then maby Ill look into making one.

^)^ DeathfireD ^)^

Re: Banning based on hostname

What do you mean routinely? Like dialup?

No, like someone who understands that they'll probably get banned and thus gets a new IP (and thus a new hostname) on a regular basis

then they would still of course get the banned page because there username is banned along with their last used ip and e-mail address.

Except that's one specific case: you shouldn't force people to have to enter username, etc before entering hostnames
Plus, bans are supposed to prevent viewing the forum in general: just because they're banned doesn't mean they can't post as a Guest

Ya I can see how this would be a better MOD but I don't understand why PunBB is being limited just to the audience of "small community's"

It isn't
There are plenty of large boards using PunBB
The key thing about PunBB is that it comes without a lot of the bloat that other forum packages have. However, if you want a PM system, you can install a mod for that. That way, while everyone starts from a small, clean, fast base, they can take that base and expand it in any way they want

I find it to be a very nice script and with some new features such as host banning it would work out for major community's

As I said, it does work out for major communities. wink
And saying that host banning is an important feature to a major community is like saying that a forum mascot is necessary for your forum members to be happy (yeah, I just made that up off the top of my head) tongue
PunBB is not meant to have every single feature under the sun. Yes, that means you might have to do a little more work through modding. However, in general, it provides you with cleaner and faster code.

14 (edited by DeathfireD 2006-05-05 05:53)

Re: Banning based on hostname

Smartys wrote:

No, like someone who understands that they'll probably get banned and thus gets a new IP (and thus a new hostname) on a regular basis

Ya proxys and stuff. But then you can just ban that whole proxy's range and not deal with it again since if a user is gonna use a proxy chances are its only to post back to something someone said as the final word. So if that happends then ban the range and be done with it.


Except that's one specific case: you shouldn't force people to have to enter username, etc before entering hostnames
Plus, bans are supposed to prevent viewing the forum in general: just because they're banned doesn't mean they can't post as a Guest

Its funny you say that since PunBB wont let me ban anyother way without first giving a username. Also if the forum is set up for registerd users to post only then the host banning would work fine. If your letting guests post then theres no need for a ban system to begin with since your opening your self up for spam, flaming and junk.

It isn't
There are plenty of large boards using PunBB
The key thing about PunBB is that it comes without a lot of the bloat that other forum packages have. However, if you want a PM system, you can install a mod for that. That way, while everyone starts from a small, clean, fast base, they can take that base and expand it in any way they want

Well a few people on here have plainly said that Pun is for small communitys and I find that sad how its being labled as that.

As I said, it does work out for major communities. wink
And saying that host banning is an important feature to a major community is like saying that a forum mascot is necessary for your forum members to be happy (yeah, I just made that up off the top of my head) tongue
PunBB is not meant to have every single feature under the sun. Yes, that means you might have to do a little more work through modding. However, in general, it provides you with cleaner and faster code.

Host banning is a major feature! The forums I run for a number of major sites need the host banning in order to filter the rif raf. IP banning dosnt work and by banning a range I basicly kill my whole fan base. Username and e-mail banning is usless since users just go to hotmail or yahoo and make a new account and then register. Also I dont see how you think host banning will effect the load time alot. I just wrote up a small host banning script for one of my sites and didnt notice a thing on a cable line. It worked so I guess ill expand it and make a mod since this is probably not going to be added as a feature anytime soon.

^)^ DeathfireD ^)^

Re: Banning based on hostname

Ya proxys and stuff. But then you can just ban that whole proxy's range and not deal with it again since if a user is gonna use a proxy chances are its only to post back to something someone said as the final word. So if that happends then ban the range and be done with it

I didn't mean proxies necessarily, I meant someone who gets a new IP from their ISP every time because they feel like doing so
And you can't ban a range if they keep using new proxies tongue

Its funny you say that since PunBB wont let me ban anyother way without first giving a username.

<span>The username to ban (case insensitive). The next page will let you enter a custom IP and e-mail. If you just want to ban a specific IP/IP-range or e-mail just leave it blank.</span>

Looks fine to me...

Also if the forum is set up for registerd users to post only then the host banning would work fine. If your letting guests post then theres no need for a ban system to begin with since your opening your self up for spam, flaming and junk.

Now that's just silly tongue
If you have guest posting you need the ban system even more to deal with the spam potential. And there are many legitimate uses for guest posting in forums (say, allowing a Bugs forum to be open to Guests so people can report not being able to login)

Well a few people on here have plainly said that Pun is for small communitys and I find that sad how its being labled as that.

I'd be interested to see where you found that: I usually go by this, personally tongue
And like I said, it's used in large communities

Host banning is a major feature!

Lets agree to disagree then: personally, I think IPs are a better solution 99% of the time (there are times when the ISP has enough ranges that you would use this, but banning a whole ISP is extreme in any case)

The forums I run for a number of major sites need the host banning in order to filter the rif raf. IP banning dosnt work and by banning a range I basicly kill my whole fan base

Then how does banning a hostname, which is essentially a larger range, NOT ban a whole lot of people? tongue

Also I dont see how you think host banning will effect the load time alot. I just wrote up a small host banning script for one of my sites and didnt notice a thing on a cable line

I read the comments on the PHP function page for gethostbyaddr

Re: Banning based on hostname

Smartys wrote:

I didn't mean proxies necessarily, I meant someone who gets a new IP from their ISP every time because they feel like doing so
And you can't ban a range if they keep using new proxies tongue

Ok ?.then you didn?t read one of my earlier posts?..where going around and around and talking about the same things but either miss understanding each other or just not connecting thoughts. Bla Im not gonna bother explaining again its to much work. Lets just say use wild cards to ban the host names and that would solve the issue of changing ips.

<span>The username to ban (case insensitive). The next page will let you enter a custom IP and e-mail. If you just want to ban a specific IP/IP-range or e-mail just leave it blank.</span>

Looks fine to me...

Well I cant get past the username ban page without banning a username. Not that, that?s a bad thing just saying I cant get past it.

Now that's just silly tongue
If you have guest posting you need the ban system even more to deal with the spam potential. And there are many legitimate uses for guest posting in forums (say, allowing a Bugs forum to be open to Guests so people can report not being able to login)

Now that?s silly. Allowing guests to post is like saying hey spam me now! At least with register users you can keep tabs on them and see what there doing. Guests there free to do anything banning them would do nothing by IP.

I'd be interested to see where you found that: I usually go by this, personally tongue
And like I said, it's used in large communities

Yes Iv seen large communities use the forum but like I said when I visit here reading comments and arguments there?s also a point where someone explains that punBB is for small communities and not large. Maby its because I read the forums over the site I don?t know.

Lets agree to disagree then: personally, I think IPs are a better solution 99% of the time (there are times when the ISP has enough ranges that you would use this, but banning a whole ISP is extreme in any case)

Ill agree with you but still security is security. Saying that you wouldn?t like an extra method of keeping your forums safe from spammers, scammers, and jerks is your opinion I guess. I just find it weird that you don?t want any extra-added security. This is like saying hey lets have sex without a condom because I took the birth control pill! But wait its not 100% protective just like IP banning. Id take security over any other feature that people suggest anyday.

Then how does banning a hostname, which is essentially a larger range, NOT ban a whole lot of people? tongue

Im not banning the whole host. A host name is made up of different parts and can be different depending on the ISP. For example some have ip, state or country, isp router, isp host name (ex. A-12-23-12-23-lund-nh-comcast.com). By banning the correct parts you will not effect the rest of the users that use that host.

I read the comments on the PHP function page for gethostbyaddr

Its one thing to read then it is to do. Since PunBB is already small and lightweight you wouldn?t notice any slow load times at all. At the most an extra 2 seconds.

Lets just agree that there?s nothing more to say. Since college is done and the sites I?m using punBB on are now open. I?m sure I will be forced to make my own MOD to ban hostnames. When and if I do; ill be sure to post it on here for you to see.

It was nice talking to you smile

^)^ DeathfireD ^)^

17 (edited by Smartys 2006-05-06 10:07)

Re: Banning based on hostname

Im not banning the whole host. A host name is made up of different parts and can be different depending on the ISP. For example some have ip, state or country, isp router, isp host name (ex. A-12-23-12-23-lund-nh-comcast.com). By banning the correct parts you will not effect the rest of the users that use that host.

Err, I'm aware of what a hostname is: are you? wink
For example, my hostname is pool-71-247-100-161.nycmny.east.verizon.net
My IP is 71.247.100.161
How would you go about banning me?
Personally, I would ban 71.247.*.*
Why?
Because all the IPs for my area are in that block of IPs.
Now, I'd love to see an example of banning with a hostname that couldn't be done with an IP except where you're trying to ban a whole ISP tongue

Now that?s silly. Allowing guests to post is like saying hey spam me now! At least with register users you can keep tabs on them and see what there doing. Guests there free to do anything banning them would do nothing by IP.

Lets just agree to disagree on that then wink

Ill agree with you but still security is security. Saying that you wouldn?t like an extra method of keeping your forums safe from spammers, scammers, and jerks is your opinion I guess.

It's that I don't need it tongue

I just find it weird that you don?t want any extra-added security. This is like saying hey lets have sex without a condom because I took the birth control pill! But wait its not 100% protective just like IP banning. Id take security over any other feature that people suggest anyday.

Host banning is not 100% protective. However, I find it only necessary when I need to ban an ISP completely, and I can do that other ways.
It's actually much more like riding your bike and saying "hey, I don't feel safe enough with this helmet: can I wear another one over it?" tongue

Its one thing to read then it is to do. Since PunBB is already small and lightweight you wouldn?t notice any slow load times at all. At the most an extra 2 seconds.

Untrue: at least from what I read 10 seconds seems to be the default timeout for the lookup. Of course, that probably varies depending on the server's settings (ie: on my computer here, DNS takes ~5 seconds to return that it found nothing)

I have nothing against anyone wanting to have hostname banning, I just feel that the unnecessary slowness it might cause would be bad as well as that in 99% of cases it's just a redundant feature

Re: Banning based on hostname

Theres more you can do with hosts banning its not made just for banning an ISP or ip. Read a bit on it since I dont have time right now to post fully all the things you can do with it.

And btw by dafault would be 10 seconds but by putting a timeout time to override it you could set it to 1 and it would still sucessfully work. but Iv tested without putting in a timeout time and it seems to work in 1 or 2 seconds. So if it was to be added im sure putting in a time out time to override the default would make it less of a hastle for people like you.

The slowness you talk about is only if you code it wrong. Theres endless ways of doing it to speed up the process. Dont just read somthing and assume thats what it is and thats the only way you can do it.

^)^ DeathfireD ^)^

Re: Banning based on hostname

Theres more you can do with hosts banning its not made just for banning an ISP or ip. Read a bit on it since I dont have time right now to post fully all the things you can do with it.

I've tried to but I've been unable to really find much other than banning an ISP (when it is quite useful).
Could you point me in the right direction or give me some examples?

And btw by dafault would be 10 seconds but by putting a timeout time to override it you could set it to 1 and it would still sucessfully work. but Iv tested without putting in a timeout time and it seems to work in 1 or 2 seconds. So if it was to be added im sure putting in a time out time to override the default would make it less of a hastle for people like you.

I don't think you can set a timeout though unless you rewrite the function (ie: http://us3.php.net/manual/en/function.g … .php#46869)
And I don't think Rickard would implement something that would be used on every page that could potentially not work on a lot of servers

The slowness you talk about is only if you code it wrong. Theres endless ways of doing it to speed up the process. Dont just read somthing and assume thats what it is and thats the only way you can do it.

I don't think it's necessarily coding it "wrong," from what I read it sounds more like not anticipating the delay from DNS servers when a lookup doesn't return anything. It's a feature of the function. You certainly can write your own function with timeouts, etc but that forces you to rely on external things that some servers might not have and others might have but might not allow

I do agree with you though (although I didn't before) that one call to gethostbyaddr per pageview probably won't add enough generation time to be noteworthy in most cases. However, I still haven't been able to find a use for this other than banning an ISP that may have multiple IP ranges but keeps the same hostname format

20 (edited by DeathfireD 2006-05-10 03:45)

Re: Banning based on hostname

Smartys wrote:

Theres more you can do with hosts banning its not made just for banning an ISP or ip. Read a bit on it since I dont have time right now to post fully all the things you can do with it.

I've tried to but I've been unable to really find much other than banning an ISP (when it is quite useful).
Could you point me in the right direction or give me some examples?

And btw by dafault would be 10 seconds but by putting a timeout time to override it you could set it to 1 and it would still sucessfully work. but Iv tested without putting in a timeout time and it seems to work in 1 or 2 seconds. So if it was to be added im sure putting in a time out time to override the default would make it less of a hastle for people like you.

I don't think you can set a timeout though unless you rewrite the function (ie: http://us3.php.net/manual/en/function.g … .php#46869)
And I don't think Rickard would implement something that would be used on every page that could potentially not work on a lot of servers

The slowness you talk about is only if you code it wrong. Theres endless ways of doing it to speed up the process. Dont just read somthing and assume thats what it is and thats the only way you can do it.

I don't think it's necessarily coding it "wrong," from what I read it sounds more like not anticipating the delay from DNS servers when a lookup doesn't return anything. It's a feature of the function. You certainly can write your own function with timeouts, etc but that forces you to rely on external things that some servers might not have and others might have but might not allow

I do agree with you though (although I didn't before) that one call to gethostbyaddr per pageview probably won't add enough generation time to be noteworthy in most cases. However, I still haven't been able to find a use for this other than banning an ISP that may have multiple IP ranges but keeps the same hostname format

Well I can?t really search for stuff on google right now but I can give you an example of a few ways of banning a host different ways then talked about already. It?s not so effective but still can slow down people you do not wish to view the site.

A host is made up of other things not just your ISP and IP as you can tell from the host you pasted before. As said it sometimes has your country, state, town or city letters in it each ISP does there host diffrently thus making host banning more effective if you really read up on it. It also sometimes has your ISPs router that you go through in order to view pages. Now lets say it has your state and you know the ISP is a world wide ISP or is known to be in other states within the US. You also know that no other members are from the state of the spammer. So you simple just put wild cards in for the state or town. (ex. pool-71-247-100-161.*.east.verizon.net). Its not as effective but certainly another option in the banning process. Now for routers, most ISPs have more then one router that forwards its users to the web. You can ban his ISP router from the host string and that will prevent him or her from posting on the forums at least until he or she resets his or her router and gets re-routed to another router owned by their ISP. But it?s unlikely that it will happen quickly it takes longer then getting a new IP. I know my ISP, Adelphia, takes hours to route me to a new router if I try disconnecting my cable modem to obtain a new IP. So even if someone did it, you could always ban their town, router and full ip. This would stop them from viewing your forums. Now there are more tricks but like I said I don?t really have time to find references on google. But you get the idea, host banning isn?t meant to be 1 thing. You use it in conjunction with other banning methods to help strengthen your security.

For example say you where spamming on my forum the first thing I would do is ban your username and e-mail. Then I would work my way to your IP and then add in your host mask and add a wild card for nycmny assuming NycmNY is from New York and since I have no one from NY that goes to my site I have little care about who else I?m banning using verizon in NY (pool-71-247-100-161.*.east.verizon.net) I can of course add in wild cards on your IP in conjunction with your state but then this would possibly ban other users (pool-71-247-*-*.*.east.verizon.net). Now this was just an example, id give it more thought before I ban anyone from a site or forum I run. I like to see what people do when there banned so I don?t always IP or host ban first. I mainly username and e-mail ban and keep an eye on new register users. Then if its the same person I IP ban them and fool with there host file banning.

Also yes setting default in the function is one way and it does not involve any other programs. It also wouldn?t be all that hard to implement into all or 1 page hell you could toss the variable in the config file to let the hosters change it to whatever they wish or disable it all together. But keep in mind the time it takes to resolve the host to IP doesn?t take as long as you think. At the most it would possibly take 10 seconds Iv never seen it go longer then that and Iv run 2 major sites using host banning. You could take a look at the forum software Simple Machines Forum for how they do the host banning and how much of a delay it pays on the forums. It?s not a whole lot but there software is cluttered with other things that cause it to be slow loading thus why I?m here lol.

^)^ DeathfireD ^)^

Re: Banning based on hostname

Well, except pool-71-247-100-161.*.east.verizon.net is the equivalent of banning my IP and pool-71-247-*-*.*.east.verizon.net is the equivlalent of banning 71.247.*.*
The problem is that the part you were wildcarding that wasn't my IP doesn't change. To ban people from NYC you should have banned pool-*-*-*-*.nycmny.east.verizon.net, except as I said that can be achieved equally well by banning using an IP and wildcards

Just out of curiosity, what would you do with this hostname?
d51A599E8.access.telenet.be

Re: Banning based on hostname

Smartys wrote:

Well, except pool-71-247-100-161.*.east.verizon.net is the equivalent of banning my IP and pool-71-247-*-*.*.east.verizon.net is the equivlalent of banning 71.247.*.*
The problem is that the part you were wildcarding that wasn't my IP doesn't change. To ban people from NYC you should have banned pool-*-*-*-*.nycmny.east.verizon.net, except as I said that can be achieved equally well by banning using an IP and wildcards

Just out of curiosity, what would you do with this hostname?
d51A599E8.access.telenet.be

Wrong, by banning every octet (*.*.*.*) your banning the whole ISP not just their state. That?s a no no if you want to still receive users from Verizon. Banning the nycmny is banning your ISPs state/town/city tag like you said your self, that doesn?t change no matter how many times you reset your cable/dsl modem So by wild carding it your stopping any IP given from the state of NY with the ISP Verizon, but still allowing other Verizon users to view the forum from other states. Banning every octet is banning their ISP, host, address and range. That?s not what where trying to do here. Lets say we do ban every octet like you sugested and I use Verizon in the state of Maine. If I try to browse the forum id be banned also since you banned the ISP octet.


Also on your second question d51A599E8.access.telenet.be is weird I wouldn?t just ban it without keeping watch on the user to see how many different host strings come from telenet.be. If there was more such as d4d493d3.access2.telenet.be and the user was using them to spam then id wild card the access part d51A599E8.*.telenet.be of course that?s not very safe if your just guessing but you get the idea. Host banning is a more refined banning method. But like you already noticed most ISPs have different strings not all are plain as day.

Plain and simple, IP banning is nice and all but there?s just some things that host banning is more refined about or more up front about.

^)^ DeathfireD ^)^

Re: Banning based on hostname

I think this is a bad idea, and I hope punbb will never implement this feature.

1. Can cause severe slow down ,and if your DNS forwarder is down, you may screw up your forum,and cause a self D.o.S tongue

2. Gives you no real security, DNS names are a piece of cake to change/spoof

3. It's not he job of a Forum, you have plenty of tools to do this ( htaccess files, httpd.conf)

The Internet mail is frecuently screwed up by DNS problems, do not broke forums too ¡¡ tongue

24 (edited by Smartys 2006-05-11 00:06)

Re: Banning based on hostname

Wrong, by banning every octet (*.*.*.*) your banning the whole ISP not just their state

Lets say we do ban every octet like you sugested and I use Verizon in the state of Maine. If I try to browse the forum id be banned also since you banned the ISP octet

Wrong wink
pool-*-*-*-*.nycmny.east.verizon.net does not ban the whole ISP
Why?
Notice the nycmny part.
Now, look at pool-71-248-10-87.bltmmd.east.verizon.net (another valid IP range)
Now, tell me: how does banning pool-*-*-*-*.nycmny.east.verizon.net do that?
All it does is ban any IPs from Verizon in NYC, which is NOT what your thing does
Now, if I banned *.verizon.net, I would be banning all of Verizon

Also on your second question d51A599E8.access.telenet.be is weird

And yet it isn't wink
How about toronto-HSE-ppp3959157.sympatico.ca?
Or 154.85-200-22.bkkb.no?
Or ACA90D41.ipt.aol.com?
Or CPE000f3d36f1bb-CM0011ae8d72e8.cpe.net.cable.rogers.com?
Or 203-217-95-78.dyn.iinet.net.au?
Or fl-71-3-115-202.dyn.sprint-hsd.net? (This one can be done relatively easily)
Or ip173-168-59-62.adsl.versatel.nl?
Or ip173-180-59-62.dialup.versatel.nl?
Or host86-137-247-148.range86-137.btcentralplus.com?
Or 64.178.114.65.dynamic.dejazzd.com?
Or 12-219-18-153.client.mchsi.com?
Or dpc6747129199.direcpc.com?
(OK, I'm getting bored coming up with examples, although I do love IRC tongue)

My point is that "odd" hostnames are not uncommon, and thus are not all that odd
These are all real hostnames. Now, tell me how you can use these other than banning ISPs or IP ranges or a specific IP?
Host banning is useful in a very small number of cases and in those cases it relies on the hope that ISPs don't route their customers through routers outside of the area in the hostname for whatever reason (like, say, enough of their hardware goes down that they have to route people to other routers).
It's useful and works on a bunch of ISPs in the US and I'm sure some internationally but I believe the vast majority don't list the location of IPs in the hostnames and thus it's useless on them except to ban the ISP

Re: Banning based on hostname

Smartys wrote:

Wrong wink
pool-*-*-*-*.nycmny.east.verizon.net does not ban the whole ISP
Why?
Notice the nycmny part.
Now, look at pool-71-248-10-87.bltmmd.east.verizon.net (another valid IP range)
Now, tell me: how does banning pool-*-*-*-*.nycmny.east.verizon.net do that?
All it does is ban any IPs from Verizon in NYC, which is NOT what your thing does
Now, if I banned *.verizon.net, I would be banning all of Verizon

My bad for some reason I was thinking you where banning the IP not the host since that's all you been talking about for the past 5 days.

Now with the above you posted what?s that tell you? It's easier to ban using the host then IP wink
Anyway its pointless to continue we both have strong feelings about banning and where not gonna quit till someone is right so why not save us time and just forget it until its requested more.

And yet it isn't wink
How about toronto-HSE-ppp3959157.sympatico.ca?
Or 154.85-200-22.bkkb.no?
Or ACA90D41.ipt.aol.com?
Or CPE000f3d36f1bb-CM0011ae8d72e8.cpe.net.cable.rogers.com?
Or 203-217-95-78.dyn.iinet.net.au?
Or fl-71-3-115-202.dyn.sprint-hsd.net? (This one can be done relatively easily)
Or ip173-168-59-62.adsl.versatel.nl?
Or ip173-180-59-62.dialup.versatel.nl?
Or host86-137-247-148.range86-137.btcentralplus.com?
Or 64.178.114.65.dynamic.dejazzd.com?
Or 12-219-18-153.client.mchsi.com?
Or dpc6747129199.direcpc.com?
(OK, I'm getting bored coming up with examples, although I do love IRC tongue)

My point is that "odd" hostnames are not uncommon, and thus are not all that odd
These are all real hostnames. Now, tell me how you can use these other than banning ISPs or IP ranges or a specific IP?
Host banning is useful in a very small number of cases and in those cases it relies on the hope that ISPs don't route their customers through routers outside of the area in the hostname for whatever reason (like, say, enough of their hardware goes down that they have to route people to other routers).
It's useful and works on a bunch of ISPs in the US and I'm sure some internationally but I believe the vast majority don't list the location of IPs in the hostnames and thus it's useless on them except to ban the ISP

And my point is you can ban the same if not more then using IP banning. Its all on your preference and time spent. Also the above addresses are not confusing, in fact there almost all easier then the first one you posted. FYI like I said 3 times already, each host has there own method of doing there string not all have country, state, town, city. Not all have routers yada yada.

Anyway like I said 4 or so posts ago, lets just stop talking about it. Ill come up with a mod sometime soon and just use that since it?s obvious that you strongly don?t like the idea.

PS.
@judas_iscariote - Its just as easy to spoof your IP. Also try reading the above posts. Adding in a time out in the function would of course solve that issue.

Lets just forget this topic for now, at least till others request this feature.

^)^ DeathfireD ^)^