linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darío Mariani" <dmarian@fi.uba.ar>
To: "Sim, CT (Chee Tong)" <CheeTong.Sim@rabobank.com>
Cc: 'admin' <linux-admin@vger.kernel.org>,
	"'nate@nateworks.ca'" <nate@nateworks.ca>
Subject: Re: where is my third NIC?
Date: Fri, 26 Jul 2002 13:51:50 -0300	[thread overview]
Message-ID: <3D417E26.7040204@fi.uba.ar> (raw)
In-Reply-To: 1E8992B3CD28D4119D5B00508B08EC5601F7BC5A@sinxsn02.ap.rabobank.com

  I suspect that things are messed up. Check in 
/etc/sysconfig/networking and /etc/sysconfig/network-scripts.

		Darío

Sim, CT (Chee Tong) wrote:
> Thanks for the info, I solved my problem with change three network cards to
> be the same.  
> 
> But I have another issue now.  I can see eth0, eth1, and eth2 when I type
> "ifconfig -a"  and I configured IP for every NIC (different network range).
> But only eth0 is connected to network.  After rebooting, only IP address for
> eth0 stay, but eth1 and eth2 gone.  Why?  Why I can't make it stay?
> 
> [root@linuxfw1 root]# ifconfig -a
> eth0      Link encap:Ethernet  HWaddr 00:10:4B:36:C0:CF
>           inet addr:50.100.100.248  Bcast:50.100.100.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:655 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:70027 (68.3 Kb)  TX bytes:4119 (4.0 Kb)
>           Interrupt:11 Base address:0x2400
> 
> eth1      Link encap:Ethernet  HWaddr 00:10:4B:0E:E9:A5
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:11 Base address:0x2000
> 
> eth2      Link encap:Ethernet  HWaddr 00:10:4B:36:F0:8F
>           BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:11 Base address:0x2480
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:8 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:560 (560.0 b)  TX bytes:560 (560.0 b)
> 
> 
> -----Original Message-----
> From: Dario Mariani [mailto:dmarian@fi.uba.ar] 
> Sent: Wednesday, July 24, 2002 6:47 AM
> To: Sim, CT (Chee Tong)
> Cc: 'admin'
> Subject: Re: where is my third NIC?
> 
>    I had some problems with the redhat-config-network with 2 cards from 
> one brand and a third from another. My solution (did not have time for a 
> correct one) was to use 3 cards of the same brand.
> 
> 		Darío
> 
> Sim, CT (Chee Tong) wrote:
> 
>>Hi..  I just installed RedHat 7.3  in a Pc with 3 NIC cards.  But only two
>>are detected eth0 and eth1.  I am sure three are working one, as I just
>>installed solaris 8 on it before install RedHat 7.3 and solaris 8 detected
> 
> 3
> 
>>cards.  How to make my eth2 appear in my Linux?
>>
>>[root@linux root]# ifconfig eth2 up
>>eth2: unknown interface: No such device
>>
>>CT
>> 
>> 
>>
>>==================================================================
>>De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
>>is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
>>onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en 
>>de afzender direct te informeren door het bericht te retourneren. 
>>==================================================================
>>The information contained in this message may be confidential 
>>and is intended to be exclusively for the addressee. Should you 
>>receive this message unintentionally, please do not use the contents 
>>herein and notify the sender immediately by return e-mail.
>>
>>
>>==================================================================
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> ==================================================================
> De informatie opgenomen in dit bericht kan vertrouwelijk zijn en 
> is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht 
> onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en 
> de afzender direct te informeren door het bericht te retourneren. 
> ==================================================================
> The information contained in this message may be confidential 
> and is intended to be exclusively for the addressee. Should you 
> receive this message unintentionally, please do not use the contents 
> herein and notify the sender immediately by return e-mail.
> 
> 
> ==================================================================
> 
> 



-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2002-07-26 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  5:02 where is my third NIC? Sim, CT (Chee Tong)
2002-07-25 11:23 ` terry white
2002-07-26 16:51 ` Darío Mariani [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-29  1:36 Sim, CT (Chee Tong)
2002-07-25 12:50 Jeffery Myers
2002-07-23 10:24 Sim, CT (Chee Tong)
2002-07-23 16:12 ` Nathan
2002-07-23 22:41 ` Darío Mariani

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=3D417E26.7040204@fi.uba.ar \
    --to=dmarian@fi.uba.ar \
    --cc=CheeTong.Sim@rabobank.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=nate@nateworks.ca \
    /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;
as well as URLs for NNTP newsgroup(s).