From: chuck <chuck@gelm.net>
To: "Chadha, Devesh" <devesh.chadha@lehman.com>
Cc: 'Ray Olszewski' <ray@comarre.com>, linux-newbie@vger.kernel.org
Subject: Re: 2 NIC cards not talking
Date: Wed, 21 Jan 2004 20:24:14 -0500 [thread overview]
Message-ID: <400F263E.F61E86FD@gelm.net> (raw)
In-Reply-To: 5F84A09ECDD5D411973000508BE32470266024F5@exnyc07.lehman.com
Hi, Chadha:
Originally, you said:
> I have a linux box with 2 NIC cards, both are properly configured.
> Both are on the same subnet, but still don't ping to one another!!
You do not show how you attempt the 'ping',
nor the error message.
Please show exact ping command attempt.
I was hoping for something like:
----------------------------------------------------------
gelmce@web:~$ ping -c 4 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 octets data
64 octets from 192.168.0.1: icmp_seq=0 ttl=127 time=1.6 ms
64 octets from 192.168.0.1: icmp_seq=1 ttl=127 time=1.4 ms
64 octets from 192.168.0.1: icmp_seq=2 ttl=127 time=1.4 ms
64 octets from 192.168.0.1: icmp_seq=3 ttl=127 time=1.3 ms
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.3/1.4/1.6 ms
The above (LAN) IP address is my hardware router, a DLink DI-604.
---------------------------------------------------------
gelmce@web:~$ ping -c 4 68.74.221.208
PING 68.74.221.208 (68.74.221.208): 56 octets data
64 octets from 68.74.221.208: icmp_seq=0 ttl=127 time=1.6 ms
64 octets from 68.74.221.208: icmp_seq=1 ttl=127 time=1.4 ms
64 octets from 68.74.221.208: icmp_seq=2 ttl=127 time=1.4 ms
64 octets from 68.74.221.208: icmp_seq=3 ttl=127 time=1.4 ms
--- 68.74.221.208 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.4/1.4/1.6 ms
------------------------------------------------------------
The above is the IP address that my ISP gives my router.
So, again, exactly how does 'ping' fail?
Chuck
"Chadha, Devesh" wrote:
>
> Well my reason for not giving is that it is a public IP and does not have
> any firewalls in place. This exposes my server much more to unauthorized
> "visit"
>
> Anyway...lets get down to getting this done.
>
> I am on RH Linux 8
> uname -a is Linux 2.4.18
> netstat -nr gives
> 192.168.1.0 0.0.0.0 255.255.255.0 U
> eth1
> xxx.xxx.xxx.0 0.0.0.0 255.255.255.0 U eth0
> 127.0.0.1 0.0.0.0 255.0.0.0
> U lo
> 0.0.0.0 xxx.xxx.xxx.1 0.0.0.0 UG eth0
>
> ifconfig gives me that eth0, eth1 and lo are correctly configured.
>
> ip_forward gives a "1"
>
> What do the gurus say???
-
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 1:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 0:32 2 NIC cards not talking Chadha, Devesh
2004-01-22 1:24 ` 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
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
[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=400F263E.F61E86FD@gelm.net \
--to=chuck@gelm.net \
--cc=devesh.chadha@lehman.com \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/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