eth0=192.168.1.2
eth1=192.168.4.2
This works great.
I i change eth1 to 10.0.0.4, nothing works. Its like it disables eth0 and eth1.

Any ideas?????????

What if the output of /sbin/ifconfig ?

And,. what is the output of /sbin/route -n ?

eth0 Link encap:Ethernet HWaddr 00:B00:78:92:07
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:16 Base address:0xe8c0

eth1 Link encap:Ethernet HWaddr 00:02:B3:0A:0B:EE
inet addr:10.0.0.4 Bcast:10.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:28 Base address:0xdcc0

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0


Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.200 0.0.0.0 UG 0 0 0 eth0

Okay, that looks good at first glance.

When you try to ping the IP address of eth0 and eth1, what is the output of ping?

Before you run ping, run ifconfig first. Every interface has a "RX packets" and "TX packets" field. As well as "errors" and some more.

Note those numbers down, then run ping and wait a few seconds unitl it exists with an error (or if it keeps waiting for something, ctrl+c it). Now run ifconfig again. Has anything changed in the RX/TX packets, or errors fields?

Hi,
FYI,
gateway for 10.0.0.4 should be 10.0.0.1
gateway for 192.168.2.2 is 192.168.2.200

I noticed there was only one gw in the route -n under eth0. Should eth1 have an entry with the gateway,

Im runningping test now

route's shouldn't matter if you try to ping the IP address of a network card in your computer. Routes come into play when you try to connect to other computers.

This changed on the eth1

RX packets:54 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0

Linux disables an NIC if more than one are on the same subnet. Windows doesn't do thi.. but then windows is wrong... It's because of the ethernet protocol and standards, it doesn't make sense to have two cards connected to the same piece of wire, as it'd cause absolute havoc. you can use bridging to connect the two subnets tho.

p.s. RAHHHHHHHHHHHHHH good to be back!

and what did ping say? was it able to ping?

The thing is..........i dont want them connected. I want one card for internal lan stuff, the other card is for the internet stuff, like email coming in. THere is no sense of having ssh/pop3 running on eth0. I want it all to run on eth1. And it does if there both on the same mask. But since eth1 is part of my internal lan, i want the ip to be 10.0.0.x.

Thanks

True, but with a netmask of 255.255.0 his original eth0 and eth1 weren't on the same piece of wire (192.168.1.0 and 192.168.4.0 would be different networks). Unless of course the netmask was set to 255.255.0.0 but that didn't seem to be the case looking at ForumKid's ifconfig output

Yes i can ping it.......

so now i'm confused. What is the problem then? From your original post I took it that you couldn't do anything including not pinging. Since that works, I'm not sure what is not working (since we didn't change any configuration).

I rebooted and the first connection that i tried to make was to 10.0.0.4. NOw i cannot connect to eth0. Its like whatever card i connect to first takes precedence and thats it.

So now i can ping 10.0.0.4 and 192.168.2.2
If i unplug 192.168.2.2 i can still ping 10.0.0.4
If i unplug 10.0.0.4, i cannot ping 192.168.2.2

Doesnt make much sense to me. Something is getting confused.