Linux PPP protocol development
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Fooling PPP into thinking its connected
Date: Sat, 23 May 2009 18:17:01 +0000	[thread overview]
Message-ID: <18968.15773.427657.82139@gargle.gargle.HOWL> (raw)
In-Reply-To: <23684368.post@talk.nabble.com>

f15radar writes:
> I have 3 freewave radios (they are serial radios) that have the ethernet
> stuff disabled.  I am using PPP to connect 2 of the radios.  I want to add
> the third radio.  If I could fool PPP into thinking it was connected (its
> getting all of the data being sent between the other 2) I could add the
> third radio.  Does anyone know how I might do that?

Mostly because of the assumptions built into those first two P's, PPP
doesn't much like multidrop operation.

I can think of a couple of ways to hack this up, though.  You could
modify the third pppd so that it doesn't negotiate at all, and (as
long as the data packets packets weren't interleaved in the air) it
would work.  The crucial problems there are that each of the first two
would (uselessly) receive packets from the other, and you'd need some
static routes on both of them to get packets to the third over the PPP
links.  And, of course, you'd have to hack up pppd fairly
substantially.

The other way to do it would be to modify the kernel's PPP support so
that it can deal with HDLC addressing (as is done with PPP over Frame
Relay).  You'd still have the potential problem of interlaced messages
on the air causing dropped frames, and the (relatively simple) routing
issue, but at least pppd state machines wouldn't need hacking.

(The interlacing problem is simple to describe: when both of those two
stations transmit at once, or even nearly so, what does the third
receive?  If it gets bunches of characters from one and then then
other, without regard to the PPP frame boundaries, then the frames
won't pass through AHDLC decoding.  The third station will see frame
drops.)

If you need it to be reliable, though, your best bet would be to get
equipment that actually supports multiple distinct point-to-point
serial links, or (better yet) a packet-based multi-access mode, rather
than trying to get Point-to-Point operation out of a party line.

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

      reply	other threads:[~2009-05-23 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23 13:05 Fooling PPP into thinking its connected f15radar
2009-05-23 18:17 ` 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=18968.15773.427657.82139@gargle.gargle.HOWL \
    --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