Hi: Kann man im ngircd /mode +k setzen, um User notfalls komplett aus dem Server zu entfernen? Danke. mm.
Michaela Merz <mm@hermetos.com> wrote:
Kann man im ngircd /mode +k setzen, um User notfalls komplett aus dem Server zu entfernen?
No, k-lines are not supported by ngircd so far. And, because ngircd supports tcp-wrappers i'm not sure if k-lines would be a meaningful feature. [ to repeat in german: Nein, aber da ngircd tcpwrapper-support hat, denke ich nicht das k-line support in ngircd eine sinnvolle Erweiterung waere. ] Gruesse, Florian
In addition to my last mail/post (ngircd and anope won't cooperate well): While anope annouces: Setting correct user modes for misch on #channel (giving modes) Setting +o on #channel for misch Setting correct user modes for misch on #channel (not giving modes) .. this is what ngircd receives: ngircd[6679]: <- connection 8: 'MODE #channel'. I'd say, we're missing a few more parameters here. It looks as if anope doesn't send them. Version is : anope-1.9.4-p1 - not sure if this is a general anope problem, or if it is related to the ngircd module. Or - maybe - I am just plain stupid and won't see my own errors :) Any help is appreciated. mm.
Michaela Merz <mm@hermetos.com> wrote:
Kann man im ngircd /mode +k setzen, um User notfalls komplett aus dem Server zu entfernen?
No, k-lines are not supported by ngircd so far.
And, because ngircd supports tcp-wrappers i'm not sure if k-lines would be a meaningful feature.
[ to repeat in german: Nein, aber da ngircd tcpwrapper-support hat, denke ich nicht das k-line support in ngircd eine sinnvolle Erweiterung waere. ]
Gruesse, Florian
Hi Michaela! Am 15.12.2011 um 22:23 schrieb Michaela Merz:
In addition to my last mail/post (ngircd and anope won't cooperate well):
While anope annouces:
Setting correct user modes for misch on #channel (giving modes) Setting +o on #channel for misch Setting correct user modes for misch on #channel (not giving modes)
.. this is what ngircd receives:
ngircd[6679]: <- connection 8: 'MODE #channel'.
I'd say, we're missing a few more parameters here. It looks as if anope doesn't send them. Version is : anope-1.9.4-p1 - not sure if this is a general anope problem, or if it is related to the ngircd module. Or - maybe - I am just plain stupid and won't see my own errors :)
Any help is appreciated.
Support for Anope is quite new and incomplete/rudimentary/buggy in r18. If you want to use it, upgrade your Anope installation to current GIT 1.9-branch and use latest ngIRCd git as well. There have been quite a few fixes and enhancements, especially in mode handling. Regards Alex
Hello: We are experiencing a big and very annoying Problem: Some clients get blocked in some channels for no reason: /join #channel #channel Cannot join channel (+b) Even a /mode -b #channel *!* doesn't change anything. If the user get's invited, he is able to join, but can't speak. Just to make sure: This only happens to about 5% of all connecting clients - and we have no way to predict which client is able to join and who isn't. Channel is pre-set Name = #channel Topic = This is our channel Modes = tn
Michaela Merz wrote...
We are experiencing a big and very annoying Problem: Some clients get blocked in some channels for no reason:
This sounds really weird. FWIW, I operate ngircd for a small network of about 40 users without any of these problems.
Just to make sure: This only happens to about 5% of all connecting clients - and we have no way to predict which client is able to join and who isn't.
* Did you check whether this is related to Anope? * If a client is banned, will a second try succeed? Does altering the nick or user name change anything? Christoph
Michaela, When someone complain about this, could you enter in the channel, type /mode #channel +b (and this will show you provably in Status window the current ban list) and then do a /whois banned-nicknamed and past both information here? I think it would be helpful if we together double check if there isn't really a match between the user host and the current channel ban list. Kurt Kraut 2011/12/17 Christoph Biedl <ngircd.anoy@manchmal.in-ulm.de>
Michaela Merz wrote...
We are experiencing a big and very annoying Problem: Some clients get blocked in some channels for no reason:
This sounds really weird. FWIW, I operate ngircd for a small network of about 40 users without any of these problems.
Just to make sure: This only happens to about 5% of all connecting clients - and we have no way to predict which client is able to join and who isn't.
* Did you check whether this is related to Anope? * If a client is banned, will a second try succeed? Does altering the nick or user name change anything?
Christoph _______________________________________________
ngIRCd Mailing List: ngIRCd-ML@arthur.barton.de http://arthur.barton.de/mailman/listinfo/ngircd-ml
Am 15.12.2011 um 18:18 schrieb Florian Westphal:
Michaela Merz <mm@hermetos.com> wrote:
Kann man im ngircd /mode +k setzen, um User notfalls komplett aus dem Server zu entfernen?
No, k-lines are not supported by ngircd so far.
And, because ngircd supports tcp-wrappers i'm not sure if k-lines would be a meaningful feature.
But G-Lines („global K-Lines“) would be useful, and I’m working on it right now ;-) And even G-Linkes can be handy if you are an IRC operator but not server admin („root“), so you can’t fiddle with /etc/hosts.{allow|deny} … Regards Alex
Teilnehmer (5)
-
Alexander Barton -
Christoph Biedl -
Florian Westphal -
Kurt Kraut -
Michaela Merz