View Issue Details

IDProjectCategoryView StatusLast Update
0001627unrealircdpublic2004-03-07 20:46
Reportertabrisnet Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionopen 
Product Version3.2-RC1 
Summary0001627: ban does not make quiet
DescriptionI have a bot on my network, a coding project by one of my admins... which sometimes, I just want to make it shutup.

so, I set a ban on it like so ~q:*!*@192.168.*.*
or I set a cloaked hostname ban like so ~q:*!*@31DE0AV3.7B503408.B253B4BDB.IP

I've also tested it w/o the extended banmode, just a regular ban. The bot still does not shut up. it has no oper. no voice or chanop.
Steps To Reproduceban bot. talk to bot in channel. bot talks back, despite ban.
3rd party modules

Activities

syzop

2004-03-07 12:28

administrator   ~0005331

Make sure the bot is also on a RC1 server.

tabrisnet

2004-03-07 12:53

reporter   ~0005334

It is. there are two servers on this network, both are running RC1.

syzop

2004-03-07 13:29

administrator   ~0005335

Does it happen with ~q bans on everyone? Perhaps you could play around a bit :P.
I've had a report before and then tested it here.. everything worked fine (turned out the +b'd person was on a bet19 server ;p).

tabrisnet

2004-03-07 15:35

reporter   ~0005337

unable to reproduce in any sane manner
I have verified that the 404 numeric is sent properly in all cases, except this bot when in this channel.

It seems to actually be specific to that bot, that channel. No. I do not know why. I even tried saparting and sajoining to reset any channel modes for this bot.

if i join the bot to #test, have the bot PRIVMSG #test, the bot is unable to speak.
if I tell the bot to speak in #surrealchat, the bot is able to speak, despite the quiet ban (which, I copied from #test to have no typos).

This is one mighty odd bug.

tabrisnet

2004-03-07 15:38

reporter   ~0005338

ok. i think i found the problem... sorry to have not found it before.
there's a ban exception list on this channel. i'll clear it.

syzop

2004-03-07 20:46

administrator   ~0005343

dumdeedum

Issue History

Date Modified Username Field Change
2004-03-07 12:24 tabrisnet New Issue
2004-03-07 12:28 syzop Note Added: 0005331
2004-03-07 12:53 tabrisnet Note Added: 0005334
2004-03-07 13:29 syzop Note Added: 0005335
2004-03-07 15:35 tabrisnet Note Added: 0005337
2004-03-07 15:38 tabrisnet Note Added: 0005338
2004-03-07 20:46 syzop Status new => closed
2004-03-07 20:46 syzop Note Added: 0005343