DangerZone Network - Revision history

Takaji at 17:30, 4 October 2017

2017-10-04T17:30:47Z

Takaji at 15:53, 4 October 2017

2017-10-04T15:53:45Z

Xorrbit: /* Overview */ Added much needed context.

2013-05-28T21:32:13Z

‎Overview: Added much needed context.

Mogigoma: /* Subnets */

2013-05-24T00:49:19Z

‎Subnets

Mogigoma at 00:29, 24 May 2013

2013-05-24T00:29:56Z

Mogigoma: /* Adapters */

2013-05-24T00:28:34Z

‎Adapters

Mogigoma: /* Subnets */

2013-05-24T00:26:53Z

‎Subnets

Mogigoma: /* Subnets */

2013-05-24T00:25:18Z

‎Subnets

Mogigoma at 00:19, 24 May 2013

2013-05-24T00:19:33Z

Mogigoma: /* VMs */

2013-05-22T23:25:58Z

‎VMs

← Older revision		Revision as of 17:30, 4 October 2017
Line 1:		Line 1:
		+	{{Archived}}
	[[Category:Networking]]		[[Category:Networking]]

← Older revision		Revision as of 15:53, 4 October 2017
Line 1:		Line 1:
		+	[[Category:Networking]]
		+
	=Overview=		=Overview=

@@ Line 1: / Line 1: @@
 =Overview=
-This article explains the layout of the networks in the DangerZone from the perspective of the gateway.
+This article explains the layout of the networks in the [http://en.wikipedia.org/wiki/Danger_Zone_%28song%29 DangerZone] from the perspective of the gateway.
 Wifi

@@ Line 64: / Line 64: @@
 | VMs
 | 10.224.0.0 - 10.255.255.255
-| 255.244.0.0
+| 255.224.0.0
 | 2,097,150
 |-
 | VPN
 | 10.192.0.0 - 10.223.255.255
-| 255.244.0.0
+| 255.224.0.0
 | 2,097,150
 |-
 | Wifi
 | 10.0.0.0 - 10.31.255.255
-| 255.244.0.0
+| 255.224.0.0
 | 2,097,150
 |-

@@ Line 27: / Line 27: @@
 ==VMs==
-The VMs exist in the <tt>10.255.0.0/16</tt> subnet, with <tt>10.255.0.1</tt> assigned to the <tt>eth-vms</tt> adapter. All IP addresses in this range are statically assigned. This range was chosen because it is the least likely to conflict with a user's home network or other VPN that they are using.
+The VMs exist in the <tt>10.224.0.0/11</tt> subnet, with <tt>10.224.0.1</tt> assigned to the <tt>eth-vms</tt> adapter. All IP addresses in this range are statically assigned. This range was chosen because it is the least likely to conflict with a user's home network or other VPN that they are using.
 VMs are permitted to receive connections on a case-by-case basis, as determined by the author of the challenge the VM is running. By default, all incoming connections to the VM network from the VPN and Wifi networks are blocked.
@@ Line 37: / Line 37: @@
 ==VPN==
-When a user wishes to access the DangerZone from the Internet, the web interface must be used to generate an OpenVPN certificate. VPN users are statically assigned addresses in the <tt>10.1.0.0/16</tt> range. The adapter <tt>tun0</tt> has been assigned the IP <tt>10.1.0.1</tt>.
+When a user wishes to access the DangerZone from the Internet, the web interface must be used to generate an OpenVPN certificate. VPN users are statically assigned addresses in the <tt>10.192.0.0/11</tt> range. The adapter <tt>tun0</tt> has been assigned the IP <tt>10.192.0.1</tt>.
 The VPN network is never permitted to access anything other than the Gateway's VPN adapter and the VM network. Said another way, the VPN network may never talk to the Internet or the Wifi network.
@@ Line 47: / Line 47: @@
 ==Wifi==
-When a user accesses the Wifi network, they will get an dynamically-assigned IP from a DHCP server in the <tt>10.0.0.0/16</tt> subnet which should be good for a week. The gateway's <tt>eth-wifi</tt> adapter is connected to this network, in fact it has a direct connection to the access point, and is assigned the IP <tt>10.0.0.1</tt>. This address range was assigned to the Wifi network because it is the most likely to conflict with a user's home network, and when they're at SkullSpace we know it's not going to conflict.
+When a user accesses the Wifi network, they will get an dynamically-assigned IP from a DHCP server in the <tt>10.0.0.0/11</tt> subnet which should be good for a week. The gateway's <tt>eth-wifi</tt> adapter is connected to this network, in fact it has a direct connection to the access point, and is assigned the IP <tt>10.0.0.1</tt>. This address range was assigned to the Wifi network because it is the most likely to conflict with a user's home network, and when they're at SkullSpace we know it's not going to conflict.
 Users connected over to the Wifi network will be at our physically at (or outside) our hackespace, and likely not connected over ethernet. This means that we need to give them access to the Internet, because they won't have another way to get to it. Users on the Wifi network should have unrestricted access to the Internet, just like if they were our non-DangerZone wifi.

@@ Line 92: / Line 92: @@
 |-
 | eth-vms
-| 10.255.0.1/16
+| 10.224.0.1
 |-
 | eth-wifi
-| 10.0.0.1/16
+| 10.0.0.1
 | HTTPS
 |-
 | tun0
-| 10.1.0.1/16
+| 10.192.0.1
 | HTTPS
 |-

@@ Line 52: / Line 52: @@
 This network never accepts incoming connections.
 =Adapters=
 {| border="1px"