Dear Darrell,
I've just gone through the same situation. All I wanted to do was forward internet traffic to a web server on the inside of my firewall. Leave port forwarding behind and use mfw (marked forward). This is the newest way to accomplish the same thing.
See man ipchains. I used the following rule to have ipchains mark the lead packet (and all the following packets in the chain) for forwarding.
ipchains -I input -p tcp -y -d yourcompany.com/32 80 -m 1
The use the following rule to have the ip masquerading redirect the marked packets to my internal web server (192.168.1.65):
ipmasqadm mfw -I -m 1 -r 192.168.1.65 80 -p 10
Instead of yourcompany.com in the first rule I had better luck by substituting the IP address instead of the domain name.
There is one gotcha that I have to resolve this evening after all my users go home. The rules will be forgotten the next time the linux firewall is rebooted. I need to find the place where e-smith keeps the rules template or add the rules to a start-up script to be executed after each reboot.
Hope this helps.
Bill