From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: "'Andrew Lunn'" <andrew@lunn.ch>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Dynamic IP/DHCP/Routing the 'right way'
Date: Tue, 06 Jun 2006 11:09:00 -0000 [thread overview]
Message-ID: <007701c68959$b316fa40$0101010a@netic.com> (raw)
In-Reply-To: <20060606105606.GB15066@lunn.ch>
Hi Andrew,
Thanks for the swift response.
SNTP - yes. Thanks for the tips there and with DNS, I'll look at those.
init_net() was not sufficient. It left the old addresses active. I've
combined StackInit and IP_SetIP, IP_SetMask to remove the old address
and mask. Still think the routing is not being updated, but before I
launched into debugging all that I wanted to ensure I wasn't
re-inventing the wheel.
Thanks ...Laurie:{)
-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: Tuesday, 6 June 2006 8:56 PM
To: Laurie Gellatly
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Dynamic IP/DHCP/Routing the 'right way'
On Tue, Jun 06, 2006 at 08:36:52PM +1000, Laurie Gellatly wrote:
> Hi All,
> I'll be working with the PHYTEC2294 board in preparation to using the
> Philips LPC2210 and LPC2102 in production.
>
> My project will allow the user to change the various IP settings
> (Address/Mask/gateway/DHCP) while the system is running. I.E. address
> and mask are updated (old addresses are deleted). Gateway changes
> cause the default route to be updated. DHCP can be turned off/on.
>
> I've found some older posts about this and tried them. Maybe I missed
> something but so far I've not found a single solution that covers all
> my needs. Is there such a solution or is there a 'right way' to
> achieve this?
You might need to write your own dhcp management thread which calls the
dhcp state machine as needed, or calls the init_net() function with your
static addressing information.
> After these I'll need to do the same for NTP and DNS.
By NTP you mean SNTP? You should be able to call
cyg_sntp_set_servers() at anytime to tell it about a change of unicast
SNTP server.
With DNS similarly cyg_dns_res_start() can be called at any time to
indicate a new server.
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
next prev parent reply other threads:[~2006-06-06 11:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 16:55 [ECOS] LPC2214 Porting issue: Garbage data on Serial Console Tom B
2006-06-05 17:08 ` [ECOS] " Tom B
2006-06-06 10:37 ` [ECOS] Dynamic IP/DHCP/Routing the 'right way' Laurie Gellatly
2006-06-06 10:56 ` Andrew Lunn
2006-06-06 11:09 ` Laurie Gellatly [this message]
2006-06-06 11:19 ` Andrew Lunn
2006-07-28 21:30 ` Joe Porthouse
2006-07-28 21:59 ` Laurie Gellatly
2006-07-29 1:52 ` Joe Porthouse
2006-07-31 7:32 ` Laurie Gellatly
2006-06-06 11:16 ` [ECOS] eCos meets SHTTPD (web server) Laurie Gellatly
2006-06-06 12:38 [ECOS] Dynamic IP/DHCP/Routing the 'right way' FALL
2006-06-06 21:26 ` Laurie Gellatly
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='007701c68959$b316fa40$0101010a@netic.com' \
--to=laurie.gellatly@netic.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
/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).