Messages in this thread | | | Subject | Network problems with 2.1.6[45] | Date | Tue, 18 Nov 1997 21:17:10 -0500 | From | Pete Toscano <> |
| |
Hello there.
I don't think this has been mentioned, but if it has, please pat me on my head, point me in the right direction, and send me on my way.... =8]
With both the 2.1.64 and 2.1.65 kernels, my network interface has been broken. It seems to work fine with 2.1.63. I'm using a NE2000-compatible ISA card and the driver gets loaded as a module. During boot-up, the card is detected fine; correct IO port and IRQ. The way I've got my system set up, I also have an alias for the card. On boot-up, this alias is assigned and routes through it are also assigned. IP-aliasing is also loaded as a module.
Everything seems to work fine, but no packets are sent out the interface. I can ping the interface IP without problems, but when I try to ping another machine on the local subnet, nothing happens. If I do an ifconfig on eth0, the transmit and receive packets remain at zero, with the error packet number steadily increasing. (I think the number of errors increased faster with 2.1.64, but I might be wrong.)
Thinking that the problem might stem from the IP-aliasing, I removed the routes, interface, and module and tried again by ifconfig-ing eth0 and re-adding the simple, non-alias routes, but the problem persisted.
If I boot into 2.1.63, there is no problem. From the syslog messages, there is no indication that anything is broken.
Is there anything that I'm doing wrong or are there any known problems that might affect this? (Is there any further data that I can provide to help fix this problem?)
thanks, pete
| |