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] IPv6 torrent and non-GUA addresses
- Next message (by thread): [ipv6-wg] IPv6 WG agenda for RIPE88
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Moock
mm at dorfdsl.de
Sun Apr 14 19:54:24 CEST 2024
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 at cartoonies.org
- Previous message (by thread): [ipv6-wg] IPv6 torrent and non-GUA addresses
- Next message (by thread): [ipv6-wg] IPv6 WG agenda for RIPE88
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]