Market of entry points to the TON network.
tongate client allows to find tongate servers by looking up members of 'ProxyOffers' overlay network in TON DHT.
Once such server is found client establishes encrypted connection to that server, starts local SOCKS5 proxy and pass
traffic to that server. When destination is ordinary domain or ip address server acts as a proxy.
When destination is a domain name with .ton TLD then server will transaparenty resolve it to the ADNL address, and then to IP adress using DHT.
- Overlay network to discover tongate servers
- Encrypted communications betwen client and server (kind of ADNL-over-TCP, works when client is behind NAT)
- SOCKS5 (work-in-progress)
- Tun interface (work-in-progress)
-
*.tondomain resolution - Payment channel between client and server
- Local http server in client with stats and payment QR-code generator
- Tray gui for starting/stopping client
To build run following commands:
> git clone --recursive https://github.com/kelvich/tongate
> cd tongate && mkdir build && cd build
> cmake ../
> make -j 6After that build directory will contain client and tongate binaries.
> ./tongate -D dbs C ton-global.config.json -a IP:PORT -s -v 2Where IP:PORT is advertised adress of that server and should be externally accessible.
To find a node to connect run following:
> ./tongate -D dbs_discovery C ton-global.config.json -a IP:PORT -v 2 -LWhere IP:PORT should be externally accessible. If you are behind the NAT you may find out your external address and set port to some random number. Usually NAT preserves senders UDP port (if it was not already occupied) and you will be able to get DHT responses back. It usually takes about a minute to gather all overlay participants while rinnung discovery behind NAT.
To connect to the selected server run:
> ./client -c SERVER_IP:PORT -p SERVER_PUBKEY -v 2That will also start local SOCKS5 server on port 5555 (which is not yet working, but just emits some stuff in log when somebody connects to it).