Skip to content

005 support for KICK doesnt work or is not implemented #1060

Description

@michaelortmann

I dont know the exact status of 005 support within eggdrop. Pls bear with me if this is not a valid Issue but simply missing functionality that would be implemented later.

With the following settings and commands i expected eggdrop to kick all 3 users matching the ban, but eggdrop only kicks one out of the three users:

.chaninfo #test6887
+enforcebans
-dynamicbans
.channel
Channel #test6887, 4 members, mode +stn:
(n = owner, m = master, o = op, d = deop, b = bot)
 NICKNAME  HANDLE     JOIN   IDLE  USER@HOST
@BotA      *          ---         <- it's me!
 t1        *         19:51                ~michael@127.0.0.1
 t2        *         19:51                ~michael@127.0.0.1
 t3        *         19:51                ~michael@127.0.0.1
End of channel info.
.+ban t*!*@*
New ban: t*!*@* (requested)
[19:52:02] Changed: 0, kick-method: 4, nr: 1
[19:52:02] #test6887: mode change '+b t*!*@*' by BotA!~BotA@127.0.0.1
[19:52:02] t1 kicked from #test6887 by BotA: Banned: requested

There is more: when i remove the ban i see a stale pending kick:

.-ban 1
Removed ban: t*!*@*
.channel
[...]
 NICKNAME  HANDLE     JOIN   IDLE  USER@HOST
@BotA      *          ---         <- it's me!
 t2        *         19:51    19m         ~michael@127.0.0.1
    (pending kick)
[...]

I was testing eggdrop version 5182a22 (Nov 1 2020) on ircd-seven-1.1.9 server.

.status
I am BotA, running eggdrop v1.9.0+etchost: 7 users (mem: 271k).
Online for 00:47 (terminal mode) - CPU: 00:00.23 - Cache hit:  2.0%
Configured with: 'CFLAGS=-O2 -D_FORTIFY_SOURCE=2 -fstack-protector-all -fstack-clash-protection -fsanitize=address,undefined -ldl'
Admin: Lamer <email: lamer@lamest.lame.org>
Config file: BotA.conf
OS: Linux 5.9.3-arch1-1
Process ID: 51736 (parent 42406)
Tcl library: /usr/lib/tcl8.6
Tcl version: 8.6.10 (header version 8.6.10)
Tcl is threaded.
TLS support is enabled.
TLS library: OpenSSL 1.1.1h  22 Sep 2020
IPv6 support is enabled.
Socket table: 20/100
Memory table: 3950/4096 (96.4% full)
Memory fault: only accounting for 278120/285848 (97.3%)
Memory table itself occupies an additional 160k static
Loaded module information:
    Channels: #test6887
[...]

server 005 has KICK:1
but eggdrop doesnt use it
i see:

[23:47:11] [!s] KICK #test6888 t1,t2,t3 :Banned: requested
[23:41:09] [s->] KICK #test6888 t1,t2,t3 :Banned: requested

which cant work for this server with KICK:1

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions