Updates to the notes, readme's + videos

Author: kristenjacobs

1-network-namespace/README.md

@@ -15,7 +15,6 @@ SSH to the VM and run the setup script to create the network namespace and the v
 
 ```
 vagrant ssh
-cd /vagrant
 ./setup.sh
 ```
 
@@ -49,3 +48,9 @@ To teardown the network:
 ```
 ./teardown.sh
 ```
+
+To test the entire flow, i.e. setup - run the tests - teardown, from your machine, run the following:
+
+```
+make
+```

2-single-node/README.md

@@ -30,3 +30,9 @@ To teardown the network:
 ```
 ./teardown.sh
 ```
+
+To test the entire flow, i.e. setup - run the tests - teardown, from your machine, run the following:
+
+```
+make
+```

3-multi-node/README.md

@@ -31,3 +31,9 @@ To teardown the network:
 ```
 ./teardown.sh
 ```
+
+To test the entire flow, i.e. setup - run the tests - teardown, from your machine, run the following:
+
+```
+make
+```

4-overlay-network/README.md

@@ -31,3 +31,9 @@ To teardown the network:
 ```
 ./teardown.sh
 ```
+
+To test the entire flow, i.e. setup - run the tests - teardown, from your machine, run the following:
+
+```
+make
+```

README.md

@@ -10,6 +10,10 @@ Examples of creating a network of linux containers (network namespaces).
 
 [4 - Overlay Network](4-overlay-network/README.md)
 
+## Talks 
+
+* 2018-06 - Bristol Cloud Native: https://www.youtube.com/watch?v=mICllKv8JM4&t=1712s 
+
 ## References
 
 https://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/

slides/Notes.md

@@ -83,13 +83,11 @@ this.
 
 ```
 ./setup.sh
-# The interfaces inside the network namespace
+# The interfaces + routes inside the network namespace
 sudo ip netns exec con ip a
-# The routes inside the network namespace
 sudo ip netns exec con ip r
-# The interfaces on the node
+# The interfaces + routes on the node
 ip a
-# The routes on the node
 ip r
 # Pings the network namespace from the node
 ping 176.16.0.1
@@ -139,15 +137,13 @@ Note: you can run multiple processes inside a network namespace, which roughly c
 
 ```
 ./setup.sh
-# The interfaces inside a network namespace
+# The interfaces + routes inside a network namespace
 sudo ip netns exec con1 ip a
-# The routes inside a network namespace
 sudo ip netns exec con1 ip r
-# The interfaces on the node
+# The interfaces + routes on the node
 ip a
-# The routes on the node
 ip r
-# Ping between the network namespaces
+# Pings between the network namespaces
 sudo ip netns exec con1 ping 172.16.0.3
 # Pings the node from the network namespace
 sudo ip netns exec con1 ping 10.0.0.10
@@ -185,22 +181,23 @@ On each node, run:
 
 ```
 ./setup.sh
+# The routes on the node
+ip r
+```
+
+From 10.0.0.20:
+
+```
+# Captures ICMP packetes on the veth20 interface connected to the bridge
+sudo tcpdump -ni veth10 icmp
 ```
 
 Then from 10.0.0.10:
 
 ```
-# The interfaces inside a network namespace
-sudo ip netns exec con1 ip a
-# The routes inside a network namespace
-sudo ip netns exec con1 ip r
-# The interfaces on the node
-ip a
-# The routes on the node
-ip r
-# Ping from a network namespaces on one node to one on the other node
+# Pings from a network namespaces on one node to one on the other node
 sudo ip netns exec con1 ping 172.16.1.2
-# Pings from a node to a network namespace on the other node
+# Pings the same network namespace from the node
 ping 172.16.1.2
 ```
 
@@ -260,12 +257,19 @@ On each node, run:
 ./setup.sh
 ```
 
-Then from 10.0.0.10:
+From 10.0.0.20:
+
+```
+# Captures ICMP packetes on the veth20 interface connected to the bridge
+sudo tcpdump -ni veth10 icmp
+```
+
+From 10.0.0.10:
 
 ```
 # Ping from a network namespaces on one node to one on the other node
 sudo ip netns exec con1 ping 172.16.1.2
-# Pings from a node to a network namespace on the other node
+# Pings the same network namespace from the node
 ping 172.16.1.2
 ```
 
@@ -279,7 +283,7 @@ To see the encapsulation process more clearly:
 On node 10.0.0.10:
 
 ```
-# Pings from a local network namespace to a remote network namespace"
+# Pings from a local network namespace to a remote network namespace
 ./send.sh
 ```