Difference between revisions of "Ban"

From Mibbit Wiki
Jump to: navigation, search
(Channel Bans)
(See also: original page is gone)
 
(27 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{notice|This page is lacking a lot of informationFeel obliged to add some.}}
+
{{articles}}
 +
{{faq|Channel bans do not have a certain expiry timeOperators have to remove the bans themselves, at their own discretion.}}
  
A ban is a method of keeping users from returning to a specific channel or server.
+
A '''ban''' prevents a user from joining a specific channel or server.
  
== Channel Bans ==
+
== Overview ==
 +
''To remove a ban, see [[Unban]].''
  
 
Banning in channels are done most commonly with the channel mode +b.   
 
Banning in channels are done most commonly with the channel mode +b.   
Line 13: Line 15:
 
To make this easier, the Mibbit client has a default [[alias]] of /ban {{hm}}.   
 
To make this easier, the Mibbit client has a default [[alias]] of /ban {{hm}}.   
  
To remove a ban, either use the IRC command of /mode #chan -b {{hm}} or the Mibbit client default alias of /unban {{hm}} or /deban {{hm}}.
+
To view the banlist, use the command /mode #chan +b or just /ban<space><enter> (if you are in the channel).
 +
A list of banned users is shown in the form of:
 +
    ''<nowiki>[</nowiki>cancel ban button<nowiki>]</nowiki> <nowiki>[</nowiki>{{hm}}<nowiki>]</nowiki> <nowiki>[</nowiki>operator who banned<nowiki>]</nowiki> <nowiki>[</nowiki>time of ban<nowiki>]</nowiki>''
  
To view the banlist, use the command /mode #chan +bA list of banned users is shown in the form of:<br /> ''<nowiki>[</nowiki>cancel ban button<nowiki>]</nowiki> <nowiki>[</nowiki>{{hm}}<nowiki>]</nowiki> <nowiki>[</nowiki>operator who banned<nowiki>]</nowiki> <nowiki>[</nowiki>time of ban<nowiki>]</nowiki>''
+
If there are ops that are new to IRC, they may accidentally ban the entire channel by banning *!*@*.  To easily recover from this, users can make sure certain [[hostmask]]s for unable to be banned with the channel mode +e.  To use, find out what the hostname of the person is, and use the command /mode #chan +e *!*@hostnameMode +e is 'exception', and if a [[hostmask]] matches one on the exception list, the user cannot be banned.
  
If there are ops that are new to IRC, they may accidentally ban the entire channel by banning *!*@*To easily recover from this, users can make sure certain hostmasks for unable to be banned with the channel mode +e.  To use, find out what the hostname of the person is, and use the command /mode #chan +e *!*@hostname.
+
You must be a channel operator, half-operator, super-operator (or admin as called on the Mibbit client and [[UnrealIRCd]]), owner, or founder to set these modesThe [[chanserv]] modes for these are +h, +o, +s, and +q.
  
You must be a channel op or half op to set bans.
+
=== Ban Types ===
  
In most IRC clients you can simply type, /ban nick or /ban user@host.
+
Some servers allow for special types of bans.  This subsection entails what they are, and how to use them on those servers.
  
Set a Ban with ChanServ:
+
==== Quiet Ban ====
 +
 
 +
This ban type makes it so that any users with a specific [[hostmask]] cannot send messages, but can receive them in the channel they are banned.  They can also join and part at will.  To issue a quiet ban on [[UnrealIRCd]], use the following format:
 +
 
 +
    /mode #chan +b ~q:{{hm}}
 +
 
 +
==== Nickchange Ban ====
 +
 
 +
This ban type makes it so that any users with a specific [[hostmask]] cannot change their nick while in the channel, but can still talk.  They can join and part at will.  To issue a nickchange ban on [[UnrealIRCd]], use the following format:
 +
 
 +
    /mode #chan +b ~n:{{hm}}
 +
 
 +
==== In Other Channel Ban ====
 +
 
 +
Do you not like those in one channel also being in your channel.  On [[UnrealIRCd]], you can prevent that using a special type of ban.  To use it, use the following format:
 +
 
 +
    /mode #chan +b ~c:#badchan
 +
 
 +
Users can prefix power modes before (+, %, @, &, and ~ for voice, halfop, op, admin, and owner respectively) it for it to work on those of that power or higher.  If one wishes to ban those that have less than a certain mode on a certain channel, they can use the following format:
 +
 
 +
  /mode #chat +eb ~c:<prefix>#chan  ~c:#chan
 +
 
 +
==== Realname Ban ====
 +
 
 +
A realname bans on real name and underscores (_) are treated also as spaces ( ).  For [[UnrealIRCd]], the format is:
 +
 
 +
    /mode #chan +b ~r:<realname>
 +
 
 +
 
 +
~x: bans can also be combined, e.g.,
 +
 
 +
    /mode # +b ~q:~c:#OtherChan
 +
 
 +
===Set a Ban with ChanServ===
 +
 
 +
{{notice|This section is convoluted.  If you can make it not so convoluted, feel free to.  To all other users, it is suggest not to read this.}}
  
 
You may wish to set a ban using ChanServ. Depending on the SIGNKICK settings of your channel this might mask which op set the ban (explained further below.)
 
You may wish to set a ban using ChanServ. Depending on the SIGNKICK settings of your channel this might mask which op set the ban (explained further below.)
Line 31: Line 70:
 
SIGNKICK Enables or disables signed kicks for a channel. When SIGNKICK is set, kicks issued with the ChanServ KICK or BAN commands will have the nick that used the command in their reason. If you use LEVEL, those who have a level that is superior or equal to the SIGNKICK level on the channel won't have their kicks signed. The command to set SIGNKICK is: /msg chanserv set #channel signkick {ON | LEVEL | OFF}
 
SIGNKICK Enables or disables signed kicks for a channel. When SIGNKICK is set, kicks issued with the ChanServ KICK or BAN commands will have the nick that used the command in their reason. If you use LEVEL, those who have a level that is superior or equal to the SIGNKICK level on the channel won't have their kicks signed. The command to set SIGNKICK is: /msg chanserv set #channel signkick {ON | LEVEL | OFF}
  
You can put a user@host in for the nickname instead if you like. For example, if we wanted to ban everyone from AOL, we would use the following: /ban #channel *!*@*aol.com and to remove that ban, we would use: /ban -r #channel *!*@*aol.com
+
== Server Bans ==
 +
An [[IRCop]] with enough privileges may ban users on servers.  The following types of server bans are as follows.  Command formats are not given for these bans, as these types of bans are server dependent, and can be found in respective documentations.
 +
 
 +
=== K-line ===
 +
The K-line is a local server ban (specific to a single server, not the entire IRC network) that bans the offensive user's hostname.
  
When banning a nickname, it is useful to know that there are different types of user@host masks you can use. The table below shows what each result of using the command: /ban NICK #
+
=== G-line ===
 +
The G-line (Global K-line) works exactly as the K-line, but is global. G-lines can expire, but in some cases they are permanent.
  
# represents the numbers in the chart below. There are 9 different types of bans - they are as follows:
+
=== Z-line ===
 +
On IRCds such as UnrealIRCd, the Z-line is a "powerful" ban, it is performed on IP address instead of the hostmask, making sure that users from that IP address will not join. Z-lines could expire, but in some cases it is permanent.
  
# *!user@host.domain
+
=== GZ-line ===
# *!*user@host.domain
+
Some IRCds support the GZ-line (Global Z-line). It is exactly as the Z-line itself, but it's global, and network-wide. UnrealIRCd has GZ-line support.
# *!*@host.domain
+
The GZ-line is an effective way of blocking static IP users, and keeping them out.
# *!*user@*.domain
 
# *!*@*.domain
 
# nick!user@host.domain
 
# nick!*user@host.domain
 
# nick!*@host.domain
 
# nick!*user@*.domain
 
# nick!*@*.domain
 
  
If you don't specify a type (number at the end of the ban), and you were to just type /ban #channel NICK then mIRC will ban the user's exact user@host.
+
=== D-line ===
 +
On other IRCds, such as Charybdis, a D-line replaces a Z-line.  It is called a D-line because it "denies" the IP address from connecting.  Charybdis does not have support for a Z-line or a GZ-line.  By using its "cluster" configuration feature, D-lines can be synchronized between servers, providing a type of 'GZ-line'.  This enables for very nice big network support since the administrator of one server may want to allow certain servers they trust to synchronize D-lines and K-lines, but not allow others.
  
#channel isn't totally necessary either. If you are on typing in a channel window, for example, #channel, you could use: /ban NICK 3
+
== See also ==
 +
* [http://archive.is/eWVU1] - archieved Toxin article on bans.
 +
* [[Unban]]
  
The above command would result in NICK being banned from #channel with the hostmask: *!*user@*.domain
+
[[Category:IRC]][[Category:Commands]][[Category:Unreal]][[Category:Mode]][[Category:Ban]]

Latest revision as of 12:40, 6 February 2016

Wiki Home | FAQ | Features | IRC Commands | IRC Modes | Widget Information | Widget: WebIRC Server Setup | URI Parameters | Wish List | Registration Information | Mibbit Staff

Home | Quick Start Guide | Live Mibbit Help


Channel bans do not have a certain expiry time. Operators have to remove the bans themselves, at their own discretion.


A ban prevents a user from joining a specific channel or server.

Overview

To remove a ban, see Unban.

Banning in channels are done most commonly with the channel mode +b.

The IRC command for banning is:

   /mode #chan +b nickname!username@hostname.  

To make this easier, the Mibbit client has a default alias of /ban nickname!username@hostname.

To view the banlist, use the command /mode #chan +b or just /ban<space><enter> (if you are in the channel). A list of banned users is shown in the form of:

    [cancel ban button] [nickname!username@hostname] [operator who banned] [time of ban]

If there are ops that are new to IRC, they may accidentally ban the entire channel by banning *!*@*. To easily recover from this, users can make sure certain hostmasks for unable to be banned with the channel mode +e. To use, find out what the hostname of the person is, and use the command /mode #chan +e *!*@hostname. Mode +e is 'exception', and if a hostmask matches one on the exception list, the user cannot be banned.

You must be a channel operator, half-operator, super-operator (or admin as called on the Mibbit client and UnrealIRCd), owner, or founder to set these modes. The chanserv modes for these are +h, +o, +s, and +q.

Ban Types

Some servers allow for special types of bans. This subsection entails what they are, and how to use them on those servers.

Quiet Ban

This ban type makes it so that any users with a specific hostmask cannot send messages, but can receive them in the channel they are banned. They can also join and part at will. To issue a quiet ban on UnrealIRCd, use the following format:

    /mode #chan +b ~q:nickname!username@hostname

Nickchange Ban

This ban type makes it so that any users with a specific hostmask cannot change their nick while in the channel, but can still talk. They can join and part at will. To issue a nickchange ban on UnrealIRCd, use the following format:

   /mode #chan +b ~n:nickname!username@hostname

In Other Channel Ban

Do you not like those in one channel also being in your channel. On UnrealIRCd, you can prevent that using a special type of ban. To use it, use the following format:

   /mode #chan +b ~c:#badchan

Users can prefix power modes before (+, %, @, &, and ~ for voice, halfop, op, admin, and owner respectively) it for it to work on those of that power or higher. If one wishes to ban those that have less than a certain mode on a certain channel, they can use the following format:

 /mode #chat +eb ~c:<prefix>#chan  ~c:#chan

Realname Ban

A realname bans on real name and underscores (_) are treated also as spaces ( ). For UnrealIRCd, the format is:

   /mode #chan +b ~r:<realname>


~x: bans can also be combined, e.g.,

   /mode # +b ~q:~c:#OtherChan

Set a Ban with ChanServ

This section is convoluted. If you can make it not so convoluted, feel free to. To all other users, it is suggest not to read this.

You may wish to set a ban using ChanServ. Depending on the SIGNKICK settings of your channel this might mask which op set the ban (explained further below.) To set the ban type: /cs ban #channel nick reason If nick is not given, it will ban you. If channel and nick are not given, it will ban you on all channels you're on, provided you have the rights to. By default, limited to AOPs or those with level 5 access and above on the channel.

SIGNKICK Enables or disables signed kicks for a channel. When SIGNKICK is set, kicks issued with the ChanServ KICK or BAN commands will have the nick that used the command in their reason. If you use LEVEL, those who have a level that is superior or equal to the SIGNKICK level on the channel won't have their kicks signed. The command to set SIGNKICK is: /msg chanserv set #channel signkick {ON | LEVEL | OFF}

Server Bans

An IRCop with enough privileges may ban users on servers. The following types of server bans are as follows. Command formats are not given for these bans, as these types of bans are server dependent, and can be found in respective documentations.

K-line

The K-line is a local server ban (specific to a single server, not the entire IRC network) that bans the offensive user's hostname.

G-line

The G-line (Global K-line) works exactly as the K-line, but is global. G-lines can expire, but in some cases they are permanent.

Z-line

On IRCds such as UnrealIRCd, the Z-line is a "powerful" ban, it is performed on IP address instead of the hostmask, making sure that users from that IP address will not join. Z-lines could expire, but in some cases it is permanent.

GZ-line

Some IRCds support the GZ-line (Global Z-line). It is exactly as the Z-line itself, but it's global, and network-wide. UnrealIRCd has GZ-line support. The GZ-line is an effective way of blocking static IP users, and keeping them out.

D-line

On other IRCds, such as Charybdis, a D-line replaces a Z-line. It is called a D-line because it "denies" the IP address from connecting. Charybdis does not have support for a Z-line or a GZ-line. By using its "cluster" configuration feature, D-lines can be synchronized between servers, providing a type of 'GZ-line'. This enables for very nice big network support since the administrator of one server may want to allow certain servers they trust to synchronize D-lines and K-lines, but not allow others.

See also

  • [1] - archieved Toxin article on bans.
  • Unban