> On Mon, 26 Jul 1999 [EMAIL PROTECTED] wrote:
>
> > I've managed to track down the proxy arp problem in 3.2-stable. It was due to
> > misalignment which led to wrong/corrupted destination address and netmask.
>
> Thank you :) If you have a second, could you go over the patch briefly,
> and exp
We upgraded the uthreads as recommended, but to no avail. :(
It appears that the on screen console errors (before the mandatory hard
reboot) haven't been the same every time.
This time (according to the TECH at our ISP) the screen was full of
scrolling 'busy count' and 'pack count' errors. I
On Mon, 26 Jul 1999 [EMAIL PROTECTED] wrote:
> I've managed to track down the proxy arp problem in 3.2-stable. It was due to
> misalignment which led to wrong/corrupted destination address and netmask.
>
> To fix the proxy arp problem, type:
>
> fetch -o - http://www.daddylonglegs.com/arp.pa
On Mon, 26 Jul 1999 [EMAIL PROTECTED] wrote:
> I've managed to track down the proxy arp problem in 3.2-stable. It was due to
> misalignment which led to wrong/corrupted destination address and netmask.
Thank you :) If you have a second, could you go over the patch briefly,
and explain what it d
I've managed to track down the proxy arp problem in 3.2-stable. It was due to
misalignment which led to wrong/corrupted destination address and netmask.
In many scenarios, the wrong address and netmask would match a existing route
in the routing table, prompting the kernel to reject the request
