Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Deprecate rp-pppoe package
Date: Tue, 20 Jul 2010 15:47:42 -0300	[thread overview]
Message-ID: <4C45EF4E.1000501@zacarias.com.ar> (raw)
In-Reply-To: <1278436093.12234.11.camel@localhost.localdomain>

On 07/06/2010 02:08 PM, Darcy L. Watkins wrote:

> Hello,
> 
> Before you remove the rp-pppoe package from buildroot, I have a
> question.  Does the pppoe plugin for pppd include the access
> concentrator (AC) support in it as well?
> 
> I ask this because most people only care about the client side and don't
> think much about the server side you connect it to.
> 
> A while back, I cross compiled the AC functionality of rp-pppoe on
> powerpc, added a freeradius client and demo'd a simple embedded AC on an
> AMCC Taihu involving, a private LAN, freeradius running on a server
> machine and a windows PC running its PPPoE client.  I was able to
> advertise numerous "services" from the Taihu and have the PC be able to
> select and connect to them using PPPoE sessions.
> 
> Regards,
> 
> Darcy

Hi.
Hmm we might keep rp-pppoe for server-side functionality.
Do you feel like migrating the package to the latest infrastructure and
updating to the latest version?
Regards.

  reply	other threads:[~2010-07-20 18:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 17:08 [Buildroot] Deprecate rp-pppoe package Darcy L. Watkins
2010-07-20 18:47 ` Gustavo Zacarias [this message]
2010-07-20 19:44   ` Darcy Watkins
2010-08-23 14:52     ` [Buildroot] [PATCH] " Darcy Watkins
2010-08-23 17:17       ` Darcy Watkins
2010-08-23 18:26         ` Gustavo Zacarias
2010-08-23 20:14           ` Darcy Watkins
  -- strict thread matches above, loose matches on Subject: below --
2010-10-13 16:13 [Buildroot] " Darcy Watkins
2010-10-13 20:09 ` Gustavo Zacarias
2010-10-15 20:25 ` Gustavo Zacarias
2010-06-01 19:51 Gustavo Zacarias

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=4C45EF4E.1000501@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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