All of lore.kernel.org
 help / color / mirror / Atom feed
From: carlsonj@workingcode.com
To: linux-ppp@vger.kernel.org
Subject: Re: absolutely baffled as to why PPP link doesn't allow pings
Date: Fri, 15 Oct 2004 18:55:15 +0000	[thread overview]
Message-ID: <16752.7443.381436.601249@carlson.workingcode.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0410151211340.11955@localhost.localdomain>

Robert P. J. Day writes:
> well, we're making progress, although not the way i would have liked.
> as a simple test, we just hooked up the serial ports of the systems
> direct connect with a serial cable, and PPP worked just dandy.
> 
> putting the modems back in the circuit re-introduced the problem.  so
> it could be the modems or the initialization strings we're using.
> back to the drawing board ...

That certainly points in a different direction.  One possibility is
that you're running into flow control problems or transparency issues
with the modems.

If they're like USR modems, then "AT&F1" usually does the trick.  If
they're not, then see the manual.  :-/

Two things to try: "asyncmap 0xa0000" and "noasyncmap".  The former
will escape XON/XOFF characters, on the theory that the modems are
eating those characters by default.  The latter will escape all
control characters.

-- 
James Carlson                                 <carlsonj@workingcode.com>

  parent reply	other threads:[~2004-10-15 18:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15 16:28 absolutely baffled as to why PPP link doesn't allow pings Robert P. J. Day
2004-10-15 16:33 ` Robert P. J. Day
2004-10-15 16:43 ` carlsonj
2004-10-15 16:52 ` Robert P. J. Day
2004-10-15 16:55 ` Bill Unruh
2004-10-15 17:07 ` carlsonj
2004-10-15 18:45 ` Robert P. J. Day
2004-10-15 18:55 ` carlsonj [this message]
2004-10-15 19:52 ` Robert P. J. Day
2004-10-15 20:25 ` carlsonj

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=16752.7443.381436.601249@carlson.workingcode.com \
    --to=carlsonj@workingcode.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.