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 17:56:04 +0000	[thread overview]
Message-ID: <4C069B34.1050308@workingcode.com> (raw)
In-Reply-To: <AANLkTikV_j1ajMThiB8B6DoaZpZ4fhlIRVVk2jK30-h8@mail.gmail.com>

James Chapman wrote:
> arun b wrote:
>> Again to clear the  confusion....
>> yes with above remote devices I have tested  for PPPoE on ATM
>> can i call this test as PPPoEoA  !!!!!
> 
> Perhaps you mean PPPoE over an RFC1483 bridged encap ATM link? And now
> you're trying to get PPP working over a VC-muxed ATM connection.

You beat me to it.

It's important to note that these are *completely* different animals.
In the PPPoE with ATM case, the ATM link is really just bridging
Ethernet.  It doesn't really "know" that there's PPP traffic inside, as
it only "sees" Ethernet.

In fact, you can carry *normal* IP traffic over that same sort of
bridged ATM link without bothering to use PPPoE at all; some ADSL
providers in fact did just that -- though most were bitten by the PPPoE
bug, some were not.  It's even easier to do this, provides better
performance, and avoids the MTU hassles of PPPoE.

In the PPPoA case, the ATM link is carrying PPP frames.  The VC is
normally dedicated to just PPP in that instance.  There's no Ethernet
involved and thus no PPPoE.  (And a bit lower overhead than any of the
above schemes.)

Don't confuse the two of them.  Except for potentially using the same
raw hardware, they're quite different in terms of design.  For instance,
the ATM termination equipment in the bridged case is a "simple" Ethernet
bridge, and not much else.  In the PPPoA case, it _must_ terminate ATM
and PPP, and then, if there are any other nodes that use the link, it
must act as a router (or NAT) for the traffic that goes over it.  With
PPPoE, those parts are in the end station that runs PPPoE and PPP.

And, no, I wouldn't call the test "PPPoEoA," though that's more or less
what you'd see on the ATM link itself.  The fact that PPPoE is
"normally" run over Ethernet that's then bridged over ATM is more a
monument to Babel than anything else.  ;-}

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

  parent reply	other threads:[~2010-06-02 17:56 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
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 [this message]
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=4C069B34.1050308@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.