Jędrzej Stuczyński
f328f3fa9e
* Squashing all the changes initial router started expanding the API initial empty openapi/swagger populated build-info endpoint wip: populating rest of swagger missing swagger data + using closure capture for immutable state running the api as a proper task in gateway 'run' fixing some version/feature clashes refactored routes structures initial host information endpoint expanded on gateway-related endpoints signing host information moved all models to separate crate unified http api client routes unification + node api client new generic cache and refresher nym-api caching node self described information removed old cache type temporarily wired up NymContractCache to NodeDescriptionProvider caching self reported host info clients using self-described gateway information fixed request timeouts for wasm fixed wasm builds post rebase fixes cargo fmt brought in wg routes into nym-node router added ErrorResponse for wireguard routes basic swagger support for wg endpoints turns out swagger can be happy with strongly typed requests output type support for wg routes using concrete error type for nym node request error fixed the registration test landing page configurability increased configurability fixed build and lints of other crates added default user-agent to http-api-client reduced severity of gateway details lookup failure changed default http port from 80 to 8080 nym-api using new default port for queries added health endpoint nym-api trying multiple ports for the client using camelcase for node status corrected health endpoint description restored and revamped 'force_tls' flag to filter all gateways that support the wss protocol fixed 'pub_key' path param in open api schema derived Debug on 'NymNodeDescription' ensuring valid public ips added init and run flags to set hostname and public ips fixed listening address being pushed to public ip fixed the positional local flag logging remote ip address of the request updated helper function to query for described gateways enabled tls in gateway client removed hack-opts from mix fetch additional changes after rebasing against origin/develop * clippy * wasm-related target locking * more clippy, but this time in tests
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.