aboutsummaryrefslogtreecommitdiff
path: root/netsec-assignment4-S4498062/exercise3/exercise3b
diff options
context:
space:
mode:
authorCamil Staps2015-10-02 15:02:11 +0200
committerCamil Staps2015-10-02 15:03:07 +0200
commiteb0a29adaab70381867f91085ebe0ba2cc2928d7 (patch)
tree2cffecfec1aa08a91cf8ca231104c439c9d6cb80 /netsec-assignment4-S4498062/exercise3/exercise3b
parentStart exercise 4 (diff)
Finish assignment 4
Diffstat (limited to 'netsec-assignment4-S4498062/exercise3/exercise3b')
-rw-r--r--netsec-assignment4-S4498062/exercise3/exercise3b7
1 files changed, 7 insertions, 0 deletions
diff --git a/netsec-assignment4-S4498062/exercise3/exercise3b b/netsec-assignment4-S4498062/exercise3/exercise3b
new file mode 100644
index 0000000..82f0f3c
--- /dev/null
+++ b/netsec-assignment4-S4498062/exercise3/exercise3b
@@ -0,0 +1,7 @@
+Internal (NAT) traffic is not meant to be VPNed. IP addresses like 10.*.*.*
+(route 4), 172.0x1*.*.* (route 5) and 192.168.*.* (route 6) can be find by your
+machine, but (usually) not by the VPN, that's why they need to be excluded and
+handled by wlp3s0. These are standard numbers, so the VPN knows about it.
+The same goes for route 9. In the DHCP dump we can see that 145.116.128.0/22 all
+belongs to a small network, and if we'd attempt to VPN this, we cannot reach the
+gateway or any other machine in our local network any more.