LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 11-01-2006, 09:35 AM   #1
Shahin
LQ Newbie
 
Registered: Oct 2006
Posts: 6

Rep: Reputation: 0
Problem with second NIC


Hi,

I haveing a problem with second nic in my Debian box.
I did install debian with one nic, evry thing is fine I can ping all the network.
When I did add the second nic (3com3c905B) problem started,
I did add to:
/interfaces:
eth1 auto
eth1 inet static
address 192.168.34.122
netmask 255.255.255.0
gateway:192.168.34.1
and so aan,

but when I attech my network cable from eth0to eth1 I can not ping noware except the eth0, when I ping some publik IP I get the message the the host is unrechebale.

when I look at networking option (network-admin)
I see the eth0 and eth1 are both actevited.
Any Idea what is going on here?
I am newbie in linux world.

Thanks,

Shahin
 
Old 11-02-2006, 02:24 AM   #2
ele0100443
LQ Newbie
 
Registered: Oct 2006
Location: Sokoto, Nigeria
Distribution: RedHat, Mandrake
Posts: 15

Rep: Reputation: 0
Your debian is assuming that you are trying to make a proxy server with your machine, as such you can not connect untill you configure your squid.conf and activate it,
From your post i assume you are not trying to make a proxy server as such here are some options:
1, Remove the second NIC card and continue working with only one card, if you need to change your IP you can do so at your network manager.
2, If you dont want to remove the second NIC card you can go to the network manager and disable the eth1 first, then disable the eth0 second and lastly enable eth1 then you can connect through the second NIC card, but dont do the network restart, becouse if you did that both of the cards are going to be enabled.
With the second option you have to do this any time you start your machine. Or from the network manager you can disable both of the card from starting automatically at startup (or type at the terminal "chkconfig network off" it will disable automatic network startup).
I will advise you if you dont really have to you should take the first option i.e. removing the second network card.
 
Old 11-02-2006, 11:55 PM   #3
hhvv
Member
 
Registered: May 2006
Location: India
Distribution: RHEL,CentOS,BSD,Ubuntu
Posts: 59
Blog Entries: 1

Rep: Reputation: 15
eth0

May i know the configuration of eth0
 
Old 11-03-2006, 04:03 AM   #4
Shahin
LQ Newbie
 
Registered: Oct 2006
Posts: 6

Original Poster
Rep: Reputation: 0
Hi,

Thanks for reply,

Let me tell u that I do't want to use the debain as a proxy server, rather I would like to use this box as a router in my network. Any Idea how should I do this?


This is the etho configuration:
eth0 auto
eth0 inet static
address 192.168.34.122
netmask 255.255.255.0
gateway:192.168.34.1
and so aan,

Thanks,

Shahin
 
Old 11-03-2006, 07:35 AM   #5
Oliv'
Senior Member
 
Registered: Jan 2004
Location: Montpellier (France)
Distribution: Gentoo
Posts: 1,014

Rep: Reputation: 36
Hello,

what about routing tables ?
have you tried to "down" eth0 with "ifdown eth0" command ?

Oliv'
 
Old 11-03-2006, 05:08 PM   #6
osvaldomarques
Member
 
Registered: Jul 2004
Location: Rio de Janeiro - Brazil
Distribution: Conectiva 10 - Conectiva 8 - Slackware 9 - starting with LFS
Posts: 519

Rep: Reputation: 34
I guess this is the problem that prevents me from using debian and its descendents.
It doesn't respect your setup, even when you use different nic chipsets and configure /etc/modprobe.conf or /etc/modprobe.d/aliases, to specify which nic you want for each ethernet interface.

Instead of the other distribution families, as Red Hat and Slackware, where you configure ethernet when entering run level 3, controlled by the init scripts, debian configures the nics at level 1, using hotplug, when it is recognizing installed hardware. So, the eth0 will be the first recognized nic, eth1 will be the second, etc.

I made an script to be used when it enters multi-user mode but it doesn't prevent the timeout when, for the first time the nic is wrongly configured. If you want to try it, I will post the script.

By the way, reading the previous posts, you reported same ip addresses for eth0 and eth1. Is this correct?
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Bi-NIC problem mstrswrd06 Linux - Networking 1 09-09-2006 04:42 PM
nic problem tonybaloney Slackware 6 10-27-2005 09:51 PM
NIC problem? Please help. wildcardmy Linux - Newbie 3 01-27-2005 09:53 PM
2 External Nic, 1 Internal Nic Router Problem trevanda Linux - Networking 0 10-13-2004 01:20 AM
3 nic problem, 1 nic don't work ldp Linux - Networking 3 07-20-2004 12:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 11:58 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration