|
|
| Author |
Message |
garethnelsonuk
none
Joined: 03 Oct 2004
Posts: 16
|
 Posted: Oct 23, 2004 9:35am Post subject: anope AKILL |
 |
|
recently i've had to ban a user from my network and so i decided to use the AKILL feature in anope's OperServ. slight problem though: they can still connect and cause trouble. they keep on connecting and someone has to /kill them (they done this 16 times until i had to manually add a kill {} block to ircd.conf on all the servers running hybrid)
anyone else had trouble with this? this particular user has been causing a lot of trouble attempting to blackmail my staff, demanding an o-line, spamming his own channel located at freenode everywhere (resulting in PMs to ops asking to /kick him) and generally causing a lot of trouble. it was practically a flood as i had to /kill them with each join
is it just anope being crap or am i doing something wrong?
apparently the akill did work but was too slow, they managed to connect and harass some of my users for about 10 minutes! |
|
| Back to top |
|
 |
Willaim
Lurker
Joined: 27 Jun 2003
Posts: 242
Location: IRC
|
| Posted: Oct 23, 2004 12:04pm Post subject: |
|
|
| do you have the AkillOnAdd directive enabled? |
|
| Back to top |
|
|
zeke
Idler
Joined: 04 Oct 2003
Posts: 325
|
| Posted: Oct 23, 2004 7:13pm Post subject: |
|
|
i haven't had any probs with akill under anope for a long time (been using since 1.4.24), so if anything, its your config
if AkillOnAdd is defined, OperServ adds the G:Line as soon as you add the akill. if it isn't, OperServ adds the G:Line as soon as it sees a matching user connect. (Most anope G:Lines are set to expire after 2 hours or 2 days or something similar, to keep the list tidy, but readds G's as necessary)
It seems most likely that its your AkillOnAdd not being defined, otherwise check the rest of your Akill configuration in services.conf |
|
| Back to top |
|
|
Plasma
Newbie
Joined: 10 Dec 2003
Posts: 63
|
| Posted: Oct 23, 2004 7:34pm Post subject: |
|
|
| Ensure your adding an akill mask that matches the user in question? |
|
| Back to top |
|
|
aquanight
Lurker
Joined: 14 Jun 2004
Posts: 118
Location: Boise, ID
|
| Posted: Oct 23, 2004 9:57pm Post subject: Re: anope AKILL |
|
|
| garethnelsonuk wrote: | | (they done this 16 times until i had to manually add a kill {} block to ircd.conf on all the servers running hybrid) |
I think for hybrid, Anope tries to use the "shared K:Lines" feature, which requires a shared {} block specify that all users on the services server may add remote K:Lines. Treat the shared {} block for services as you would a U:Line / ulines {} block for any other IRCd: all servers need it set correctly, or things go horribly wrong.
*edit* I think the reason for this is because Hybrid IIRC requires 3 opers from different servers to add the same G:Line for it to be effective. */edit* |
|
| Back to top |
|
|
garethnelsonuk
none
Joined: 03 Oct 2004
Posts: 16
|
| Posted: Oct 25, 2004 4:55pm Post subject: |
|
|
i'll try adding the shared { } block
see if that works...
thanks |
|
| Back to top |
|
|
W-Unit
Newbie
Joined: 29 Jul 2004
Posts: 83
|
| Posted: Oct 25, 2004 7:15pm Post subject: |
|
|
Why bother AKILLing when you can G:Line?
/quote gline ADDRESS EXPIRY :REASON |
|
| Back to top |
|
|
w00t
Eleet
Joined: 09 Jun 2004
Posts: 699
Location: Nowra, Australia
|
| Posted: Oct 25, 2004 11:48pm Post subject: |
|
|
I don't know why you had /quote there, nor the ":". Try:
GLINE <user@host mask or nick> [time] <reason>
Secondly, not all IRCds have GLINE, or GLINE doesn't mean what it does in Unreal. |
|
| Back to top |
|
|
aquanight
Lurker
Joined: 14 Jun 2004
Posts: 118
Location: Boise, ID
|
| Posted: Oct 26, 2004 12:09am Post subject: |
|
|
Yes, not all IRCds define GLINE the same way.
Hybrid: 3 opers must add the same gline for it be effective. Each oper must be on a different server.
Bahamut: Only services can add AKILLs.
IRCu: GLINEs can be local to a server (counter-intuitive - isn't that the same as a KLINE?  ), or only belong to a specific set of servers, or belong to all servers.
Some examples.
w00t: Some clients (most notably the command-line unix-based ones) don't like using /gline directly. |
|
| Back to top |
|
|
w00t
Eleet
Joined: 09 Jun 2004
Posts: 699
Location: Nowra, Australia
|
| Posted: Oct 26, 2004 12:11am Post subject: |
|
|
| aquanight wrote: | | w00t: Some clients (most notably the command-line unix-based ones) don't like using /gline directly. |
Screw them then I've only used ircII on a command line, can't remember how that reacted to gline. |
|
| Back to top |
|
|
W-Unit
Newbie
Joined: 29 Jul 2004
Posts: 83
|
| Posted: Oct 30, 2004 9:23am Post subject: |
|
|
| w00t wrote: | I don't know why you had /quote there, nor the ":". Try:
GLINE <user@host mask or nick> [time] <reason>
Secondly, not all IRCds have GLINE, or GLINE doesn't mean what it does in Unreal. |
I had it in there to try to make it as cross-IRCd and cross-client as possible. I don't know of any off the top of my head but I'm sure there are some clients that don't like you using /gline directly. Also, when the server sees the "reason" field it sees them preceeded with a : but removes it when giving output to a user. For instace, sending this command -> Server: gline *@thishostdoesntexist.net 0 :no reason gives this output Permanent G:Line added for *@thishostdoesntexist.net on Sat Oct 30 15:20:51 2004 GMT (from W-Unit!w.dresh@netadmin.wtfnet.org: no reason). I know that in certain IRCds you must prefix the reason for a /kill with a : so I assumed that this might be the same for a G:line.
And if a G:Line is different on their IRCd, I think he is intelligent enough to replace G:Line with whatever applies to him. |
|
| Back to top |
|
|
|
Register
Log in
