Frequently Asked Questions

NymVPN Support & FAQ page (opens in a new tab) contains all essential FAQs regarding the client. This page (below) is a source of additional information often seeked by users, operators and developers testing NymVPN.

If you interested to read more about Nym platform, you can have a look at Nym general FAQ (opens in a new tab) and read through Nym's technical documentation (opens in a new tab), Developer Portal (opens in a new tab) and Operators Guide (opens in a new tab).

NymVPN

If this your first time hearing about NymVPN, make sure you visit NymVPN webpage (opens in a new tab), the official NymVPN support & FAQ page (opens in a new tab) and the proceed to the introduction and guide on how to install, run and test the client.

Below are some extra FAQs which came out during the previous alpha testing rounds.

What's the difference between 2-hops and 5-hops

The default is 5-hops (including Entry and Exit Gateways), which means that the traffic goes from the local client to Entry Gateway -> through 3 layers of Mix Nodes -> to Exit Gateway -> internet. this option uses all the Nym Mixnet features for maximum privacy.

                      ┌─►mix──┐  mix     mix
                      │       │
            Entry     │       │                   Exit
client ───► Gateway ──┘  mix  │  mix  ┌─►mix ───► Gateway ───► internet
                              │       │
                              │       │
                         mix  └─►mix──┘  mix

The 2-hop option is going from the local client -> Entry Gateway -> directly to Exit Gateway -> internet. This option is good for operations demanding faster connection. Keep in mind that this setup by-passes the 3 layers of Mix Nodes. The anonymising features done by your local client like breaking data into same-size packets with inserting additional "dummy" ones to break the time and volume patterns is done in both options.

            Entry         Exit
client ───► Gateway ────► Gateway ───► internet

We highly recommend to read more about Nym network overview (opens in a new tab) and the Mixnet traffic flow (opens in a new tab).

Why do I see different sizes of packets in my terminal log?

One of features of Nym Mixnet's clients is to break data into the same size packets called Sphinx, which is currently ~2kb. When running NymVPN, the data log shows payload sizes, which are the raw sizes of the IP packets, not Sphinx. The payload sizes will be capped by the configured MTU, which is set around 1500 bytes.

What is 'poisson filter' about?

By default --enable-poisson is disabled and packets are sent from the local client to the Entry Gateway as quickly as possible. With the poisson process enabled the Nym client will send packets at a steady stream to the Entry Gateway. By default it's on average one sphinx packet per 20ms, but there is some randomness (poisson distribution). When there are no real data to fill the sphinx packets with, cover packets are generated instead.

Enabling the poisson filter is one of the key mechanisms to de-correlate input and output traffic to the Mixnet. The performance impact however is dramatic: 1 packer per 20ms is 50 packets / sec so ballpark 100kb/s. For mobile clients that means constantly sending data eating up data allowance.

Nym Mixnet Architecture and Rewards

We have a list of questions related to Nym Nodes and the incentives behind running them under FAQ pages (opens in a new tab) in our Operators Guide (opens in a new tab). For better knowledge about Nym architecture we recommend to read Nym network overview (opens in a new tab) and the Mixnet traffic flow (opens in a new tab) in our technical documentation (opens in a new tab).

Project Smoosh

Project Smoosh is a code name for a process in which different components of Nym Mixnet architecture get smooshed into one binary. Check out Smoosh FAQ (opens in a new tab) in Operators Guide to read more.

Exit Gateway

Part of the the transition under code name Project Smoosh is a creation of Nym Exit Gateway (opens in a new tab) functionality. The operators running Gateways would have to “open” their nodes to a wider range of online services, in a similar fashion to Tor exit relays. The main change will be to expand the original short allowed.list (opens in a new tab) to a more permissive setup. An exit policy (opens in a new tab) will constrain the hosts that the users of the Nym VPN and Mixnet can connect to. This will be done in an effort to protect the operators, as Gateways will act both as SOCKS5 Network Requesters, and exit nodes for IP traffic from Nym VPN and Mixnet clients.

Read more how the exit policy gets implemented here (opens in a new tab)
Check out Nym Operators Legal Forum (opens in a new tab)
Do reach out to us with any experiences you may have running Tor Exit relays or legal findings and suggestions for Nym Exit Gateway operators

Nym Integrations and SDKs

If you are a dev who is interested to integrate Nym, have a look on our SDK tutorials:

CLI Mac Gui