17 Feb
2016
17 Feb
'16
8:06 p.m.
On Wed, 17 Feb 2016, Toussaint OTTAVI wrote:
Our sites already connected, or being connected, are
:
- La Punta (JN41IW) : North of Ajaccio bay : VHF repeater, meteo station,
remote contest station tests (TS590 with beam and PA).
- Coti-Chjavari (JN41JS) : South of Ajaccio bay : UHF repeater
- TK5EP home in Ajaccio : Our President, OpenVPN client (test of future VPN
user access)
- TK1BI (me) home in Soccia : IPSEC VPN (site-to-site VPN), 2.4 GHz user
access, UHF repeater with Raspberry/DIAL VoIP testing (current project), and
various other things being tested
- TK5DG in Ajaccio : a user which hosts the first "TkNet box" (a
router/ipsec) behind its home ADSL box. It has a 2.4 GHz uplink to La Punta.
- TK1CX/P in Corte : solar-powered site on a mountain, UHF repeater, APRS, HF
+ 50 MHz station, d-star hotspot (5 GHz link ready to be installed, waiting
for spring...)
- TK4NU in Ajaccio : d-star fan, owns several d-star equipments, is impatient
to be connected to the network (but I'm not ready for d-star yet...)
- MEDI (my company) : datacenter (core of the network : hp Proliant ML350G5
full redundant "second hand" dedicated for hams, HyperV virtuaization, all
the VMs running Debian 8)
- OVH (cloud provider in France) : small server with Proxmox virtualization,
serves as an additional VPN concentrator to reduce latency.
- TK1BI/M : my car, also called "MAEVA", for "Multimedia Autonomous
Embedded
Vehicle Automation" ;-) It's a Raspberry Pi, with 3G/4G router, 2 WiFi
antennas (AP and client), VPN, VLANs (Pro, public and ham),
computer-controlled VHF and UHF TRX, Asterisk, GPS, Bluetooth, HiFi/music
player and car OBDII integration. (under heavy development...)
- TK1BI/P : my Android phone, for mobile VPN testing, monitoring/supervision,
If it were me planning a network based on the above information I would
reserve a /19 but assign a /20, then advertise the /20 via BGP to whom ever you
can get to announce it.
I didn't see any design plans so lets just make one up for fun here.
Being extremely liberal and not knowing the architecture layout that you
have decided upon, I think it's safe to say this probably a more the adequate
assignment for each of the 11 sites.
Per site assignments
--------------------------------------
4 x /27 LAN blocks
8 x /30 RF Links to this site
16 x /32 Loopbacks
If we break that down into assignable assignments:
1408 IP's assigned to LAN blocks
4 x /27 x 11 sites
Assign /21 to LAN Blocks (2,048 IP's)
352 IP's assigned to RF Links
8 x /30 x 11 sites
Assign /23 to RF Links (512 IP's)
176 Loopbacks
16 x /32 x 11 sites
Assign a /24 range to loopbacks (256 IP's)
I would round up /23 + /24 into a /22, and then add the /21 which would
be roughly 12 /24's but since that's not on a even boundary I would move it up
to 16 which makes it a /20, hence the final assignment of a /20 to start with.
I would also mention don't pre-allocate IP blocks to each of the 11
sites until you have a actual need to use the IP Space as this will actually
allow you to grow beyond 11 sites without having to ask for more IP space. Since
I don't think you will actually need 4 lan blocks of a /27 size at each site.
Not to mention the buffer fill space of 5 x /24's that are included in the /20
assignment for the above to make it fall on a even boundary. Lots of growth room
here.
Tim Osburn
080-4633-4671
http://www.m2os.com
W7RSZ / JG1MBR
https://instagram.com/tim.osburn/