From: Christopher Fowler <cfowler@outpostsentinel.com>
To: linux-ppp@vger.kernel.org
Subject: Re: serial line is looped back!
Date: Thu, 28 Dec 2006 18:21:55 +0000 [thread overview]
Message-ID: <1167330115.31503.6.camel@shuttle.linxdev.com> (raw)
In-Reply-To: <cfd1efa00612270035p56f20450ncda10c76d10fa379@mail.gmail.com>
On Thu, 2006-12-28 at 10:17 -0800, Bill Unruh wrote:
>
> In many situations you should end with '\d\c' so that your chat script
> does
> not send a carriage return, which it does for '' which you use to end
> it.
> Many isps see taht carriage return as a request to start a regular
> login
> session rather than ppp. However in your case I guess it is a gsm
> phone or
> something you are using.
I never new that. Typically all my devices call only Linux servers so
it is Linux calling Linux with mgetty on each end. Never had a problem
with that carriage return.
prev parent reply other threads:[~2006-12-28 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 8:35 serial line is looped back! zhang guocheng
2006-12-27 18:53 ` Bill Unruh
2006-12-28 6:29 ` zhang guocheng
2006-12-28 18:17 ` Bill Unruh
2006-12-28 18:21 ` Christopher Fowler [this message]
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=1167330115.31503.6.camel@shuttle.linxdev.com \
--to=cfowler@outpostsentinel.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;
as well as URLs for NNTP newsgroup(s).