Messages in this thread | | | Date | Thu, 29 Apr 1999 19:01:46 -0500 (CDT) | From | "Chad C. Walstrom" <> | Subject | EQL problems - Update (fwd) |
| |
Heya. I'm not sure how you report bugs here (NEWBIE ALERT -- sorry), but I feel that I have indeed encountered a problem, bug or no. The letter below details the problems I've had with EQL and the kernel 2.2.5. Ultimately, I recompiled the 2.0.36 kernel to get a working EQL environment.
See if this checks out for you as well...
Chewie ---------- Forwarded message ---------- Date: Tue, 27 Apr 1999 22:39:40 -0500 (CDT) From: Chad C. Walstrom <chewie@soncom.com> To: Debian User's List <debian-user@lists.debian.org> Subject: EQL problems - Update
Chewie here, with a quick update on the EQL problems I was having. In case you hadn't seen the previous post, here's a quick synopsis. I had compiled the 2.2.5 kernel with eql support, initiated my two modem connections with no (absolutely NO) compression, and enslaved the devices to the eql device. My routing table was set up correctly, and I watched the tcpdump on each device to find that data was being sent and received, but just not finalized. The initiating program didn't receive packets...they seemed to disappear somewhere between the modem device and the eql device.
Well, since I had done everything right, as according to documentation and the advice of a friend, we decided to go back to the 2.0.36 kernel. Lo-and-behold, it worked! After establishing a stable eql environment, I applied the firewall and masquerading rules to make the connection LAN accessible. Mission accomplished.
The short and long of it, eql on kernels newer than 2.0.36 should be assumed to be broken until further notice. I will be reporting the bug to the tracker sometime tomorrow morning.
Chewie
AKA: Chad Walstrom <chewie@soncom.com>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |