[an error occurred while processing this directive] [an error occurred while processing this directive]
Op/Voice Information .....

Bans & Mask Type Definitions

[ Page 1 ]    [ Page 2 ]   [ Page 3 ]    [ Page 4 ]   

MASKS

Now that we know what are the parts from an IP , we can use that info to set up our bans . The following info has been taken from the November 97 Newsletter (hint: there are lots of good info in those newsletter, you can find them here)

The available mask types are:

0: *!user@host.domain
1: *!*user@host.domain
2: *!*@host.domain
3: *!*user@*.domain
4: *!*@*.domain
5: nick!user@host.domain
6: nick!*user@host.domain
7: nick!*@host.domain
8: nick!*user@*.domain
9: nick!*@*.domain

Okay, when a person logs onto the internet, their ip shows four things.

Nick Userid@host.domain.

For example, this is me:

bossmom is bossmom@elwo-01-122.dialup.netins.net * Enjoy the Journey........

nickname - bossmom
userid - bossmom
host - @elwo-01-122.dialup. - See Note (1)
domain - netins.net - See Note (2)
real name info - * Enjoy the Journey........ - See Note (3)

Note (1): Your Host is whatever connection you receive from your local ISP's (Internet Service Provider) computer. Everyone is assigned a number, or some manner of identification, each time you log on.

Note (2): Many times the country a person is from can be seen from the domain)

Note (3): Please don't put your real name here ;)

Ok, now that we've got that straight (right?) let's go over each mask type, and how we use them for banning purposes.

0:*!user@host.domain
Bans the entire ip, and the *! bans the exact hostname. However, if the person logs off, and logs on again, then the 'host' (remember, this is your computer connection) will change, and the ban becomes ineffective.

1:*!*user@host.domain
Pretty much the same as the line above, except that the *!*user will ban anybody with the userid in their userid. For instance, let's say someone banned *!*mom@*.host.domain. If another person tried to join using *!*nuttymom@*.host.domain, the ban would STILL keep them out, since their userid contained 'mom@'.

2:*!*@host.domain
The *!* is like a wildcard, and this ban will pick up anybody from a particular host.domain. However, still not very effective as all a person has to do is log off and log back on again, hence changing the 'host' connection, and then an innocent person who happens to get the previous guy's host-computer connection, is now banned.

3: *!*user@*.domain
This is the ban mask that we generally use. X also automatically selects this ban mask, so I figure if it's good enough for X, then it's good enough for us. Okay, the *!*user = ident (for mIRC, you'll find this under file/setup/ident), and the *.domain means that anyone using that userid@domain is banned. This is generally a good ban to set. Even if the person logs off, and logs back on, the ban will catch them, as it's not dependent on the host connection, but only dependent on the userid@domain. One problem exists, though. For the more computer literate, they might figure out that if they change their userid, then they can keep getting around the ban. It's these folks that get the domain ban, or the following ban type 4:

4:*!*@*.domain
This ban is reserved for the really nasties. The ones that know that if they change their userid, the *!*user@ part, they can get back into the channel. This ban mask bans everyone that uses a particular domain. For instance, if a ban were set as *!*@*.netins.net, it would ban everyone from that domain, including me. We only set these in extreme cases.

5:nick!user@host.domain
Not a very effective ban, as it selects an exact nickname/userid@host.domain. If the person were to change any part of any of that information, then the ban would no longer be effective.

6:nick!*user@host.domain
Pretty much the same as the previous one (not an effective ban)

7:nick!*@host.domain
Will ban a specific nick from a specific host.domain. Still not very effective, because if someone changes their nickname, or logs off then back on again (which changes the 'host'), then the ban is no longer effective.

8:nick!*user@*.domain
Bans a specific nick/ident from a particular domain. This will catch someone if they log off, then log back onto IRC, BUT..still won't catch them if they change their nick or userid, so this is not a very effective ban either.

9:nick!*@*.domain
Bans anyone using a particular nickname from a particular domain. You can probably figure out the problems with this one. IF a person changes their nickname, then the ban no longer is effective.

As you have seen not all the bans are useful. The default ban for us is number 3. It's the most complete, and is also X's default ban mask . We can use number 2 to ban clones . As you know clone definition is two connections from a same modem, so if we ban @host.domain, we are precisely banning those clones. Bans of type 4, domain bans, are for those nasty guys that get around our regular bans by changing their userid. We must be careful with these bans because they are affecting many people, perhaps a fellow op or a friend .

There are two other bans there are not in that list and we use a lot in channel :

Nick ban: nick!*@* -- we ban that specific nick (very good for bad nicks)

Userid ban: *!*userid@* -- very good against nasty IPs

What about numeric ips? We use number three as default also. As you may remember, the host part in a numeric ip was the last number so number three ban would be:

Userid@first-number.second-number.third-number.*
Beginner@177.55.42.*

Let's move to the next page to learn about setting bans.


[ Page 1 ]    [ Page 2 ]   [ Page 3 ]    [ Page 4 ]   


 


[an error occurred while processing this directive]
[an error occurred while processing this directive]