Download
|
|
|
|
Step 1: Download
|
|
|
Step 2: Compilation (Unix Version)
|
|
To compile you must extract that compressed tar to some directory such as a subdirectory of a normal users. NOTE BNC IS NOT DESIGNED TO BE RAN AS ROOT OR SUID. DOING SO CAN POTENTIALLY COMPROMISE THE SECURETY OF THE MACHINE.
With that in mind, log into the shell as a normal user. After uncompressing the archive (considering your reading this, i hope you already figured this out) into your shell, Change to that directory.
Compiling BNC requires that you run the GNU autoconf created script ./configure which will calculate system-dependent values and option needed by BNC to properly operate on a wider range of OS's. After configure is done doing its job, BNC is made by running 'make' which is included with most GNU C compilers. After make completes, unless an unexpected error has occured, the executable binary 'bnc' should be located in that directory.
|
|
Step 3: Installation (Unix Version)
|
|
The best method for installation is to move the executable to a different subdirectory of your home directory on the shell along with the script bncchk and the configuration file (normally bnc.conf) that you make yourself using the provided example file 'example.conf'. An example is as follows (sizes and directory names depends on you):
bnc@XNation:/home/bnc/phbnc$ ls -lF
-rwx------ 1 bnc users 544 Aug 7 11:13 bncchk*
-rwx------ 1 bnc users 6794 Aug 7 09:57 bncsetup*
-rw------- 1 bnc saints 747 Apr 14 20:08 bnc.conf
-rw------- 1 bnc saints 4 Apr 13 19:14 pid.bnc
|
|
Step 4: Configuration (Unix Version)
|
|
Most of the configuration is contained within a configuration file bnc.conf which it looks for in its current directory. BNC will not run if this file is not present, or if the file fails to satisfy the required information to properly load. An option configuration file can be specified on the command line of BNC.
The configuration file is line based, each line is a seperate option. What option is set is determined by the Directive in this format:
Directive_Name:Argument:Argument....
Required directives are D (Daemon Configuration) and S (Supervisor Password).
Format is as follows:
D:Listening port number:Maxusers limit number:Password
Listening port: Port number on the host to attach to.
Maxusers limit number: Number of users that can be connected to BNC at the same time, 0 means unlimited.
Password: An optional password required for an user to be able to use the proxy daemon.
S:Password
Password: A required Password for a normal user to become an admin through use to the pre-connect command /quote MAIN (pass). It is best to make the Supervisor pass and the listening pass be two seperate passes.
All the other directives can be best represented within the example.conf file included with current versions of BNC, and are beyond the scope of this document. Please take time to read the config file and all included documentation before requesting new features.
Also note that after you compile bnc you can use ./bncsetup to create .conf files for you.
|
|
Step 5: Cron Tab (Unix Version)
|
BNC includes a script called bncchk that uses the pid file created by the BNC executable to determine if it is executing. The bncchk file needs to be edited and the proper lines modified:
BNCBIN=bnc
BNCPIDFILE=pid.bnc
BNCPATH=/home/bnc/bnc2.6.4
The name of the varible basically tells it all.
Inside the crontab should be the line:
0,10,20,30,40,50 * * * * /home/myself/bncchk >/dev/null 2>&1
Modify the path to the bncchk file. This line will check to see if bnc is running every 10 minutes, and if it is not running, will attempt to restart BNC with the information provided by the varibles in the bncchk file.
|