All posts by mlapaglia

Homebrew – Tripple END

This past weekend I made a “Tripple END” from Great Fermentations. The employees at the store helped me modify the recipe to taste more like the “Tripple de Ripple”, a beer served at a local establishment I am fond of. We added 2 extra pounds of light malt extract, another 8 oz of dark liquid candi, and switched to a Canadian Belgium yeast, capable of handling higher alcohol concentrations. The Tripple de Ripple has a ~10% ABV while the Tripple END only has 7.5% so yeast engineered to withstand higher ABV were required.

IMG_20150221_124149

Since there would be an abnormally high amount of sugar in the wort after boiling, the number of yeast required to get fermentation started was higher. To overcome the amount of yeast that would die after pitching (due to the amount of lysed cells caused by the concentration of sugar a starter was required. During boiling the yeast starter was created with half a cup of DME, one pouch of liquid yeast, and 1.5L of water. I have a Stir Starter, a magnetic stir plate much cheaper than professional stir plates. This starter helped double the number of yeast being pitched, increasing the chance of a successful fermentation and speeding along the process as well. The starter was positioned in range of the heat lamps in the overhead hood to increase the temperature of the starter a few degrees to get the yeast started quickly.

IMG_20150221_154712

Another 6.5 gallon carboy was added to the fleet, here’s the initial etching of the gallon indicators on the side of the glass:

IMG_20150222_140619

Looking good!

IMG_20150222_140610

Since the density of the wort post-boil would be much higher due to the concentration of the sugar I added a pump to push the wort through the counter flow chiller because the copper tubing has a small internal diameter. The chiller helps the wort get from ~210° F to ~65° F at 1 gal/min into the fermentation carboy. In order to prevent contamination post-boil it is important to complete this task as fast as possible, since contaminates will affect the fermentation process and final taste of the beer.

IMG_20150222_140641

The next day fermentation was underway!

download_20150223_094355

Setting up Routing and Remote Access Service on Windows Server 2012

Recently I came across a need to implement a simple VPN connection to my home network. I have a Windows Server 2012 box hosting my IIS, which also supports VPN connections over SSTP through the Routing and Remote Access Service (RRAS) without any need for 3rd party software on either server or client side.

To get started I followed the instructions on technet which outlined how to add the feature to the server and start the service. I already had port 443 forwarded through my router for IIS.

I was unable to get my external Windows client to connect right off the bat. I needed to configure a few extra settings. The server was unable to reach the local router DHCP services. I worked around this by adding a static IP pool for the server to pull from instead of the router:

Capture

I took this range of IPs out of what the router would hand out to clients to keep any IP address conflicts at bay.

I ensured that the user I was attempting to log in as had remote access permissions through the MMC console:

Capture

Windows 7 and above supports the VPN connection natively:

Capture

I found that after setting up the connection modifications were required to get the client using the correct protocol and credentials:

Capture

After these changes I was able to make a successful connection and tunnel my connection through my home network.

Capture

Since the SSTP protocol is basically an SSH connection, a valid trusted certificate is required to be installed on the server. the Windows VPN client does not support trusting non-verified certificates. If your connection address is mattlapaglia.com, a SSL certificate with the same CN is required on the server. I already had a certificate installed on the server for use with IIS which RRAS picked it up automatically. I was surprised there was no issue with IIS and RRAS fighting for control of port 443 (used with both RRAS for SSTP and IIS for SSL connections)