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: Thu, 03 Jun 2010 13:13:52 +0000	[thread overview]
Message-ID: <4C07AA90.1030704@workingcode.com> (raw)
In-Reply-To: <AANLkTikV_j1ajMThiB8B6DoaZpZ4fhlIRVVk2jK30-h8@mail.gmail.com>

arun b wrote:
> Hi James,
> 
> Yes I am convinced with your schismatic-presentation, now I know what
> exactly it need to run server.
> 
> And I would say,  it is not possible  for me to test PPPoA because.
> 1) As we neither have DSLAM with uplink is ATM path nor the built in
> support for PPP, rather it has only Ethernet-uplink .

I assume that's what you meant by "RJ-11" in your previous postings.

For what it's worth, RJ-11 is typically used for Ethernet, but can also
be used for DS-1 and other signals.  It's just an electromechanical
connector, and saying you have "RJ-11" doesn't tell us much about what
sort of equipment you're using.  (Other than what it looks like ...)

> 2) Also do not available of any  Linux-server which terminates the ATM-path.
> So I will have  to explore the possibility, how can I arrange this...!
> 
> So one doubt again, Could you please name the know-standard-devices
> (manufactures/makes) for Linux-server in the below diagram, which has
> support of similar server-command mentioned by you in the previous
> e-mail.

As the other James mentioned, this really isn't the right list for that
sort of question, because it's not so related to PPP, and the people you
need aren't necessarily subscribed to this list.  You may need to do
some investigation on your own.

It's unclear what hardware you need to support.  You probably need to
work that out.  Perhaps the simplest answer (to test PPPoA and ignoring
all else) would be to get two ATM NICs and connect them back-to-back; see:

http://www.linux.org/docs/ldp/howto/ATM-Linux-HOWTO/signaling.html#SIGNALING.RUNNING-TWO-ATM-NICS-BACK-TO-BACK

Or even simpler with the ATM/TCP "test" driver.  Or maybe you need to
invest in some ADSL test gear or have your system evaluated by a
commercial testing service.

An even better answer would be to scout around for an ATM or ADSL expert
to advise you.

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

  parent reply	other threads:[~2010-06-03 13:13 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
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 [this message]
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=4C07AA90.1030704@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.