Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Solve the mystery of ::84.209.139.0 #4

Open
pastly opened this issue Jul 30, 2021 · 1 comment
Open

Solve the mystery of ::84.209.139.0 #4

pastly opened this issue Jul 30, 2021 · 1 comment

Comments

@pastly
Copy link
Collaborator

pastly commented Jul 30, 2021

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))
@pastly
Copy link
Collaborator Author

pastly commented Aug 1, 2021

I did a clean full scan of the real Tor network and this didn't happen >:(

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant