Difference between revisions of "Warzone:IPRanges"

From CCCHHWiki
Jump to: navigation, search
(ip ranges: - updated to 10.160.0.0/14)
Line 25: Line 25:
 
! VPN IP for test pings
 
! VPN IP for test pings
 
|- bgcolor="#efefef"
 
|- bgcolor="#efefef"
| 10.104.0.0/14
+
| 10.160.0.0/14
 
| warzone range
 
| warzone range
 
| warzone range  
 
| warzone range  
Line 31: Line 31:
 
|
 
|
 
|- bgcolor="#f8f8f8"
 
|- bgcolor="#f8f8f8"
| 10.104.0.0/23
+
| 10.160.0.0/23
 
| *reserved*
 
| *reserved*
| single hosts
+
| orga network, single hosts approved by the orga.
 
| This range may be used for Single-IP-VPN nodes like servers which would participate directly but do not need a subnet. Normally you would use a /24.
 
| This range may be used for Single-IP-VPN nodes like servers which would participate directly but do not need a subnet. Normally you would use a /24.
 
|
 
|
 
|-
 
|-
| 10.104.0.1/32
+
| 10.160.0.1/32
 
| aurora
 
| aurora
 
| haegar laptop
 
| haegar laptop
 
|
 
|
| 10.104.0.1
+
| 10.160.0.1
 
|- bgcolor="#f8f8f8"
 
|- bgcolor="#f8f8f8"
| 10.104.2.0/23
+
| 10.160.2.0/23
 
| *reserved*
 
| *reserved*
 
| subnets
 
| subnets
Line 49: Line 49:
 
|
 
|
 
|-
 
|-
| 10.104.2.0/28
+
| 10.160.2.0/28
 
| vpnhub1
 
| vpnhub1
 
| vpnhub1.hamburg.ccc.de
 
| vpnhub1.hamburg.ccc.de
 
| vpn gateway
 
| vpn gateway
| 10.104.2.1
+
| 10.160.2.1
 
|-
 
|-
 
| <b>your subnet</b>
 
| <b>your subnet</b>
Line 61: Line 61:
 
| <b>vpn ip for ping tests</b>
 
| <b>vpn ip for ping tests</b>
 
|- bgcolor="#f8f8f8"
 
|- bgcolor="#f8f8f8"
| 10.104.23.0/24
+
| 10.160.23.0/24
 
| *reserved*
 
| *reserved*
 
| *reserved*
 
| *reserved*
Line 67: Line 67:
 
|
 
|
 
|- bgcolor="#f8f8f8"
 
|- bgcolor="#f8f8f8"
| 10.104.42.0/24
+
| 10.160.42.0/24
 
| *reserved*
 
| *reserved*
 
| *reserved*
 
| *reserved*

Revision as of 19:57, 12 May 2010

Back

Warzone IP Ranges and Participants:

We need to have non colliding ip ranges and therefore we need some coordination of the used ip ranges.

First of all we would like to be compilant to the used ip ranges of freifunk and dn42.

The IP ranges overall are defined in the freifunk wiki ip-net page as root source.

So we use 10.104.0.0/14. That should leave enough space for everone untill ipv6 is not the future but the present. (Real IPv6 ranges already in use can also be announced on the VPN, but there are no thoughts about private/internal adressing yet.)

Alternatively we could use 10.160.0.0/13. I have reserved this ip range in the freifunk wiki. (User:mc.fly)

Procedure: Add your subnet below and drop User:Haegar a message with the infos specified at DebianHowto#6._Mail_haegar.40ccc.de_the_info so he can add you to the official listing.

ip ranges

IP-subnets Unique Name Node Remarks VPN IP for test pings
10.160.0.0/14 warzone range warzone range warzone range
10.160.0.0/23 *reserved* orga network, single hosts approved by the orga. This range may be used for Single-IP-VPN nodes like servers which would participate directly but do not need a subnet. Normally you would use a /24.
10.160.0.1/32 aurora haegar laptop 10.160.0.1
10.160.2.0/23 *reserved* subnets This range may be used for small users which do not want/need a whole /24 - allocate only /29 and /28 from here.
10.160.2.0/28 vpnhub1 vpnhub1.hamburg.ccc.de vpn gateway 10.160.2.1
your subnet your unique name your url / description your remarks vpn ip for ping tests
10.160.23.0/24 *reserved* *reserved* *reserved*
10.160.42.0/24 *reserved* *reserved* *reserved*
your subnet your unique name your url / description your remarks vpn ip for ping tests