MASQ CLI Testing - Linux

Getting started on Ubuntu

Command Line Interface testing is where we test the basic functionality and changes made by the developers. It can be a tricky and fiddly thing to master, it takes no prisoners for errors or mistyping and can be frustrating. Like anything, it takes patience and practice. Do not be put off by it, just keep at it and reach out to testers in Discord if you have issues. I have laid this document out as I do things. You may decide I do things in a stupid way or maybe I missed something. I’ve been doing this a while but I will endeavour to start it from the beginning to get you to a point where you can at least start the node (not fully functional) for testing purposes.
If you have previously tested MASQ Node you need to DELETE ALL OLD NODE DATABASE FILES BEFORE you start again (node-data.db)

Steps Outlined in this Guide

    Downloading latest stable Binaries from GitHub Actions
    Extracting them to your local disk
    Start the Command Line Interface (CLI)
    Initialize the MASQDaemon
    Setting Configuration for MASQ Node
    Starting masq Node Process

Setting Up MASQ Binaries

Open the file manager and create a new folder named Masq in your home directory
Download the Binaries for the Masq software:
Actions · MASQ-Project/Node
GitHub
Binaries are different versions of the software that change each time a new feature or fix is added. The simplest way to get started it to pick a set of Binaries which show a green tick like this
As of 17 Sep 2021, that last stable build in Actions can be found here:
Once you have clicked on a Binary you will see the Binaries for the 3 operating systems
We are using Ubuntu in this guide.
Click on the Ubuntu version and the download will begin.
Go to downloads and copy and paste the downloaded zip file into your previously created Masq folder. You should now have this
    1.
    Right click the file and select extract here and you will get a folder named Build results ubuntu-latest go in the folder then generated and then bin and you will see this
These are the files you want for testing. Copy them and paste into your Masq folder.
You should see something like this
Now we have the Binaries and we are ready to start using terminal

Start the Commandline Interface (CLI)

Now right click anywhere in the folder to open the drop down box in there choose Open in terminal or alternatively you can press Ctrl + Alt + T to open the terminal.
We are now in the terminal, it should show that we are in the masq folder, if you are not in the masq folder type cd Masq and it should bring you right into the Masq folder
Now it's time to start the MASQ Daemon (MASQNode):
    Type: chmod +x MASQNode to make the file executable so we can execute it
    Execute the file by typing sudo ./MASQNode --initialization to start the daemon
    It may ask for your password, enter it to confirm
You should see this:
Now open another terminal window (do not close the daemon window) in the same manner as before - here we will now start the MASQ Node now
    First make the file executable by typing chmod +x masq
    Execute the file by typing sudo ./masq
    It may ask for your password, enter it to confirm
We are now in interactive mode which shows a blinking curser after masq> and this makes your life easier (you can stay in standard mode but that requires a few more commands and you will get to know this as you test)
Now type: setup and press enter
You are now in the setup mode where you can configure the nodes many settings
A breakdown of what these are and how you configure them can be found here
The above link shows there are several things you can configure. This guide will not be going through each one but will give you the easiest way to get CLI up and running and start a Node for testing with the minimum information required.
The above screenshot shows the following message:
1
ERRORS:
2
neighborhood-mode Node cannot run as --neighborhood-mode standard without --ip specified
Copied!
This is telling us to set a value for ip which in the most basic way can be supplied a value that satisfies the requirements, but does have to be your actual ip address for testing. Remember we are not setting up a fully functional Node, we are simply doing the basics to allow testing.
In order to specify a ip type setup --ip 1.2.3.4and press enter
You should see this:
This shows us the setup list again but now the STATUS alongside ip is Set to 1.2.3.4 and the ERRORS message has disappeared.‌

Starting masq Node Process

We can now start the Node by typing… Wait for it. start
1.2.3.4 is not your real IP - you can find your real IP with the help of websites like https://whatismyipaddress.com/
If you have followed the guide correctly you should see something like this in the terminal window
You should also see some action on the Daemon CLI screen which we opened, started and then left alone.
Congratulations you have taken the first step to testing on CLI! There is much more to learn about parameters which can be found on the link provided earlier. If you would like to look around and make yourself familiar with things you can use the help commands which are available on 2 places as some things can only be done at certain stages: If you have not yet started the Node using start, you can use: setup --help
If you have started your Node successfully you can use : help

Subverting DNS

To consume over MASQ Network you need to subvert your DNS to 127.0.0.1 or proxy your browser to 127.0.0.1:80 and 127.0.0.1:443 (this is for HTTP and HTTPS traffic)
To subvert your DNS, find your network adaptor settings (usually its in the system settings of your machine) and change your DNS from 'Automatic' to manually use 127.0.0.1
If you can disable IPv6 as an option is recommended to do this as well.

Shutting down Node and Reverting DNS

The cleanly shutdown node, in your Node terminal (not the Daemon terminal), type shutdown in interactive mode, or masq shutdown from a terminal if you aren't in interactive mode.
Ensure that you revert your environment DNS back to Automatic or your default settings before you subverted them, or you will not regain connection to the internet.
Last modified 26d ago