Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having some problems getting the second ethernet card to work in my desktop.
It's a 3com 3c905tx card and is accurately recognized by kudzu. I'm running fedora core 2 kernel 2.6.8.1
lsmod reports that the card is using the 3c59x module. upon calling ifconfig, the following is reported for eth1:
Code:
eth1 Link encap:Ethernet HWaddr (hidden)
inet6 addr: fe80::260:8ff:fecd:fa20/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:4 carrier:4
collisions:0 txqueuelen:1000
RX bytes:6778 (6.6 Kb) TX bytes:0 (0.0 b)
Interrupt:22 Base address:0xdec0
the problem is that the card is not accepting DHCP for some reason. The card works PERFECTLY in windows xp in the same computer.
Code:
sohmc@bart:/home/sohmc# dhclient eth1
Internet Software Consortium DHCP Client V3.0.1rc12
Copyright 1995-2002 Internet Software Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
sit0: unknown hardware address type 776
sit0: unknown hardware address type 776
Listening on LPF/eth1/00:60:08:cd:fa:20
Sending on LPF/eth1/00:60:08:cd:fa:20
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Any help would be appreciated. DHCP works for the on-board ethernet card and works for the rest of the network.
Hmmm.... networks are can be annoying sometimes (I've had plenty of cases where they were ) Other than asking you to (double) check whether all the cables are plugged in correctly, I can't really say much, but here goes:
Does this command do anything for you # ifup eth1?
Have you tried doing the # dhclient eth1 more than once in a row? That solved the problem for me sometimes, because of some unknown reason my router just didn't initiate a connection.
Are both ethernets connected to the same router? Does the first one get initialized on boot, and the second one (like.. do you have to do ifconfig eth1 up)?
Originally posted by student04
Does this command do anything for you # ifup eth1?
Code:
sohmc@bart:/home/sohmc# ifup eth1
Determining IP information for eth1... failed.
Quote:
Originally posted by student04
Have you tried doing the # dhclient eth1 more than once in a row? That solved the problem for me sometimes, because of some unknown reason my router just didn't initiate a connection.
I have tried running dhclient several times before giving up. The link light on the card flickers when it sends it's broadcast message.
Quote:
Originally posted by student04
Are both ethernets connected to the same router? Does the first one get initialized on boot, and the second one (like.. do you have to do ifconfig eth1 up)? [/B]
Well, yes and no. The goal is for me to set up an Internet router with my server. To test the ethernet card, I unplugged the cable from my on-board network card (eth0) and plugged it into my PCI 3x905 card (eth1). I should admit, a few times when I ran `/etc/init.d/network restart`, when initializing eth1, I got some strange output. After a good restart, it didn't do that anymore.
Both network cards are set up to be started on-boot. I have the same problems: IP address is not given.
Oh, here is another interesting fact. I gave eth1 a defined IP address and it cannot ping anything.
Thanks for your help student04. Do you have any other suggestions I could try?
A couple other things you might try are:
-- Release the IP from within Microsoft Windows before you boot into Linux
-- Make sure you're powering down, not just rebooting, when you switch OS.
Originally posted by DavidPhillips Does it work with a static ip?
nope. Just sits there, not pinging... I mean, eth1 will say it has an IP address, but try pinging something and it says something along the lines of "192.168.1.50: destination unreachable."
Quote:
Originally posted by rbochan A couple other things you might try are:
-- Release the IP from within Microsoft Windows before you boot into Linux
-- Make sure you're powering down, not just rebooting, when you switch OS.
The ethernet card works PERFECTLY out of the box in windows. I get an IP address and everything. I have powered down, unplugged, waited 2-3 minutes, powered up repeatedly.
I assume at this point that all hope is loss and I should go out and buy another card.
The thing that caught my eye was the card state, UP BROADCAST MULTICAST.
If you check your other nics with ifconfig or whatever, you'll probably see that they also say 'RUNNING'........right ?
So, it sounds like the card doesn't detect a carrier.
Question: Does the card have other connectors, like a BNC conecter. (other connecters apart from the ethernet RJ-45 connection) ??
If so, it is possible that it is waiting for something to happen there, and not listening on the RJ-45 port.
I believe there is a driver option to set the card to use just the RJ-45 connection, but i haven't found it yet.
I have a problem with a 3c590C card using the same driver.
Its fixed ip address.
If the other end of the line is operational when the machine is powerd on, the card works and shows state UP BROADCAST MULTICAST RUNNING.
Otherwise, it shows state UP BROADCAST MULTICAST.
When this is the case, after bringing the nic down and up again (sometimes a few times in a row) with "ifconfig eth1 down ; ifconfig eth1 up",
a following "ifconfig eth1" call on it's own shows the card is in state UP BROADCAST MULTICAST RUNNING, and it works.
If the cable is unplugged or the other machine turned off, the RUNNING flag goes off eventually, and the nic needs to be brought down and up again (as above) with the cable in and the other machine on before it works again.
Somebody suggested that the negotiation on these cards was poor.
However, another chap suggested that when the signal goes down on the RJ-45 connection, the card switchs over to listening on the BNC connection forever thereafter. Hence why the ehternet only worked again when it was brought down and up.
I'd be interested to hear if this is your problem. Try it with a static ip.
Also, i'd be interested to hear if you or anybody else finds out or knows the driver option to give here so that only the ethernet RJ-45 connection on this card is used.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
) Other than asking you to (double) check whether all the cables are plugged in correctly, I can't really say much, but here goes:
