View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005985 | unreal | ircd | public | 2021-10-28 09:02 | 2021-12-30 16:52 |
| Reporter | armyn | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 5.2.1.1 | ||||
| Summary | 0005985: How to deal with people who bypass bans in IPv6 even 12 year olds do it and without intentionally bypassing | ||||
| Description | Hi I noticed that in glines this: /gline *@2a01:xxx:1b4:60:xxxx:a88a:f16:1 then the user often returns very quickly to the IRC server with this ip: *@2a01:xxx:1b4:60:xxxx:a88a:f16:2 and *@2a01:xxx:1b4:60:xxxx:a88a:f16:3 etc ... How to make UnrealIRCd able to glide the first 4 tracks: *@2a01:xxx:1b4:60:* as soon as you type /gline *@2a01:xxx:1b4:60:xxxx:a88a:f16:1 is there an easy way to do this via UnrealIRCd? Also I heard that an IPv6 works like this: AAAA:AAAA:AAAA:AAAA:P:P:P:P that AAAA:AAAA:AAAA:AAAA is the equivalent of the public IP and that P:P:P:P is like the local ip prive Is it true ? So 2 devices under the same box, it will therefore have 2 different ipv6: AAAA:AAAA:AAAA:AAAA:P:P:P:P1 and AAAA: AAAA:AAAA:AAAA:P:P:P:P2 and in reality we should therefore always ban AAAA:AAAA:AAAA: AAAA:* and never AAAA:AAAA:AAAA:AAAA:P:P:P:P ? | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
For channels, so for chanops banning users (not ircops), this is useful information on cloaking: https://www.unrealircd.org/docs/Cloaking#Cloaked_IP_addresses As you can see in the table, a chanop can ban *!*@*:CCCCCCCC:IP For *LINES, as an IRCOp, you can use CIDR, like *@2a01:xxx:1b4:60:xxxx:a88a:f16:0:1/64 That /64 is basically a wildcard for the last 64 bits of the address. Maybe we can update https://www.unrealircd.org/docs/CIDR to show an IPv6 example. |
|
|
Just to clear: in the CIDR example I gave you, it means the same as what you can do with wildcards: *@2a01:xxx:1b4:60:* With CIDR it is just a bit easier to do without thinking. You simply type /64 at the end of the IPv6 IP. |
|
|
Thank I didn't know about the /gline *@2a02:000:a36:40b0:a995:300a:e92c:46c2/64 Before I put this: /gline *@2a02:000:a36:40b0: * And for the ban on the channels will be useful too, you just have to create a duplicator with a bot that puts a ban on the *!*@*:CCCCCCCC:IP |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-10-28 09:02 | armyn | New Issue | |
| 2021-12-30 13:37 | syzop | Note Added: 0022339 | |
| 2021-12-30 13:38 | syzop | Note Edited: 0022339 | |
| 2021-12-30 13:42 | syzop | Note Edited: 0022339 | |
| 2021-12-30 13:42 | syzop | Note Edited: 0022339 | |
| 2021-12-30 13:43 | syzop | Note Added: 0022340 | |
| 2021-12-30 13:44 | syzop | Note Edited: 0022340 | |
| 2021-12-30 15:53 | armyn | Note Added: 0022343 | |
| 2021-12-30 16:52 | syzop | Assigned To | => syzop |
| 2021-12-30 16:52 | syzop | Status | new => closed |
| 2021-12-30 16:52 | syzop | Resolution | open => no change required |
