So by changing the card to 10.0.0.4, I can no longer connect to 192.168.2.2. I can ping but no connection can be made

When i try to connect to 192.168.2.2 my RX packets go up but not TX.
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:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:16 Base address:0xe8c0

I even tried changing my routing table.

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.2.200 255.255.255.0 UG 0 0 0 eth0
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 10.0.0.1 0.0.0.0 UG 0 0 0 eth1


Windoz blows....but then again......i would be having this problem.

now there are two default gateway's setup. That simply won't work as expected. It may be cause for the confusion of the kernel and nothing works.

But I am stumped as to why you can't ping one IP when unplugging the other card (But you said it does work when you reverse it).

Let's re-create the problem situation.

unplug 10.0.0.4 you can't ping 192.168.2.2 right?

now show the output of ifconfig and route -n

unplug 10.0.0.4 you can't ping 192.168.2.2 right --> CORRECT

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:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 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:164 errors:0 dropped:0 overruns:0 frame:0
TX packets:123 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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 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
~

I ping 192.168.2.2 and i went behind the box. Saw that both nics were flashing. I have no clue as of why.

I'm at a loss I'm afraid as to what would cause this let alone how to fix it.

If i disable 10.0.0.4 I can then access 192.168.2.2.

For some reason it cant handle 2 nics. It has to be a routing issue. Binding to both cards or the wrong card.

I have no friggen idea.

192.168.2.0 * 255.255.255.0 U 0 0 0 eth0
10.0.0.0 * 255.0.0.0 U 0 0 0 eth1
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.2.200 0.0.0.0 UG 0 0 0 eth0


I can ping both 10.0.0.4 and 192.168.2.2. However when i enable eth1, I can no longer connect to eth1. I can still ping 192.168.2.2 though.
Does anyone have any suggestions.
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:129 errors:0 dropped:0 overruns:0 frame:0
TX packets:117 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:229 errors:0 dropped:0 overruns:0 frame:0
TX packets:195 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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

arp
10.0.0.1 ether 00:03:47:99D:3F C eth1
10.0.0.2 ether 00:E0:98:87:AF:93 C eth1
192.168.2.200 ether 00:02:B3:17:FE:C3 C eth0
arp -a
? (10.0.0.1) at 00:03:47:99D:3F [ether] on eth1
? (10.0.0.2) at 00:E0:98:87:AF:93 [ether] on eth1
? (192.168.2.200) at 00:02:B3:17:FE:C3 [ether] on eth0

This shows that eth0 is bound to its gateway of 192.168.2.200. So why cant i connect to this sucka???

Thanks as always

FYI: SSh is bound to both cards so thats not the problem
tcp 0 0 10.0.0.8:22 0.0.0.0:* LISTEN 591/sshd
tcp 0 0 192.168.2.2:22 0.0.0.0:* LISTEN 591/sshd

logfile shows:
Jan 19 19:10:23 me kernel: eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:B00:78:92:07, I/O at 0xe
8c0, IRQ 16.
Jan 19 19:10:23 me kernel: Receiver lock-up bug exists -- enabling work-around.
Jan 19 19:10:23 me kernel: Board assembly 07195d-000, Physical connectors present: RJ45
Jan 19 19:10:23 me kernel: Primary interface chip i82555 PHY #1.
Jan 19 19:10:23 me kernel: General self-test: passed.
Jan 19 19:10:23 me kernel: Serial sub-system self-test: passed.
Jan 19 19:10:23 me kernel: Internal registers self-test: passed.
Jan 19 19:10:23 me kernel: ROM checksum self-test: passed (0x04f4518b).
Jan 19 19:10:23 me kernel: Receiver lock-up workaround activated.
Jan 19 19:10:23 me kernel: eth1: OEM i82557/i82558 10/100 Ethernet, 00:02:B3:0A:0B:EE, I/O at 0xdcc0, IRQ
28.
Jan 19 19:10:23 me kernel: Board assembly a08922-002, Physical connectors present: RJ45
Jan 19 19:10:23 me kernel: Primary interface chip i82555 PHY #1.
Jan 19 19:10:23 me kernel: General self-test: passed.
Jan 19 19:10:23 me kernel: Serial sub-system self-test: passed.
Jan 19 19:10:23 me kernel: Internal registers self-test: passed.
Jan 19 19:10:23 me kernel: ROM checksum self-test: passed (0x04f4518b).

:smash:

Are you saying that you can ping 10.0.0.4 even though eth1 isn't enabled? I wonder where that is coming from.

I just remembered some weird problem in the 'ping' command from a recent Redhat version when I was forced to use it (until i replaced it with LFS) (late 6.x or early 7). It couldn't ping something though it should be perfectly ping'able and the ohter way around too. I ended up compiling the netkit-base package from source (where the ping command comes from) after which everything was fine again.

I imagine Redhat has updates for this, so try and find an updated netkit-base rpm from somewhere.

Or download the source and install it yourself.

But being able to ping an interface that's not brought up yet is just weird. Time for a new kernel perhaps

NO,
Im saying that both eth0 and eth1 are able to be pinged. Doesnt matter if 1 is unplugged or not. I can ping both interfaces and can only connect to eth1.Why can i ping eth0 and not connect? I dont even know where to look

Do you have a firewall enabled that might be blocking the connection attempts to eth0?

firewall is disabled. All i have to do is disable eth1 and then i can connect to it eth0.

Very wierd..I guess i just dont know what im doing