1. How do I setup psybnc to use multiple networks at the same time?
The first thing you need to do is add in another network:
/addnetwork [name] --- adds in a network with the name you specify. Keep in mind that network names are case-sensitive. You'll be typing the name a lot, so if you're adding in dalnet, use an abbreviation such as dal or dn or something similar.

Once you have the network added, you need to choose your vhost for that network:
/bvhost [network]'[vhost] --- sets your vhost on the network you specify.

The next step is to add servers:
/addserver [network]'[ircserver]:[port] --- adds a server and port to the new network.

All commands are prefixed with the [network]~ as follows:
/join dn~#shellfx --- joins #shellfx on network dn.
/msg dn'nickname hello --- sends the message "hello" to the user nickname on network dn.

Miscellaneous Commands
/bconnect [network]~ --- connects you to the network you specify (assuming you have servers added for that network)
/bquit [network]~ --- quits you from that network. You'll still be connected to your primary network. Note, if you do /bquit, you'll be quitted from all your networks.
/switchnet [new network] :[current network] --- This command will let you switch your primary network. By doing this, you won't have to prefix all your commands with the 'net syntax.

2. What is a Shell Account?
A shell account is basically a personal account on a server that's connected to the Internet via a dedicated, high-speed connection. Shell accounts run the Unix operating system. You access the shell via telnet and FTP. The account provides you with space (usually around 5 MB to 30 MB for basic accounts) for storing files and running programs on the Unix machine. The most popular flavours of Unix you'll encounter with shell accounts are the Linux and FreeBSD operating systems. Unfortunately, unlike Eggdrop, shell accounts generally aren't free. But since they're always connected to the Internet, shell accounts are the most popular and cost effective platform for hosting IRC bots. Shell accounts can also be used for other things, IRC-related and otherwise, such as running a bouncer, running your own IRC server, downloading files at high speed for temporary storage (until you're ready to download them to your machine), sending/receiving e-mail, and maintaining a web site. You don't have to be experienced with Unix in order to set up and maintain a bot on a shell account, but you will need to learn a few basic commands.

3. How to using psyBNC ?
Setting up your Account

The first thing you need to do is connect to your bnc. In your irc client, open up theconnect dialogue box and add in another server. Name it My BNC orsomething like that, enter the IP and port, and enter the password that youchose (either through menuconfig or in the conf file). Now make sure that yourident is set to your username. It's also a good idea to set your e-mail addressto username@whatever.com. If psy can't get an ident response fromyou, it checks your e-mail addy as verification of the username. If everythinggoes well, you'll see this when you connect:

-Welcome- psyBNC2.3.1'

Now you need to get connected to irc: first, you need to select your vhost. To see what vhosts are available, at your shell prompt type:

vhosts

As there is no way to view the vhosts in psy, you can only use this command from your shell. This command is only available if your shell provider has created such a function, but in my experience 99% have. After your vhost is selected, you'll need to add in some irc servers, and set a few other options. the commands follow below. All commands appear like this /mycommand, everything else after it is an explanation. All brackets are for my purposes, don't use brackets in any command!

/bvhost [vhost] -- (this command used to be /vhost) -- [vhost] is your vhostin alpha form (ie, this.is.a.cool.vhost.com and not 127.0.0.1)

/addserver [server] :[port] -- server can be inalpha or numeric form...

Once you add in the server, psy will auto-connect to it in a short while. Youcan add in more servers so that if one goes down, psy can reconnect to a differentone. Just use the command above again. For server managment:

/listservers -- lists all the servers you have added

/delserver [n] -- deletes the server with #[n] (as shown by the listservers command)

/jump -- disconnects you from your current server and attempts to connect to the next server in your list

/bquit -- disconnects you from the server until you force it to connect

/bconnect -- connects you to irc

Now, remember that psy will keep you connected to irc even when you're notconnected to the bnc. So, these commands are helpful:

/setaway [message] -- psy will display this message to all channels you're on when you quit the bnc. It will NOT repeat this message (since that's gay). To remove the message, just type /setaway

/setawaynick [nick] -- when you quit the bnc, psy will auto-change your nick to the nick you set here. When you reconnect, it'll auto change it back to what's shown in the mirc nick.

OK, now for some more commands that ppl find useful. Remember that ALL commands are in the README file that came with psybnc. I'm not going to repeat all of them.

/playprivatelog -- plays the log of all messages sent to you when you were disconnected from the bnc. The log will be opened in a window called -psyBNC.

/eraseprivatelog -- erases the aforementioned log.

psy has a damn cool feature in that it allows encryption. You can encrypt textsent to a channel or a person. Each person needs to have the same key to viewthe text. This is helpful if you're paranoid, or if you want to have a privateconversation in a public channel. (Why you wouldn't just pm is beyond me ;)It also makes you look l33t lol.

/encrypt [password] :[channel/person] -- make sure everyone you want to speak with has the same key. And they need to be using psybnc as well. duh.

/listencrypt -- lists your current encryptions

/delencrypt [n] -- deletes encryption #[n] as shown by the listencryption command.
[edit]
User Management

Obviously, if you have your bnc compiled as singleuser, this section is pointlessfor you. But for everyone else, I'm sure you want to add in other users, deletethem, etc... Here's the commands to do it:

/adduser [user] :[real name]' --- the [user] is what the person will have to set their ident to. The [real name] part is what ppl will see when doing a /whois. for example: /adduser mynick :me love you long time

will show this in the first line of a whois:

mynick is ident@vhost * me love you long time.

/deluser [user] -- deletes the user.

/password [new pass] -- changes your password. If you're an admin,you can change other ppl's passwords: /password [user] :[pass]

/madmin [user] -- makes a user into an admin (choose your admins carefully!)

/unadmin [user] -- removes admin rights from a user. /bwho --- see who is added to your bouncer. Also shows if they're connected, what server they're connected to, and what their IP is.

I recommend you secure your bnc even more by restricting what IPs can connect to it:

/addallow [IP or mask] --- lets whatever IP or mask you specify connect to the bnc. IPs can be definite, ie. 12.12.12.34 or masked, 12.12.12.*. You can also use hostnames and masks such as *.myisp.com.

/listallow --- lists the allowed connections. /delallow [n] --- deletes allow #n as shown by listallow.
[edit]
DCC Stuff

This section assumes that you compiled your bnc with DCCFILE and DCCCHAT. Ifyou did not, then you can do all your dcc stuff as you normally wouldin your irc client, but remember that your real IP will be revealed by doing this.Like I stated before, the benefit of psyBNC is that it hides your IP during DCCsessions, but in order to do this, your life gets a bit harder. First, let'sgo over the basic DCC commands:

/dccchat [user] --- opens a dcc chat session with the user you specify. /dccsend [file] :[user] --- sends a file to the person you specify. The file MUST be in ~/psybnc/downloads/USERx (where USERx is your user #. Not sure what your user # is? do a /bwho

/dccanswer [user] --- if someone sends you a dcc chat request, psy will inform you through a notice. You must then type this to accept the request. /dccget [file] :[user] --- gets a file that was dcc'd to you by someone. This file will be stored in the ~/psybnc/downloads/USERx directory.

/dccsendme [file] --- tells psy to send you the file you specify. Use this after you get a file from another user and then want to get it from your shell. This is the only way people without shell access can get their files.

/listdcc --- lists all dcc's

/dcccancel [n] --- cancels dcc # n as shown by /listdcc

If you wish to use SSL encrypted DCC sessions, precede the value of the commandwith "S=" ie: /dccchat S=l33th4x0r - Note that the other person musthave an SSL capable client.

Now for the cool stuff, my favorite feature of psy is its ability to stay permanently connected to a bot through a DCC, and to ask this bot for ops. As anyone who has experience with running a botnet knows, one of the easiest ways for a channel to be taken over is to have some idiot /msg [bot] OP [password], when the bot's nick was taken by someone else. With psy, however, the askop request can be done two ways: through the partyline when a DCC is initiated, or through a msg that first checks the mask of the person being sent the request. Sweet, eh? So, the commands to do it:

/adddcc [botname] [username] [password] :[host]:[port] --- The botname is obviously the name of the bot, The username and password are your personal l/p that you use to gain access to the bot's partyline. The host is the host of the bot. It can be either the alpha-form, or the actual IP address. I prefer the actual IP address, since it's possible DNS can be down. And finally, the port is the port that the bot listens on for user connections. Some bots listen for other bots on one port and for users on another, so make sure you get the right one :)

/listdcc --- lists all dcc's /deldcc [n] --- deletes dcc # n as shown by /listdcc

Now, for the askops part: This part assumes you added in a DCC to the bot as shown above. If you don't have partyline access, you can still add an askop, but I'll get to that later.

/addask [#chan] [password] :-[botname] --- The chan is the channel you want to get ops on, the password is your password, and the bot's nick, preceded with a :-, is the bot which you have a dcc enabled to.

/listask --- lists all the askops you have

/delask [n] --- deletes askop # n as shown by /listask

Now, if you don't have partyline access, you can add the askop in this way:

/addask [#chan] [password] :[bothost] --- where chan is the channel you want to be opped on, your password is your password (duh), and the bothost is the bot's hostmask. A hostmask, for the uninformed, is formed like this: username!ident@host. Since a bot is set to use a different nick if someone takes their default, set the host for something like: *!mybot@damn.cool.vhost.com.
[edit]
Multiple Networks

One of my other favorite things about psyBNC :) Do you have a bunch of channelsyou hang in on efnet, but also one or two channels on dalnet that you like togo to? If you're like me, you do...but you alo hate having multiple mirc sessionsopen. Fret no more! psyBNC can solve your problems by allowing you to connectto more than one network with the same mirc client. For this section I'll assumethat you're familiar with most of the commands in psy. If not, get familiarwith them before you try to do this. Ok, let's get into the commands.

The first thing you need to do is add in another network:

/addnetwork [name] --- adds in a network with the name you specify. Keep in mind that network names are case-sensitive. Furthermore, you'll be typing the name a lot, so if you're adding in dalnet, use the name dal or dn or something similar.

Once you have the network added, you need to choose your vhost for that network. If you don't choose one, it'll default to the IP the bnc is on, usually somethinggay like "my-shell-company.com". So:

/bvhost [network]~[vhost] --- sets your vhost on the network you specify.

See this command? This is the format for all commands used on multiplenetworks. Simply prefix the syntax of the command with [network]. So, to givesome other examples:

/addserver dn~irc.dal.net:6667 --- adds in the server irc.dal.net with port6667 to the dn network.

/join dn~#fxp --- joins #fxp on network dn. (btw, I hear that some freaky pplhang in this particular channel ;)

/msg dn~joeschmoe beeyatch sends the message "beeyatch" to the userwith the nick joeschmoe on network dn.

Now, some weird things about multiple networks:

· Your nick in the nicklists for channels on other networks will show the nickyou're using on your primary network. So, even if you do: /nick dn~TwatMuffin,even though other ppl will now see you as TwatMuffin in their list, you'll seeyourself as mynick, or whatever nick you use.

· If you get opped/voiced in a channel, you won't see it in the nicklist. You'lljust appear to be a regular schmoe.

· Let's say JoeSmith is in #chat on efnet, your primary network. You head overto dalnet, and he's there in #fxp. Everyone else in #fxp will look like dn~BobJones,but JoeSmith will be just JoeSmith. If you try to msg him by dbl-clicking onhis nick int he dalnet channel, you'll really be sending a msg to him on efnet.You have to use dn~JoeSmith to talk with him on dalnet.

Some final things. Maybe you don't always want to be on more than one network.I prefer to always be on efnet, and then head to my other networks when I wantto talk with ppl there.

/bconnect [network]~ --- connects you to the network you specify (assuming you have servers added for that network)

/bquit [network]~ --- quits you from that network. You'll still be connected to your primary network. Note, if you do /bquit, you'll be quitted from all your networks.

/switchnet [new network] :[current network] --- This command will let you switch your primary network. By doing this, you won't have to prefix all your commands with the ~net syntax.

For example, let's say that you are on EFNet and DalNet. Efnet is your primary network (you dont need to prefix anything with the ~ format) and DalNet is added as ~dn. If you currently did /msg mynick, you would be messaging mynick on efnet.

If you do /switchnet dn :ef your current network will be assigned to dn - DalNet. Now if you /msg mynick you will get mynick on DalNet. To msg him on EFNet, you would have to do /msg ef~mynick - since ef was the prefix you assigned in the switchnet command. To switch back to your original config, you'd do: /switchnet ef :dn

OK, multiple networks also includes the psy internal network. Think of it as an ircd inside your bnc. By using the network name intyou can create private channels that only people connected to your bnc can access. For example, /join int~#partyline will have you join the internal channel #partyline. You can set modes/ops/topic in the internal channels just like you would on a normal channel. Do a whois on someone in an internal channel, it looks neat ;)

You can also privately msg other people connected to your bnc: /msg $[nick].

Prefix it with a $ andpsy will send it directly to the person on the bnc; it will not pass throughthe irc server. (So if you both are on SSL-enabled clients/bncs - the message is perfectly secure in transit!)
[edit]
Linking

A cool aspect of psy is the ability form a psy-net through the linkage of multiplepsybncs. The benefit of this is to create a private internal network securefrom snooping, and secure from takeovers! Furthermore, you can let ppl on otherbouncers use your machine's vhosts if you wish. As you should have realizedby now, preceding an IP with S= creates an SSL port.

So, to create a link to another bouncer:/linkto [name of other bnc] :[IP]:[port]

The other bouncer would have to do the following:/linkfrom [name of other bnc] :[IP]:[port]

To view all your links:/listlinks

I love to have everything encrypted, including my links. To create an encrypted link:/setlinkkey [link #] :[password] After doing this on both psy's, do:/relink [link #] on either bouncer to reset

To enable the sharing of vhosts:/relaylink [name of other bnc] :n --- where n=0to disable vhost sharing; 1 to enable it.

Final note: If you use hostmasks to restrict connections to your bnc, you mustadd the other bnc's IP as an allowed host!!
[edit]
Appendix

For one reason or another, you might want to edit your psybnc.conf (especiallyif menuconfig doesn't work for you). So, here are the applicable lines and whatthey mean. I'm sure I've missed a few lines, so if you find anything and know what it does, please email me at mynick(at)mynick(dot)net. Notethat all the variables in psybnc.conf are CAPITALIZED and that there are nospaces on either side of the equal sign.

Variables are shown in this style.

###SYSTEM SETTINGS###

PSYBNC.SYSTEM.PORT1= The port your bnc is going to listen on. use a PORTx variable if you want multiple ports. PSYBNC.SYSTEM.ME= The name of your bouncer.

PSYBNC.SYSTEM.HOST1= The IP your bnc is going to listen on. Use HOSTx for multiple hosts. If you want an SSL port, Put an 'S=' before the IP.

PSYBNC.SYSTEM.DCCHOST= The IP that will be used for DCC sessions. PSYBNC.HOSTALLOWS.ENTRY0= The first IP that will be allowed to connect to your bouncer. Use *;* for everyone. This can include masks. The first * indicates the IP, not sure what the * after the ; denotes... can't find anything anywhere about it.

###USER SETTINGS###

(note that USERx can be substituted for USER1 where x is an integer)

USER1.USER.LOGIN= The login name for the user (ident)

USER1.USER.NICK= The nick the user will use on irc.

USER1.USER.USER= The 'real name' of the user (what appears in the whois) USER1.USER.PASS= The password of the user (this will be shown in encrypted form; if you change the password in psybnc, then restart it, the password will become encrypted.) USER1.USER.RIGHTS= 0-not an admin; 1-an admin

USER1.USER.ACOLLIDE= 0-disable anti-collide; 1-enable anti-collide

USER1.USER.SYSMSG= 0-Do not show system messages to the user; 1-Show them USER1.USER.VHOST= The user's vhost USER1.USER.AWAYNICK= The user's away nick

USER1.USER.AWAY= The user's away msg

USER3.USER.LEAVEMSG= The message shown when you disconnect from the bnc USER1.USER.VLINK= (0/1) Not sure what this does (default =0) USER1.USER.PPORT= (0/1) Not sure what this does (default =0)

USER1.USER.PARENT= (0/1) Not sure what this does (default =0)

USER1.USER.QUITTED= 0-User is connected to irc; 1-User is quitted USER1.USER.DCCENABLED= 0-dcc is diabled; 1-dcc is enabled. USER1.USER.AIDLE= 0-anti-idle is disabled; 1-it's enabled.

USER1.USER.LEAVEQUIT= 0-when the user disconnects from the bnc, they stay on all their channels; 1-when they quit, they leave all the channels, but still stay connected to irc.

USER1.USER.AUTOREJOIN= 0-if you get kicked when not on the bnc, psy will not rejoin the channel; 1-psy sill rejoin the channel for you if you get kicked. USER1.USER.LASTLOG= (0/1) Not sure what this does (default =0) USER1.SERVERS.SERVER1= The first server of the user.

USER1.SERVERS.PORT1= The port for server number 1.

USER1.CHANNELS.ENTRY0= The first channel the user wants to sit on. USER1.CHANNELS.KEY0= The key for the first channel. (This is encrypted as of version 2.3.0) USER1.INTCHANS.ENTRY0= An internal channel the user wants to sit on.

USER1.AOP.ENTRY1= Entry for someone to get ops from your client in the form of hostmask;password. (not covered in this tutorial)

###LINKAGE STUFF###

LINKS.LINK1.PORT= Port for link 1 LINKS.LINK1.NAME= name of the otehr bnc

LINKS.LINK1.IAM= name of the other bnc (redundant?)

LINKS.LINK1.HOST= IP of the link

LINKS.LINK1.PASS= Password for the link (used only by the bncs)

LINKS.LINK1.ALLOWRELAY= 0-Do not share vhosts; 1-Allow the sharing of vhosts LINKS.LINK1.CRKEY= Key set by negotiation between the bncs

LINKS.LINK1.TYPE= 0-Your bouncer links to theirs; 1-Their bouncer links to yours.

###DCC AND ASKOP STUFF###

(note: I don't recommend editing any of these variables through psybnc.onf -> use the commands in mirc.

USER1.DCC.ENTRY0= Stuff pertaining to DCC #0

USER1.ASK.ENTRY0= Stuff pertaining to AskOp #0
[edit]
Setting Crontab

The basic form for a crontab entry is (to the best of my knowledge):

So, if you like to check every 10min, it would be:

0,10,20,30,40,50 * * * * /path/to/my/process

Included with psybnc is psybncchk. Open this file and change the line that reads PSYBNCPATH=/set/path/here. Set it to your psybnc directory of course. Make sure this file has execute perms; in your shell, type:

chmod 700 psybncchk

Then add the following to your crontab (use crontab -e to edit your crontab): (this example is for a check every 10 minutes:

0,10,20,30,40,50 * * * * /home/shell/psybnc/psybncchk >/dev/null 2>&1

The >/dev/null 2>&1 part tells crontab not to send you an e-mail whenever itrestarts psybnc. Omit that part if you like e-mail.
[edit]
SSL Enabled Clients

If you have compiled psyBNC with SSL and created an SSL listening port, youmust use an SSL capable client to connect. It is possible to use anyclient with SSL if you create a tcp wrapper (using something such as stunnel),but I will not get into that. So if you're using mIRC or another non-SSL client, search googlefor tutorials on how to create an SSL wrapper.

At the moment, I am only aware of 1 client with built in SSL support (tho Imay be prejudiced since it is the only client i use other than BX): XChat.I highly recommend this client - both for real operating systems like linuxor BSD, and even for windows. One thing to note: when connecting to your bncw/ SSL, tell XChat to accept invalid certs! Going by SSL-standards, an applicationthat encounters a self-signed certificate (which I guarantee you have) shouldeither prompt the user for confirmation or kill the connection. XChat choosesthe latter (something i disagree with) but by telling it to accept invalid certs,it will work fine.
Retrieved from "http://www.psybnc.co.uk/index.php/Tutorial"

3. Reasons to use psyBNC
a) To stay connected to IRC 24/7. Even when you close mirc the psyBNC will maintain your connection, so when you connect later, you'll instantly be back on the channels you left.

b) Hold your nick or op's in a channel.

c) Hide your IP address, even in DCC connections. In other bncs, a direct client-client session is opened, revealing your IP. With psyBNC the connection is bounced through the shell with your IP remains secure.

d) You can connect to mulitple networks and link psyBNCs together.

4. What is a dedicated server?
A dedicated server refers to the rental and exclusive use of a computer and the connection to the Internet, housed in the hosting company's premises. A dedicated server is usually needed for Websites (or a set of related sites) that may develop a considerable amount of traffic. The server can be configured and operated remotely by you the client. The use of a dedicated server saves the client router, Internet connection, security system and network administration costs.

5. How do I access my shell account?
You access your shell account via ssh. SSH is a program similar to telnet, which will give you access to the shell on the remote machine. It is better than telnet because it uses encryption, meaning your password and text are not transmitted in clear text. If you do not have ssh, feel free to download ssh from http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe

6. Can I use my own domain for personal/custom vhost?
Yes you can use your own domain as vhost. Just change the dns/nameservers of the domain to dns1.shellsnet.us and dns2.shellsnet.us or u can point your vhost to our empty ip and mail us about it at support@shellsnet.info

7. Installing Unreal IRCD
Hopefully you have already downloaded the source. If not, you can find it here: http://www.unrealircd.com. After you have downloaded that, fire up your favorite ftp client and upload it to the root directory of your shell. You could also get the source by using lynx or wget. Example wget command:

wget http://unrealircd.pimpmylinux.org//Unreal3.2.7.tar.gz

The next step is to decompress this file (.tar.gz is kinda like a .zip file for all you windoze ppl out there). To do this, type:

tar zxvf Unreal3.2.7.tar.gz

Notice that it's case-sensitive. Everything in unix is case-sensitive. Keep that in mind for everything in the future. You can now remove the file you downloaded with the following command:

rm Unreal3.2.3.tar.gz
Now that we've untarred our UnrealIRCd file, we need to move to that directory:

mv Unreal3.2 ircd

then..

cd ircd

And now that we're in the ircd directory, we need to run the configuration wizard:

./Config

So we've got the script running. The first thing you're greeted with is the release notes for Unreal 3.2.3, now this is a lot of reading, and isn't really necessary, so just press enter once, then spacebar until you see:
==[ ADDITIONAL INFO ]==
* See ChangeLog
[Enter to continue]

Press enter and you'll be greeted with the first question.

Do you want to enable the server anti-spoof protection?
[No] ->

I've never actually come across a server that uses this, so just press enter to move on to the second question.

What directory are all the server configuration files in?
[/usr/local/username/Unreal3.2/] ->

Well we haven't changed the directory, so just press enter to move on to the third question.

What is the path to the ircd binary including the name of the binary?
[/usr/local/username/Unreal3.2/src/ircd] ->

Again, we haven't changed this path, so just press enter to move on to the fourth question.

Would you like to compile as a hub or as a leaf?
Type Hub to select hub and Leaf to select leaf.
[Hub] ->

If you're not going to link your server to any other IRC servers, just press enter. However, if you are going to link your server to another IRC server, and this server is going to be a leaf on that network, type 'Leaf' and press enter. If you are linking your server to another IRC server and your server will be the Hub, just press enter.

What is the hostname of the server running your IRCd?
[shellsnet.info] ->

This question has already been answered for you by the configuration script, so just press enter to move on to the next question.

What should the default permissions for your configuration files be? (Set this to 0 to disable)
It is strongly recommended that you use 0600 to prevent unwanted reading of the file
[0600] - >

The default value for this question is the one you should use, so just press enter.

Do you want to support SSL (Secure Socket Layer) connections?
[No] ->

Not many servers use this method of connection, and I doubt you will need to, and if you did, you'd know if you did, so just press enter to move on.

Do you want to enable IPv6 support?
[No] ->

You definitely don't need this feature, so just press enter to move on to the next question.

Do you want to enable ziplinks support?
[No] ->

You don't really need this feature either, and if you did, you'd know you did (sound familiar?) so press enter.

Do you want to enable remote includes?
[No] ->

You don't really need this, so just press enter to move on to the next question. Getting monotnous now isn't it? Hang in there.

Do you want to enable prefixes for chanadmin and chanowner?
This will give +a the & prefix and ~ for +q (just like +o is @)
Supported by the major clients (mIRC, xchat, epic, eggdrop, Klient, PJIRC, etc.) with the notable exceptions of irssi, KVIrc and CGI:IRC.
This feature should be enabled/disabled network-wide.
[No] ->

Well now, this is a nice feature. It pretty much explains itself though... If you have registered the channel, you will be ~yournick instead of @yournick in the channel, and anyone who you have added to the SOP list, or who is +a in the channel, will be &theirnick instead of @theirnick. Either type 'Yes' if you want to enable this feature, or just press enter if you don't want it.

What listen() backlog value do you wish to use? Some older servers
have problems with more than 5, others work fine with many more.
[5] ->

This value doesn't need to be edited, so press enter to move on to the next question.

How far back do you want to keep the nickname history?
[2000] ->

This value doesn't need to be edited either, so press enter to move on.

What is the maximum sendq length you wish to have?
[3000000] ->

You guessed it, you don't need to edit this either. Press enter to move on to the next question.

How many buffer pools would you like?
This number will be multiplied by MAXSENDQLENGTH.
[18] ->

And yet again ... just press enter to move on.

How many file descriptors (or sockets) can the IRCd use?
[1024] ->

You do need to change this value (wahey!), to however many users are allowed to connect to your IRCd.

Would you like any more parameters to configure?
Write them here:
[] ->

No, we don't want to configure anything else, so just press enter and sit back while it compiles itself. You might be thinking that there were a lot of questions that you didn't need to answer, but some networks do, so don't worry any more about that.

After that has finished compiling (it should take about a minute) you'll see the following message amongst some fancy borders and other information:

Now all you have to do is type 'make' and let it compile. When that's done, you will receive other instructions on what to do next.

Hey, this script is taking over my job, telling you what to do! Okay then, just type 'make' and ... let it compile, this should take a little longer than it did last time. When it's finished, you'll see a message beginning with:

Compile is now complete. You should now read the documentation and learn how to configure your IRCd as it is out of scope as you have to configure it as per your requirements, all networks have different requirements.

After you have edited unrealircd.conf, you can start Unreal from your shell. In the ircd directory, type the following command:

./unreal start

If you receive no errors, you should now be able to connect to your IRCd!

8. I am incapable of setting up my bnc/shell account. What should I do?
Please join us on IRC (Internet Relay Chat), #Shellnet on DaLnet or Aseanchat. You may ask anyone in the channel for assistance, or you may contact an administrative representative. Our technical support is 100% free, so please use it to your advantage. We will hopefully be able to rectify the problem you may have.

9. Can I run bots, irc, bnc on my web hosting package?
We offer basically two type of hosting packages, web hosting and shell hosting.

If you opt for web hosting, you cannot run bots, bnc etc...

But if you sign up for shell/ircd/irc hosting packages, you are allowed to run it.

10. What is Web Hosting?
In order to have a web site on the internet you first need to have a web server. Unfortunately, running your own web server can be expensive and require a lot of know-how to keep it up and running around the clock. Most home networks don't have the speed or bandwidth to host a professional website.

Web hosting companies are basically real estate agents for the world wide web. They provide space on their web servers for you to put your website files and are connected to fast networks. Many companies also provide tools to help you enhance your website.

11. How do I change my shell account password?
After you login to our server into your account you must type "passwd". Our system will then ask you for your old password and your new password twice.

12. How do I kill a background process?
In your shell type "ps x" which will display a list of running processes and their respective PID numbers. To kill a process find its pid number and type "kill -9 pid#".

13. How many connections to IRC am I allowed to have from my PsyBNC?
There should be no more than 2 connections to IRC from any single BNC process running on our servers. Launching more than 2 connections to IRC from your BNC would be considering cloning and against IRC policies in several IRC Network and also break our policies.

14. How to check my e-mails using the Webmail?
Inside your Control Panel, E-mail Manager section, select the Webmail icon and login using your e-mail address and password.

Or you can use via http://www.yourdomain.com/webmail
Please use your email address as username (eg. myname@mydomain.com)

15. Command Available
Available Commands

getpsy ( Psybnc 1 admin + 1 user )
getpsy2 ( Psybnc 1 admin + 1 user )
getpsy3 ( Psybnc 1 admin + 2 user )
getpsy4 ( Psybnc 1 admin + 3 user )

getbnc ( Bnc auto installation )
getegg ( Eggdrop auto installation )