You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This are targeting to Quality Assurance (QA) testing for our development, but will be helpful for you to prepare your machine to run from Command Line (CLI)
5
+
These guides target Quality Assurance (QA) testing for our development, but they also help you prepare a machine to run MASQ from the command line (CLI).
4
6
5
7
:::warning
6
8
7
9
Running MASQ from CLI **will** require technical knowledge and possibly adjustments to the network adaptor settings.
8
10
9
11
MASQ and the developers are not responsible for any issues that arise from user changes to their environment or machine!
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
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
Now we have the Binaries and we are ready to start using terminal
69
69
70
70
## Start the Commandline Interface (CLI)
71
71
72
72
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 open another terminal window **(do not close the daemon window)** in the same manner as before - here we will now start the `masq` interactive tool
97
97
@@ -100,13 +100,13 @@ Now open another terminal window **(do not close the daemon window)** in the sam
100
100
101
101
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)
A breakdown of what these are and how you configure them can be found [here](https://github.com/MASQ-Project/Node/blob/master/README.md#run-masq-node-locally)
112
112
@@ -130,13 +130,12 @@ In order to specify a ip type `setup --ip 1.2.3.4`and press enter
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.
77
77
@@ -82,7 +82,7 @@ We now have to navigate to the Masq folder you created earlier using this CLI. T
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).
Troubleshooting tips for issues that often block MASQ Node from starting or connecting — firewall rules, Port 53 conflicts, and Linux `--real-user` permissions.
When you try to start your MASQ Node, do you see a message that looks something like one of these?
6
5
```
7
6
thread 'main' panicked at 'Cannot bind socket to V4(0.0.0.0:53): Os { code: 10048, kind: AddrInUse, message: "Only one usage of each socket address (protocol/network address/port) is normally permitted." }'
@@ -16,34 +15,27 @@ If you see both of those parts in the message, then you are definitely afflicted
16
15
17
16
If you don't care about what the problem is or why it happens, and you just want to know how to fix it, skip down to the **Solutions** section.
Windows includes a service called Internet Connection Sharing (ICS) that listens on port 53. It's a somewhat dated service from the days before widespread WiFi availability that allows you to make your Windows machine a nexus through which other people can connect their machines to the Internet. If you're not already aware that you're doing this, you probably don't need to have ICS active.
24
21
25
-
### Linux <ahref="#linux"id="linux"></a>
26
-
22
+
### Linux \{#linux}
27
23
Some Linux distributions (we know about Ubuntu Desktop >=16.04 and some versions of Mint, but there are probably others) come with an installed utility called `dnsmasq`. This utility is intended to let folks with small home LANs give intelligible names to their computers, printers, TVs, DVRs, mobile devices, and other Internet-enabled devices, rather than having to reference them by numeric IP address. You may instead have a distribution (for example Ubuntu 18.04) that uses `systemd-resolved` for this purpose. We'll generically call this dns caching.
28
24
29
25
DNS caching works by putting up a small DNS server on your local machine that fields name-resolution requests for things like "LivingRoomTV" and returns IP addresses like 192.168.0.47. This means that when you want to control your TV from upstairs, or watch its video feed, or whatever it allows you to do remotely, you can call it "LivingRoomTV" (or select it from a list) rather than having to remember its IP address (which may change unexpectedly).
30
26
31
-
### In General <ahref="#in-general"id="in-general"></a>
32
-
27
+
### In General \{#in-general}
33
28
Any software that uses a DNS server to convert an intelligible name into an IP address will contact that DNS server on Port 53; it's part of the widely-accepted DNS protocol. Therefore, every DNS server must listen on Port 53 for requests if it expects to receive any.
34
29
35
30
Unfortunately, only one server can listen on Port 53 (or any port) at one time.
36
31
37
-
## The Problem <ahref="#the-problem"id="the-problem"></a>
38
-
32
+
## The Problem \{#the-problem}
39
33
MASQ Node also includes a small DNS server that allows applications on your computer to send and receive data on the MASQ Network. Since this is a DNS server, it must also listen on Port 53. This means that a DNS-subverting MASQ Node and preexisting port 53 software are irredeemably inimical to one another and cannot ever operate simultaneously on the same computer.
40
34
41
35
Eventually, MASQ Node will be able to operate in regimes other than DNS subversion, which means that under some circumstances, and in the presence of certain sacrifices, it will be compatible with other port 53 software; but that's in the future, not the present.
### Windows <ahref="#windows-1"id="windows-1"></a>
46
-
37
+
## Solutions \{#solutions}
38
+
### Windows \{#windows-1}
47
39
Internet Connection Sharing can be an annoyance. We had problems with it starting spontaneously after we stopped it, and reenabling itself and starting after we disabled it, and coming back into action over a reboot, in all cases monopolizing port 53 and preventing MASQ Node from starting. However, the solution turned out to be simple: we just installed all pending updates (in our case, they ended at version 1809), and the problem went away. We disabled ICS, and it stayed disabled.
48
40
49
41
ICS can be enabled and disabled for individual network interfaces, but you'll need to disable it across your entire system to free up port 53 for MASQ Node.
@@ -52,16 +44,13 @@ To do so, press your Windows button and type Services. Scroll down to where you
52
44
53
45
If it is, then right-click on the Internet Connection Sharing item and choose Properties. Pull down the "Startup type" list and choose "Disabled" so that it can't be restarted once it stops. Now click the "Stop" button to kill the service. You'll get a dialog box with a progress bar; the service should stop fairly quickly. After it does, click "OK" and verify that the service list now shows the service as "Disabled" in the "Startup Type" column, with no value at all in the "Status" column. If that's the case, you've successfully disabled ICS.
54
46
55
-
### Linux <ahref="#linux-1"id="linux-1"></a>
56
-
47
+
### Linux \{#linux-1}
57
48
We know of two reasonable solutions to the **Port 53 Problem** in Linux: a complicated and annoying one that allows you to keep using dns caching, and a much simpler and easier one that consists of disabling dns caching but will no longer allow you to use intelligible names for the devices on your LAN.
58
49
59
-
#### Complicated And Annoying: Docker <ahref="#complicated-and-annoying-docker"id="complicated-and-annoying-docker"></a>
60
-
50
+
#### Complicated And Annoying: Docker \{#complicated-and-annoying-docker}
61
51
This solution is too complex to detail here, but in broad strokes it involves running a Docker container that contains a version of Linux that does _not_ have the **Port 53 Problem**, starting the MASQ Node and a browser in that container, and having the browser display its window on the X11 server running on your host machine. We at MASQ have used this solution in the past, and you can see how we've done it by looking in our [source code](https://github.com/MASQ-Project/Node/tree/master/node/docker/linux_node). After installing Docker on your machine, you may be able to put together a similar solution.
62
52
63
-
#### Simple But Incompatible: Disable DNS Caching <ahref="#simple-but-incompatible-disable-dns-caching"id="simple-but-incompatible-disable-dns-caching"></a>
64
-
53
+
#### Simple But Incompatible: Disable DNS Caching \{#simple-but-incompatible-disable-dns-caching}
Copy file name to clipboardExpand all lines: docs/advanced-use/common-challenges/user-permissions-real-user.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# User permissions --real-user
1
+
# User permissions (`--real-user`)
2
2
3
-
## User permissions --real-user
3
+
## User permissions `--real-user`
4
4
5
5
The Node will refuse to run unless it can relinquish root privileges once it has opened its ports. Long-running root-privileged servers with network access are a serious security risk.
0 commit comments