beware ircd is downloaded as zip file. to install, create a new folder, and unzip the files into it. The program is now installed, and in fact, you could now already run the server, using the default settings.
you can manage the server from a dos shell without access to the desktop, but if you do use the desktop, you can double click the batch files.
The program does not run visible; there are is no window, tray-icon, etc. it just runs.The files are:
|rehash.bat||re-load configuration files|
|example.conf||how to make or edit ircd.conf|
|ircd.motd||empty MOTD file|
for configuration, there are 2 files: ircd.conf and bircd.ini. they can be read and edited with a text editor such as notepad.
ircd.conf uses a standard (ircu) ircd.conf compatible format with "conf lines". read the default shipped ircd.conf for basic information or example.conf for detailed information. it should be easy to find help about ircd.conf on internet.
bircd.ini contains all "settings" which alter the behavior of bircd. all settings are in setting=value format, and have a comment which explains what the setting does.
almost all changes to the config files can be applied to a running server using "rehash" - thus without bringing the server down.
This is recommended if you want to run the server permanently, and you have windows NT (NT4, 2000, XP, or later)
Install: type "bircd install" on a dos prompt when you're in the beware ircd directory.
This will do 2 things: add an entry to the services database, and set an option in bircd.ini so it will run as service.
After you've done this, start the service using "net start bewareircd", and do not start bircd.exe normally - it won't work.
To uninstall, type "bircd uninstall". this will remove bewareircd from the services list, and unset the option in bircd.ini so it runs normally.
note: if you want to use a custom service name (for example as to run another server as service) change "ntservicename=" in bird.ini BEFORE you install the service.
"bircd install auto" will install the service in a way that it starts automatically when windows starts.
For users, there is user mode +x to get a hidden host as defined in the vhost* settings in bircd.ini; a "accountname.users.network.org" as on undernet, a crypted IP, or everyone the same host (as defined in the ini). other modes may be added later.
For privileged users/network staff, there is "sethost" (/sethost command, S:lines in ircd.conf, sethost* settings in bircd.ini) to get an arbitrary/custom host.
important: if using host hiding, the following settings in bircd.ini to "1": secretnotices, secrettrace, secretstats. because they would allow users to see real hosts.
for your own mask, /whois yourself.
save changes, use rehash.bat to apply changes. in your client, type /oper name password
Note, if you use the userid@ part, you must have ident.
note that you can use a hostname instead of an IP, but only if the IP's reverse dns is that hostname. this is a limitation fo beware ircd. "free dns forward" names will not work.
then as ircop do command: /connect (name of other server)
for an automatic connection, you need to fill in the port field (default 4400). in the Y:line of the class (the last number in the C:line), set the "connection" frequency. Y:class:pingfreq:connectfreq:maxlinks:sendq for example Y:20:30:300:1:1000000
free dynamic DNS forward problem:
it can be your IP changes all the time (dynamic IP) and you use a dns name which resolves to that IP. problem is bircd can't *reverse* the IP to the hostname, so even though bircd can connect to the dns name, the accepting end can't verify that the incoming IP is actually the dns name mentioned in the C:line. workaround:
make a C:line with the dns name. make a N:line with the same fields, but with the IP mask which always matches the IP. example:
C:otherserver.dyndns.org:password:otherserver.yournet.org:4400:20 N:11.22.33.*:password:otherserver.yournet.org::20the "name" field must be the name the other server has in the M:line rather than the DNS hostname.
if you get errors like these: "Server numeric collision (ABAH])" that means theres more than 1 server using the same server numeric. change the numeric, the last parameter in the M:line in ircd.conf, so all servers have a *different* value.
services link as server. it is in fact a "pseudo server", which appears on a net like for example "channels.network.name". it brings "pseudo clients", which appear as users with nicks like ChanServ, etc. minimum configuration which needs to be done in services is this:
example ircd.conf lines for services:
C:127.0.0.1:password:services.server.name::20 N:127.0.0.1:password:services.server.name::20 H:*::services.server.name
note: if the services runs on the same machine as the ircd to which it connects, you can use IP address 127.0.0.1.
M:server.name:18.104.22.168:server fullname field::12 P::22.214.171.124:S:4400 P::126.96.36.199:C:6667