linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: monitoring raw data
Date: Mon, 15 Jul 2019 18:24:16 +0000	[thread overview]
Message-ID: <a5cba29c-1943-92db-0b6e-a61dae007ccc@workingcode.com> (raw)
In-Reply-To: <5D29B187.6040400@bfs.de>

On 07/13/19 08:03, walter harms wrote:
> while searching i found this:
>  https://github.com/ya-jeks/gsmmux
> 
> ever heard about it ?

I've never heard of it, but it does indeed look like the solution you're
looking for.  You would just run pppd over one of the ptys allocated by
that tool, and then use your AT commands on another pty.

More generally, neither pppd nor its associated kernel drivers have any
sort of multiplexing scheme for carriage of non-PPP data.

On a commercial system I once worked on, we had specially-designed
modems that had a separate management-only serial port so that we could
issue commands without disrupting the data port.  Life with
consumer-grade modems is different.  I've heard of people trying to do
the Hayes-patented TIES "<delay>+++<delay>ATH1<nl>AT...<nl>ATO<nl>"
stuff with modified drivers in the past, but none of that (if it ever
was successful) ended up merging into the main code.  A virtual-port
based scheme (as you're citing) sounds a lot more promising.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

      parent reply	other threads:[~2019-07-15 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13 10:25 monitoring raw data walter harms
2019-07-13 11:10 ` Lev
2019-07-13 12:03 ` walter harms
2019-07-15 18:24 ` James Carlson [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=a5cba29c-1943-92db-0b6e-a61dae007ccc@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 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).