Network related tutorials
 |
Roll Your Own Firewall |
| Post date: March 28, 2006, 21:03 Category: Network Views: 1445 Comments: 0 |
| Tutorial quote: A comprehensive user friendly guide to setting up your own firewall on GNU/Linux. |
 |
Tunneling SSH over HTTP(S) |
| Post date: March 12, 2006, 09:03 Category: Network Views: 1380 Comments: 0 |
| Tutorial quote: This document explains how to set up an Apache server and SSH client to allow tunneling SSH over HTTP(S). This can be useful on restricted networks that either firewall everything except HTTP traffic (tcp/80) or require users to use a local (HTTP) proxy. |
 |
Running Apache2 With PHP5 And PHP4 At The Same Time |
| Post date: February 28, 2006, 00:02 Category: Network Views: 1888 Comments: 0 |
| Tutorial quote: This tutorial shows how to install and configure Apache2 with PHP5 and PHP4 enabled at the same time. Because it is not possible to run both PHP5 and PHP4 as Apache modules, we must run one of them as CGI, the other one as Apache module. In this document I will use PHP5 as Apache module and PHP4 as CGI, and I will describe the setup for the Linux distributions Debian Sarge (3.1) and Ubuntu 5.10 (Breezy Badger). |
|
Installing and Configuring Exim4 |
| Post date: February 25, 2006, 12:02 Category: Network Views: 1602 Comments: 0 |
| Tutorial quote: Installion of Exim4 from the latest Debian GNU/Linux packages is easy. The installation is now based around debconf. If you are upgrading from a simple Exim3 configuration, you can use exim_convert4r4 to convert your configuration file to the new format. If you used the previous version of this guide, which covered Exim3, the conversion should succeed without incident. I intend to discuss configuration via debconf, including setting up local delivery to Maildir format, handling local domain email, and configuring smarthosting for outbound email. |
|
Automated distributed backups for laptops |
| Post date: February 14, 2006, 21:02 Category: Network Views: 1041 Comments: 0 |
Tutorial quote: This document will describe the setup I made for automating the backup tasks for all laptops here in the house. My servers use the same backup server and infrastructure, but right now they don't have the checks and scripts because they are online 24/7 and my backup server is triggering the backup process. This is however not true at all for the laptops.
Laptops can be at different places, powered down, suspended, put to sleep etc. So I needed a different approach for them. |
|
Aggregating network interfaces |
| Post date: February 12, 2006, 07:02 Category: Network Views: 1409 Comments: 0 |
| Tutorial quote: Using more than one hard drive to achieve better performance and fault tolerance is very common. Less well known is that it's also possible to aggregate more than one network interface into a single logical interface. In Linux, this is handled by the bonding driver. Benefits of doing this are much the same as the benefits of aggregating discs using RAID: if one device dies, your server carries on working and by using two devices in parallel, performance can be improved. |
|
Setting up an SSL server with Apache2 |
| Post date: February 12, 2006, 07:02 Category: Network Views: 1235 Comments: 0 |
| Tutorial quote: With the introduction of the Apache2 packages in Debian it is much simpler to create and use a secure SSL protected webserver than in the old days with Apache 1.3, here we'll show how it is done. |
|
Getting started with SSH |
| Post date: February 11, 2006, 04:02 Category: Network Views: 1060 Comments: 0 |
| Tutorial quote: The following sections hope to provide enough information to setup a user new to ssh with the appropriate files necessary for accessing remote hosts in a secure manner. |
 |
How I created my own .mac replacement |
| Post date: February 7, 2006, 21:02 Category: Network Views: 1615 Comments: 1 |
Tutorial quote: My .mac subscription is 60 days from renewal so I have to ask myself, "how useful is .mac to me?
Is .mac worth it to me? Many of the reasons I don't find .mac useful are the same reasons I encourage others to use .mac. One has to keep in mind that I'm not an "average" computer user. My needs are different and Apple wouldn't make any money trying to sell a .mac like service to guys like me. This is not an "I hate .mac" site but rather an explanation of the motivation and methods I used to provide myself with comparable services that are more usable to me. I publish it so that others may benefit from what I have learned.
This is published to help others, but don't expect free support from the author. Support requests that arrive without monetary compensation for my time will almost certainly be ignored. Instead, try using the support forums and maybe someone will help you out.
To understand why I did this, you might want to read about my use of .mac services.
Project Goals:
Retain the useful features: Regardless of whether or not I renew my subscription, I want to retain the features I have found most useful (iDisk, iSync (between computers), iCal sharing, and Backup).
Enhance the useful features: Simply retaining the useful features would be an utter failure. The most value can be found in addressing the shortcomings of each feature. For iDisk, speed and disk space are the impediments to it's usefulness. iSync already works quite well. iCal sharing works well but publish and subscribe updates are sloooow. Backup is hamstrung by the iDisk space issue. |
|
How to set up a mail server on a GNU / Linux system |
| Post date: February 7, 2006, 07:02 Category: Network Views: 2394 Comments: 0 |
Tutorial quote: Easy to follow howto on setting up a mail server with unlimited users and domains, with IMAP/Pop access, anti-spam, anti-virus, secure authentication, encrypted traffic, web mail interface and more.
Based on an Ubuntu distribution platform, but instructions are distro generic. |
|
|
