Panlab: Brewing IDEAS

Hi Dr. Pan, it seems piconet fails to work on win10.
here is my experience testing piconet on win10:

1. Download VirtualBox and multipass from Official website on Internet.
   *note that it is better not to change installation directory for them in case of incompatibility issues, use the default directory instead.
2. Run piconet
   I used 'Git bash' to run linux subsystem on win10 to run piconet.

   Code: Select all

   cd ~/csc361-lab-setup-master

   Code: Select all

   ./piconet run

   However, it seems on win10, the time out problem still exists even if the uvic vpn is not used
   here is the error I got:
   ""
3. Creating piconet
   launch failed: The following errors occurred:
   piconet: timed out waiting for response
4. - Waiting for VM piconet to come up
   Error: Timed out waiting for VM to come up
   ""
   But, it can be seen from multipass that piconet instance is created:
   =====================================================
   Name State IPv4 Image
   mp1 Running N/A Ubuntu 18.04 LTS
   piconet Running N/A Ubuntu 18.04 LTS
   =========================================================

I am not sure if it is my problem that any configurations went wrong during the process.

jamesrxy wrote:

""

• Creating piconet
  launch failed: The following errors occurred:
  piconet: timed out waiting for response
• - Waiting for VM piconet to come up
  Error: Timed out waiting for VM to come up
  ""
  But, it can be seen from multipass that piconet instance is created:
  =====================================================
  Name State IPv4 Image
  mp1 Running N/A Ubuntu 18.04 LTS
  piconet Running N/A Ubuntu 18.04 LTS
  =========================================================

I am not sure if it is my problem that any configurations went wrong during the process.

can you access the running piconet by

$ multipass shell piconet

? normally, it shall show the ipv4 address associated with each running vm instance, e.g.,

$ multipass list
Name                    State             IPv4             Image
piconet                 Running           192.168.64.2     Ubuntu 18.04 LTS

and after you multipass shell accessed piconet,

ubuntu@piconet:~$ ip netns 
r (id: 2)
h2 (id: 1)
h1 (id: 0)

shall show the three (child) namespaces inside piconet, i.e., h1 (client host), r (router) and h2 (server host) for our virtual csc361 lab setup

for windows tester: if you cannot get the piconet script to configure the vm automatically, just copy the files in bin, etc and lib inside the installation package to /usr/local/bin (set the script executable with "chmod a+x"), /usr/local/etc and /usr/local/lib, respectively, inside the vm, and copy the files in systemd/system in the installation package to /etc/systemd/system inside the vm, and then enable

/usr/bin/sudo /bin/systemctl enable ttyd.service
/usr/bin/sudo /bin/systemctl enable piconet.service
/usr/bin/sudo /bin/systemctl daemon-reload

and lunch

/usr/bin/sudo /bin/systemctl start piconet
/usr/bin/sudo /bin/systemctl start ttyd

on your local computer, open html/ui.html with your chrome, and you shall see the 4-pane interface

the new piconet in a container (instead of vm) with jupyterlab user interface, hosted in the "cloud" with gitlab integration, a step closer to the real deployment for the fall

persistent

vs non-persistent http connection

recursive (r-eth0) vs iterative (r-eth2) dns query

tcp connection establishment (3-way handshake)

and release (4-way handshake)

and flow control (the opening and closing of the flow-control window)

tcp error control: packet loss

and retransmission by dupack

vs loss

and retransmissions by timeout

tcp congestion control (reno, initcwnd=1, sack=0): packet loss and retransmission by timeout

and the increase of congestion window during congestion avoidance

and the inflation of congestion window during duplicate acknowledgment and eventual retransmission by triple dupack

and new loss during recovery

and

and bursty losses

before

vs after

nat

pan wrote:

persistent

Screen Shot 2020-08-28 at 2.36.45 PM.png

vs non-persistent http connection

Screen Shot 2020-08-28 at 2.38.24 PM.png

Hi Dr.Pan, I see the commands used in your screenshots and that in the manual are different for Lab3. Which one I should follow? Do I need to modify the commands in the manual?

liuuvic wrote:

pan wrote:

persistent

Screen Shot 2020-08-28 at 2.36.45 PM.png

vs non-persistent http connection

Screen Shot 2020-08-28 at 2.38.24 PM.png

Hi Dr.Pan, I see the commands used in your screenshots and that in the manual are different for Lab3. Which one I should follow? Do I need to modify the commands in the manual?

Also, if I start nginx on terminal 4 and run

root@r piconet> wget -e robots=off --no-http-keep-alive -r 172.16.1.2:80

I get:

http://172.16.1.2/
Connecting to 172.16.1.2:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 612 [text/html]
Saving to: ‘172.16.1.2/index.html’

172.16.1.2/inde 100%[====>] 612 --.-KB/s in 0s

2020-08-30 10:49:34 (30.4 MB/s) - ‘172.16.1.2/index.html’ saved [612/612]

FINISHED --2020-08-30 10:49:34--
Total wall clock time: 0.003s
Downloaded: 1 files, 612 in 0s (30.4 MB/s)

The only file downloaded is the index.html, which can be found in the left of the window.

liuuvic wrote:

pan wrote:

persistent vs non-persistent http connection

Hi Dr.Pan, I see the commands used in your screenshots and that in the manual are different for Lab3. Which one I should follow? Do I need to modify the commands in the manual?

either one is fine. they are for the same purposes

liuuvic wrote:

Also, if I start nginx on terminal 4 and run root@r piconet> wget -e robots=off --no-http-keep-alive -r 172.16.1.2:80 I get: http://172.16.1.2/Connecting to 172.16.1.2:80... connected. HTTP request sent, awaiting response... 200 OK Length: 612 [text/html] Saving to: ‘172.16.1.2/index.html’ 172.16.1.2/inde 100%[====>] 612 --.-KB/s in 0s 2020-08-30 10:49:34 (30.4 MB/s) - ‘172.16.1.2/index.html’ saved [612/612] FINISHED --2020-08-30 10:49:34-- Total wall clock time: 0.003s Downloaded: 1 files, 612 in 0s (30.4 MB/s) The only file downloaded is the index.html, which can be found in the left of the window.

that's because your html directory where your nginx serves only has a placeholder index.html. you can use the sample html files in http://panlab.cs.uvic.ca/web3/download/ ... p?id=34494 and put them in the document directory where nginx serves incoming http requests (often /var/www/html)

static routing for piconet (h1-r-h2) in the new docker container with the new jupyterlab interface

interworking within a network

and between

so piconet works well for all 10 lab modules inside the docker container too