Thank you to everyone who responded to my request for help. It appears that I was the victim of my own stupidity. I inadvertantly grabbed an old 100MB hub to use (not a 10/100MB hub). Needless to say, the 3c509 cards did not work. I have replaced the hub and everything is fine now.
On another note, I have determined that there is a small but vital piece of information missing from the linux Ethernet HOWTO. That is, if you attempt to specify any parameters on the 3c509 driver line(s) in the /etc/modules file, the driver will NOT load. Once the cards are appropriately set with the DOS utility, the simple "3c509" entry works like a charm. Thanks again, Dave ----- Original Message ----- From: "Dave Rose" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, April 07, 2004 8:06 PM Subject: [leaf-user] trouble accessing firewall > I am standing up a bering firewall and have made it through the 3c509 > troubleshooting phase, or so I thought. I am unable to ping the internal > side of the firewall from my other computers. > > My hardware > ----------------- > 486DX4 100Mhz > PCI video card > 20MB RAM > Floppy disk > 3c509B-TP (I have two of these cards installed in the ISA bus) > > > Hardware configuration > ------------------------------- > NO Hard drive (controller disabled in BIOS) > NO comm/parallel ports (disabled in BIOS) > Set the 3c509-TP cards to IRQ7,5 and IO addresses of 0x300,0x280 and > disabled the ISA plug and play feature and successfully ran the 3COM > diagnostics function on each card) > > > Software configuration > ---------------------------- > 1.) downloaded the bering 1.2 software (Windows utility to make the boot > floppy- Bering_1.2_img_bering-1680.exe from > http://download.sourceforge.net/leaf/) > > 2) downloaded the bering 1.2 modules (Bering_1.2_modules_2.4.20.tar.gz from > http://download.sourceforge.net/leaf/) > > 3) I booted the floppy I made in the first step and added the 3c509.o > ethernet card driver to /lib/modules > > 4.) I modified /etc/modules to add the line > > 3c509 > > 5) I pretty much left /etc/network/interfaces to the default settings since > they are set up initially for the configuration that I am looking for > > > The problem > -------------------- > Although the system recognizes both cards (IRQs and IO addresses) at > startup, the eth1 interface fails to activate, light up the led on the hub > and can not be pinged from my other workstation on the internal lan. Any > ideas how to proceed would be much appreciated. > > Thanks > Dave > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
