nothing after eth0 with more than 1 network card
Hi. Our server needs 2 ethernet cards, on internet and one local. I can get either the local lan or the internet by swapping cables but not both at the same time. Swapping the cards still only gives me eth0 active. Yast (version with 8.0) identifies both no problem and the little green lights are on. Adding a third and fourth card results in the same problem. Any ideas anyone? Is there anyting in Bios I should know about? This is a new machine with a new install of 8.0. Thanks, Steve.
Hi. Our server needs 2 ethernet cards, on internet and one local. I can get
either the local lan or the internet by swapping cables but not both at the same time. Swapping the cards still only gives me eth0 active. Yast (version with 8.0) identifies both no problem and the little green lights are on. Adding a third and fourth card results in the same problem. Any ideas anyone? Is there anyting in Bios I should know about? This is a new machine with a new install of 8.0. Thanks, Steve.
What network card model ? If it is ISA card, you must configure I/O and IRQ BEFORE configuration, run the config program for the card and set up one I/O and one IRQ diferent to each one ! If is PCI card can be bios, put them in "auto" in plug'play section abd try again . Fábio Rabelo
For pci cards check they are visible to the system with lspci For isa cards try using isapnp or check what are the jumpers in the card to see IRQ. Usually you would like to have different IRQ for each card. When booting your computer you shall see a BIOS message with a list of devices... check both cards are there. What is the output of ifconfig -a ? What is the config for eth0 and eth1 in your /etc/modules? If you can switch from eth0 to eth1 and back.... What you mean switch cable? Are you able to connect a crossed cable to eth0 and ping it? The same way for eth1? But no connectivity eth0 - eth1? My gut feeling is your hardware is well configured but your network not. Check what ip address and mask are you using for each NIC. Check how is routing configured... It may be pretty normal that you can not ping eth1 from eth0 if your network is not well configured. Are you trying ipmasquerading? Check that as well. Regards, Pep Serrano. On Wednesday 08 May 2002 18:35, steve wrote:
Hi. Our server needs 2 ethernet cards, on internet and one local. I can get either the local lan or the internet by swapping cables but not both at the same time. Swapping the cards still only gives me eth0 active. Yast (version with 8.0) identifies both no problem and the little green lights are on. Adding a third and fourth card results in the same problem. Any ideas anyone? Is there anyting in Bios I should know about? This is a new machine with a new install of 8.0.
Hi. Sorry I didn't explain myself very well. We have a simple server with 2 ethernet cards. One is eth0 and the other eth1, for internet and local lan respectively. Either I can have internet on the server when the internet cable is in eth0 or I can have the local lan (Samba) when the hub cable is in eth0. The card in the second slot as eth1 does nothing. In other words the lan can't see the internet whan the internet line is in eth0 and the local lan via the hub is in eth1, which is what I want. I have another (0ur old server, glad I kept it!) server working perfectly with this setup. Internet comes in on eth0 and out to the lan on eth1. Both cards are PCI. Both cards are recognised by the bios and in Yast. I have swapped the cards from one slot to the other to see if they are both working and they are. The setup is the same on both machines. Shouldn't the bus be available to both cards no matter what their position on the motherboard? There is no firewall on the new machine (although I've tried with it too) and both have squid with exactly the same configuration. I have tried with 8.0 and 7.3 new installs and have stayed with 7.3 as then I have a direct comparison between the machine that works and the one that doesn't. Going crazy. Please tell me it's a motherboard problem! Steve. On Thursday 09 May 2002 11:35, Pep Serrano wrote:
For pci cards check they are visible to the system with lspci For isa cards try using isapnp or check what are the jumpers in the card to see IRQ. Usually you would like to have different IRQ for each card.
When booting your computer you shall see a BIOS message with a list of devices... check both cards are there.
What is the output of ifconfig -a ? What is the config for eth0 and eth1 in your /etc/modules?
If you can switch from eth0 to eth1 and back.... What you mean switch cable? Are you able to connect a crossed cable to eth0 and ping it? The same way for eth1? But no connectivity eth0 - eth1? My gut feeling is your hardware is well configured but your network not. Check what ip address and mask are you using for each NIC. Check how is routing configured... It may be pretty normal that you can not ping eth1 from eth0 if your network is not well configured. Are you trying ipmasquerading? Check that as well.
Regards, Pep Serrano.
On Wednesday 08 May 2002 18:35, steve wrote:
Hi. Our server needs 2 ethernet cards, on internet and one local. I can get either the local lan or the internet by swapping cables but not both at the same time. Swapping the cards still only gives me eth0 active. Yast (version with 8.0) identifies both no problem and the little green lights are on. Adding a third and fourth card results in the same problem. Any ideas anyone? Is there anyting in Bios I should know about? This is a new machine with a new install of 8.0.
When booting your computer you shall see a BIOS message with a list of devices... check both cards are there.
What is the output of ifconfig -a ? What is the config for eth0 and eth1 in your /etc/modules?
Hi Here is the output of ifconfig -a:
eth0 Link encap:Ethernet HWaddr 00:10:5A:E7:AD:51 inet addr:192.168.0.22 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::210:5aff:fee7:ad51/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:103 errors:0 dropped:0 overruns:0 frame:0 TX packets:192 errors:0 dropped:0 overruns:0 carrier:34 collisions:0 txqueuelen:100 RX bytes:72299 (70.6 Kb) TX bytes:21480 (20.9 Kb) Interrupt:18 Base address:0xa000 eth1 Link encap:Ethernet HWaddr 00:50:BF:D2:E7:02 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::250:bfff:fed2:e702/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:540 (540.0 b) TX bytes:348 (348.0 b) Interrupt:21 Base address:0xd000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:282 errors:0 dropped:0 overruns:0 frame:0 TX packets:282 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:81713 (79.7 Kb) TX bytes:81713 (79.7 Kb) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) -------------------------------- Yast recognises the cards: 3Com Corporation 3C905B Fast Etherlink XL 10/100 Configured as eth0 with address 192.168.0.22 Realtek Semiconductor Co., Ltd. RT8139 Configured as eth1 with address 192.168.0.1 but has added nothing to /etc/modules.conf as it usually did with 7.3. I have done a: modprobe 3c59x modprobe 8139too but still I can only get anything out or into the eth0. I have added alias eth0 3c59x alias eth1 8139too to /etc/modules.conf and rebooted. Still nothing from eth1 What am I mising? Thanks, Steve.
-------------------------------- Yast recognises the cards:
3Com Corporation 3C905B Fast Etherlink XL 10/100 Configured as eth0 with address 192.168.0.22 Realtek Semiconductor Co., Ltd. RT8139 Configured as eth1 with address 192.168.0.1
but has added nothing to /etc/modules.conf as it usually did with 7.3. I have done a: modprobe 3c59x modprobe 8139too but still I can only get anything out or into the eth0.
I have added alias eth0 3c59x alias eth1 8139too to /etc/modules.conf and rebooted. Still nothing from eth1
What am I mising?
A proper routing table. What is the output of "route -n"? Do you know from your ISP what is the IP number of their gateway? -- Rafael
On Friday 10 May 2002 13:39, Rafael E. Herrera wrote:
-------------------------------- Yast recognises the cards:
3Com Corporation 3C905B Fast Etherlink XL 10/100 Configured as eth0 with address 192.168.0.22 Realtek Semiconductor Co., Ltd. RT8139 Configured as eth1 with address 192.168.0.1
but has added nothing to /etc/modules.conf as it usually did with 7.3. I have done a: modprobe 3c59x modprobe 8139too but still I can only get anything out or into the eth0.
I have added alias eth0 3c59x alias eth1 8139too to /etc/modules.conf and rebooted. Still nothing from eth1
What am I mising?
A proper routing table. What is the output of "route -n"?
Do you know from your ISP what is the IP number of their gateway?
Hi and many thanks. Of course I will get the information from the route -n and the IP. It's just that we've never had to do this before. We just put in 192.168.0.254 as a dummy gateway in Yast and all our previous servers have worked fine. But that was under 7.3. has this changed for 8.0? Our ISP confirms this and says that we don't need it as our ADSL router does it for us. Back tomorrow with the route -n. Meanwhile, are my alias and modprobes above correct? Thanks, Steve.
steve wrote:
A proper routing table. What is the output of "route -n"?
Do you know from your ISP what is the IP number of their gateway?
Hi and many thanks. Of course I will get the information from the route -n and the IP. It's just that we've never had to do this before. We just put in 192.168.0.254 as a dummy gateway in Yast and all our previous servers have worked fine. But that was under 7.3. has this changed for 8.0? Our ISP confirms this and says that we don't need it as our ADSL router does it for us. Back tomorrow with the route -n. Meanwhile, are my alias and modprobes above correct?
If you see both eth interfaces when you type ifconfig, then I would assume they are OK. Remember that the first network card you load becomes eth0, and the second becomes eth1. For the machines on the 192.168.0.x network, you don't need a gateway. For the machine that has the connection to the ISP, the default gateway should be the one provided by them. I would suggest you use an IP number different than your local lan network. For example set eth0 to 192.168.100.22 and netmask 255.255.255.0. Set eth1 to 192.168.0.1 and netmask 255.255.255.0 -- Rafael
On Friday 10 May 2002 19:07, Rafael E. Herrera wrote:
steve wrote:
A proper routing table. What is the output of "route -n"?
Do you know from your ISP what is the IP number of their gateway?
Hi and many thanks. Of course I will get the information from the route -n and the IP. It's just that we've never had to do this before. We just put in 192.168.0.254 as a dummy gateway in Yast and all our previous servers have worked fine. But that was under 7.3. has this changed for 8.0? Our ISP confirms this and says that we don't need it as our ADSL router does it for us. Back tomorrow with the route -n. Meanwhile, are my alias and modprobes above correct?
If you see both eth interfaces when you type ifconfig, then I would assume they are OK. Remember that the first network card you load becomes eth0, and the second becomes eth1.
For the machines on the 192.168.0.x network, you don't need a gateway.
For the machine that has the connection to the ISP, the default gateway should be the one provided by them. I would suggest you use an IP number different than your local lan network. For example set eth0 to 192.168.100.22 and netmask 255.255.255.0. Set eth1 to 192.168.0.1 and netmask 255.255.255.0
Here is the routing table of our present server: the one that works with 7.3: Destination Gateway Genmask Flags MetricRef Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0 On our new machine under 8.0 we have tried the same but only eth0 works. the other card does nothing. So we tried your suggestion: Destination Gateway Genmask Flags MetricRef Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0 Now I can get Samba out through to the local network from eth1 and internet *only* on the server but not on the clients. Progress! Our ISP has given me the IP address of the router as 80.24.171.55/192 but has told me not to include it in the setup as our ADSL modem takes care of it for us. What is the /192 bit? Where would I enter this in Yast2 if I were to try it? Thanks for your patience. Steve.
steve wrote:
On Friday 10 May 2002 19:07, Rafael E. Herrera wrote:
steve wrote:
A proper routing table. What is the output of "route -n"?
Do you know from your ISP what is the IP number of their gateway?
Hi and many thanks. Of course I will get the information from the route -n and the IP. It's just that we've never had to do this before. We just put in 192.168.0.254 as a dummy gateway in Yast and all our previous servers have worked fine. But that was under 7.3. has this changed for 8.0? Our ISP confirms this and says that we don't need it as our ADSL router does it for us. Back tomorrow with the route -n. Meanwhile, are my alias and modprobes above correct?
If you see both eth interfaces when you type ifconfig, then I would assume they are OK. Remember that the first network card you load becomes eth0, and the second becomes eth1.
For the machines on the 192.168.0.x network, you don't need a gateway.
For the machine that has the connection to the ISP, the default gateway should be the one provided by them. I would suggest you use an IP number different than your local lan network. For example set eth0 to 192.168.100.22 and netmask 255.255.255.0. Set eth1 to 192.168.0.1 and netmask 255.255.255.0
Here is the routing table of our present server: the one that works with 7.3: Destination Gateway Genmask Flags MetricRef Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
On our new machine under 8.0 we have tried the same but only eth0 works. the other card does nothing. So we tried your suggestion:
Destination Gateway Genmask Flags MetricRef Use Iface 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 0.0.0.0 192.168.0.254 0.0.0.0 UG 0 0 0 eth0
Now I can get Samba out through to the local network from eth1 and internet *only* on the server but not on the clients. Progress!
Revise the network configuration on your samba clients. Set their IP number to one of 192.168.0.x, netmask 255.255.255.0 and gateway the same IP as your server or empty, try both. Do not use 192.168.0.0 or 192.168.0.255 as IP numbers. Don't forget to write down the old values, just in case.
Our ISP has given me the IP address of the router as 80.24.171.55/192 but has told me not to include it in the setup as our ADSL modem takes care of it for us. What is the /192 bit? Where would I enter this in Yast2 if I were to try it? Thanks for your patience.
The /192 sounds wrong. One sometimes can use this format 192.168.0.0/16 to be equivalent to 192.168.0.0/255.255.0.0, that is, the first 16 bits (the number of 1's in 255.255 written in binary form) of the IP number specify the network part of an IP address, so the possible values are 1 through 32. -- Rafael
Hi all, i just installed gpp under Suse 8.0. seems to me that this C++ compiler dows not work accordingly. as a test: coba2.cc is a well-functioning program (run previously under 7.2) g++ -Wall -o coba2 coba2.cc coba2 bash: coba2: command not found the flwgs hv been installed as well: autoconf, automake, binutils, gcc, glibc-devel, libgpp, gppinfo, gppshare. Could someone help me please? Regards, Setyo Nugroho -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
Do you have . in your path. Normally, the dot (.) is not placed in your patch by default. Try ./coba2 On 10 May 2002 at 16:01, Setyo Nugroho wrote:
Hi all, i just installed gpp under Suse 8.0. seems to me that this C++ compiler dows not work accordingly.
as a test: coba2.cc is a well-functioning program (run previously under 7.2)
g++ -Wall -o coba2 coba2.cc coba2 bash: coba2: command not found
the flwgs hv been installed as well: autoconf, automake, binutils, gcc, glibc-devel, libgpp, gppinfo, gppshare.
Could someone help me please?
Regards, Setyo Nugroho
-- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
-- Jerry Feldman Portfolio Partner Engineering 508-467-4315 http://www.testdrive.compaq.com/linux/ Hewlett-Packard Company 200 Forest Street MRO1-3/F1 Marlboro, Ma. 01752
participants (6)
-
Fábio Rabelo -
Jerry Feldman -
Pep Serrano -
Rafael E. Herrera -
Setyo Nugroho -
steve