<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="en-BE" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US">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....<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
<b><span style="color:black">From: </span></b><span style="color:black">ipv6-wg <ipv6-wg-bounces@ripe.net> on behalf of Marco Moock <mm@dorfdsl.de><br>
<b>Date: </b>Saturday, 6 April 2024 at 09:50<br>
<b>To: </b>ipv6-wg@ripe.net <ipv6-wg@ripe.net><br>
<b>Subject: </b>[ipv6-wg] IPv6 torrent and non-GUA addresses<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:11.0pt">Hello!<br>
<br>
I want to share some experience and ask if other people here also<br>
noticed that behavior.<br>
<br>
I operate an IPv6 torrent client (qbittorrent/libtorrent) and I noticed<br>
various things:<br>
<br>
The client itself sometimes uses non-GUA source addresses when<br>
connecting to GUA addresses in the default setting. When binding to the<br>
GUA address only, it uses only them.<br>
<a href="https://github.com/qbittorrent/qBittorrent/issues/19618">https://github.com/qbittorrent/qBittorrent/issues/19618</a><br>
<br>
This seems to be not yet fixed.<br>
<br>
I also notice a reasonable amount of incoming traffic with non-GUA<br>
addresses like from 63ed:b73b::/32 or 485f:1207::/32, ac11:1::/32 etc.<br>
<br>
This also shows that some ISPs don't seem to prohibit their<br>
customers from sending such packages.<br>
<br>
Does anybody here also experienced that?<br>
Is there any monitoring at exchange points to find the source?<br>
<br>
-- <br>
kind regards<br>
Marco<br>
Send unsolicited bulk mail to 1711396344muell@cartoonies.org<br>
<br>
-- <br>
<br>
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit:
<a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>