All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPPoA server setup how to?
Date: Wed, 02 Jun 2010 10:57:38 +0000	[thread overview]
Message-ID: <4C063922.3030003@workingcode.com> (raw)
In-Reply-To: <AANLkTikV_j1ajMThiB8B6DoaZpZ4fhlIRVVk2jK30-h8@mail.gmail.com>

On 06/02/10 05:26, James Chapman wrote:
> starts a pppd instance on ATM VPI 0, VCI 80 and assigns IP 192.168.1.1
> to the local interface and 192.168.1.2 to the peer when the PPPoA peer
> connects on VPI 0, VCI 80. If you are building a DSLAM-like box which
> accepts connections from many PPPoA clients, you will need to start a
> pppd instance for every possible ATM VPI/VCI that clients might use...

That's one possibility.  Another would be having UNI Q.2931 signaling
set up the virtual circuit for you, and launching pppd based on the
signaling.

I don't think the existing implementation includes the bits required to
do that.  You'd have to write it yourself.  And it (obviously) depends
on what sort of connection you have to the network.

>> Well I coated this (PADI, PADO,...) because, wanted to know does PPPoA
>> also follows these message sequence or it has new set of sequence ?
> 
> No, they are for PPPoE.

The closest equivalent to those messages I can imagine would be the ATM
signaling mechanism referenced above.

But I think it's probably time to take a step back and ask the obvious
question: can you tell us what you've got (in terms of hardware,
software, and operational environment) and what you're trying to do (in
as much high-level detail as possible)?

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

  parent reply	other threads:[~2010-06-02 10:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 14:54 PPPoA server setup how to? arun b
2010-06-01 15:10 ` James Carlson
2010-06-02  7:58 ` arun b
2010-06-02  9:26 ` James Chapman
2010-06-02 10:57 ` James Carlson [this message]
2010-06-02 13:21 ` arun b
2010-06-02 13:58 ` arun b
2010-06-02 14:26 ` James Carlson
2010-06-02 16:35 ` arun b
2010-06-02 16:54 ` James Chapman
2010-06-02 17:41 ` arun b
2010-06-02 17:41 ` James Chapman
2010-06-02 17:54 ` arun b
2010-06-02 17:56 ` James Carlson
2010-06-02 18:20 ` arun b
2010-06-02 19:56 ` James Chapman
2010-06-03  7:56 ` arun b
2010-06-03  9:21 ` James Chapman
2010-06-03 13:13 ` James Carlson
2010-06-03 13:14 ` arun b
2010-06-03 13:21 ` James Carlson
2010-06-03 13:58 ` arun b
2010-06-03 13:59 ` James Carlson
2010-06-05  7:46 ` arun b
2010-06-06 21:17 ` James Carlson

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=4C063922.3030003@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.