Skip to content

Solve the mystery of ::84.209.139.0 #4

Description

@pastly

This relay somehow resulted in both ::84.209.139.0 and 84.209.139.0

https://metrics.torproject.org/rs.html#details/AC717A01B8E3C00E7617EF65117A4E99C02DC7A0

This script shows me the only way I can get the '::' prefix is by supplying it myself.

#!/usr/bin/env python3
import socket
def f(host: str):
    for ret in socket.getaddrinfo(host, None, proto=socket.IPPROTO_TCP):
        print(ret)

if __name__ == '__main__':
    f('cm-84.209.139.0.getinternet.no')
    print('---')
    f('84.209.139.0')
    print('---')
    f('::84.209.139.0')
$ python3 a.py
(<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('84.209.139.0', 0))
---
(<AddressFamily.AF_INET: 2>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('84.209.139.0', 0))
---
(<AddressFamily.AF_INET6: 10>, <SocketKind.SOCK_STREAM: 1>, 6, '', ('::84.209.139.0', 0, 0, 0))

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions