Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Well after trying out, ircd-hybrid, Unrealircd and inspircd. I could still not do what I need for my irc server.

I need to make a secure channel / server. what I want to do is I want to have it so only users with a specified Vhost are allowed to speak (server wide).


  • (this user cannot speak in the server)
  • (This user can speak, preferably a Oper.)

This brings me to my next question. could I just make it so only Oper users can talk server-wide?

Also I can add I am running Centos 5.9 64bit on a CNserver. And I do NOT want to add services (Like anope, hybrserve, or any other)

share|improve this question

closed as off-topic by Bryan, Ward, mdpc, dawud, Dave M Aug 23 '13 at 14:19

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is a site dedicated to professionals; novice questions are off-topic. Please see the Help Center for more information on topicality. The best advice we can give you is to hire a professional to help you out." – Bryan, Ward, mdpc, dawud, Dave M
If this question can be reworded to fit the rules in the help center, please edit the question.

What particular problem in a professional environment are you attempting to solve? – voretaq7 Aug 21 '13 at 14:55
"I do not want to add services" <- everything from registration to setting opers properly onwards relies on this. Not getting services practically cripples your irc server. – Journeyman Geek Aug 22 '13 at 0:05

I'm going to be blunt: You're Doing It WRONG.

IRC already has a facility for restricting who can speak in channels (two of them in fact -- Voice (+v) and Operator (+o))
You can combine these with other common IRC tools (like eggdrop bots) to op and/or voice authorized individuals, and whether that's what you want or not is irrelevant, it's how it should be done.

Using the host mask to control this is woefully insecure (and woe be upon the folks who configure their eggdrop bots to trust hostmasks).
I can change my hostmask to be whatever I want (because I happen to have control over my reverse DNS, and the username is arbitrary data supplied by the client). Relying on that as a security mechanism is thus fundamentally flawed.

The alternative, making it so only operators can talk server-wide, is also an option, though not one you would be able to exercise if you were to become part of a larger "normal" IRC network.
Implementing this solution would require some custom edits to the ircd source code, and is left as an exercise for the reader.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.