Jon Häggblad
d912844543
* WIP: QA network details * Initial implementation to multiplex socks5-client sends * Introduce TransmissionLane enum * WIP * WIP: client requests connection id * WIP * mulitplex somewhat done * Remove closed lanes * WIP: connection handling over ws * Remove unused published active connections shared data * Start on status timer * Max number of connections, and prune * Some tidy * Remove commented out code and tweak log * Tidy * Tweak log output * Rename to TransmissionBuffer * Use number of msg sent instead of time to rank age of lanes * Create client-connections crate * Remove waker call that probably are not needed * Extract out some types from real traffic stream module * Revert to develop qa.env * Tweak comments, tidy for getting ready to merge * Update changelog * wasm client compile fixes * rustfmt
Copyright 2022 - Nym Technologies SA contact@nymtech.net SPDX-License-Identifier: Apache-2.0 -->
Network requester
The network requester is used to interpret socks5 client messages that need to be proxied to a running service i.e. a host and a port.
If you have a service that you want to expose to the mixnet, you'd need to first run the native client and provide the client address to your users that will use it in their socks5 configuration.
After starting the native client, start the network requester and configure it,
setting your service's endpoint in
${HOME}/.nym/service-providers/network-requester/allowed.list
Running in open-proxy mode allows any traffic to be proxied by the network
requester.
Statistics service
The network requester can be ran as a gatherer of statistics for all
the services it proxies. For that, run the binary with the
enable-statistics flag enabled. Anonymized statistics are then sent to
a central server, through the mixnet.