Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1] 2 3 ... 10
 1 
 on: Yesterday at 03:59:32 PM 
Started by Daniel - Last post by Jens Voss
Code: [Select]
/msg global help

 2 
 on: Yesterday at 03:38:04 PM 
Started by Daniel - Last post by Daniel
Good day,
I have the latest Anope version, but am unable to send global messages to users.
The only global messages that do work, are the services shutdown,restart, and startup messages. However, if a services root tries to send a global message, all they get is, "Attention please!" And, "global: Unknown command."
As far as I know, I have all of the oper things set correctly, and the global module is loaded.
Below is what I have, I'd appreciate some help with this if at all possible.
Anope Config
opertype
{
   name = "Services Root"

   commands = "*"

   privs = "*"
}
   oper
{
   name = "phoenix"

   type = "Services Root"

   /* If set, the user must be an oper on the IRCd to gain their Services
    * oper privileges.
 */
   require_oper = yes

   /* An optional password. If defined the user must login using "/msg OperServ LOGIN" first */
   password = ""

   /* An optional SSL fingerprint. If defined, it's required to be able to use this opertype. */
   #certfp = "ed3383b3f7d74e89433ddaa4a6e5b2d7"

   /* An optional list of user@host masks. If defined the user must be connected from one of them */
   #host = "*@*.anope.org ident@*"

   /* An optional vHost to set on users who identify for this oper block.
    * This will override HostServ vHosts, and may not be available on all IRCds
    */
   vhost = "oper.chavezapps.us"
}
Hopefully the above configuration should help in resolving this. For reference, I am running Anope 2.0.5 on Unix.

 3 
 on: October 20, 2017, 07:20:14 AM 
Started by Amy Scarlett - Last post by genius3000
Ah, I figured out why myself: I forgot to load m_chanprotect.so in modules.conf (I am using InspIRCd).
A nice simple fix, gotta like those. I will point out though that m_chanprotect (while perfectly fine to use) is deprecated in favor of m_customprefix. The example modules.conf has defaults available for founder, admin, and halfop with m_customprefix (unload m_halfop as well).

 4 
 on: October 20, 2017, 07:13:57 AM 
Started by Amy Scarlett - Last post by Amy Scarlett
Ah, I figured out why myself: I forgot to load m_chanprotect.so in modules.conf (I am using InspIRCd).

 5 
 on: October 20, 2017, 01:41:33 AM 
Started by Abner - Last post by Abner
I found the problem:

/*
         * The default options for newly registered channels. Note that changing these options
         * will have no effect on channels which are already registered. The list must be separated
         * by spaces.
         *
         * The options are:
         * -      keeptopic: Retain topic when the channel is not in use
         * -          peace: Disallow users from kicking or removing modes from others who are of the same
         *                     access level or superior
         * -     cs_private: Hide the channel from ChanServ's LIST command
         * -     restricted: Kick/ban users who are restricted from the channel
         * -      cs_secure: Enable channel security, requiring the user to be identified with NickServ in
         *                     order to be considered for being on the access list of the channel
         * -      secureops: Only allow operator status to be given if the user is on the access list
         * -  securefounder: Only allow the real founder of the channel to drop the channel, change it's
         *                     password, or change the founder or successor
         * -       signkick: Use of ChanServ's KICK command will cause the user's nick to be signed to the kick.
         * - signkick_level: Same as above, but the kick will not be signed if the user is at the same access
         *                     level or superior to the target
         * -      topiclock: Disallow the topic to be changed except with ChanServ's TOPIC command
         * -        persist: Keep the channel open at all times
         * -       noautoop: Disables autoop on the channel
         * -  cs_keep_modes: Enables keep modes on the channel, which retains modes when the channel is
         *                     not in use.
         * -           none: No defaults
         *
         * This directive is optional, if left blank, the options will default to keeptopic, cs_secure, securefounder,
         * and signkick. If you really want no defaults, use "none" by itself as the option.
         */
        defaults = "keeptopic peace cs_private restricted cs_secure secureops securefounder signkick signkick_level topiclock persist noautoop cs_keep_modes"

The mode restricted was set in the chanserv.conf

 6 
 on: October 19, 2017, 09:40:43 PM 
Started by Amy Scarlett - Last post by genius3000
My first question would be what IRCd and does it support +q (owner)?
Assuming that it does:
1) Does ChanServ INFO #ChiruNET show you as founder?
2) What happens when you try ChanServ OWNER #ChiruNet ?
If 1) yes and 2) it gives you +q then
3) Are you on the access list as AOP? ChanServ ACCESS #ChiruNet LIST

If ChanServ is currently giving you +o (op) upon joining then it's not an AutoJoin setting, so hopefully the above can get this figured.

 7 
 on: October 19, 2017, 05:38:54 PM 
Started by Amy Scarlett - Last post by Amy Scarlett
Hmmmm... I'm using latest stable version (2.0.5) and it doesn't want to work properly...

+q isn't assigned to me when I have definitely registered the #ChiruNET channel on my network. Not entirely sure why - I am identified to NickServ, OperServ and /oper command on the network. Where there should be an ~ is an @ next to my nick.

Could anyone be of assistance, thanks! ^^

 8 
 on: October 19, 2017, 04:16:06 PM 
Started by cronusnigger - Last post by cronusnigger
CRONUS SO THAT IS YOUR BOT PROTECTION YOU WANTED TO TELL FREENODE ABOUT ROFL!! WHAT A DUMB NIGGER!! TOOK 5 MINS TO CODE IT TO GET AROUND YOUR SHITTY IRCD PROTECTION LOL

 9 
 on: October 17, 2017, 11:38:24 PM 
Started by Abner - Last post by Abner
That message is sent when you have registration set to require admin confirmation. It cannot be changed from within the config; only within the code itself and that is not a supported method.

Ok thanks mate.

 10 
 on: October 17, 2017, 11:37:54 PM 
Started by Abner - Last post by Abner
Guys,

When I into at any channel, #Ajuda as a example, I receive:

Now talking on #Ajuda
* myirc.network sets mode +n on #Ajuda
* myirc.network sets mode +t on #Ajuda

I registered this channel and I receive:

* ChanServ sets mode +r on #Ajuda

john registered his nick and received this:

* john sets mode: +r

When john try to access the #ajuda, he receive:

* You were kicked from #Ajuda by ChanServ (You are not permitted to be on this channel.)

#Ajuda +nrt

If I ( channel founder ) leave the #Ajuda and enter again, I have this:

* Now talking on #ajuda
* myirc.network sets mode +n on #ajuda
* myirc.network sets mode +t on #ajuda
* services.myirc.network removes channel operator status from "abner"
* *** Notice -- TS for #ajuda changed from 1508277878 to 1508277137
* ChanServ sets ban on *!*@abner-ip
* ChanServ sets mode +r on #ajuda
* ChanServ sets mode +n on #ajuda
* ChanServ sets mode +t on #ajuda

When I clear the modes using:

/msg operserv mode #Ajuda CLEAR ALL

I have:

ChanServ removes ban on *!*@john-ip
* ChanServ sets mode -n on #Ajuda
* ChanServ sets mode -r on #Ajuda
* ChanServ sets mode -t on #Ajuda

When john try again into in #Ajuda, I have:

* john (~john@john-ip) has joined
* ChanServ has kicked john from #Ajuda (You are not permitted to be on this channel.)
* ChanServ sets ban on *!*@john-ip
* ChanServ sets mode +r on #Ajuda
* ChanServ sets mode +n on #Ajuda
* ChanServ sets mode +t on #Ajuda

Chanserv disobey the CLEAR command. Every channel that i register I have this "problem", my confs:

ircd.conf

/*
 * service {}: specifies a server which may act as a network service
 *
 * NOTE: it is very important that every server on the network
 *       has the same service {} block.
 */
service {
        /* name: the actual name of the service. Wildcards are not allowed. */
        name = "services.myirc.network";

        /* The 'name' directives can be stacked. */
        name = "stats.example.net";
};

chanserv.conf

/*
         * Modes that are required to be set and only set on all registered channels.
         * These modes can not be locked or unlocked. The registered channel mode is
         * automatically always required, if such a mode exists.
         */
        require = "r"

nickserv.conf

 /*
         * If set, Services will set the channel modes a user has access to upon identifying, assuming
         * they are not already set.
         *
         * This directive is optional.
         */
        modeonid = yes

        /*
         * If set, Services will set these user modes on any user who identifies.
         *
         * This directive is optional.
         */
        modesonid = "+r"

Thank you for any help.

Pages: [1] 2 3 ... 10