From: Andrew Lunn <andrew@lunn.ch>
To: Aaron M Paulos <apaulos@ece.cmu.edu>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] obtaining ip assigned by dhcp at runtime
Date: Wed, 29 Jun 2005 20:57:00 -0000 [thread overview]
Message-ID: <20050629205736.GH8479@lunn.ch> (raw)
In-Reply-To: <001601c57ceb$d7588a70$3201a8c0@macrtft>
On Wed, Jun 29, 2005 at 04:48:01PM -0400, Aaron M Paulos wrote:
> Hello,
>
> I'm working with demo boards/gdb stub to develop software, and basically
> have multiple logical IPs aliased to a single physical interface.
>
> Is there a function call succeeding init_all_network_interfaces(), to
> get the assigned DHCP IP?
Have you seen show_network_tables in
net/bsd_tcpip/current/src/ecos/support.c. It shows you one way to get
this information.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-06-29 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 20:49 Aaron M Paulos
2005-06-29 20:57 ` Andrew Lunn [this message]
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=20050629205736.GH8479@lunn.ch \
--to=andrew@lunn.ch \
--cc=apaulos@ece.cmu.edu \
--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).