no connectivity for clent machines but gateway works

[joePRL]

Hello Everyone:

I'm working on a new server adding wireless connectivity WITHOUT having the wired and the wireless networks seeing each other. So the new firewall has 3 NICs. One for the external gateway (eth0), one for our wired LAN (eth1) and one for our
wireless LAN (eth2).

Our old firewall is running Gentoo with kernel 2.4.27 and the new firewall has kernel 2.6.12. Both use gentoo-sources.

I can't get our new firewall to allow our internal clients to surf the 'net although named and dhcp work.

I first thought that my firewall was doing something wrong, so to simplify task I used the firewall which I know works (i.e. from our old, functional firewall) although it is doesn't do anything about wireless.

Here's what happened.

New firewall started up with no complaints. All interfaces came up with the proper numbers
eg.
Starting eth1
Bringing up eth1
192.168.0.214 [ok]

named and dhcp were started manually and responses were [ok]

Turn on firewall manually:
./firewall-temporary
no complaints

Ping google from new-firewall, no response. But this was expected.
I have to give the following command:
"route add default eth0"

Ping google from new-firewall, success. Lynx connects to MIT too.

Go to a client machine, release the dhcp lease, renew it. Success.
Client can NOT access internet.
Client can access our mail server via internal ip.
Client can NOT access new-firewall's internal interface (192.168.0.214).
192.168.0.214 is supposed to up and is plugged into the hub with a cable that I proved works earlier.
Plus, the cable must work if a client machine get obtain a lease from the dhcp server.

So what's not happening?

Here's my configuration file for the interfaces:
NOTE: the external ip was changed for security, there is a real number in the actual file.

[Ph0eniX]

[joePRL]

That's my intention. The following code segment comes from /etc/dhcp/dhcpd.conf: