Thanks for your help, but I'm about ready to buy some new hardware. I have 5 of the 3C509B NICs. I downloaded the 3Com PNP tools which are a self expanding .exe. That didn't do me any good, because it expects to have a hard drive in the system for the expansion. I really don't want to install M$ on a hard drive!!
But I discovered the isapnp site, ock.demon.co.uk/isapnptools/ and from there found a dos version that lets me boot dos, then swap disks and run a couple of tools to configure the cards. The tools say they configure with the io and irqs that I set. However, that doesn't work with Bering. I still get just two interfaces instead of four. I've tried linking to 3c509.o to make it look like I have another driver, and I've copied 3c509.o to another filename and listed that in /etc/modules and I still get operation not supported by device. I have a couple of other old NICs that aren't PNP, but without enough information to know what driver they take. I don't want to waste a good machine for a firewall, but it's looking more like that will have to be done. How is everyone else handling more than two interfaces? -- Sincerely, David Smead http://www.amplepower.com. On Thu, 11 Apr 2002, Charles Steinkuehler wrote: > > BTW, does anyone know how to detemine which RJ45 is which interface on the > > D_LINK DFE-570TX with the tulip driver? > > IIRC, the "top" connector (the one farthest from the PCI connector) is the > first interface to get recognized (ie eth0 if this is the only card in the > system), and the connector closest to the PCI connector is the "last" > interface (ie eth3). > > Regarding your ISA problems: Make sure you have the cards set for unique > I/O and IRQ values. You'll probably also have to pass the values to the > driver for it to recognize all the cards. One word of warning...not all > network drivers will support an arbitrary number of cards. It's possible > (but unlikely with the 3com cards) the driver will not recognize more than > two NIC's. If this is the case, there are a couple work-arounds you can > try, including using a different driver (I think there are at least 2 linux > drivers for most 3com stuff), and loading the same driver again with a > different name (ie copy your driver.o file to driver2.o, and make another > entry in /etc/modules for it). > > Charles Steinkuehler > http://lrp.steinkuehler.net > http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) > > _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
