From: pa3gcu <pa3gcu@zeelandnet.nl>
To: Beolach <beolach@comcast.net>, chuck <chuck@gelm.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: 2 NIC cards not talking
Date: Fri, 23 Jan 2004 07:33:48 +0100 [thread overview]
Message-ID: <200401230733.48137.pa3gcu@zeelandnet.nl> (raw)
In-Reply-To: <40109D5D.2060708@comcast.net>
On Friday 23 January 2004 05:04, Beolach wrote:
> chuck wrote:
> > [snip]
> >
> > 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. :-|
>
> The -I option doesn't take an interface name (ie eth0), but rather the
> IP address (ie 192.168.0.1) assigned to the interface.
Get your facts right, it does take an interface name as option.
From the manual page of ping;
-I interface address
Set source address to specified interface address. Argument may be numeric IP
address or name of device. When pinging IPv6 link-local address this option
is required.
root@localhost:/# ping -I eth0 192.168.10.23
PING 192.168.10.23 (192.168.10.23) from 192.168.10.15 eth0: 56(84) bytes of
data.
64 bytes from 192.168.10.23: icmp_seq=1 ttl=255 time=0.151 ms
64 bytes from 192.168.10.23: icmp_seq=2 ttl=255 time=0.148 ms
64 bytes from 192.168.10.23: icmp_seq=3 ttl=255 time=0.153 ms
Now if i try that from my router then i get the same as Chuck gets, why it is
i dont know and to be honest i dont really care as i do not see the point in
using the -l option in this case period.
Now if you explain your problem AND show us the configuration you use "To the
letter" then maybe someone here can help you to solve your problem.
The examples i sent you and the most explanatory mail from Ray should have
given you enough infomation to have solved it anyway.
> Conway S. Smith
>
--
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
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 6:33 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
2004-01-23 4:04 ` Beolach
2004-01-23 6:33 ` pa3gcu [this message]
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=200401230733.48137.pa3gcu@zeelandnet.nl \
--to=pa3gcu@zeelandnet.nl \
--cc=beolach@comcast.net \
--cc=chuck@gelm.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