This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[ipv6-wg] IPv6 torrent and non-GUA addresses

Previous message (by thread): [ipv6-wg] No more Google IPv6 stats?
Next message (by thread): [ipv6-wg] IPv6 torrent and non-GUA addresses

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Marco Moock mm at dorfdsl.de
Sat Apr 6 09:50:23 CEST 2024

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 at cartoonies.org

Previous message (by thread): [ipv6-wg] No more Google IPv6 stats?
Next message (by thread): [ipv6-wg] IPv6 torrent and non-GUA addresses

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]