Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upRouting Between VMs (Skywire) #3886
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
0pcom
referenced this issue
in skycoin/skywire
May 7, 2018
Closed
VM implementation of Skywire with QubesOS #53
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
0pcom
commented
May 7, 2018
|
Thank you marmarek I will try that |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
0pcom
commented
May 7, 2018
|
works |
0pcom
closed this
May 7, 2018
andrewdavidwong
added
the
resolved
label
May 8, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
0pcom commentedMay 7, 2018
•
edited
Edited 1 time
-
0pcom
edited May 7, 2018 (most recent)
Qubes OS version:
4.0
Affected component(s):
networking / routing between VMs
Steps to reproduce the behavior:
I am attempting to replicate the skywire apparatus setup using QubesOS.
Create and name a VM
Install Dependencies if needed:
curl git mercurial make binutils gcc bison screen bashInstall GO from source
3.1) Setup $GOPATH variable by appending the following to
.bashrc3.2) append the following to
/etc/profile3.3)
source ~/.bashrcGo to '127.0.0.1:8000' with a web browser and verify that the node appears (may take a minute to show up)
REPEAT STEPS 1-4
Launch the node and tell it to connect to the IP address of the other VM
127.0.0.1:8000with a web browser in the first VM to see if the second node appearsExpected behavior:
Nodes running in other VMs are able to connect to the manager
Actual behavior:
General notes:
Even if the manager VM is set as the netVM of the node VMs this does not work, which is weird because the node VM connects to the internet through the manager VM(!)
Other Anomalies:
Time can be saved if you clone the system AFTER you have set up GO and downloaded skywire BUT BEFORE installing or running skywire (avoids multiple nodes with the same key)
When I clone the VM at that point, the configuration sometimes does and sometimes does not appear in the clone.
Also, it seems that when I delete a VM and create another one with the same name there are sometimes remnants of the old VM terminal history in the newly created VM.