View Issue Details

IDProjectCategoryView StatusLast Update
0006295unrealircdpublic2023-07-04 16:41
Reporterarmyn Assigned Tosyzop  
PrioritynormalSeveritytweakReproducibilityhave not tried
Status closedResolutionno change required 
Product Version6.1.1.1 
Summary0006295: Show ipv6 and ipv4 in whois or whowas or in a command like /futurgline
DescriptionEvery 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.
TagsNo tags attached.
3rd party modules

Activities

westor

2023-07-04 13:49

reporter   ~0022940

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.

syzop

2023-07-04 16:40

administrator   ~0022941

Last edited: 2023-07-04 16:41

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 :)

Issue History

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