From: chuck <chuck@gelm.net>
To: Beolach <beolach@comcast.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: 2 NIC cards not talking
Date: Thu, 22 Jan 2004 16:23:45 -0500 [thread overview]
Message-ID: <40103F61.C9C1687A@gelm.net> (raw)
In-Reply-To: 400F5151.1000305@comcast.net
Hi, Beolach:
Thanks.
I asked, but Chadha never reported his (exact) 'ping' usage,
nor the (exact) error message.
:-|
Chuck
Beolach wrote:
>
> ping has a -I option that allows you to specify the source interface. I
> haven't used this option myself, but I would guess Chadha used some
> thing like this: 'ping -I eth0 192.168.1.1'.
>
> Conway S. Smith
>
> chuck wrote:
> > Dear Chadha:
> >
> > In (4.) & (5.)...
> >
> > I know how to ping from a host with an 'eth0' or 'eth1' device.
> > I do not know how to ping from 'eth0' or from 'eth1'.
> >
> > Sorry, I cannot help.
> >
> > Chuck
> >
> > "Chadha, Devesh" wrote:
> > <snip>
> >
> >
> >>4.Pinging 192.168.1.1 from eth0 gave destnation host unreachable and pinging
> >>xxx.xxx.xxx.xxx from eth1 gave the same.
> >>
> >>5. I can connect to internet using eth0 since I can browse the internet. I
> >>can also ping the gateway from eth0
> >
> > <snip>
> >
-
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-22 21:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 2:31 2 NIC cards not talking 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-22 21:39 Chadha, Devesh
2004-01-23 0:52 ` chuck
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
2004-01-22 13:52 Chadha, Devesh
[not found] <5F84A09ECDD5D411973000508BE32470266024F6@exnyc07.lehman.co m>
2004-01-22 5:56 ` Ray Olszewski
[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=40103F61.C9C1687A@gelm.net \
--to=chuck@gelm.net \
--cc=beolach@comcast.net \
--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