Still can't get it going. I have loaded the module for the 3c509 driver, (I'm using 2 ISA 3c509B cards) but only get 1 showing up in ip addr:
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:a0:24:12:bd:9c brd ff:ff:ff:ff:ff:ff
Did you edit this output, or am I forgetting what "ip addr show" reports? I would expect the other interfaces each to have a line like the last line under lo: .
I ask because we need to figure out whether the problem is with the *creation* of the interfaces or with the *configuration* of the interface? That is, does eth1 not exist at all, or does it exist but lack an IP address? Here's how to sort that part out.
1. Before Linux boots, look at the system's BIOS message display and see if it shows 2 or 1 NICs. If 2, note the IRQs it mentions. (This can be hard to do, as this info often is onscreen only for a second or two, so you may have to start the boot process several times to spot it.) If not, make sure your BIOS is set up to assign IRQs to both isa slots. You don't mention your hardware here, but if it is a mixed isa/pci mobo, you may be running into a problem caused by trying to use both the pci and the isa slot in a "shared" pair ( where the BIOS permits you to use ony one of the slots).
2. After Linux boots/inits, see if 2 NICs are associated with IRQs and IO base ports, by checking /pdoc/interrupts and /proc/ioports .
3. Try "ip link show" to see if there is an unconfigured eth1 present on the system.
The later problems, with the routing table and the firewall ruleset, are derivative of whichever problem besets the second NIC. So there is no need to pursue that level of investigation further until we have figured out where the second NIC is hiding.
If you find that no eth1 interface is being created, you may have one of these two problems:
1. The second NIC is defective.
2. Both NICs are assigned the same IRQ and/or IO base.
To check these possibilities, try running the system with the NICs in one at a time. If it works (for eth0) with one but not the other, you have the first problem. If both work but turn up with the same IRQ &/or IO bases, you have the second problem. (In the second case, you can check Becker's site to see if he has a config utility for the 3c509 -- I don't remember one, but I think he added some new ones after I stopped using 3Com NICs -- or you can get the DOS-based NIC-configuration utility 3Com provides (or once did; I assume it is still available on their Website) ... as I recall, the 3c509 never supported PnP, so you will have to fix this problem by hand.
(BTW, it has been some years since I used 3c509 cards, or any isa NIC for that matter, but I do recall that the 3c509 module was perfectly able to handle multiple NICs. So don't go astray down that road.)
If you find that eth1 is present but unconfigured, you need to tell us what IP address you are trying to assign to it, and how.
nothing in ip route. The meassages log shows the driver is loaded:
[remainder deleted]
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ------------------------------------------------------------------------ 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
