From: Christian <crich-ml@beronet.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Way how frames are read in pppd
Date: Mon, 30 Oct 2006 15:06:23 +0000 [thread overview]
Message-ID: <454614EF.3000301@beronet.com> (raw)
In-Reply-To: <4540C35F.9010104@beronet.com>
>>>
>>>
>>do you know of any library implementing AHDLC ? I'm right now trying to
>>use spandsps implemetation, but it seems not receive a frame..
>>
>>
>
>
>
I've done some progress in using the hdlc stuffing/destuffing from
spandsp, it reports that it first has some good FRAME_OK, then after 3
bytes it gets an ABORT, but still says it found a (bad) frame, which
looks like:
received [37]: 3f f1 0 a1 9f d0 4f e8 27 f0 b3 f8 89 fc 64 7e 2 3f 81 9f
c0 4f e0 27 f5 93 cd fb c9 e3 8d fc e4 7e 22 3f 85
would you say this is a correct ppp frame? (looks like it contains a 7e
which should be part of hdlc i think .. )
>You can feel free to use this one:
>
> ftp://ftp.workingcode.com/pub/carlson/ppp/ahdlc.c
> ftp://ftp.workingcode.com/pub/carlson/ppp/ahdlc.h
>
>
>
I tried to fetch them, but i got:
wget ftp://ftp.workingcode.com/pub/carlson/ppp/ahdlc.c
--15:58:57-- ftp://ftp.workingcode.com/pub/carlson/ppp/ahdlc.c
=> `ahdlc.c'
Resolving ftp.workingcode.com... 24.128.38.122
Connecting to ftp.workingcode.com[24.128.38.122]:21... connected.
Logging in as anonymous ... ^[[ALogged in!
=> SYST ... done. => PWD ... done.
=> TYPE I ... done. => CWD /pub/carlson/ppp ... done.
=> PASV ...
couldn't connect to 24.128.38.122:31221: Connection timed out
Retrying.
Many thanks so far for clarifying these things to me :-)
next prev parent reply other threads:[~2006-10-30 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 14:17 Way how frames are read in pppd Christian
2006-10-30 12:48 ` James Carlson
2006-10-30 13:44 ` Christian
2006-10-30 13:56 ` James Carlson
2006-10-30 14:11 ` Christian
2006-10-30 14:49 ` James Carlson
2006-10-30 15:06 ` Christian [this message]
2006-10-30 15:13 ` James Carlson
2006-10-30 23:15 ` Paul Mackerras
2006-10-31 17:21 ` Christian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=454614EF.3000301@beronet.com \
--to=crich-ml@beronet.com \
--cc=linux-ppp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.