Janus

From IRC Wiki
Revision as of 03:19, 27 June 2011 by D3M0N (talk | contribs)
Jump to navigation Jump to search
Janus

Programming language: Perl
Platform: Linux, BSD, Windows, Apple OS X, Unix
Status: Active
License: Affero GNU Public License
Latest release: 1.10
Homepage: http://sourceforge.net/projects/janus-irc

Configuration

Janus will not start without a properly configured janus.conf in its root directory (traditonally ~/janus). This file contains an example configuration. You should never leave default values. If you do, the whole world has your information!

Set Block

The set block contains unique information about your Janus service.

  • name: Your janus “name”. (Not client's nick!)
  • save: Where Janus will save multiple types of information gathered via runtime.
  • janus_nick: The nickname of your client connecting. This is what you will /msg <ClientNick> HELP to.
  • janus_host: The vHost Janus will connect with.
  • janus_ident: The user/ident Janus will connect with.
  • password: The password the admin account will have. You will identify as IDENTIFY <password>, where “password” is set here.
  • lmode: This is how Janus will treat linking. Valid parameters include link and bridge.
    • link: The traditional method of linking; links only specific channels.
    • bridge: Will link all channels between servers, making opers more global. You should use 1 set of services here!
  • pidfile: Janus will create this file with its running PID. You should set this!
  • datefmt: Defines logging style.
  • runmode: mplex(-daemon) or uproc(-daemon).
    • mplex: Multiplex support. Running './configure' will tell you if Multiplex is supported. This is recommended.
    • uproc: Used if Multiplex is not available
    • -daemon: Daemonize the process

As seen in the example below: 

set {
	name Janus
	save janus.dat
	janus_nick JanusServ
	janus_host I.Link.Your.Channels
	password AdMiNpAsSwOrD
	lmode link
        runmode mplex-daemon
	pidfile janus.pid
	datefmt %m-%d
}

Modules Block

Modules allow Janus to function. Without many of these modules, you will have a misconfigured or malfunctional Janus Client. Anything prefixed with Modules:: is optional. We've configured with some recommended ones.

“::” indicates folder in relation to the src/ folder. For example, Modules::Ban points to src/Modules/Ban.pm. “*” indicates all files in the directory ending with “.pm”. Commands::* will load all modules in src/Commands/.

Example Module block shown below with all available modules: 

modules {
	Commands::*
	Modules::Ban
	Modules::BanSet
	Modules::Claim
	Modules::KeepMode
	Modules::Qline
	Modules::Services
	Modules::Signals
	Modules::Spamfilter
	Modules::WhoisFilter
}

Ban

Allows per-network bans of specific expressions matching users. Causes an auto-kickban when the user joins a remote channel.

BanSet

Faster ban implementation for large ban lists (hundreds) by using exact matches rather than a linear search of regular expressions.

Claim

Prevents opers and other network's services from changing modes in a shared channel if that channel has been claimed by certain network(s). When this setting is used on a channel, the home network should be the only network to link the channel, otherwise there will be floods of output to logging channels and files, eventually causing time delays, desyncs, and possibly splits if not attended to rapidly.

KeepMode

Stores the modes of a channel and restores them on a relink. Useful if you use “setmode” to change mode not available on the home network's ircd.

Services

Prevents communcation to and from remote services, and prevents services kills from being translated into kicks unless they are repeated.

Signals

Rehashes the janus server on reciept of a SIGHUP.


Log Block

Janus logs all events it sees, including errors, commands, and simple connections. The log block defines where it will store and write this information. Logging is supported to a channel, and to files.

log log/janus-%m-%d.log { is an example of logging to a file. The second parameter (log/janus-%m-%d.log) indicates which folder to save the information to, in relation to the root directory. If your root directory is janus/, it will be stored in janus/log. %m is a variable for month, while %d is a variable for the day.

log Hub#Services { will log to #Services on the Hub network. The second parameter (“Hub”) is the shortname for the network's channel to log to. This is defined in a link block, later on in the configuration.

Example Log Blocks below: 

log log/%Y-%m-%d-%H:%M:%S {
	type File
	filter debug info warn err audit command debug_in info_in warn_in err_in hook_err
        rotate 86400
}

log Hub#Services {
	type Channel
	style color
	filter info warn err audit command info_in warn_in err_in hook_err 
}

Listen Block

Similar to UnrealIRCd's listen block, this defines which IP and port to bind to. Multiple listen blocks may be defined at once. If that is so, Janus will take precedent to the first IP it has bound to when linking to networks.

Example Listen Blocks below: 

listen *:8005
-Can be used if there is only one ip available on the machine

listen 0.0.0.0:8005
-Can be used if there are one or more ip's available on the machine

Link Block

You must have one link block for each network. This is how Janus links to your IRCd. Two link blocks are required for a functioning Janus. Any less and its just wasted space.

  • link <name>: This is the unique identifier for the network. It will be referred to this way when linking channels, settings, etc. It is the tag used on conflicting nicks as well. This should be very short, and may only contain characters A-Z / a-z.
  • type: The protocol of the server.
    • Unreal: UnrealIRCd 3.2.x+
    • Inspircd_1100: InspIRCd 1.1
    • Inspircd_1500: InspIRCd 1.5
    • Inspircd_1200: InspIRCd 1.2
    • Inspircd_2000: InspIRCd 2.0
  • TS6: TS6 Generic IRCd (ShadowIRCd, Charybdis, ircd-ratbox, etc.). NOTE: An extra configuration line is required for this ircd <name of ircd>
  • linkaddr: IP of the server we're connecting to.
  • linkbind: IP Address to bind to when connecting. Used for multi-homed hosts. (Optional).
  • linkport: Port to connect on.
  • linktype: Use plaintext or SSL.
    • plain: No special encryption. Plain Text.
    • ssl: Use Secure Socket Layers or GnuTLS.
  • sendpass: Password to send to the server on authentication.
  • recvpass: Password to accept from the server on authentication.
  • linkname: Pseudo-Server to create and connect with. The uplink will receive a connection from this server name.
  • netname: Network Name for the uplink. This will show up in /WHOIS for users connected on that network.
  • autoconnect: Turn autoconnect on or off
    • 1: Autoconnect on start, on rehash, and after so many seconds (defined with /msg Janus AUTOCONNECT)
    • 0: Do not autoconnect; wait for the server to try to connect to us.
  • untrusted: Hide all users real-hosts and IPs from Operators on this network.
    • 1: Hidden as 0.0.0.0. This does not conflict with anything.
    • 0: IPs and hosts will be visible.

Example Link lock below:

Unreal Link Block 

link net {
	type Unreal
	linkaddr 127.0.0.1
        linkbind 255.255.255.0
	linkport 8005
	linktype plain
	sendpass PaSs
	recvpass pAsS
	linkname net.domain.com
	netname MyNetwork
	autoconnect 1
        untrusted 0
}

InspIRCd Link Block 

link net {
	type InspIRCd_2000
	linkaddr 127.0.0.1
        linkbind 255.255.255.0
	linkport 8005
	linktype plain
	sendpass PaSs
	recvpass pAsS
	linkname net.domain.com
	netname MyNetwork
	autoconnect 1
        untrusted 0
}

TS6 Link Block 

link net {
	type TS6
        ircd charybdis
	linkaddr 127.0.0.1
        linkbind 255.255.255.0
	linkport 8005
	linktype plain
	sendpass PaSs
	recvpass pAsS
	linkname net.domain.com
	netname MyNetwork
	autoconnect 1
        untrusted 0
}

F.A.Q.

Who created Janus?

Janus was created by Daniel De Graaf (danieldg) in 2008, De Graaf is currently heading the InspIRCd 2.0 development. Daniel no longer maintains the Janus project nor does he support it.

What is Janus?

Janus' short description is the Janus Inter-Network Channel Linker. In basic terms, it provides server administrators the ability to link non-common IRCd's as if they were the same flavor of IRCd. Both networks may keep their services, and both networks can be picky about which channels they would like to share, and the channels they wish to keep local/private. As JanusIRC used to say "It is a Relay Bot on steroids."

Why use Janus?

Janus allows server administrators the chance to link their channels to another server and vis versa with out having to share ALL channels on the network. Each network still have their own irc ops, although those channels which are shared can be controlled by any irc op, unless the channel is claimed with Janus.

Do I have to install Janus too?

No! Only one person needs to host Janus. We estimate between 250-360 different networks can be hosted on Janus before someone has to edit the source code. Janus runs on it's own, and links to two or more IRC Daemons.

Is it easy to link a Janus?

Yes! You add Janus just like you would another server by linking with a link block. It can link to multiple networks and selectively share channels with various network on a per share and link basis.

Where can I download Janus?

The Latest Stable Release, 1.10, can be downloaded here.

What IRCd's can link with a Janus?

How do I use Janus once it's installed?

Click here for a guide that demonstrates how to use Janus

Retrieved from "https://www.irc.wiki/index.php?title=Janus&oldid=3306"