The Best Multiplatform Development Environment that Ever Lived on One Box
Firewalling support for Linux has gone through many changes. Unlike other aspects of the kernel's evolution that have been methodical, each change to the firewalling modules has been radical compared to prior versions. The downside of this is each change to the way Linux deals with firewalling has a new learning curve associated. Like other areas of Linux development, however, each release has been very stable and has provided support for backward compatibility. Linux is evolving into a mature, enterprise-strength firewalling solution, as evidenced by companies like Watchguard.
In previous releases of the kernel, the firewall configuration tool was called ipchains. Now, with the 2.4 release, this has once again changed to a tool called iptables. Both of these tools run on the command line but hook into the kernel to configure firewall settings at a very low level. The iptables arrangement offers significant advantages over the ipchains way of kernel organization, but ipchains will be supported for some time as a kernel loadable module. For more information, see kernel.org and IPCHAINS-HOWTO.
For my purposes, ipchains offered more than adequate support for my needs. My major concerns regarding firewalling were:
Lock down all extraneous/unused ports and services to have a safe box. Since I would potentially be housing sensitive information while developing software for my clients, it was important that the box be adequately protected.
Provide NAT (network address translation) services to my internal network, often called IP masquerading. Since I only had one valid IP address and a number of workstations needing access to the Internet, I needed to provide a way for to manage multiple connections through my single (real) internet connection.
Provide port tunneling services, where appropriate, to other internal boxes. In some cases, I had other machines running internet protocols internally that I wanted to allow access to from the Internet.
The ASCII diagram below shows our network/firewall setup:
|------| ------- 192.168.1.0 | | | | W1 |----------------| | 11 | | |------| | | |---------| |------| | | | | | | eth0|200 D|eth1 Internet | W2 |----------------|--------------| Linux |--------------------- | 12 | | | | |------| | |---| | | | |---------| |------| | | | | | | | VM | | W3 |----------------| | 201 | | 13 | | | | |------| -------- |---------|
The internal network is 192.168.1.0. Each machine on the diagram above shows the last number in its IP address. The Linux box has two physical adapters. The internal one (eth0) has an address on the internal network (200), while the external adapter (eth1) obtains its address dynamically via DHCP. This is why it is marked with a D on the diagram.
It is ipchains that allows NAT between the internal network and the Internet. All outgoing connections are allowed. All incoming connections are disallowed, with the exception of port 80 (HTTP), port 22 (SSH) and port 8080 (for an HTTP server running on the VM machine). These services will be explained in more detail below.
Notice the VM machine is shown "behind" the Linux box. This will be explained in more detail in the VMware section below.
A simple program named redir, found at sammy.net, allows services running on an internal machine to be accessed from the outside (Internet) network. This program accepts connections on a certain port and proxies those connections to another port on a different machine.
First of all, external connections must be allowed to the port on the Linux box. In my case, this port is 8080. The redir command we execute looks like this:
redir --lport=8080 --caddr=192.168.1.101 --cport=8080 --syslog &
The lport is the listen port of the local machine. The caddr and cport settings are the connection address and port, respectively. The syslog parameter instructs redir to log all connections to the standard system log.
As a result of this command, any connections to the Linux box on port 8080 will be served by the web server running on the VM box (also from port 8080).
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Home, My Backup Data Center
- Tech Tip: Really Simple HTTP Server with Python
- Please correct the URL for Salt Stack's web site
1 hour 15 min ago
- Android is Linux -- why no better inter-operation
3 hours 31 min ago
- Connecting Android device to desktop Linux via USB
3 hours 59 min ago
- Find new cell phone and tablet pc
4 hours 57 min ago
6 hours 26 min ago
- Automatically updating Guest Additions
7 hours 35 min ago
- I like your topic on android
8 hours 21 min ago
- This is the easiest tutorial
14 hours 57 min ago
- Ahh, the Koolaid.
20 hours 35 min ago
- git-annex assistant
1 day 2 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?