A guide to ALL ban modes/extbans/banmasks needed

Shining Phoenix · Post by **Shining Phoenix** » Sun Jan 07, 2007 7:55 am

8:14pm Mode change by Phoenix: +b nq:*!*@*
8:14pm Mode change by Phoenix: -b nq:*!*@*
[20:14] <Phoenix> That was not supposed to work...

I once thought
+b/e/I ~[extban]:[nick!username@host]/[channel]/[realname]
was all the bans. But then...
+b +nick!username@host
+b nick!username@IP/range
+b nq:nick!ident@host
...I found more stuff. Testing every character combo to see what it does would take ages, so could someone write a complete guide on the darn things? More ways to ban/except/invite just keep popping up.
Heck knows what +I ~nq:nick!username@host does, since chmode i doesn't affect nickchanging or speaking

JanisB · Post by **JanisB** » Sun Jan 07, 2007 12:13 pm

http://www.vulnscan.org/UnrealIRCd/unre ... e_bantypes ?

Shining Phoenix · Post by **Shining Phoenix** » Mon Jan 08, 2007 4:12 am

ROFL
Believe it or not, I did read the bit in that manual

Not everything is in there.

Jason · Post by **Jason** » Mon Jan 08, 2007 4:44 am

You just didn't read it closely. Note the importance of the ~ for extbans. It is missing in your examples. Also: Your ban examples are valid. They are just not valid extbans. Since : is not a valid nick character, those bans will just never match.

Shining Phoenix · Post by **Shining Phoenix** » Mon Jan 08, 2007 4:56 am

Ahh, I never thought it would let you put in a : as a character in the nick matching bit. That makes a lot of my questions go away.

Mode change by Phoenix: +I ~n:*!*@*
^What exactly will that do?

Mode change by Phoenix: +I ~c:@#anotherchannel
^That should let a user with @ or higher in #anotherchannel into this one when it is invite only, but alas it did not work. Why did it not work?

Post by **Jobe** » Mon Jan 08, 2007 12:12 pm

As far as i know and understand extended bans are just that, extensions to ban and ban exceptions which i believe does not include invite exceptions.

I may be wrong though.

Although the documentation at http://www.vulnscan.org/UnrealIRCd/unre ... e_bantypes doesnt suggest anything about including +I's only +b's and +e's

Shining Phoenix · Post by **Shining Phoenix** » Mon Jan 08, 2007 11:43 pm

So now I've got two scenarios:
1. Extbans are meant to work with +I but they are broken OR
2. They are not meant to work, and don't, but the IRCd does it anyway.

Anyone know for sure which it is?