Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Got a problem on a SuSe 8.2 box. I'm trying to set it up as a firewall, using Yast's built in firewall feature. So this spare computer should be a hardware firewall. If I understand this correctly, you set up a computer with two ethernet cards. Run a wire from the wall to eth0, then run another from eth1 to your internal network.
I've got one Ethernet card working on this computer, but only one. If I enter ifconfig, I get a readout for the loopback and for eth0. During bootup, the computer initializes eth0 but not eth1. It won't detect the card, and acts as though it doesn't exist.
I entertained the idea that the card was broken, but I tried this same thing inside another machine. SuSe autodetected the card just fine. I even switched the one working card to a different slot on the motherboard. Since it still worked, I know that the slot is fine.
How can I get this thing to work with two network cards? How can I get eth1 to work?
First, let's confirm that the second card is being seen. What are the results of running:
Code:
lspci
This command simply lists what devices are present in the PCI slots. Second, please post the make and model of both cards you're using, and indicate which is eth0 and which is eth1. Another likely issue could be that your eth1 card requires a kernel module that is not being loaded. Please also post the results of running:
Code:
lsmod
That command will list which kernel modules have been loaded, and if we know what NIC you're using, chances are good that someone will know which module is needed to support it.
Finally, have you tried simply bouncing eth1?
Code:
ifconfig eth1 down
ifconfig eth1 up
ifconfig
These commands will bring down the eth1 interface, then bring it back up, then list what interface connections you've got.
Note: the above is not intended to be a solution (although it may resolve the problem) but rather as a useful first step in diagnosing what a few likely issues could be. Good luck with it. -- J.W.
you can check if it's recognized by looking at "ifconfig -a". this will show all your interfaces (up or not).
if it's not there add the following kernel parameter to your prompt at bootup:
ether=0,0,eth0 ether=0,0,eth1
..to tell the kernel that there are two cards (be sure both cards are supported).
look at the ethernet-howto.
we need more information. send in relevant lines from the commands J.W. mentioned.
Originally posted by J.W.
First, let's confirm that the second card is being seen. What are the results of running:
Code:
lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo VP] (rev 47)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 02)
00:07.3 Bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 10)
00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22)
00:0b.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
01:00.0 VGA compatible controller: S3 Inc. Trio 64 3D (rev 01)
This command simply lists what devices are present in the PCI slots. Second, please post the make and model of both cards you're using, and indicate which is eth0 and which is eth1.
Okay.
eth0 --> 3Com 3C905C-TX Fast Etherlink for PC Management NIC
eth1 --> Kingston KNE100TX Fast Ethernet
Also, and I don't know if this is relevant, but they have two different statically assigned IP addresses.
Another likely issue could be that your eth1 card requires a kernel module that is not being loaded. Please also post the results of running:
Code:
lsmod
That command will list which kernel modules have been loaded, and if we know what NIC you're using, chances are good that someone will know which module is needed to support it.
These commands will bring down the eth1 interface, then bring it back up, then list what interface connections you've got.
Tried that. No good. Doesn't an rcnetwork restart accomplish the same goal?
I also want to clarify that ifconfig will show both Ethernet cards (it wouldn't before, but I got that fixed) and both are autodetected. I can ping from eth0 to eth1 and vice versa. I can ping from eth0 to the outside, but I cannot ping from eth1 to the outside.
Note: the above is not intended to be a solution (although it may resolve the problem) but rather as a useful first step in diagnosing what a few likely issues could be. Good luck with it. -- J.W.
I apologize but I am not familiar with SuSe, however, here is how I would do it in RHEL:
Below is a snippet of my /etc/sysctl. I would set IP forwarding to 1
more /etc/sysctl.conf
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.
# Controls IP packet forwarding
net.ipv4.ip_forward = 0
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.