All in one server (DHCP, DNS, NTP and VPN)

In the previous posts, I’d decided to split up some of the services onto more than one PI.  Currently I have three Raspberry PI’s Employed performing functions for my network.  My Raspberry PI, is performing the DHCP, DNS and NTP roles.  My PI 2 is doing the job of a Wake on Lan server.  It’s basically a web server that can send out the magic packets.  And my PI 3, is doing the VPN stuff.

Having seen how this is performing, I don’t see a problem with combining all of those services onto my PI2.  Which I originally bought for to do all of this.  Rather than take down my Wake on Lan server, I’m going to use a second PI 3 to produce an all in one box.  As part of this, I’m going to alter the way that my WOL service is implemented.  I’ll post details of that when I’m done.   For now.  I’m going to get the DHCP, DNS, NTP and VPN going on a single PI.

To implement this, I’m going to use my previous posts, but I’m going to put things together in a different order as I think it will make it easier to implement everything, also there is a feature that I missed out on which I’m going to try and make work on this PI  the feature is to have the DHCP server register my machines on the DNS server automagically rather than using hard coded values.  This will make managing the DNS much easier.

 

So, this time, I’m going to do things in this order…

http://#/?p=382

http://#/?p=388

http://#/?p=402

At this point, I’ll break off and implement the feature to have the DNS server update the DHCP server.

Then once all of that is working, I’ll rebuild the VPN

http://#/?p=331

I’ll pay attention to this post so that everything is pointed at my new server.

http://#/?p=391

 

At the end of this, I’ll have a single PI doing all of those tasks.  I think that a PI 2 or PI 3 will be more than capable of performing all of those tasks, and more.  The caveat here is that I’m not planning on overloading the VPN with lots of activity – it’s likely that I’ll have a maximum of 4 connections (iPhone, iPad, Laptop, and windows desktop) and even then, it’s more likely to be just one connection rather than more than one at a time.

Leave a Reply

Your email address will not be published. Required fields are marked *