View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006295 | unreal | ircd | public | 2023-07-04 13:46 | 2023-07-04 16:41 |
Reporter | armyn | Assigned To | syzop | ||
Priority | normal | Severity | tweak | Reproducibility | have not tried |
Status | closed | Resolution | no change required | ||
Product Version | 6.1.1.1 | ||||
Summary | 0006295: Show ipv6 and ipv4 in whois or whowas or in a command like /futurgline | ||||
Description | Every time I ban an IPv4 or IPv6 address, there are always users who find an alternative. For example, if I ban a user connected via IPv4, they then bypass the ban using IPv6 (or vice versa). It would be ideal to be able to detect both IPv4 and IPv6 of a user in order to ban both IPv4 and IPv6/64 each time. | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
|
The same can happen with someone that uses VPN and switches over IP's :) i think you cannot find someone who uses IPv4 his IPv6 address or vice-versa , but not sure. |
|
Yeah, like westor says, unfortunately if a client is connected through IPv4 then you cannot see what would have been their IPv6 address, and vice-versa. Those addresses are unrelated and not known to the server. Someone on IRC pointed that you could do a DNS reverse lookup on the host for both A and AAAA, but for pretty much every ISP host this would not result in a record for the other IP protocol, the hostnames are always different for IPv4 and IPv6, so that is useless. It's really only for some custom vhosts that you MAY get a match. So that isn't worth the effort at all (and then you can just ban by host of course). So, no sadly this is not possible, it is in a similar category of people asking to ban mac addresses, that is information that is not known to the IRCd either :) |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-07-04 13:46 | armyn | New Issue | |
2023-07-04 13:49 | westor | Note Added: 0022940 | |
2023-07-04 16:40 | syzop | Assigned To | => syzop |
2023-07-04 16:40 | syzop | Status | new => closed |
2023-07-04 16:40 | syzop | Resolution | open => no change required |
2023-07-04 16:40 | syzop | Note Added: 0022941 | |
2023-07-04 16:41 | syzop | Note Edited: 0022941 |