Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Anope 2.0.5 + Ircd Hybrid 8.2.22 : ChanServ Ban Everyone!  (Read 380 times)

0 Members and 1 Guest are viewing this topic.

Abner

  • Anope User
  • Offline Offline
  • Posts: 10
Anope 2.0.5 + Ircd Hybrid 8.2.22 : ChanServ Ban Everyone!
« on: October 17, 2017, 11:37:54 PM »

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.
« Last Edit: October 18, 2017, 04:27:09 AM by Abner »
Logged

Abner

  • Anope User
  • Offline Offline
  • Posts: 10
Re: Anope 2.0.5 + Ircd Hybrid 8.2.22 : ChanServ Ban Everyone!
« Reply #1 on: October 20, 2017, 01:41:33 AM »

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
Logged
Pages: [1]   Go Up