Skip to content
This repository was archived by the owner on Feb 17, 2023. It is now read-only.
This repository was archived by the owner on Feb 17, 2023. It is now read-only.

Automate pool submission #9

Description

@darkk

Email me ... with public IP address of your server ... to our community-supported pool

I suggest to automate submission of IP addresses to the pool to reduce manual labor. Here are some possible issues to think about:

  • docker container may be behind NAT even with --net=host when it's run at, for example, end-user's SOHO network. Any of IP address discovery methods may be used to overcome that: TXT o-o.myaddr.l.google.com, A whoami.akamai.net, opendns, ripe, yandex and so on.
  • in case of SOHO network uPNP may be used to get public IP as well (and do port forwarding on behalf of user)
  • submission endpoint should, probably, be protected: e.g. it may be Onion Service in Tor network, RPC-over-DNS, or just plain good Qrator/Cloudflare if collateral freedom is not important :)
  • proxies should, probably, be auto-checked from temporary network endpoints for same protection reasons: to avoid DDoS and blackholing of the checker IP address
  • all pool proxies should have same user/pass for DNS-based pool to work, AFAIK telegram can't do better discovery & balancing at the moment :-(

OTOH, I'm looking at all those issues and I'm not sure if "userbase" of the docker image is large enough, so I would not be surprised if the issue will be closed with WONTFIX resolution :-)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions