From: chuck <chuck@gelm.net>
To: "Chadha, Devesh" <devesh.chadha@lehman.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: 2 NIC cards not talking
Date: Thu, 22 Jan 2004 19:52:17 -0500 [thread overview]
Message-ID: <40107041.6DDDE143@gelm.net> (raw)
In-Reply-To: 5F84A09ECDD5D411973000508BE3247026602500@exnyc07.lehman.com
Hi, Devesh:
I think 'destination host unreachable' is a routing problem.
I think that then no packets are transmitted.
If true, ping would not run and there is no ping failure.
I think we are done with your original problem of 'ping' failure.
I am guessing, because you never reported the output of
ifconfig eth0, eth1, lo
only that they were 'configured correctly'.
Is eth0 == external network (internet?)?
Is eth1 == internal network 192.168.1.1?
If yes, why would they ping each other?
I see no reason for your internal NIC to 'talk to' your external NIC.
I see no reason for your external NIC to 'talk to' your internal NIC.
I think the two NICs should never see each others packets without
passing through the router host.
From your previous 'netstat -nr' report,
from that host,
if you 'ping -c 4 192.168.1.x'
the host will route the packets to eth1;
if you ping any other address
the host will route the packets to eth0.
OBTW, when I
ping -I eth0 192.168.1.1
ping: bad interface address 'eth0'
is what I get. I do have an eth0 device. :-|
HTH, Chuck
"Chadha, Devesh" wrote:
>
> The name is Devesh.
>
> I have already answered the question in an earlier email. However, once
> again for your convenience,
>
> Ping -I eth0 192.168.1.1 gives Destination host unreachable.
> Ping -I eth1 xxx.xxx.xxx.xxx also gives Destination host unreachable.
>
> So pinging from eth0 to ip of eth1 and vice versa give dest host
> unreachable.
>
> Pinging from eth1 to external gateway also gives dest host unreachable.
>
> Let me know if u need more info
>
> Regards,
> Devesh
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-01-23 0:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 21:39 2 NIC cards not talking Chadha, Devesh
2004-01-23 0:52 ` chuck [this message]
2004-01-23 4:04 ` Beolach
2004-01-23 6:33 ` pa3gcu
2004-01-23 16:54 ` Ray Olszewski
2004-01-23 10:55 ` chuck
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 13:52 Chadha, Devesh
[not found] <5F84A09ECDD5D411973000508BE32470266024F6@exnyc07.lehman.co m>
2004-01-22 5:56 ` Ray Olszewski
2004-01-22 2:31 Chadha, Devesh
2004-01-22 4:02 ` Beolach
2004-01-22 4:16 ` chuck
2004-01-22 4:28 ` Beolach
2004-01-22 4:32 ` Beolach
2004-01-22 21:23 ` chuck
[not found] <5F84A09ECDD5D411973000508BE32470266024F5@exnyc07.lehman.co m>
2004-01-22 1:35 ` Ray Olszewski
2004-01-22 0:32 Chadha, Devesh
2004-01-22 1:24 ` chuck
[not found] <5F84A09ECDD5D411973000508BE32470266024F2@exnyc07.lehman.co m>
2004-01-22 0:01 ` Ray Olszewski
2004-01-21 21:52 Chadha, Devesh
[not found] <5F84A09ECDD5D411973000508BE32470266024E7@exnyc07.lehman.co m>
2004-01-21 17:08 ` Ray Olszewski
2004-01-21 16:47 Chadha, Devesh
2004-01-21 15:23 Chadha, Devesh
2004-01-21 16:38 ` pa3gcu
2004-01-21 16:47 ` Juan Facundo Suárez
2004-01-21 15:13 Juan Facundo Suárez
2004-01-21 14:25 Chadha, Devesh
2004-01-21 21:44 ` chuck gelm net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40107041.6DDDE143@gelm.net \
--to=chuck@gelm.net \
--cc=devesh.chadha@lehman.com \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox