Anope Support > 1.8.x/1.7.x Support (Read Only)

Unexpected AKILL ADD behaviour

(1/1)

Zomatillo Lajaronius:
here's what I entered and the replies I got:
/msg OperServ AKILL ADD +0 NameToKill@* We don't know you
[16:25:51] -> *OperServ* AKILL ADD +0 NameToKill@* We don't know you
[16:25:51] -OperServ- Deleted 1 entries from the AKILL list.
[16:25:51] -OperServ- NameToKill@* added to the AKILL list.
/msg operserv AKILL list
[16:26:28] -> *operserv* AKILL list
[16:26:28] -OperServ- Current AKILL list:
[16:26:28] -OperServ-   Num   Mask                              Reason
[16:26:28] -OperServ-     1   NameToKill@*                      We don't know you

Why would an entry be removed ? None of my opers have akilled this user ...

Adam:
This means that there was another akill mask on the list prior that matched what you added.

Zomatillo Lajaronius:

--- Quote from: Adam on February 27, 2017, 01:15:51 AM ---This means that there was another akill mask on the list prior that matched what you added.

--- End quote ---

If that was so, then what was the person doing on the server, seeing them connect was what triggered me to akill them.
Am I wrong about akills ? If your host matches an akill entry, you never get to connect to the server is what I thought.

Adam:
For example adam@* is more broad than adam@1.2.3.4, so the akill for adam@1.2.3.4 would be removed. I could still be online, but not from 1.2.3.4.

Zomatillo Lajaronius:

--- Quote from: Adam on February 27, 2017, 02:02:56 AM ---For example adam@* is more broad than adam@1.2.3.4, so the akill for adam@1.2.3.4 would be removed. I could still be online, but not from 1.2.3.4.

--- End quote ---

OK, now I get it, thanks very much.

Navigation

[0] Message Index