Michael W. Ryan on Mon, 19 Jun 2000 17:22:35 -0400 (EDT) |
Okay, I've solved part of my problem. It appears that the problem was related to the IRQ of the second NIC. I've installed a different type of NIC in place of the second 3c905B (an Intel EtherExpress Pro 10/100) and adjusted the IRQ for the NIC (it appears that the NIC drivers can/will not recognize a NIC on IRQ 9). The interface works like a champ now. Unfortunately, the system still isn't routing requests between the two subnets. From the 192.168.1.128 network (eth1), I can ping both 192.168.1.129 and 192.168.1.2, but I can't ping anything in the 192.168.1.0 network (eth0). IPv4 forwarding *is* on. Firewalling is turned off. From what I've been able to read in HOWTOs, I've done everything I need to in order to get packets to route from one subnet to the next. I'm at a complete loss here. Michael W. Ryan, MCP, MCT | OTAKON 2000 mryan@netaxs.com | Convention of Otaku Generation http://www.netaxs.com/~mryan/ | http://www.otakon.com/ No, I don't hear voices in my head; I'm the one that tells the voices in your head what to say. ______________________________________________________________________ Philadelphia Linux Users Group - http://plug.nothinbut.net Announcements - http://lists.nothinbut.net/mail/listinfo/plug-announce General Discussion - http://lists.nothinbut.net/mail/listinfo/plug
|
|