From: Thomas Chen <tchen@on-go.com>
To: linux-ppp@vger.kernel.org
Subject: ppp MULTILINK issue / problem
Date: Tue, 04 May 2004 14:37:23 +0000 [thread overview]
Message-ID: <BCBD226C.57C%tchen@on-go.com> (raw)
i am testing PPP MULTILINK
server side is running LINUX 2.4.18-3
client side is running LINUX 2.4.19
the link between them are 56k analog modems
i can place calls and set up the MUTILINK.... and the
links are bundled together just fine....
now i am testing "UNBUNDLING" of the link.... if i unplug
the one of the modem (not the master link), i do not see
the IP traffic anymore, though i do see data on the serial
link (i put a serial line monitor on the serial port),
but no more IP packets coming out of PPP
i do see a couple linkes of mp_construct sequencing error
appreciate if any pointer on where to look....
thansk
tom
next reply other threads:[~2004-05-04 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 14:37 Thomas Chen [this message]
2004-05-04 14:42 ` ppp MULTILINK issue / problem James Carlson
2004-05-04 22:45 ` Paul Mackerras
2004-05-04 23:05 ` Thomas Chen
2004-05-04 23:13 ` Paul Mackerras
2004-05-05 11:17 ` James Carlson
2004-07-16 16:22 ` Matthew N. Dodd
2004-07-19 2:05 ` Thomas Chen
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=BCBD226C.57C%tchen@on-go.com \
--to=tchen@on-go.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox