public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Hugo Tyson <hmt@redhat.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: DHCP shuts down Ethernet device?
Date: Tue, 24 Apr 2001 06:00:00 -0000	[thread overview]
Message-ID: <wwtd7a2cv51.fsf@masala.cambridge.redhat.com> (raw)
In-Reply-To: <3AE48294.6C00FA4C@redhat.com>


Jonathan Larmour <jlarmour@redhat.com> writes:
> Anthony Massa wrote:
> > >> I am running RedBoot on an MBX board and downloading my eCos
> > >application
> > >> with networking support.
> > >>
> > >> I noticed your post about the Ethernet device shutdown and
> > >was wondering if
> > >> I could possibly be running
> > >> into the same problem.
> > >
> > >Only if you don't have a DHCP server on your net and you're
> > >trying to use
> > >the ethernet driver for other purposes than the TCP/IP stack.
> > 
> > I have a DHCP server on my net.  However, my confusion comes with the fact
> > that I have RedBoot coming up using BOOTP, which I have a server for as
> > well.  So, RedBoot gets its IP address.  Is this address then passed onto
> > the application, or is the application layer supposed to get its own, new
> > address?

The latter.  The app gets a separate IP address.

> > I'm a little confused about how the RedBoot and eCos app layer stack coexist
> > on my target.  I am using the RedBoot Ethernet for debugging the
> > application.
> 
> They each get their own *IP* addresses. Or one can be static and the other
> dynamic, or whatever you want. Think of them as completely separate.

...but they share a MAC address (inevitably).  Which means that it is
unlikely to work correctly if you have *both* IP addresses acquired
dynamically, because the BOOTP or DHCP server doesn't know who is asking,
so doesn't know which of the two IP addresses to serve.

I suppose that, since RedBoot uses BOOTP only, and the eCos stack uses DHCP
only, if you tell your DHCP server to ignore BOOTP requests, then they
would be distinguished correctly.  But the servers are quite entitled to
cancel the address they handed out "last time" if they see the same MAC
address asking for (and getting) a different address.

I always configure a static IP address in RedBoot's fconfig world, for use
by RedBoot, and let the eCos app get a dynamic address from DHCP.  That
works fine.

	- Huge

  reply	other threads:[~2001-04-24  6:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 12:25 Anthony Massa
2001-04-23 12:29 ` Jonathan Larmour
2001-04-24  6:00   ` Hugo Tyson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-23 11:49 Anthony Massa
2001-04-23 12:22 ` Jonathan Larmour

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=wwtd7a2cv51.fsf@masala.cambridge.redhat.com \
    --to=hmt@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).