Google Answers Logo
View Question
 
Q: Setting up an IRCD Server on Fedora Core ( No Answer,   0 Comments )
Question  
Subject: Setting up an IRCD Server on Fedora Core
Category: Computers > Software
Asked by: coderoyal-ga
List Price: $20.00
Posted: 08 Jun 2004 16:11 PDT
Expires: 12 Jun 2004 16:05 PDT
Question ID: 358377
Help! I would like someone to take a look at my irc settings and tell
me what I am  doing wrong. I am tryin to set up a basic IRC server to
be used as a chat room on our website. We will be using a java client
which is automatically configured to connect to the server.

I installed IRCD from source. I created the ircd.conf file and ircd
appears to start sucessfully. It's running under an ircd account and
the group ID and user ID is set up for it.

I believe I am missing something in the conf file that is preventing
the server from working.

I'll just list the active lines in the ircd.conf file below:

# A: [MANDATORY]. This line lists your administrative information
# (contact address, etc). To view this information, /admin (server) will
# show it to you.
#
# A:<Your Name/Location>:<Your E-Mail Addr>:<other info>::<network name>
# Note that <network name> *must* be one word.
#
A:Alan Owen, Hermon School Department:Daemon
<Alan_Owen@brittany-snow.com>:IRC Server::IRCnet

# P: [MANDATORY]. This field allows the server to listen on various ports
# for connections. Any internet domain port that is below 1024 means the
# ircd has to be run as root, or from inetd. The server can listen to ports
# in the UNIX domain or the internet domain. If you wish to create a port
# in the UNIX domain you must compile with UNIXPORT defined in config.h.
#
# P:<YOUR Internet IP#>:<*>::<Port>:
# P:<Directory>:<*>:<*>:<Port>:
#
# Note that it's a good idea to open some more ports than 6667 for
# server-server connections and local clients in case some running wild
# client blocks the default 6667.
#
# The default, an internet domain socket on port 6667 listening on all
# ip addresses of the machine running ircd
#P::::6667:
#
# an internet domain socket listening on port 6668 on address 206.252.192.20
# (again useful if you're running virtual interfaces)
P:66.186.176.230:::6667:
#
# This line is an example of a UNIX domain socket in /tmp
P:/tmp/.ircd:*::6668:

# This would allow access for any client reaching this line which doesn't
# already have at least one connection to the net.  if you run an open server
# in a net this might be the right choice, talk to your uplinks first anyway.
# resolving clients matching this line would be shown as user@host since
# the field <TARGET Hosts NAME> is empty.
# Note listing this i: line first, it will be checked *last*, meaning it is
# the "fall-through".
i:*@*::::

# O:<TARGET Host NAME>:<Password>:<Nickname>:<Port>:<Class>
#
# If the person in "Nickname" is not coming from the hostname defined in
# the first field then the person will get the error message "No O: lines
# for your host".
#
# Note that you don't need to use 'Nickname' to become operator, if you're
# using some other nick at that moment '/oper Nickname' will do also.
#
#O:*.bu.edu:Zaphod:Trillian::10
O:*:(operator access password removed for security, but exists in conf file):*::*

All the other options in the conf file to my knowledge don't apply to
me because I'm not acting as a "hub" or a "leaf". I'm trying to run as
an independent IRC server.

Running on Fedora Core I kernel 2.4.22-1.2188.nptlsmp
IRC Version 2.11.0a8

If we need to, we can both schedule a time and connect to the server
via ssh and redo the configuration together, which I will pay an
additional $20 to do if it's neccisary.

Clarification of Question by coderoyal-ga on 12 Jun 2004 16:05 PDT
I figured out the answer! The configuration was correct all along. The
issue was related to iptables being turned on by default with the
installation. I found this out by running the command:

service iptables stop

This showed that it was running and stopped the service.

I later removed iptables via the following command. 

rpm -e iptables

It will list dependencies so you just need to retype the rpm -e
command and list the dependencies with iptables. Ex:

rpm -e iptables dependency1 dependency2

That was my solution!
Answer  
There is no answer at this time.

Comments  
There are no comments at this time.

Important Disclaimer: Answers and comments provided on Google Answers are general information, and are not intended to substitute for informed professional medical, psychiatric, psychological, tax, legal, investment, accounting, or other professional advice. Google does not endorse, and expressly disclaims liability for any product, manufacturer, distributor, service or service provider mentioned or any opinion expressed in answers or comments. Please read carefully the Google Answers Terms of Service.

If you feel that you have found inappropriate content, please let us know by emailing us at answers-support@google.com with the question ID listed above. Thank you.
Search Google Answers for
Google Answers  


Google Home - Answers FAQ - Terms of Service - Privacy Policy