I saw that 10+ years ago when experimenting IPv6 torrents. AFAIK, those addresses are plain IPv4 addresses in the wrong part of the address field. Sigh.... From: ipv6-wg <ipv6-wg-bounces@ripe.net> on behalf of Marco Moock <mm@dorfdsl.de> Date: Saturday, 6 April 2024 at 09:50 To: ipv6-wg@ripe.net <ipv6-wg@ripe.net> Subject: [ipv6-wg] IPv6 torrent and non-GUA addresses Hello! I want to share some experience and ask if other people here also noticed that behavior. I operate an IPv6 torrent client (qbittorrent/libtorrent) and I noticed various things: The client itself sometimes uses non-GUA source addresses when connecting to GUA addresses in the default setting. When binding to the GUA address only, it uses only them. https://github.com/qbittorrent/qBittorrent/issues/19618 This seems to be not yet fixed. I also notice a reasonable amount of incoming traffic with non-GUA addresses like from 63ed:b73b::/32 or 485f:1207::/32, ac11:1::/32 etc. This also shows that some ISPs don't seem to prohibit their customers from sending such packages. Does anybody here also experienced that? Is there any monitoring at exchange points to find the source? -- kind regards Marco Send unsolicited bulk mail to 1711396344muell@cartoonies.org -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ipv6-wg