I am writing this article in order to help users ban correctly. I have realized that many problems in channels can be resolved if a op knew how to ban a user the right way. As a oper on UnderNet I get countless requests to help channels with an abusive user that "keeps coming back" in the channel. Some people will still find ways to get around bans in a channel, but I see all to often someone just redial to gain access. Some just have to change their user@ to get back in as well. So here is a quick lesson on how to ban the right way.
We will run through the different ways to ban a person.
The basics of a Ban
We are going to pretend we are banning driedee@fg67543-a.frl.home.net.
*** stazia sets mode: +b *!*driedee@*
/mode #channel +b *!*user@*
This ban will only ban the persons user@*. This means they can change their user@ reconnect and come right back in your channel. This ban is pretty much worthless.
*** stazia sets mode: +b *!*driedee@fg67543-a.frl.home.net
/mode #channel +b *!*user@host
This ban works really nice. However they can change their user@ quick, reconnect and guess what? Come right back in your channel. This ban can be used the first time but if they come back again I would suggest banning with the ban below.
*** stazia sets mode: +b *!*@fg67543-a.frl.home.net
/mode #channel +b *!*@host
This ban bans the entire host. No matter what their user@ is they will not be able to come back in the channel. This is the perfect ban for users that are on a permanent connection like cable and (A)DSL, as usually their @host doesn't change each time they connect to the Internet. However, on other types of connection (dialup modems) the host can change. For abusive users that change hostmask as they re log on you can use the next ban:
*** stazia sets mode: +b *!*@*.frl.home.net
This ban will keep this person out for good (except for one other reason which I will explain next) because it uses wildcards (*) in the ban.
What if his hostmask sometimes does not resolve?
Using this address still as our example: driedee@fg67543-a.frl.home.net
There are two parts to a address. You have the IP address which is numeric and the reverse dns which is the longer version. Sometimes it happens that a hostmask does not resolve correctly, and the user would not have his normal hostmask, but the numeric IP version of a hostmask.
You can use the /dns command in mIRC to get either IP address with:
/dns nick
*** Looking up fg67543-a.frl.home.net
*** dns Asmo is 212.120.104.251
So now let's say that he logs back on but his address is numeric. He could go around the ban you set above which was *!*@*.frl.home.net
If that happens you would do the ban below
/mode #channel +b *!*@212.120.104.*
Always good to take off the last set of numbers and use a wildcard (*), since that is the part that changes if the user does not have a permanent connection, like dialup modems.
Help, the channel is getting Join Flooded!
Also if you have a join flood in your channel and the addresses have a ~ in front of the user@ (e.g. ~driedee@fg67543-a.frl.home.net) You would want to set a ban like this for a little bit so the flood stops:
/mode #channel +b *!~*@*
That would ban everyone with a ~ before the user@ from your channel. This way your channel would not be entirely locked, like it will be when you set the channel to invite only with /mode #channel +i There is a small danger in this technique, some scripts might deop/kick users that fit a certain ban mask. If other channel ops have a ~ in their mask, they might be thrown of the channel by you. Tip: open a new temporary channel like #blahtestblah, invite some friends, op them and set a *!~*@* ban. This way you will know if it is save to use it whenever you really need it
? Discuss This Article here.
|
Syndicate
