View Issue Details

IDProjectCategoryView StatusLast Update
0000474unrealircdpublic2003-11-20 19:44
ReporterMrBOFH Assigned Tosyzop  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.2-beta12 
Summary0000474: problem with banning
Description* Now talking in #moo
* moomoo ([email protected]) has joined #moo
* MrBOFH sets mode: +b *!*@141.153.163.160
* moomoo ([email protected]) has left #moo
* moomoo ([email protected]) has joined #moo

You cant ban by IP....
Additional InformationAny idea when 3.1.5 will be released?
TagsNo tags attached.
3rd party modules

Activities

mister

2002-11-20 18:42

reporter   ~0000730

the ban is a text comparison

if you ban *!*@1.2.3.4 then only users with 1.2.3.4 for host (I know it is an IP, but for the server this is only host, a text string) will be banned

so a user coming with @1-2-3-4.com won't be rejected, even if is IP is 1.2.3.4 (and notice also that in one case you have - and in the other case you have . between the numbers... )

MrBOFH

2002-11-20 19:12

reporter   ~0000731

Yes im aware of that... and on alot of ircd's you can ban by IP even if they are coming in with a host mask as long as it resolves to that IP. It would be very nice if that could be done here also.

screaming_lord

2002-11-21 19:42

reporter   ~0000733

hello, have u tried banning by typing

*!*@141.153.163.*

that will work

MrBOFH

2002-11-22 05:31

reporter   ~0000735

If my mask is pool-141-153-163-160.mad.east.verizon.net banning *!*@141.153.163.* wont work either.

I'm just asking that it be made to work like that, so that even if you come in with a hostmask of pool-141-153-163-160.mad.east.verizon.net if the ip is banned.. it keeps you out. Many IRCD's allow for it and its usefull.

syzop

2003-04-19 20:49

administrator   ~0002424

Added in .1747.

Issue History

Date Modified Username Field Change
2003-04-19 20:49 syzop Status acknowledged => resolved
2003-04-19 20:49 syzop Resolution open => fixed
2003-04-19 20:49 syzop Assigned To => syzop
2003-04-19 20:49 syzop Note Added: 0002424
2003-11-20 19:44 syzop Status resolved => closed