Re: Second ethernet card seems to cause networking failure?
On Mon, 25 May 2009 08:37:33 +1200 Chris Bannister mockingb...@earthlight.co.nz wrote: On Fri, May 22, 2009 at 09:25:29AM -0700, Frank Miles wrote: I recently added a second networking card to a hardware-test PC. This elderly machine had been working reasonably well. The second networking card is for eth1, etc., and /sbin/ifconfig shows things as properly connected, with eth0 being the outside interface and eth1 being an internal 192.168.x.x interface for some special internal systems that have absolutely no need to communicate with the outside world, just this one PC. So now you have a gateway? What firewall configuration software are you using? What is the output of cat /etc/network/interfaces The weird thing is that with normal booting configuration, pinging INet addresses fails. This seems to be related to the order in which the interfaces come up: doing ifdown eth1 ; ifdown eth1 ; ifup eth0; ifup eth1 causes pings to fail; but if eth0/eth1 are reversed (bringing up eth0 last), or eth1 is simply suppressed, pinging URLs works (i.e. ping www.debian.org). Sounds to me like both are setting a default gw. The last one takes precendence so if you bring up eth0 last the default gw is set to the outside world, if you bring eth1 last the default gw is in the local network and assuming the dns address is not on the same subnet as eth0 requests are going through the default gateway to eth1 which has no idea what to do with them Have you a local DNS server? Regrettably this last does not entirely solve things - for example, I cannot do system updates: apt-get update fails to connect. Error? times out? unable to contact … ? Eventually, if I play around long enough (killing eth1, killing my firewall - which hasn't changed since before adding the second NIC,...) I can do a system update but it's not entirely clear what the critical steps were to get that working. killing the firewall mmm ... I freely admit that I'm a hardware guy - I don't know much about networking. I don't know much about networking either but if I was asking this question I'd provide at least the config files (see above), exact error messages from logs (if any … if none say so.), exact messages on screen, (if none, say so) Does anyone have a suggestion on where I might look to get this working properly? Without sacrificing eth1? Or at least some better diagnostic[s] to track down where packets are getting lost? Of course, I'd only post to this list after I'd used apt-cache search network test | wc -l and saw that it shows 83 packages which fit that search criteria and see that there is not really anthing useful, ok there is ping, but you've already used that. So I'd try apt-cache search network diagnos | wc -l ok 14, and see … that there is nothing very useful. We're at the mercy of the package maintainers to at least put some decent search terms in the descriptions and not just copy a paragraph off the upstream website or manpage. So I'd state I'd searched the packages and didn't really see anything useful. Also describe the network a bit more -DSL? Is this the first time you are connecting to the net with this machine etc. You may then get a response from someone who sees an anomaly with your setup, and might even help. But, and this is a stab in the dark, I think you have to tell the firewall about your new interface. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Second ethernet card seems to cause networking failure?
Thanks, Adrian. I was sure that it wasn't just the firewall at this point - that it was necessary to kill eth1 to get eth0 fully functional. I was wrong. This is now just a firewall problem. And this is a handcrafted beast, with lotsa rules. I wouldn't dream (well, not yet anyway) of asking anyone else to find the wart. Regrettably, I have a fire to put out - one of the ongoing experiments that we support is in dire need of some hardware we are developing - so I will have to defer that (and some clarification/simplification of the firewall) until after our hardware is out the door. Thanks again! -Frank -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Second ethernet card seems to cause networking failure?
2009/5/28 Frank Miles f...@u.washington.edu: Regrettably, the problem persists - though possibly with a different threshold of sorts, as pinging now seems to work. However- apt-get update still hangs. I have to kill BOTH the firewall and eth1 in order to make this work (not seeming to wait indefinitely for communication). I think the gateway correction is definitely a step in the right direction. Ok, looks like were moving forward. Can you provide the output of iptables -L before and after you kill the firewall. Just to clarify: traffic works as expected with the firewall shut down? What are you using for a firewall configuration? Adrian -- 24x7x365 != 24x7x52 Stupid or bad maths? erno hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Second ethernet card seems to cause networking failure?
2009/5/27 Frank Miles f...@u.washington.edu: Sure, can provide more info... /etc/network/interfaces : auto lo iface lo inet loopback # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth0 inet static address xxx.yyy.zzz.32 network xxx.yyy.zzz.0 netmask 255.255.255.0 broadcast xxx.yyy.zzz.255 gateway xxx.yyy.zzz.100 pre-up /etc/iptables/iptables.sh start post-down /etc/iptables/iptables.sh stop # The secondary network interface auto eth1 #iface eth0 inet dhcp iface eth1 inet static address 192.168.42.100 network 192.168.42.0 netmask 255.255.255.0 #broadcast 192.168.42.255 gateway 192.168.42.100 This here looks wrong, you don't set a default gateway for the local lan. Route will figure it out. If you comment that out restart networking, one of the interfaces (Hopefully eth0) will have a default entry in 'route'. like: caprica:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.0.0 * 255.255.255.0 U 0 00 eth1 211.31.0.0 * 255.255.240.0 U 0 00 eth0 default c211-31-0-1.roc 0.0.0.0 UG0 00 eth0 caprica:~# HTH, Adrian -- 24x7x365 != 24x7x52 Stupid or bad maths? erno hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Second ethernet card seems to cause networking failure?
Following up, particularly on Adrian Levi's suggestion to eliminate the gateway spec in /etc/network/interfaces: Thanks, Adrian! Your idea makes sense. Trying it: it changes the routing table exactly as you described, causing my routing table to match yours (excepting, of course, the specific IP#s). Regrettably, the problem persists - though possibly with a different threshold of sorts, as pinging now seems to work. However- apt-get update still hangs. I have to kill BOTH the firewall and eth1 in order to make this work (not seeming to wait indefinitely for communication). I think the gateway correction is definitely a step in the right direction. In case someone want to know (I'm not trying to withhold information!) my /etc/apt/sources.list is very boring: deb http://http.us.debian.org/debian stable main contrib non-free deb http://security.debian.org/ stable/updates main contrib non-free Thanks to everyone for your ideas... hopefully the next one will resolve matters entirely. -f -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Second ethernet card seems to cause networking failure?
Sure, can provide more info... /etc/network/interfaces : auto lo iface lo inet loopback # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth0 inet static address xxx.yyy.zzz.32 network xxx.yyy.zzz.0 netmask 255.255.255.0 broadcast xxx.yyy.zzz.255 gateway xxx.yyy.zzz.100 pre-up /etc/iptables/iptables.sh start post-down /etc/iptables/iptables.sh stop # The secondary network interface auto eth1 #iface eth0 inet dhcp iface eth1 inet static address 192.168.42.100 network 192.168.42.0 netmask 255.255.255.0 #broadcast 192.168.42.255 gateway 192.168.42.100 === route result: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface xxx.yyy.zzz.0 * 255.255.255.0 U 0 00 eth0 192.168.42.0* 255.255.255.0 U 0 00 eth1 === To reiterate: * The fundamental breakdown involves communication over the eth0 interface. Things just seem to hang when trying stuff like apt-get update. * ssh'ing into this machine from another host (directly to the IP of this machine) always works. * firewall is unchanged; well, ok, added: $IPT -A OUTPUT -o eth1 ! -s 192.168.42.0/25 -j DROP $IPT -A OUTPUT -o eth1 -s 192.168.42.0/24 -j ACCEPT $IPT -A INPUT -i eth1 ! -s 192.168.42.0/24 -j DROP $IPT -A INPUT -i eth1 -s 192.168.42.0/24 -j ACCEPT All communication with 192.168.42.x devices is functional. Listing iptables -L -n -v shows eth0 where it should. * simply turning firewall off (allowing everything) does not (at least by itself) fix eth0 communication. * as you can see, this is IPs are entirely static - no dhcp * network-manager not installed Since turning eth1 entirely OFF seems key to restoring eth0 full functionality, I agree that somehow the system seems confused about which interface to use. Any other thoughts/ideas welcome! -f * -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Second ethernet card seems to cause networking failure?
On Tue, 26 May 2009 18:20:07 +0200, Frank Miles wrote: Sure, can provide more info... /etc/network/interfaces : auto lo iface lo inet loopback # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth0 inet static address xxx.yyy.zzz.32 network xxx.yyy.zzz.0 netmask 255.255.255.0 broadcast xxx.yyy.zzz.255 gateway xxx.yyy.zzz.100 pre-up /etc/iptables/iptables.sh start post-down /etc/iptables/iptables.sh stop # The secondary network interface auto eth1 #iface eth0 inet dhcp iface eth1 inet static address 192.168.42.100 network 192.168.42.0 netmask 255.255.255.0 #broadcast 192.168.42.255 gateway 192.168.42.100 === route result: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface xxx.yyy.zzz.0 * 255.255.255.0 U 0 0 0 eth0 192.168.42.0* 255.255.255.0 U 0 0 0 eth1 === To reiterate: * The fundamental breakdown involves communication over the eth0 interface. Things just seem to hang when trying stuff like apt- get update. * ssh'ing into this machine from another host (directly to the IP of this machine) always works. * firewall is unchanged; well, ok, added: $IPT -A OUTPUT -o eth1 ! -s 192.168.42.0/25 -j DROP $IPT -A OUTPUT -o eth1 -s 192.168.42.0/24 -j ACCEPT $IPT -A INPUT -i eth1 ! -s 192.168.42.0/24 -j DROP $IPT -A INPUT -i eth1 -s 192.168.42.0/24 -j ACCEPT All communication with 192.168.42.x devices is functional. Listing iptables -L -n -v shows eth0 where it should. * simply turning firewall off (allowing everything) does not (at least by itself) fix eth0 communication. * as you can see, this is IPs are entirely static - no dhcp * network-manager not installed Since turning eth1 entirely OFF seems key to restoring eth0 full functionality, I agree that somehow the system seems confused about which interface to use. Any other thoughts/ideas welcome! -f * This may be a somewhat naive question, but ... Do the HWaddr's reported by ifconfig correctly match the MAC addresses for both eth0 and eth1? Rich -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Second ethernet card seems to cause networking failure?
Andrei Popescu wrote: On Fri,22.May.09, 09:25:29, Frank Miles wrote: [snip troubles with two network cards] Please provide your /etc/network/interfaces And also add the output of 'route'. It seems to me that somehow all traffic is routed via eth1, instead of only 192.x.x.x. Sjoerd signature.asc Description: OpenPGP digital signature
Re: Second ethernet card seems to cause networking failure?
On Fri, May 22, 2009 at 09:25:29AM -0700, Frank Miles wrote: I recently added a second networking card to a hardware-test PC. This elderly machine had been working reasonably well. The second networking card is for eth1, etc., and /sbin/ifconfig shows things as properly connected, with eth0 being the outside interface and eth1 being an internal 192.168.x.x interface for some special internal systems that have absolutely no need to communicate with the outside world, just this one PC. The weird thing is that with normal booting configuration, pinging INet addresses fails. This seems to be related to the order in which the interfaces come up: doing ifdown eth1 ; ifdown eth1 ; ifup eth0; ifup eth1 causes pings to fail; but if eth0/eth1 are reversed (bringing up eth0 last), or eth1 is simply suppressed, pinging URLs works (i.e. ping www.debian.org). Regrettably this last does not entirely solve things - for example, I cannot do system updates: apt-get update fails to connect. Eventually, if I play around long enough (killing eth1, killing my firewall - which hasn't changed since before adding the second NIC,...) I can do a system update but it's not entirely clear what the critical steps were to get that working. I freely admit that I'm a hardware guy - I don't know much about networking. Does anyone have a suggestion on where I might look to get this working properly? Without sacrificing eth1? Or at least some better diagnostic[s] to track down where packets are getting lost? TIA! Version 4 As you are suggested to show /etc/network/interfaces there isn't really a need for, as long as you start /etc/ini.d/networking after any changes and controll it with ifconfig -a. The last one isn't really necessary. I disabled any thingy of avahi, because there isn't any need for it (/etc/default/avahi-daemon, /etc/network/if-up.d/avahi-autoip and /etc/network/if-up.d/avahi-autoip changed from 755 to 644 by chmod and avahi-daemon -k) Then go on for routing - this should be fine now, IP-Masquerade-HOWTO if you like. Networking is fine with 3, I don't know anything with 5. -- Fuer die p.t.Leser: Die naechste Zeile enthaelt alle Informationen. LG Matthias:-) .--. -.-- .-. --.. .-. .- ..-. ..- -. -.-. --. .--- ...- .-. .- ...- .- .- .-. . .-. ..-. --. -. --.- --. .- --.- .-.. -.- .--. .. --- .-. ...- .. ...- .-. .- .- -. --.- -... --. -. --. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Second ethernet card seems to cause networking failure?
Do you have network-manager installed? It's not very good with setups with mixed static/dynamic ips. If you've got network-manager, remove it and set things up manually. Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore (Daniel Dickinson's Website) http://cshore.is-a-geek.com signature.asc Description: PGP signature
Re: Second ethernet card seems to cause networking failure?
On Fri,22.May.09, 09:25:29, Frank Miles wrote: [snip troubles with two network cards] Please provide your /etc/network/interfaces Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Second ethernet card seems to cause networking failure?
On Fri, May 22, 2009 at 09:25:29AM -0700, Frank Miles wrote: I recently added a second networking card to a hardware-test PC. This elderly machine had been working reasonably well. The second networking card is for eth1, etc., and /sbin/ifconfig shows things as properly connected, with eth0 being the outside interface and eth1 being an internal 192.168.x.x interface for some special internal systems that have absolutely no need to communicate with the outside world, just this one PC. So now you have a gateway? What firewall configuration software are you using? What is the output of cat /etc/network/interfaces The weird thing is that with normal booting configuration, pinging INet addresses fails. This seems to be related to the order in which the interfaces come up: doing ifdown eth1 ; ifdown eth1 ; ifup eth0; ifup eth1 causes pings to fail; but if eth0/eth1 are reversed (bringing up eth0 last), or eth1 is simply suppressed, pinging URLs works (i.e. ping www.debian.org). Have you a local DNS server? Regrettably this last does not entirely solve things - for example, I cannot do system updates: apt-get update fails to connect. Error? times out? unable to contact … ? Eventually, if I play around long enough (killing eth1, killing my firewall - which hasn't changed since before adding the second NIC,...) I can do a system update but it's not entirely clear what the critical steps were to get that working. killing the firewall mmm ... I freely admit that I'm a hardware guy - I don't know much about networking. I don't know much about networking either but if I was asking this question I'd provide at least the config files (see above), exact error messages from logs (if any … if none say so.), exact messages on screen, (if none, say so) Does anyone have a suggestion on where I might look to get this working properly? Without sacrificing eth1? Or at least some better diagnostic[s] to track down where packets are getting lost? Of course, I'd only post to this list after I'd used apt-cache search network test | wc -l and saw that it shows 83 packages which fit that search criteria and see that there is not really anthing useful, ok there is ping, but you've already used that. So I'd try apt-cache search network diagnos | wc -l ok 14, and see … that there is nothing very useful. We're at the mercy of the package maintainers to at least put some decent search terms in the descriptions and not just copy a paragraph off the upstream website or manpage. So I'd state I'd searched the packages and didn't really see anything useful. Also describe the network a bit more -DSL? Is this the first time you are connecting to the net with this machine etc. You may then get a response from someone who sees an anomaly with your setup, and might even help. But, and this is a stab in the dark, I think you have to tell the firewall about your new interface. -- Chris. == I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. -- Stephen F Roberts -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Second ethernet card seems to cause networking failure?
I recently added a second networking card to a hardware-test PC. This elderly machine had been working reasonably well. The second networking card is for eth1, etc., and /sbin/ifconfig shows things as properly connected, with eth0 being the outside interface and eth1 being an internal 192.168.x.x interface for some special internal systems that have absolutely no need to communicate with the outside world, just this one PC. The weird thing is that with normal booting configuration, pinging INet addresses fails. This seems to be related to the order in which the interfaces come up: doing ifdown eth1 ; ifdown eth1 ; ifup eth0; ifup eth1 causes pings to fail; but if eth0/eth1 are reversed (bringing up eth0 last), or eth1 is simply suppressed, pinging URLs works (i.e. ping www.debian.org). Regrettably this last does not entirely solve things - for example, I cannot do system updates: apt-get update fails to connect. Eventually, if I play around long enough (killing eth1, killing my firewall - which hasn't changed since before adding the second NIC,...) I can do a system update but it's not entirely clear what the critical steps were to get that working. I freely admit that I'm a hardware guy - I don't know much about networking. Does anyone have a suggestion on where I might look to get this working properly? Without sacrificing eth1? Or at least some better diagnostic[s] to track down where packets are getting lost? TIA! -f -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
adding a second ethernet card
I'm running slink. My eth0 is an ne2000 and works fine. I want to add a second ne2000. I've tried editing the lilo.conf file with: append=ether 12,0x300,eth1, then runing lilo and then rebooting but no luck. What is the process? thanks, -tom-
Re: adding a second ethernet card
On Sat, Jul 24, 1999 at 10:56:36PM -0400, Donna Lopolito wrote: I'm running slink. My eth0 is an ne2000 and works fine. I want to add a second ne2000. I've tried editing the lilo.conf file with: append=ether 12,0x300,eth1, then runing lilo and then rebooting but no luck. What is the process? thanks, -tom- On a IP-Masquerading server I've got, I've also got two cards (different brands, though). I believe that the easiest way to do this is by compiling your network driver as a module. That way, you can use modprobe (and later /etc/modutils/aliases) to specify configuration options and unload/reload the driver while playing with settings without rebooting. From the kernel docs for 2.2.10 (should apply to 2.0.36 tho): The ne module is an exception to the above. A NE2000 is essentially an 8390 chip, some bus glue and some RAM. Because of this, the ne probe is more invasive than the rest, and so at boot we make sure the ne probe is done last of all the 8390 cards (so that it won't trip over other 8390 based cards) With modules we can't ensure that all other non-ne 8390 cards have already been found. Because of this, the ne module REQUIRES an io=0xNNN argument passed in via insmod. It will refuse to autoprobe. Hope this helps, as always, reply if you have questions/problems/et al -- Stephen Pitts [EMAIL PROTECTED] webmaster - http://www.mschess.org
Re: Second ethernet card
On Wed, 12 Aug 1998, Christopher J. Morrone wrote: I was wondering where I should set up the configuration for my second ethernet card. I have two ethernet cards, both PCI and Tulip chipset, which are currently detected just fine during bootup. I set up the ethernet networking like normal during the Debian installation, and it works fine. What I want to do now is enable the second ethernet card. (This computer is essentially node 0 for a beowulf, and the other nodes do not need to access the outside world, so I don't believe that I need any type of ip forwarding.) So I basically just want to know where I should put my custom configuration for the second ethernet card. Should I just add it to the /etc/init.d/network file? Or is there a better place to put the configuration? Thanks! (Please Cc the response to me, I was knocked off the debian-user list because our server was bouncing too many messages.) I put the configuration of my second NIC in /etc/init.d/network as you suggested when I did a similar thing on my own. One was just a 192.168.1.1 for my local LAN while the other is using dhcpc and both are configured with ifconfig and routed in that file. Hope this answers your question well enough. Ehren Wilson
Second ethernet card
I was wondering where I should set up the configuration for my second ethernet card. I have two ethernet cards, both PCI and Tulip chipset, which are currently detected just fine during bootup. I set up the ethernet networking like normal during the Debian installation, and it works fine. What I want to do now is enable the second ethernet card. (This computer is essentially node 0 for a beowulf, and the other nodes do not need to access the outside world, so I don't believe that I need any type of ip forwarding.) So I basically just want to know where I should put my custom configuration for the second ethernet card. Should I just add it to the /etc/init.d/network file? Or is there a better place to put the configuration? Thanks! (Please Cc the response to me, I was knocked off the debian-user list because our server was bouncing too many messages.)
Re: Q: Second Ethernet Card
I am planing on purchasing a 256k DSL to my Linux server. I currently have one Ehternet card that is connected to my home PC with a crossover cable. I will need to purchase an additional Ethernet card for my Server to connect to the DSL connection. Should I purchase the cable and then completely rebuild the server from the ground up with the two Ethernet cards, or just place the second one in and go from there? If I just place the second one in, what will have to be done to get it online? Just put the second card and configure it. It has couple pitholes, but is not that hard. If the DSL line endst to a RJ45 connector, the ger a Intel EtherExpress card and be happy. There are a few HOWTOS in you know where :) BTW - As I get ready to place my server on the net with DSL, I was planning to setup Sendmail for email, Apache as my Web Server and TIC as my Firewall (to protect my home PC on the other Ethernet card). Does this look OK? or is there something else I should do? In my experience Exim is easier and more secure and . etc. I've been using it for some 5-6 months now, without problems. The hamm version is pretty good. Apache sounds good, but I have now experience, same with firewalls. Just about the time to learn :) --j -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Q: Second Ethernet Card
I am planing on purchasing a 256k DSL to my Linux server. I currently have one Ehternet card that is connected to my home PC with a crossover cable. I will need to purchase an additional Ethernet card for my Server to connect to the DSL connection. Should I purchase the cable and then completely rebuild the server from the ground up with the two Ethernet cards, or just place the second one in and go from there? If I just place the second one in, what will have to be done to get it online? BTW - As I get ready to place my server on the net with DSL, I was planning to setup Sendmail for email, Apache as my Web Server and TIC as my Firewall (to protect my home PC on the other Ethernet card). Does this look OK? or is there something else I should do? Thanks. Dean Sullinger -- [EMAIL PROTECTED] http://www.crl.com/~deans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Second Ethernet Card
I have recompiled the kernel to support IP forwarding. One of two 3C509 Cards that I have on my machine works. What is required to get my second Ethernet Card working? I have tried to add the append=ether=11,0x320.eth1 statement to lilo.conf but it doesn't make it work. Any ideas? Thanks, Drazen I haved two 3c509. 1)To run with both you must compile driver into kernel (not as module). 2) Configure NIC's: turn PNP off, check IRQ and IO (with 3c5x9cfg.exe - get newest version from www.3com.com). Mirek -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Second Ethernet Card
On Tue, 2 Sep 1997, Mirek Kwasniak wrote: I haved two 3c509. 1)To run with both you must compile driver into kernel (not as module). though mine is a different model (3C590), I had no problem with modules. I have 3 (three) 3C590, with ip-masq, compiled as module, which are detected w/o any problems at boot time, with PNP on. Maybe is because I have a diff. model. :-) I using v.030-all (12/23/96) and 2.0.30 kernel. []s, Mario O.de MenezesMany are the plans in a man's heart, but IPEN-CNEN/SP is the Lord's purpose that prevails http://curiango.ipen.br/~mario Prov. 19.21 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Second Ethernet Card
Have you disabled plug and play? If not, boot to DOS, put in your 3Com diskettes, run 3c5x9cfg and disable it. Also note your IO and IRQ's just to double check. I've had good luck with two 3c509's at my old job once I disabled pnp. Chip - Chip Atkinson [EMAIL PROTECTED] (work) Xi Graphics[EMAIL PROTECTED] (home) Denver, CO (303)298-7478 (work) On Thu, 26 Jun 1997, Lalovic, Drazen wrote: I have recompiled the kernel to support IP forwarding. One of two 3C509 Cards that I have on my machine works. What is required to get my second Ethernet Card working? I have tried to add the append=ether=11,0x320.eth1 statement to lilo.conf but it doesn't make it work. Any ideas? Thanks, Drazen -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Second Ethernet Card
I have recompiled the kernel to support IP forwarding. One of two 3C509 Cards that I have on my machine works. What is required to get my second Ethernet Card working? I have tried to add the append=ether=11,0x320.eth1 statement to lilo.conf but it doesn't make it work. Any ideas? Thanks, Drazen -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Second Ethernet Card
On Thu, 26 Jun 1997 14:12:00 EDT Lalovic, Drazen ([EMAIL PROTECTED]) wrote: I have recompiled the kernel to support IP forwarding. One of two 3C509 Cards that I have on my machine works. What is required to get my second Ethernet Card working? I have tried to add the append=ether=11,0x320.eth1 statement to lilo.conf but it doesn't make it work. Any ideas? The 3c509 driver in 2.0.30 can only cope with one card. You need to patch it to get more than one. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Second Ethernet Card
On Thu, 26 Jun 1997, Lalovic, Drazen wrote: : I have recompiled the kernel to support IP forwarding. One of two 3C509 : Cards that I have on my machine works. What is required to get my second : Ethernet Card working? : I have tried to add the append=ether=11,0x320.eth1 statement to : lilo.conf but it doesn't make it work. Any ideas? : Read the Multiple Ethernetcards FAQ: append=ether=0,0,eth0 ether=0,0,eth1 Remco. -- // Remco van de Meent // email: [EMAIL PROTECTED] // www: http://oloon.student.utwente.nl //Never make any mistaeks. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Second Ethernet Card
THANK YOU FOR YOUR HELP. DO YOU KNOW THE PATCH NAME? THANKS, DRAZEN -- From: Philippe Troin To: Lalovic, Drazen Subject: Re: Second Ethernet Card Date: Thursday, June 26, 1997 3:45PM On Thu, 26 Jun 1997 14:12:00 EDT Lalovic, Drazen ([EMAIL PROTECTED]) wrote: I have recompiled the kernel to support IP forwarding. One of two 3C509 Cards that I have on my machine works. What is required to get my second Ethernet Card working? I have tried to add the append=ether=11,0x320.eth1 statement to lilo.conf but it doesn't make it work. Any ideas? The 3c509 driver in 2.0.30 can only cope with one card. You need to patch it to get more than one. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Second Ethernet Card
THANK YOU FOR YOUR HELP. DO YOU KNOW THE PATCH NAME? THANKS, DRAZEN -- From: Philippe Troin To: Lalovic, Drazen Subject: Re: Second Ethernet Card Date: Thursday, June 26, 1997 3:45PM On Thu, 26 Jun 1997 14:12:00 EDT Lalovic, Drazen ([EMAIL PROTECTED]) wrote: I have recompiled the kernel to support IP forwarding. One of two 3C509 Cards that I have on my machine works. What is required to get my second Ethernet Card working? I have tried to add the append=ether=11,0x320.eth1 statement to lilo.conf but it doesn't make it work. Any ideas? The 3c509 driver in 2.0.30 can only cope with one card. You need to patch it to get more than one. Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Second Ethernet Card
Re: Second Ethernet Card
Hi, Maybe I can help. Check http://cesdis.gsfc.nasa.gov/linux/drivers/3c509.html which talks about Linux and 3com 3c5*9 Ethercards. I just got a new version of the 3c509 driver for my card to get a fix for the 'Waiting for 3c509 to discard packet, status 2001.' nag some of you might have seen. The page has a link to the 3c509.c file which has this in the comments: FIXES: Alan Cox: Removed the 'Unexpected interrupt' bug. Michael Meskes: Upgraded to Donald Becker's version 1.07. Alan Cox: Increased the eeprom delay. Regardless of what the docs say some people definitely get problems with lower (but in card spec) delays v1.10 4/21/97 Fixed module code so that multiple cards may be detected, other cleanups. -djb The URL straight to the driver source is http://cesdis.gsfc.nasa.gov/linux/drivers/3c509.c // Heikki Drazen Lalovic wrote: THANK YOU FOR YOUR HELP. DO YOU KNOW THE PATCH NAME? THANKS, DRAZEN -- From: Philippe Troin To: Lalovic, Drazen Subject: Re: Second Ethernet Card Date: Thursday, June 26, 1997 3:45PM [cut] The 3c509 driver in 2.0.30 can only cope with one card. You need to patch it to get more than one. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Second Ethernet Card
- Chip Atkinson [EMAIL PROTECTED] (work) Xi Graphics[EMAIL PROTECTED] (home) Denver, CO (303)298-7478 (work) On Thu, 26 Jun 1997, Philippe Troin wrote: On Thu, 26 Jun 1997 14:12:00 EDT Lalovic, Drazen ([EMAIL PROTECTED]) wrote: I have recompiled the kernel to support IP forwarding. One of two 3C509 Cards that I have on my machine works. What is required to get my second Ethernet Card working? I have tried to add the append=ether=11,0x320.eth1 statement to lilo.conf but it doesn't make it work. Any ideas? The 3c509 driver in 2.0.30 can only cope with one card. You need to patch it to get more than one. Phil. Really? That's a step back from last fall, when I got two 3c509s to work in a machine at my previous employer. The biggest problem that we had was plug and play. The old cards didn't have it, and worked fine. The new cards did have it, and it drove us nuts until we found out about it and disabled it using 3c5x9cfg in DOS. After that it worked very well. As Remco pointed out, -- Read the Multiple Ethernetcards FAQ: append=ether=0,0,eth0 ether=0,0,eth1 Remco. --- This is basically what we did, but we actually provided the IRQ and IO numbers. Chip -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
