I have a bunch of test CentOS/FreeBSD servers and I wanted to get all the notifications sent to my e-mail instead of logging to each server and check the status of each one of them. Some of my servers are behind my home network where outbound port 25 (SMTP) is blocked by the ISP. So, I decided to use my main postfix server which is already configured to use port 587 for SMTP using TLS. In this post, I’ll explain how I configured my test servers to relay e-mails.
Use the following links to see how I configured the postfix main server for CentOS and FreeBSD.

CentOS 7

There are some prerequisites for CentOS 7. It comes with postfix installed and it has built-in Cyrus SASL already, but we need another Cyrus SASL package for login support. In addition, CentOS doesn’t come up with the mail command, so we have to install that as well.

Prerequisites

Install Cyrus SASL package and the mail client.

yum install cyrus-sasl-plain mailx

postfix main config file

Edit /etc/postfix/main.cf and add these lines at the end.

relayhost = [server.domain.com]:587
smtp_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_use_tls = yes
smtp_tls_CAfile = /etc/ssl/certs/server.domain.com.crt

The first line is your main postfix server that will receive the e-mail from the client servers, the 4th line is the file where you are going to store the username and password for the user that’s able to login to the main postfix server and the 6th line is the certificate of the main postfix server.

SASL Authentication

Edit /etc/postfix/sasl_passwd and add this line.

[server.domain.com]:587 mail@domain.com:YourPassword

You have to specify your main postfix server, the username and the password for a valid user that’s able to login to that server and receive e-mails. Once completed, execute postmap.

postmap /etc/postfix/sasl_passwd

e-mails to relay

I wanted to send all of my root e-mails to my main server, so what you have to do is edit /etc/aliases and scroll all the way down at the bottom. Un-comment the root line and specify where do you want your root emails to be forwarded.

root: mail@domain.com

If you have some cron jobs that run under some other username, specify them in this file, e.g. someuser: some-email@email.com.
After you are done, type newaliases.

newaliases

Public certificate

You will also need the public certificate of your e-mail server. Get the certificate in a PEM format and paste it into a new file /etc/ssl/certs/server.domain.com.crt. Or, in my case, I have a wildcard certificate for my domain, so I can get it using this command.

openssl s_client -connect server.domain.com:443 < /dev/null | \
sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > /etc/ssl/certs/server.domain.com.crt

Final step

Restart the postfix server on the client server, send a test e-mail and check the result.

systemctl restart postfix
echo "This is a test." | mail -s "Test e-mail" root
tail /var/log/maillog

FreeBSD 11

Unlike CentOS, FreeBSD doesn’t come up with postfix, instead it uses sendmail. So, we have to remove sendmail, install postfix and follow similar config as with CentOS.

Prerequisites

We have to install postfix from the ports because it doesn’t come up with Cyrus SASL. It comes with dovecot SASL, but I am not sure if it works in a client config. On the other hand, FreeBSD comes with mail installed. Install the postfix port, not the package.

cd /usr/ports

If you get an error that there is no such file or directory, get the ports tree. If you can cd to that folder, skip the step below to install the ports tree.

portsnap fetch
portsnap extract

Install postfix.

cd /usr/ports/mail/postfix
make all install clear

When this dialog box pops-up, select BDB and SASL as highlighted.

Execute these lines so you replace sendmail with postfix.

sysrc postfix_enable="YES"
sysrc sendmail_enable="NONE"
mv /usr/local/etc/mail/mailer.conf /usr/local/etc/mail/mailer.conf.old
install -m 0644 /usr/local/share/postfix/mailer.conf.postfix /usr/local/etc/mail/mailer.conf

Add the following lines to /etc/defaults/periodic.conf

daily_clean_hoststat_enable="NO"
daily_status_mail_rejects_enable="NO"
daily_status_include_submit_mailq="NO"
daily_submit_queuerun="NO"

Make sure Cyrus SASL is installed.

postconf -a

You should see cyrus and dovecot there.

postfix main config file

Edit /usr/local/etc/postfix/main.cf and add these lines at the end.

relayhost = [server.domain.com]:587
smtp_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
smtp_sasl_password_maps = hash:/usr/local/etc/postfix/sasl_passwd
smtp_use_tls = yes
smtp_tls_CAfile = /usr/local/etc/ssl/server.domain.com.crt

The first line is your main postfix server that will receive the e-mail from the client servers, the 4th line is the file where you are going to store the username and password for the user that’s able to login to the main postfix server and the 6th line is the certificate of the main postfix server.

SASL Authentication

Edit /usr/local/etc/postfix/sasl_passwd and add this line.

[server.domain.com]:587 mail@domain.com:YourPassword

You have to specify your main postfix server, the username and the password for a valid user that’s able to login to that server and receive e-mails. Once completed, execute postmap.

postmap /usr/local/etc/postfix/sasl_passwd

e-mails to relay

I wanted to send all of my root e-mails to my main server, so what you have to do is edit /etc/aliases and scroll a little bit way down. Un-comment the root line and specify where do you want your root emails to be forwarded.

root: mail@domain.com

If you have some cron jobs that run under some other username, specify them in this file, e.g. someuser: some-email@email.com.
After you are done, type newaliases.

newaliases

Public certificate

You will also need the public certificate of your e-mail server. Get the certificate in a PEM format and paste it into a new file /usr/local/etc/ssl/server.domain.com.crt. Or, in my case, I have a wildcard certificate for my domain, so I can get it using this command.

openssl s_client -connect server.domain.com:443 < /dev/null | \
sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > /usr/local/etc/ssl/server.domain.com.crt

Final step

Restart the postfix server on the client server, send a test e-mail and check the result.

service postfix restart
echo "This is a test." | mail -s "Test e-mail" root
tail /var/log/maillog

You will notice that the e-mails that come from FreeBSD are always sent by Charlie Root. If you have multiple FreeBSD boxes, the e-mails from various FreeBSD servers will come as Charlie Root which might be a bit confusing. So do a chpass and change the line Full Name, so instead of Full Name: Charlie &, do something like Full Name: servername Charlie &.

chpass

Do :wq if your default editor is vi to save the changes.

norem for Linux/*BSD

A small utility written in Bourne shell (compatible with both sh and bash, which means works without changes on all *BSD/Linux) that strips comments from a source file. E.g. I am too lazy to scroll through /etc/ssh/sshd_config file to look for any valid directives.
Here is /etc/ssh/sshd_config on FreeBSD.

#       $OpenBSD: sshd_config,v 1.98 2016/02/17 05:29:04 djm Exp $
#       $FreeBSD: releng/10.3/crypto/openssh/sshd_config 296853 2016-03-14 13:05:13Z des $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options override the
# default value.

# Note that some of FreeBSD's defaults differ from OpenBSD's, and
# FreeBSD has a few additional options.

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

# The default requires explicit activation of protocol 1
#Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Ciphers and keying
#RekeyLimit default none

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin no
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
#PubkeyAuthentication yes

# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
#AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# Change to yes to enable built-in password authentication.
#PasswordAuthentication no
#PermitEmptyPasswords no

# Change to no to disable PAM authentication
#ChallengeResponseAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'no' to disable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
#UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation sandbox
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum FreeBSD-20160310

# no default banner path
#Banner none

# override default of no subsystems
Subsystem       sftp    /usr/libexec/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#       X11Forwarding no
#       AllowTcpForwarding no
#       PermitTTY no
#       ForceCommand cvs server

With this utility, I can just do:

norem -f /etc/ssh/sshd_config

… and voila…You have the meat without the bones.

Subsystem       sftp    /usr/libexec/sftp-server

Almost all *nix utilities have “#” as a comment, but some languages such as Java and C++ use “//” for comments. In this case, we have to run:

norem -f file -c "/"

The utility is not smart enough for multi-line comments such as “/*…*/”
Here is the source:

#!/bin/sh

usage()
{
    echo "usage: norem [-f file ] | [-c char] | [-e]] | [-h]]"
    echo "Prints a file skipping the lines that start with -c"
    echo "By default empty lines are not printed, use -e yes to include them"
    echo "Kliment Andreev - 2016"
}

if [ "$#" == "0" ]; then
        usage
        exit 1
fi

while [ $# -gt 0 ]; do
        key="$1"

        case $key in
                -f|--file)
                        FILENAME="$2"
                    shift
                        ;;
        -c|--char)
                        CHARACTER="$2"
                        shift
                ;;
                -e|--empty)
                EMPTY="$2"
                shift
                ;;
        *)
                usage
                        exit
                ;;
        esac
        shift
done

if [ -z "${CHARACTER}" ]; then
        CHARACTER="#"
fi

if [ -z "${EMPTY}" ]; then
        cat ${FILENAME} | sed "/^\\${CHARACTER}/d" | awk /./
else
        cat ${FILENAME} |sed "/^\\${CHARACTER}/d"
fi

norem for PowerShell

The same utility for PowerShell. The input parameters are the same.

Param(
	[string]$fileName,
	[string]$char="#",
	[string]$empty
)

function usage {
    Write-Host "usage: norem [-f file ] | [-c char] | [-e]]"
    Write-Host "Prints a file skipping the lines that start with -c"
    Write-Host "By default empty lines are not printed, use -e yes to include them"
    Write-Host "Kliment Andreev - 2016"
}

if ($psboundparameters.Count -eq 0) {
    usage
    exit
}

if ($empty.ToUpper().Contains("Y")) {
    Get-Content $fileName | Where { $_ -notmatch "^" + $char }
}
else {
    Get-Content $fileName | Where { $_ -notmatch "^" + $char } | Where {$_.trim() -ne ""}
}

This is a very simple setup to run squid proxy. You can use the provided config file to run the proxy as a transparent proxy but you have to deal with pf and port 3128 (default squid port) and your OpenBSD server must act as a internet router. In my case, I have FreeBSD that does the NAT job and my OpenBSD is a regular server on the network. I don’t mind to setup my browsers manually to use this non-transparent proxy.

First, you have to install squid from packages.

export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386
pkg_add squid-2.6.STABLE13.tgz

At the end of the installation, you’ll see the following.

--- squid-2.6.STABLE13 -------------------NOTES ON OpenBSD POST-INSTALLATION OF SQUID 2.6
The local (OpenBSD) differences are:                

configuration files are in              /etc/squid
sample configuration files are in       /usr/local/share/examples/squid
error message files are in              /usr/local/share/squid/errors
sample error message files are in       /usr/local/share/examples/squid/errors
icons are in                            /usr/local/share/squid/icons
sample icons are in                     /usr/local/share/examples/squid/icons
the cache is in                         /var/squid/cache
logs are stored in                      /var/squid/logs              

the ugid squid runs as is               _squid:_squid               

Please remember to initialize the cache by running "squid -z" before
trying to run Squid for the first time.                

You can also edit /etc/rc.local so that Squid is started automatically:                

if [ -x /usr/local/sbin/squid ]; then
        echo -n ' squid';       /usr/local/sbin/squid
fi                

First, let’s edit /etc/rc.local and add the last part (lines 20 to 22) so squid starts automatically. Regardless of the configuration files, we can run squid -z now to build the cache. Default configuration file /etc/squid/squid.conf won’t work, so we have to make some small changes before we start squid for the first time. Edit /etc/squid/squid.conf and change the following.

#acl our_networks src 192.168.1.0/24 192.168.2.0/24
#http_access allow our_networks

change to

acl our_networks src 192.168.1.0/24
http_access allow our_networks

Make sure that the IP and subnet match your network. Also, change the e-mail address that shows in the browser for any errors that might occur (page not found, internal server error etc).

# cache_mgr webmastercache_mgr klimenta@whatever.org

Before you start squid, change the proxy settings in all of your browsers. Remember, this is not a transparent proxy, so you have to change it manually. If you don’t change the proxy settings, it doesn’t matter, you can still access the internet, you just won’t be able to go through the proxy server. The IP address of my OpenBSD/squid server is 192.168.1.7.
Internet Explorer: Click Tools, Internet Options, Connections tab, then LAN settings.

Firefox: Click Tools, Options, Network tab, then Settings.

Opera: Click Tools, Preferences, Advanced tab, then Proxy servers.

Now, start squid by using

/usr/local/sbin/squid

Fire up the browser and go to www.google.com. If everything is OK, you’ll see the known page. You can also check the logs too.

tail -f /var/squid/logs/access.log
1205505033.035    111 192.168.1.3 TCP_MISS/200 3071 GET http://www.google.com/ - DIRECT/64.233.169.99 text/html
1205505033.156    120 192.168.1.3 TCP_MISS/200 8882 GET http://www.google.com/intl/en_ALL/images/logo.gif - DIRECT/64.233.169.99 image/gif  

Recently I got a laptop that came without CD or floppy. This laptop supports PXE boot so the only choice was to install Ubuntu over the network. In order to do that, I needed a DHCP server that supports PXE boot, tftp server and of course the boot file that will start the installation over the network. You can see my previous article on how to setup a DHCP server on OpenBSD. Installation of the tftp server is very easy on OpenBSD. You have to edit /etc/inetd.conf and uncomment the first entry for tftp.

ident           stream  tcp     nowait  _identd /usr/libexec/identd     identd -el
ident           stream  tcp6    nowait  _identd /usr/libexec/identd     identd -el
tftp            dgram   udp     wait    root    /usr/libexec/tftpd      tftpd -s /tftpboot
#tftp           dgram   udp6    wait    root    /usr/libexec/tftpd      tftpd -s /tftpboot

Now, you need to refresh inetd process and create the home/root folder for the tftp.

kill -HUP `cat /var/run/inetd.pid`
mkdir /tftpboot  

Make sure that tftp is working. Type q to exit.

tftp localhost
tftp> q

Next, you have to download the Ubuntu network installation file and place it in /tftpboot. Put this file in /tftpboot and unpack it with:

tar xzvf netboot.tar.gz

You have to change the MAC address in /etc/dhcpd.conf to match the MAC address on the computer where you want to install Ubuntu. Restart the computer, choose network boot and install.

The original DHCP server that is provided with OpenBSD is a custom build based on ISC DHCP v2. I was having problems running PXE Boot on the original DHCP server, mentioned in my previous article, so this article will describe how to setup ISC DHCP that works with PXE and TFTP.
First, we have to stop the old server running. The easiest way of doing that is to kill the dhcpd process.

kill -9 `cat /var/run/dhcpd.pid`

In addition, we have to edit /etc/rc.conf and change the line dhcpd_flags=”” to dhcpd_flags=NO, so the original server won’t start after the computer restart. Then, we have to download and install ISC DHCP server from OpenBSD ftp site.

export PKG_PATH=ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386/
pkg_add isc-dhcp-server-3.0.4p0.tgz

The old dhcp program is /usr/sbin/dhcpd and the new one is /usr/local/sbin/dhcpd. Edit /etc/rc.local and add the following line:

if [ -x /usr/local/sbin/dhcpd ]; then
   echo -n ' ISC DHCP Server starting...'
   /usr/local/sbin/dhcpd
fi

This is a simple startup. If you need to use multiple startup configuration files, consider using variables in /etc/rc.local and /etc/rc.local.conf.

Now, let’s configure the dhcp server. First make a copy of the original /etc/dhcpd.conf and replace it with this one.

ddns-update-style none;   

# Definition of PXE-specific options
# Code 1: Multicast IP address of bootfile
# Code 2: UDP port that client should monitor for MTFTP responses
# Code 3: UDP port that MTFTP servers are using to listen for MTFTP requests
# Code 4: Number of seconds a client must listen for activity before trying
#         to start a new MTFTP transfer
# Code 5: Number of seconds a client must listen before trying to restart
#         a MTFTP transfer   

option space PXE;
option PXE.mtftp-ip               code 1 = ip-address;
option PXE.mtftp-cport            code 2 = unsigned integer 16;
option PXE.mtftp-sport            code 3 = unsigned integer 16;
option PXE.mtftp-tmout            code 4 = unsigned integer 8;
option PXE.mtftp-delay            code 5 = unsigned integer 8;
option PXE.discovery-control      code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr   code 7 = ip-address;   

# PXE specific options
class "pxeclients" {   

  match if substring (option vendor-class-identifier, 0, 9) =
        "PXEClient";
  option vendor-class-identifier "PXEClient";
  vendor-option-space PXE;
  # At least one of the vendor-specific options must be set in order
  # for the boot ROM on the client to recognize us as a PXE
  # compliant server. We set the MCAST IP address to 0.0.0.0 to tell
  # the boot ROM we can't provide multicast TFTP, so it will have to
  # use just plain ol' TFTP instead (address 0.0.0.0 is considered
  # as "no address").
  option PXE.mtftp-ip 0.0.0.0;
}   

  subnet 192.168.1.0 netmask 255.255.255.0 {   

  option subnet-mask 255.255.255.0;
  option routers 192.168.1.1;
  option domain-name "chombe.org";
  option domain-name-servers 192.168.1.2, 192.168.1.8;   

  pool {
      range 192.168.1.50 192.168.1.254;
  }   

  # cluster nodes
  group {
     filename "pxelinux.0";
     host node1 {
        hardware ethernet 00:11:43:47:38:9c;
        next-server 192.168.1.7;
        fixed-address 192.168.1.49;
     }
  }
}

Line 37 is your network. From line 39 to line 42, you specify the “options”, parameters that each DHCP client will get, such as subnet mask, the gateway, the domain name suffix and the DNS server(s).
Specify the DHCP range in line 45. Explanation of every line of this configuration file will require another article and if you are interested, you can visit the ISC site and read the instructions. What is important is the last part where filename “pxelinux.0” specifies the boot file, hardware ethernet specifies the MAC address of the client that will be assigned 192.168.1.49 (out of the DHCP scope) and next-server is the TFTP server’s IP address. See the next article on how to configure a tftp server.

One of my computers running OpenBSD 3.7 that was a DNS, DHCP, NTP and proxy server recently crashed (HDD failure). I have another DNS server running on a different machine and I didn’t much care about NTP and proxy. But, DHCP server was playing an important role. I lost connection on all of my computers because the wireless router was using pass-through DHCP from the OpenBSD machine. I configured the laptops to use static IPs for a day until I bought a new HDD and reinstalled OpenBSD 4.2
First, I edited /etc/rc.conf and replaced dhcpd_flags=”NO” with dhcpd_flags=””. Then, I used ifconfig to check the name of the ethernet adapter. In my case it is xl0.

ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33208
        groups: lo
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:08:74:22:25:3c
        groups: egress
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::208:74ff:fe22:253c%xl0 prefixlen 64 scopeid 0x1
enc0: flags=0<> mtu 1536

I edited /etc/dhcpd.interfaces and added xl0 at the very end, so it looked like this.

# $OpenBSD: dhcpd.interfaces,v 1.1 1998/08/19 04:25:45 form Exp $
#
# List of network interfaces served by dhcpd(8).
#
# ep0
# ed0 le0
# de1
xl0

xl0 is the listener interface. You can have multiple interfaces. Since I have only one network card, xl0 is the only option.

DHCP server stores its leases in a file /var/db/dhcpd.leases. This file is not there, so we have to create it first.

touch /var/db/dhcpd.leases

The last part involves you to modify the configuration file, where you can specify the scope and other parameters of the DHCP server. I made a copy of the original file, in case something goes wrong.

cp /etc/dhcpd.conf /etc/dhcpd.conf.orig

Then I edited /etc/dhcpd.conf to suit my needs. This is the simplest working configuration.

shared-network LOCAL-NET {
option domain-name "your-domain-here";
option domain-name-servers 192.168.1.2, 192.168.1.8;
        subnet 192.168.1.0 netmask 255.255.255.0 {
        option routers 192.168.1.1;
        range 192.168.1.50 192.168.1.254;
        }
}

• option domain-name “your-domain-here” means I have used your-domain-here as DNS name. So, your DHCP client host will have this value as suffix.
• Next parameter, option domain-name-servers 192.168.1.2, 192.168.1.8; is the address or addresses of your DNS servers that will be assigned to the computer that will lease an IP.
• The line after that tells the DHCP server what’s the network class and subnet. My network is 192.168.1.0/24, /24 is 255.255.255.0, /16 is 255.255.0.0 etc….
• The gateway assigned (option routers) in my case is 192.168.1.1.
• And I also choose the scope of my DHCP to be from 192.168.1.50 to 192.168.1.254.

Now, I can start the server by using:

dhcpd

If everything is OK, you’ll get the prompt back. Let’s verify that DHCP server is working.

ps -waux | grep dhcpd
_dhcp 8667 0.0 0.1 672 768 ?? Is 3:54AM 0:00.00 dhcpd</pre>

I went back to my Windows laptop and verified that everything is OK.

C:\Documents and Settings\klimenta\ipconfig /all
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix .  : your-domain-here
Description . . . . . . . . . . . : Intel(R) PRO/100 VM Network Connection
Physical Address. . . . . . . . . : 00-08-02-E4-34-0D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.7
DNS Servers . . . . . . . . . . . : 192.168.1.2
                                    192.168.1.8
Lease Obtained. . . . . . . . . . : Thursday, December 01, 2011 8:36:04 AM
Lease Expires . . . . . . . . . . : Thursday, December 01, 2011 8:36:04 PM

And I can verify on the DHCP server that it leased an IP.

tail /var/db/dhcpd.leases
# All times in this file are in UTC (GMT), not your local timezone.
# The format of this file is documented in the dhcpd.leases(5) manual page.
lease 192.168.1.50 {
        starts 6 2011/12/01 08:36:04;
        ends 6 2011/12/01 20:36:04;
        hardware ethernet 00:08:02:e4:34:0d;
        uid 01:00:08:02:e4:34:0d;
        client-hostname "bigbeat";
}