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
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
Am 06.04.2024 um 08:56:53 Uhr schrieb Eric Vyncke (evyncke):
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.
Interesting. Do you know what causes that? -- Gruß Marco Send unsolicited bulk mail to 1712386613muell@cartoonies.org
Am 06.04.2024 um 08:56:53 Uhr schrieb Eric Vyncke (evyncke):
AFAIK, those addresses are plain IPv4 addresses in the wrong part of the address field.
Another strange address is fe0e:f33d:c8d5:2a01:xxx:xxx:2:aaa1 The last 80 bits are the beginning of my machine's IPv6 address. I also saw 1:5a9c:fcff:fe0e:f33d:c8d5:2a01:170 The last 32 bits are the first of my IP address. Did anybody else also saw that? Some addresses also have my 64 bit identifier at the left side as their source address. Is there any way to find that out which clients create such requests and why even operating systems let an application send such packages out when they aren't attached to any interface? -- kind regards Marco Send unsolicited bulk mail to 1712386613muell@cartoonies.org
participants (2)
-
Eric Vyncke (evyncke) -
Marco Moock