Files
nym/service-providers/network-requester
Jędrzej Stuczyński a43d183b4f Feature/wasm client updates (#1673)
* Compiles but runtime time fails

* wip

* Beginning of clean-up - creation of config to keep things together

* Removed unused module

* Removed hardcoded constants

* Easier way of sending binary messages

* WIP cleanup before machine switch

* Upgrade wasm-bindgen to 0.2.83

* Fixed compilation warnings for wasm client

* all clients compiling without warnings

* disabling topology refresh in wasm

* Added a config option to disable loop cover traffic stream

* config changes

* Make webassembly work in a web worker
- `wasm-timer` modified to work in web worker
- add worker target to webpack
- add client to call from HTML
- update README to build WASM for bundling (this does not build ES modules)

* Restored topology refreshing

* correctly polling items in the wasm delay_queue

* Allow client to read up to 8 messages at once from gateway connection (#1669)

* Allow client to read up to 8 messages at once from gateway connection

* Importing tokio::select in wasm32 target

* Updated changelog

* missing imports

* Introduced disable_main_poisson_packet_distribution to force real_traffic_stream to disable poisson sending (#1664)

* Introduced disable_main_poisson_packet_distribution to force real_traffic_stream to disable poisson sending

* Updated changelog

* Adjusting default settings

* Introduced a client-configurable option to force it to use extended packet size

* local adjustments

* Removed warning associated with receiving extended packets

* Minimal v2-required changes

* Updated changelog

* explicitly allowing clippy drop_non_drop

Co-authored-by: Mark Sinclair <mmsinclair@gmail.com>
2022-10-10 16:27:51 +01:00
..
2022-09-22 17:26:37 +02:00
2022-10-10 16:27:51 +01:00
2022-06-09 16:58:51 +03:00

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.