This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Multiple PPP interfaces in single unit
- From: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- To: Nick Garnett <nickg at ecoscentric dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Wed, 28 Jul 2004 15:27:08 +0200
- Subject: Re: [ECOS] Multiple PPP interfaces in single unit
- References: <1091017108.3449.13.camel@famine> <m3zn5ke0iq.fsf@xl5.calivar.com>
On Wed, 2004-07-28 at 15:15, Nick Garnett wrote:
> Øyvind Harboe <oyvind.harboe@zylin.com> writes:
>
> > Is it possible to use the PPP stack to chain multiple devices via
> > the serial ports?
> >
> > I.e.:
> >
> > Unit 1
> >
> > Serial 1 talks to PC via PPP
> > Serial 2 talks to unit #2 via PPP
> >
> > Unit 2:
> >
> > Serial 1 talks to Unit #1 via PPP
> > Serial 2 talks to Unit #3 via PPP
>
> We cannot do this at present, it's an explicit limitation of the
> current implementation. The expectation was that most eCos devices
> would be solitary remote devices that were dialled into, or dialled
> out. So a single PPP connection would be the ususal case.
>
> The main problem is that the PPPD code was designed to instantiate a
> separate Unix process for each PPP channel. So there are a lot of
> global variables that would need to be duplicated in some way.
Seperate C++ namespace for each PPPD?
- Write a pppd2.h file
---
namespace PPPD2;
---
- Compile PPPD twice, but second time add option:
g++ -include pppd2.h ...
> The
> code within the TCP/IP stack itself should not need changing, however.
>
> This is not a trivial job unfortunately, and anything we do would
> seriously inhibit any efforts to update the PPP code from the BSD
> repository.
--
Øyvind Harboe
http://www.zylin.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss