public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Retallack, Mark \(Siemens\)" <mark.retallack@siemens.com>
To: "Gonçalo Antunes" <gmma@gmma.net>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] setting up SLIP/PPP incoming connections
Date: Fri, 20 May 2005 09:24:00 -0000	[thread overview]
Message-ID: <B573B0465A4EFB42997BADDC2FBDE1540948F2@ples506a.stcl.siemens.co.uk> (raw)

Ppp has no concept of server or client. It is a peer to peer connection. Each peer can wait for the other end to connect. So Yes, the PPP stack in eCos can act like a "Server". 

I don't think SLIP is available. 

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Gonçalo Antunes
Sent: 20 May 2005 00:14
To: Nick Garnett
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] setting up SLIP/PPP incoming connections


I understand that PPP only works with FreeBSD stack... but I would like to 
know if there is a way to put the eCos application to wait for PPP 
connections. I want eCos to be the PPP server, not the client... is it 
possible?
If not possible... is SLIP avaiable?

Thank you.

Gonçalo

----- Original Message ----- 
From: "Nick Garnett" <nickg@ecoscentric.com>
To: "Gonçalo Antunes" <gmma@gmma.net>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Thursday, May 19, 2005 4:07 PM
Subject: Re: [ECOS] setting up SLIP/PPP incoming connections


Gonçalo Antunes <gmma@gmma.net> writes:

> Hi to all!
>
> I'm trying to setup an eCos application on a i386 pc.
> This application will  focus on serving info throught the eCos HTTP
> server.
> The ethernet component is OK... but I would also like to put up
> running a SLIP or PPP server and serve the ecos webpage through it.
> Can anyone help me on setting up the PPP server ? Which net Stack do
> you recommend?

PPP only works with the FreeBSD stack.

To set it up, just follow the instructions in the documentation:

http://ecos.sourceware.org/docs-latest/ref/ppp.html

-- 
Nick Garnett                                     eCos Kernel Architect
http://www.ecoscentric.com                The eCos and RedBoot experts




-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2005-05-20  7:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20  9:24 Retallack, Mark (Siemens) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-19 15:08 [ECOS] C++ Support Raghavendra K
2005-05-19 15:58 ` [ECOS] setting up SLIP/PPP incoming connections Gonçalo Antunes
2005-05-20  2:14   ` Nick Garnett
2005-05-20  8:17     ` Gonçalo Antunes
2005-05-20 10:01       ` Nick Garnett
2005-05-19 19:40 ` Gonçalo Antunes

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=B573B0465A4EFB42997BADDC2FBDE1540948F2@ples506a.stcl.siemens.co.uk \
    --to=mark.retallack@siemens.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gmma@gmma.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).