If you own an IRC server, and would like to enable people to access it from Mibbit without issues, it's simple to get set up.

First of all, anyone who uses Mibbit connects from one of our four IP address to your IRC server. This needs to be handled by the IRC server. The default setup for most IRC servers is to only allow 3 or so connections from any single IP, which means that only 3 .. 12 Mibbitians would be able to connect to the server. There are two solutions to this: WebIRC (best) or a trust/session increase.

Contents

Mibbit IP addresses

IP

rDNS

207.192.75.252

ircip1.mibbit.com

64.62.228.82

ircip2.mibbit.com

78.129.202.38

ircip3.mibbit.com

109.169.29.95

ircip4.mibbit.com

Advanced: If you would like to automatically generate your own IRCd configurations using a script of some form either for remote include or other method depending on your IRCd you will be able to find all current Mibbit WEBIRC IPs in the ircip.mibbit.com round robin host name. If you don't know what this means, don't ask, just skip it.

WebIRC/CGI:IRC Blocks

The webirc protocol allows Mibbit to send over the users real IP address and hostname to the IRC server. This means that cloaks, and bans, and all other hostname/IP based things work exactly as they should. When you whois the user, it'll look like they are connecting directly from their own IP, and not through Mibbit.
This is also known as a cgiirc{} block on some servers.
This is the best method of having Mibbit connect to your network seamlessly.

If you wish to set up a Web:IRC configuration for Mibbit, please follow the following steps.

Choose a WebIRC password.

This password should be between 6-20 alphanumeric characters. Please don't use special characters.

Configure your servers. How to do so is listed below for each server type.

IP addresses are in the section above for reference and in each IRCd specific section below.

Please have your settings saved and rehashed

Gather the following information so that you may supply it in the following step.

Network name

Will be shown in the server tab, so keep it short but meaningful. For irc.example.net could be "Example Net"

A list of all DNS entries that point to your network.

e.g., irc.blah.net, blah.com, oldname.com etc.

In the case that not all servers in your network are set up with WebIRC, a list of the servers with WebIRC enabled.

Preferred connect server or round robin and the port number (if not 6667)

e.g., irc.blah.net:1234 (will be used by the main client)

If you have SSL, we prefer that port (and please tell us that it's SSL).

Inspircd

1.) Locate the cgiirc module in the modules.conf (or inspircd.conf) called m_cgiirc.soLook for

<module name="m_cgiirc.so">

and uncomment it.

2.) Locate the cgihost tag below and configure as follows:

Choose type as Webirc

In the password attribute, replace <password> with the password you chose.

In the mask attribute, enter our IP addresses (64.62.228.82, 207.192.75.252, 78.129.202.38, 109.169.29.95)Note: In some cases its been reported that connection from mibbit users were not resolved to the correct address. In some cases this can be fixed by setting the mask to "*". Try it only as last resort.

Warning: if all mibbitians get the same Mibbit@*.mibbit.com (or the obfuscated version) as ident@host after the changes, you need to reload the cgiirc module (after every change, even if they claim the bug was fixed).

The major difference from your normal <connect> block should be the allow parameter and the globalmax and localmax. The reason for these changes is so that the server does not identify several users of mibbit as coming from the same IP and then raises a session exceeded error.

If you are having problems getting the module to work, try rehashing and reloading the module after configuration changes. The easiest way to do this is by rehashing, then issuing the command "/reloadmodule m_cgiirc.so". Sometimes only a server restart helps.

Nefarious

If F:CRYPT_OPER_PASSWORD is set to TRUE (default) you will need to use "/mkpasswd <password>" to crypt the password before adding it to the W:Line. If F:CRYPT_OPER_PASSWORD is set to FALSE then you will have to put the password in the W:Line in plain text.

To check the version and revision use "/version" or "/quote version" depending on your IRC client and then look for:

Always check your config with the following command (path to your charybdis installation)/bin/ircd -conftest to make sure it loads the module correctly and your config is intact. Anyways, if that succeeds it shows: notice: loading module extensions/m_webirc.so ...

Hybrid

While attempting to support webirc for ircd-hybrid I discovered that the module linked by this page no longer compiled properly for the current stable release (as of this writing 7.2.3). After a bit of time with Google I discovered this article.

As of posting, there is concern that host cloaking can override this module and render the host back to the original Mibbit IP. This can be seen as the user is presented with a clear message that webirc conversion was successful, yet /whois shows the host reverted. Disabling host cloaking does prove that the webirc process is working. This is not a recommendation to disable host cloaking. This was seen on hybrid-7.2.3+plexus-3.0.0(20070716_2-509

Other

The protocol is pretty simple. The first command sent to the server is:

WEBIRC <password> cgiirc <hostname> <ip>

(NO <> brackets around password!)

The server then uses the hostname and ip for that connection.

Trust/session limit increase

If webirc is unavailable, mibbit sends over the users IP address and hostname.
In the ident reply, we send the users IP address in hex form.
We also set the users realname to be their hostname.
If you use this method, you can ban individuals on their username.
You just need to increase the connection limit for the Mibbit IP, and please remember NOT to k-line/ban the whole of *.mibbit.com . Ban individuals instead.