MASQ CLI Testing - Windows
This guide will allow you to set up for testing MASQ development cards, using Command Line Interface (CLI) for Windows - written by the trusty Testing Manager Stew
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)
- Downloading latest stable Binaries from MASQ Node GitHub
- Extracting them to your local disk
- Start the Command Line Interface (CLI)
- Initialize the MASQDaemon
- Setting Configuration for MASQ Node
Create a new folder called Masq on your C drive:
Navigate to your
Right click the mouse, Scroll down to New then Folder and click it. Rename that folder
Download the latest Binaries for the MASQ Node software here:
Once you have clicked on a Binary you will see the Binaries for the 3 operating systems. We obviously want the Windows version, as we are using Windows in this guide.
Click on the Windows version and the download will begin.
Go to downloads and cut/paste the downloaded zip file into your recently created
You should now have this:
Right click the file, select Extract here and you will get the below:
These are the files you want for testing. Copy and paste into your
Masqfolder. You should see something like this:
Now we have the Binaries (MASQNode and masq) and we are ready to start using CLI.
To run MASQ Node from CLI you will need to use a command line console or terminal window with elevated privileges
Using the Windows search bar type:
On the right hand side, click 'Run as Administrator' and click Yes on the confirmation message that pops up. You should see this:
We now have to navigate to the Masq folder you created earlier using this CLI. These commands assume you have created the Masq folder in the same location as I did above. Creating that folder elsewhere will mean the below command may not work and you will have to navigate to the Masq folder in the location you created it.
- Press Enter
- Press Enter
CLI should now show you are in the right place:
The daemon service is currently the MASQNode binary file under the bin directory
In CLI type :
You may get a pop up window where your Antivirus scans the file, wait for that to finish
We now need to open another CLI window as we did before, but this time do not type anything yet.
You should now have 2 CLI open that look like this:
At this point, there is no need to touch the one that is running the Daemon
Ignore the first window (left) for now. Let's concentrate on the right hand side window. This CLI window is currently doing nothing but we have navigated to the Masq folder ready to look at how we set-up and start a Node.
In this CLI window type:
We are now in interactive mode which 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).
Press Enter You should see the below:
A breakdown of what these are and how you configure them can be found below:
The above link shows that there are several things you can configure along with the status of them.
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 screenshot of
setupshows a message:
neighborhood-mode Node cannot run as --neighborhood-mode standard without --ip specified
This is telling us to set a value for
ip. In the most basic way, we can supply a value which satisfies the requirements but does have to be your actual public ip address. Remember we are not setting up a fully functional Node, we are simply doing the basics to allow testing.
In order to specify an
setup --ip 188.8.131.52
You should see this:
This shows us the setup list again but now the STATUS alongside ip is
Setto 184.108.40.206 and the
ERRORSmessage has disappeared.
We can now start the Node by typing… Wait for it.
In Windows, you may see an admin prompt asking you to allow 'masqnode' process through Windows firewall. Allow that so the Node software can connect to the network
Press Enter If you have followed all the above correctly you should see something like this:
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:
If you have started your Node successfully you can use :
To consume over MASQ Network you need to do EITHER
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.
The cleanly shutdown node, in your Node terminal (not the Daemon terminal), type
shutdownin interactive mode, or
masq shutdownfrom 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.