Brad and others,
Thanks for your great help - I didn't have to install DOS onto a hard
drive!! I downloaded the 3c5x9cfg.exe, about 230 kB. Before using it to
configure the cards you have to disable pnp. That's done using the same
executable, but with some command line args. I found pnpdsabl.bat which
does the trick.
fog.bio.unipd.it/pub/Networking/Drivers/3Com/3Com509-3Com509B/Disk2/pnpdsabl.bat
After that I got five cards configured and when Bering boots they load at
the correct addresses and show the selected IRQ!!
cat /proc/ioports looks good, however cat/proc/interrupts doesn't show any
interrupts for the cards. I don't have any cables plugged in at this
point - are interrupts actually required before /proc/interrupts show up?
I used irqs 3,5,7,11 and 15.
What I get for cat /proc/interrupts is:
CPU0
0: 886070 XT-PIC timer
1: 1190 XT-PIC keyboard
2: 0 XT-PIC cascade
NMI: 0
ERR: 0
I'm guessing that the column under the CPU0 is the count of occurence
since it goes up every time I run the command. So where are my other
interrupts????
--
Sincerely,
David Smead
http://www.amplepower.com.
On Sun, 14 Apr 2002, Brad Fritz wrote:
>
> My apologies for the rather long reply inline...
>
> On Sat, 13 Apr 2002 21:42:51 PDT David Smead wrote:
>
> > I have 5 of the 3C509B NICs.
>
> I have 6 3c509b cards in two of my firewalls. One is Dachstein
> and the other is Bering. I can testify that all 12 work fine
> when properly configured with 3c5x9cfg.exe. More on that below.
>
> > 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!!
>
> All you really need is the 226k 3c5x9cfg.exe. Someone has a
> copy posted at
> http://www.urz.uni-heidelberg.de/Netzdienste/nm/misc/3comnic/
> I ran a comparison of the md5 checksum with a known good copy
> from 3com and they match.
>
> [brad@brad-nb tmp]$ wget \
> http://www.urz.uni-heidelberg.de/Netzdienste/nm/misc/3comnic/3c5x9cfg.exe \
> 2> /dev/null
> [brad@brad-nb tmp]$ md5sum /tmp/3c5x9cfg.exe
> acd53047824a7438c097e7d58be5bdcd 3c5x9cfg.exe
> [brad@brad-nb tmp]$ md5sum /mnt/disk/3c5x9cfg.exe
> acd53047824a7438c097e7d58be5bdcd /mnt/disk/3c5x9cfg.exe
>
> IIRC, you only need MS DOS to extract the 3c509x1.exe disk
> image...still it's a shame it's not a plain self-extracting zip
> file.
>
>
> > 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.
>
> >From your description, I can't tell if you found 3c5x9cfg.exe at
> the url above or some other tool. Either way, you definitely want
> to make sure you disable PnP on the cards and, as other list members
> have said, give each separate IO and IRQ addresses. Here's the setup
> from one of my firewalls.
>
> # cat /proc/ioports
> [..]
> 0300-030f : 3c509
> 0310-031f : 3c509
> 0320-032f : 3c509
> 0330-033f : 3c509
> 0340-034f : 3c509
> 0350-035f : 3c509
> [..]
>
> # cat /proc/interrupts
> [..]
> 5: 14051544 XT-PIC eth0
> 7: 3714433 XT-PIC eth1
> 8: 47 XT-PIC rtc
> 9: 61372 XT-PIC eth2
> 10: 0 XT-PIC eth3
> 11: 0 XT-PIC eth4
> 12: 0 XT-PIC eth5
> [..]
>
> (I don't use the parallel port or any sound cards on this
> machine.)
>
> You should probably check that all NICs are using the same
> transceiver types and duplex values from 3c5x9cfg.exe too.
>
> <aside>
> If you jot down the MAC addresses from 3c5x9cfg.exe and
> physically arrange the cards in order ascending or descending
> MAC address it makes it much easier to keep track of which
> NIC maps to which ethN interface.
> </aside>
>
> > 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.
>
> Sure sounds like you still have an IO port or IRQ conflict. If
> you configure the cards properly with 3c5x9cfg.exe, you will only
> need a single
>
> 3c509
>
> line in /etc/modules and the driver will autmagically recognize
> all your 3c509b NICs. That's the setup in my 6 3c509b Bering box,
> and they all work fine.
>
> > 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?
>
> In my opinion the 3c509b NICs are great cards. I bought a lot
> of 25 for about $2 a piece on eBay and whenever I can, I use
> them exclusively in the firewalls I build. Before I use one,
> I configure it with the copy of 3c5x9cfg.exe on a dos bootable
> floppy. Here's the uptime info from one of those firewalls
> right before I unplugged it to hook it up to a UPS:
>
> [brad@brad-nb brad]$ cat systen_router_uptime
> systenrouter: -root-
> # uptime
> 16:18:16 up 218 Days (5254h), load average: 0.00 0.00 0.00
>
> I had *zero* problems with the NICs during that period and
> the same is true for the 3c509b NICs in my other firewalls.
>
> Hope that helps, Dave. Let me know if you need further details
> from any of my config files.
>
> --Brad
>
>
> > --
> > Sincerely,
> >
> > David Smead
> > http://www.amplepower.com.
>
> _______________________________________________
> Leaf-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-user
>
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
