On Sun, 26 Aug 2001, Edouard Gomez wrote:
> This patch is wrong, aal5 specification is clear on this point, aal5
> frame info is 8 bytes long that's why I've put 8 (and not 6). But you're
> right, only 6 bytes are used, the 2 bytes unused are part of the
> specification and must be currently in
Hi,
The latest pppoa3 seems stable but I'm having problems running with -v 1 or -v 2 flags
(which seems to be
crashing it). I thinks it is something in the report function when is re-assembles
aal5 frames. With no diags
it runs fine. Anyone else running this latest code (from Friday?)
BTW on
Tim Woodall wrote:
>
> Been through this code quite carefully last night.
>
> Spotted one problem, one slight improvement, and one grammatical error.
>
> First the improvement.
>
> --- atm.c.origFri Aug 24 08:16:46 2001
> +++ atm.c Fri Aug 24 08:19:43 2001
> @@ -209,7 +209,7 @@
>
On Sun, 19 Aug 2001, Edouard Gomez wrote:
> Hello,
>
> I'm still developing pppoa3 (that's a good news) but I have some
> problems and I don't find how to resolve them.
>
> So I post this message to try to find help. I need help from a good
> hacker who knows about threads and threads mutex in
