public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: "Juan Facundo Suárez" <facundo.suarez@ensi.com.ar>
To: linux-newbie list <linux-newbie@vger.kernel.org>
Subject: Re: 2 NIC cards not talking
Date: Wed, 21 Jan 2004 13:47:10 -0300	[thread overview]
Message-ID: <004a01c3e03e$368fe520$680410ac@pcinstru1> (raw)
In-Reply-To: 5F84A09ECDD5D411973000508BE32470266024E7@exnyc07.lehman.com

 mmm, the ask is, how are you trying to conect your lan to internet ? using
iptables ?, using squid?

 What the system says if you execute "ifconfig" ?, are both up ?

 You are goingo to need more than a dhcp server to share internet to your
lan. I guess you are goingo to use iptables at least.

 Sorry if i am saying to you, things you just know. May be i don't
understand you. :s

--
Facundo Suárez
Neuquén - Argentina
FDSoft
mail y jabber: faco@fdsoft.com.ar
facundo.suarez@ensi.com.ar

----- Original Message -----
From: "Chadha, Devesh" <devesh.chadha@lehman.com>
To: "'Juan Facundo Suárez'" <facundo.suarez@ensi.com.ar>; "linux-newbie
list" <linux-newbie@vger.kernel.org>
Sent: Wednesday, January 21, 2004 12:23 PM
Subject: RE: 2 NIC cards not talking


| Juan,
|
| Eth0 has the external assigned IP by my ISP. Eth1 has a 192.168.x.x ip
| address. Eth1 acts as the DHCP server for my LAN. My LAN is working fine.
I
| can connect machines to the LAN and even connect one machine to another.
|
| But I cannot get eth1 to talk to eth0. I cannot connect the LAN to the
| internet nor connect to any internal machine from outside!!
|
| Do I need to bridge the 2 NICs ???
|
| Regards,
| Devesh
|
|
| -----Original Message-----
| From: Juan Facundo Suárez [mailto:facundo.suarez@ensi.com.ar]
| Sent: Wednesday, January 21, 2004 10:13 AM
| To: linux-newbie list
| Subject: Re: 2 NIC cards not talking
|
|
| Sorry, i don't understand at all. You say that you have two cards, in the
| same machine, are them in the same subnet ? why don't you put one, wich
| connects to "outside" in one, and the other in another subnet?. I have
| working a firewall/router with iptables, and the card is connected to de
| adsl-modem has 192.168.1.10, and the card to brins internet to the lan has
| 192.168.0.1.
|
|  If you cannot ping from a machine in one subnet, to another in other
| subnet, maybe you need to load the kernel-module wich does that job.
|
| --
| Facundo Suárez
| Neuquén - Argentina
| FDSoft
| mail y jabber: faco@fdsoft.com.ar
| facundo.suarez@ensi.com.ar
|
| ----- Original Message -----
| From: "Chadha, Devesh" <devesh.chadha@lehman.com>
| To: <linux-newbie@vger.kernel.org>
| Sent: Wednesday, January 21, 2004 11:25 AM
| Subject: 2 NIC cards not talking
|
|
| | Hi,
| |
| | 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!!
| |
| | I need to setup the box as the firewall/router that has eth0 set as
| external
| | and eth1 as internal serving as DHCP server to other computers on the
| | network. Both have static IPs assigned to them.
| |
| | Regards,
| | Devesh
| | 6-6859
| |
| |
| | ----------------------------------------------------------------------
| | ----
| ----
| | This message is intended only for the personal and confidential use of
| | the designated recipient(s) named above.  If you are not the intended
| recipient of
| | this message you are hereby notified that any review, dissemination,
| | distribution or copying of this message is strictly prohibited.  This
| | communication is for information purposes only and should not be
| | regarded
| as
| | an offer to sell or as a solicitation of an offer to buy any financial
| | product, an official confirmation of any transaction, or as an
| | official statement of Lehman Brothers.  Email transmission cannot be
| | guaranteed to
| be
| | secure or error-free.  Therefore, we do not represent that this
| information is
| | complete or accurate and it should not be relied upon as such.  All
| | information is subject to change without notice.
| |
| | -
| | 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
|
| -
| 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
|
| --------------------------------------------------------------------------
----
| This message is intended only for the personal and confidential use of the
designated recipient(s) named above.  If you are not the intended recipient
of this message you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited.  This
communication is for information purposes only and should not be regarded as
an offer to sell or as a solicitation of an offer to buy any financial
product, an official confirmation of any transaction, or as an official
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be
secure or error-free.  Therefore, we do not represent that this information
is complete or accurate and it should not be relied upon as such.  All
information is subject to change without notice.
|
| -
| 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
|

-
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

  parent reply	other threads:[~2004-01-21 16:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 15:23 2 NIC cards not talking Chadha, Devesh
2004-01-21 16:38 ` pa3gcu
2004-01-21 16:47 ` Juan Facundo Suárez [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
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: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='004a01c3e03e$368fe520$680410ac@pcinstru1' \
    --to=facundo.suarez@ensi.com.ar \
    --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