Additional Information

Introduction

We provide additional information concerning Mycelium and how to properly use it.

Connect to Other Nodes

If you want to connect to other nodes, you can specify their listening address as part of the command (combined with the protocol they are listening on, usually TCP);

mycelium --peers tcp://83.231.240.31:9651 quic://185.206.122.71:9651

If you are using other tun inferface, e.g. utun3 (default), you can set a different utun inferface

mycelium --peers tcp://83.231.240.31:9651 quic://185.206.122.71:9651 --tun-name utun9

Hosted Public Nodes

A couple of public nodes are provided, which can be freely connected to. This allows anyone to join the global network. These are hosted in 3 geographic regions, on both IPv4 and IPv6, and supporting both the Tcp and Quic protocols. The nodes are the following:

These nodes are all interconnected, so 2 peers who each connect to a different node (or set of disjoint nodes) will still be able to reach each other. For optimal performance, it is recommended to connect to all of the above at once however. An example connection string could be:

--peers tcp://188.40.132.242:9651 "tcp://[2a01:4f8:212:fa6::2]:9651" quic://185.69.166.7:9651 "tcp://[2a02:1802:5e:0:8c9e:7dff:fec9:f0d2]:9651" tcp://65.21.231.58:9651 "quic://[2a01:4f9:5a:1042::2]:9651"

It is up to the user to decide which peers he wants to use, over which protocol. Note that quotation may or may not be required, depending on which shell is being used.

Default Port

By default, the node will listen on port 9651, though this can be overwritten with the -p flag.

Check Network Information

You can check your Mycelium network information by running the following line:

mycelium inspect --json

Where a typical output would be:

{
  "publicKey": "abd16194646defe7ad2318a0f0a69eb2e3fe939c3b0b51cf0bb88bb8028ecd1d",
  "address": "3c4:c176:bf44:b2ab:5e7e:f6a:b7e2:11ca"
}

Test the Network

You can easily test that the network works by pinging to anyone in the network.

ping6 3c4:c176:bf44:b2ab:5e7e:f6a:b7e2:11ca

Key Pair

The node uses a x25519 key pair from which its identity is derived. The private key of this key pair is saved in a local file (32 bytes in binary format). You can specify the path to this file with the -k flag. By default, the file is saved in the current working directory as priv_key.bin.

Running without TUN interface

It is possible to run the system without creating a TUN interface, by starting with the --no-tun flag. Obviously, this means that your node won't be able to send or receive L3 traffic. There is no interface to send packets on, and consequently no interface to send received packets out of. From the point of other nodes, your node will simply drop all incoming L3 traffic destined for it. The node will still route traffic as normal. It takes part in routing, exchanges route info, and forwards packets not intended for itself.

The node also still allows access to the message subsystem.

API

The node starts an HTTP API, which by default listens on localhost:8989. A different listening address can be specified on the CLI when starting the system through the --api-server-addr flag. The API allows access to send and receive messages, and will later be expanded to allow admin functionality on the system. Note that message are sent using the identity of the node, and a future admin API can be used to change the system behavior. As such, care should be taken that this API is not accessible to unauthorized users.

Message System

A message system is provided which allows users to send a message, which is essentially just "some data" to a remote. Since the system is end-to-end encrypted, a receiver of a message is sure of the authenticity and confidentiality of the content. The system does not interpret the data in any way and handles it as an opaque block of bytes. Messages are sent with a deadline. This means the system continuously tries to send (part of) the message, until it either succeeds, or the deadline expires. This happens similar to the way TCP handles data. Messages are transmitted in chunks, which are embedded in the same data stream used by L3 packets. As such, intermediate nodes can't distinguish between regular L3 and message data.

The primary way to interact with the message system is through the API. The message API is documented in here. For some more info about how to use the message system, see the Message section.

Inspecting Node Keys

Using the inspect subcommand, you can view the address associated with a public key. If no public key is provided, the node will show its own public key. In either case, the derived address is also printed. You can specify the path to the private key with the -k flag. If the file does not exist, a new private key will be generated. The optional --json flag can be used to print the information in json format.

mycelium inspect a47c1d6f2a15b2c670d3a88fbe0aeb301ced12f7bcb4c8e3aa877b20f8559c02

Where the output could be something like this:

Public key: a47c1d6f2a15b2c670d3a88fbe0aeb301ced12f7bcb4c8e3aa877b20f8559c02
Address: 27f:b2c5:a944:4dad:9cb1:da4:8bf7:7e65

Troubleshooting

Root Access

You might need to run Mycelium as root. Some error messages could be something like: Error: NixError(EPERM).

Enable IPv6 at the OS Level

You need to enable IPv6 at the OS level. Some error messages could be something like: Permission denied (os error 13).

• Check if IPv66 is enabled
  • If disabled, output is 1, if enabled, output is 0

  sysctl net.ipv6.conf.all.disable_ipv6
  

• Enable IPv6

  sudo sysctl net.ipv6.conf.all.disable_ipv6=0
  

Here's some commands to troubleshoot IPv6:

sudo ip6tables -S INPUT
sudo ip6tables -S OUTPUT

VPN Can Block Mycelium

You might need to disconnect your VPN when using Mycelium.

Add Peers

It can help to connect to other peers. Check the Mycelium repository for peers.