>>>What kernel version are you running?
>> 2.2.14-5.0
>
>Ahh... you are running an RPM'd kernel I'll bet with a RAM disk. well, since you are going to be setting up IP Masq, you might as well get your kernel compile out of the way now.

Yes, the default kernal out of the RedHat box. I don't know about the RAM disk


>Get 2.2.18 and compile with with firewall support (and all the fw mods) as well as aliasing. Don't forget to compile in your network drivers.
>

OK. Question. For my application can I use workstation ( I like the KDE XWindow interface). I am going to install Apache (with some web sites), Samba, NAT with a firewall (recomendations?), and mySQL for an ODBC application.


>> rtl8139 & 3c509 are default drivers for Red Hat 6.2 I believe the 3c509 is compiled & the rtl8139 is a module but don't quote me.
>
>Don't quote you? Is this your machine or not? =)

Hay! I told you I was a newbee. I saw that info go by on one of about a billion screens I was viewing when I tried to get the whole thing running.

>Say: /sbin/lsmod
>Those list the modules. Everything else that is supported is compiled in.

Will do.

>
>> It won't ping itself although the loop back will. Also, it won't ping from another workstation on the same 192.168 net.
>
>Yikes. Then you have some problems. What happens if you only bring up one interface at a time (only eth0 and then only eth1). It sounds as if your second card is being goofy.

See the DOOOO! below.


>
>>>What distro are you running?
>> ?
>
>Red Hat 6.2 is your distribution (or distro for short).

We figured that out finally after I had already replied. Thanks though.
>
>j


We got the cards to run!!!!!!!!!!!!!! It came down to eliminating all the things that were NOT present when both cards were up. The only thing that was left was what was in common. That turned out to be ME! I was the only thing in common and sure enough I entered the wrong IP network address for both cards I put in 192.174.168 instead of 192.168.174. DOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!!!!!!
Guess my MCP in TCP/IP is now forfeit.

Both cards now function perfectly. We have now moved on to routing. To test the system we connected it to our 90.0.0 network and our 192.168.174 workstation net.
netstat -r is now set to the following:

Destination Gateway GenMask Flags MSS Window Irtt Iface
192.168.174.107 * 255.255.255.255 UH 0 0 0 eth0
90.0.0.3 * 255.255.255.255 UH 0 0 0 eth1
90.0.0.0 * 255.255.255.0 U 0 0 0 eth1
192.168.0.0 * 255.255.0.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo

We can ping 90.0.0 series computers and 192.168.174 series computers from the linux server. From the 90.0.0 series computers we can ping 192.168.174.107 the eth0 card on the linux server. From 192.168.174 series work stations we cannot ping 90.0.0 series computers and cannot ping 90.0.0.3 - eth1 on the linux server.

Any Ideas?

Thanks in advance.