Problem: We want to be able to access X and GDM remotely via XDMCP (e.g. Exceed) , but we don't want to have X running on the server console.

Solution:
In order to pull X with GDM from the server for clients, but not have X on the system console(0), comment out the "0=Standard" line in the /etc/X11/gdm/gdm.conf file.




Problem: How do we let DNS server data through an iptables firewall?

Solution:
Set NS1 to the IP for the DNS server:
NS1='145.109.133.187'
Set NSMASTER to the IP/32 for the DNS Master server for zone transfers:
NSMASTER='16.84.122.140/32'
Set NSSLAVE to the IP/32 for the DNS Slave server for zone transfers:
NSSLAVE='215.143.121.177/32'

# Client-Server
iptables -A INPUT -i eth0 -p udp --sport 1024:65535 -d $NS1 --dport 53 -j ACCEPT
iptables -A OUTPUT -o eth0 -p udp -s $NS1 --sport 53 --dport 1024:65535 -j ACCEPT
# Server-Server
iptables -A INPUT -i eth0 -p udp --sport 53 -d $NS1 --dport 53 -j ACCEPT
iptables -A OUTPUT -o eth0 -p udp -s $NS1 --sport 53 --dport 53 -j ACCEPT
# Zone Transfers
# Allow outbound transfers to slave server.
iptables -A INPUT -i eth0 -p udp -s $NSSLAVE --sport 53 -d $NS1 --dport 1024:65535 -j ACCEPT
iptables -A INPUT -i eth0 -p tcp -s $NSSLAVE --sport 1024:65535 -d $NS1 --dport 53 -j ACCEPT
iptables -A INPUT -i eth0 -p udp -s $NSSLAVE --sport 1024:65535 -d $NS1 --dport 53 -j ACCEPT
iptables -A OUTPUT -o eth0 -p udp -s $NS1 --sport 1024:65535 -d $NSSLAVE --dport 53 -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp -s $NS1 --sport 53 -d $NSSLAVE --dport 1024:65535 -j ACCEPT
# Allow inbound transfers from master server.
iptables -A INPUT -i eth0 -p tcp -s $NSMASTER --sport 1024:65535 -d $NS1 --dport 53 -j ACCEPT
iptables -A INPUT -i eth0 -p udp -s $NSMASTER --sport 53 -d $NS1 --dport 1024:65535 -j ACCEPT
iptables -A OUTPUT -o eth0 -p udp -s $NS1 --sport 53 -d $NSMASTER --dport 1024:65535 -j ACCEPT
iptables -A OUTPUT -o eth0 -p udp -s $NS1 --sport 1024:65535 -d $NSMASTER --dport 53 -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp -s $NS1 --sport 1024:65535 -d $NSMASTER --dport 53 -j ACCEPT

Thanks to Chris Dundon for figuring out the hard parts.




Problem: How do we use Evolution and connect to shared mailboxes off an Exchange server?

Solution: An IMAP login command always takes the form "? LOGIN <mailbox> <password>". What Evolution thinks of as the "username" is actually the full mailbox name, which in the case of Exchange is ntdomain/username/shared_id. So to access the "SHAREDBOX" mailbox, I would use "CHICAGODOMAIN/tcallawa/SHAREDBOX" for my username.




Problem: What Gigabit Ethernet controllers are supported in RHEL 2.1 and 3?

Solution: GigE cards driven by drivers in the RHEL 2.1 kernel:

3Com 3C940 (sk98lin)
3Com 3C941 (sk98lin)
3Com 3C985(B) (acenic)
Allied Telesyn AT-2970LX (sk98lin)
Allied Telesyn AT-2970LX/2SC (sk98lin)
Allied Telesyn AT-2970SX (sk98lin)
Allied Telesyn AT-2970SX/2SC (sk98lin)
Allied Telesyn AT-2970TX (sk98lin)
Allied Telesyn AT-2970TX/2TX (sk98lin)
Allied Telesyn AT-2971SX (sk98lin)
Allied Telesyn AT-2971T (sk98lin)
Alteon AceNIC (acenic)
Broadcom Tigon3 based gigabit (tg3)
D-Link 2000-based gigabit cards (dl2k)
D-Link DGE-530T (sk98lin)
D-Link DGE-500T (ns83820)
EG1032 v2 Instant Gigabit (sk98lin)
EG1064 v2 Instant Gigabit (sk98lin)
Farallon PN9000-SX PCI (acenic)
Intel Pro/1000 (e1000)
Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit) (sk98lin)
Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron) (sk98lin)
Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus) (sk98lin)
Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS) (sk98lin)
Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox) (sk98lin)
Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn) (sk98lin)
Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte) (sk98lin)
Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill) (sk98lin)
Marvell RDK-8001 Adapter (sk98lin)
Marvell RDK-8002 Adapter (sk98lin)
Marvell RDK-8003 Adapter (sk98lin)
Marvell RDK-8004 Adapter (sk98lin)
Marvell RDK-8006 Adapter (sk98lin)
Marvell RDK-8007 Adapter (sk98lin)
Marvell RDK-8008 Adapter (sk98lin)
Marvell RDK-8009 Adapter (sk98lin)
Marvell RDK-8010 Adapter (sk98lin)
Marvell RDK-8011 Adapter (sk98lin)
Marvell RDK-8012 Adapter (sk98lin)
Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (sk98lin)
N-Way PCI-Bus Giga-Card (sk98lin)
National Semiconductor DP83820 driven devices (ns83820)
NetGear GA620 (acenic)
Packet Engines GNIC-II PCI (hamachi)
Packet Engines G-NIC PCI (yellowfin)
PureData's PDP8023Z-TG (ns83820)
SGI Gigabit (acenic)
SMC EZ Card 1000 (SMC9452TXV.2) (sk98lin)
SMC SMC9462TX (ns83820)
SOHO-GA2000T (ns83820)
SOHO-GA2500T (ns83820)
SysKonnect SK-9521 (sk98lin)
SysKonnect SK-9521 v2.0 (sk98lin)
SysKonnect SK-9821 (sk98lin)
SysKonnect SK-9821 v2.0 (sk98lin)
SysKonnect SK-9822 (sk98lin)
SysKonnect SK-9841 (sk98lin)
SysKonnect SK-9841 v2.0 (sk98lin)
SysKonnect SK-9842 (sk98lin)
SysKonnect SK-9843 (sk98lin)
SysKonnect SK-9843 v2.0 (sk98lin)
SysKonnect SK-9844 (sk98lin)
SysKonnect SK-9851 (sk98lin)
SysKonnect SK-9861 (sk98lin)
SysKonnect SK-9861 v2.0 (sk98lin)
SysKonnect SK-9871 (sk98lin)
SysKonnect SK-9871 v2.0 (sk98lin)
SysKonnect SK-9872 (sk98lin)

RHEL 3 also has driver support for:

Realtek 8169 (r8169)

In RHEL 3, the following drivers are only included in -unsupported:
hamachi
sk98lin
yellowfin

All other drivers mentioned in the 2.1 list are included in the supported drivers for RHEL 3.