public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Laurie Gellatly" <laurie.gellatly@netic.com>
To: <jporthouse@toptech.com>, <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Dynamic IP/DHCP/Routing the 'right way'
Date: Fri, 28 Jul 2006 21:59:00 -0000	[thread overview]
Message-ID: <OBEELMDOHGDFDEMJCJCJGEHMKDAA.laurie.gellatly@netic.com> (raw)
In-Reply-To: <MDAEMON-F200607281730.AA3005201md50000000459@toptech.com>

Hi Joe,
Taking Andrew's suggestion I rolled my own. Would you like to see a copy?

			...Laurie:{)

-----Original Message-----
From: Joe Porthouse [mailto:jporthouse@toptech.com]
Sent: Saturday, 29 July 2006 7:30 AM
To: ecos-discuss@ecos.sourceware.org; 'Laurie Gellatly'
Subject: RE: [ECOS] Dynamic IP/DHCP/Routing the 'right way'


Laurie,
Did you find a solution that worked?  I'm also dealing with this same issue.
Thanks,
Joe Porthouse
Toptech Systems, Inc.
Longwood, FL 32750

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andrew Lunn
Sent: Tuesday, June 06, 2006 7:19 AM
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 09:09:29PM +1000, Laurie Gellatly wrote:
> 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.

I think this is a new wheel, at least i've not seen a public available
wheel which does this.

cyg_route_reinit() might help with your routing problem.

     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




-- 
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:[~2006-07-28 21:59 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
2006-06-06 11:19         ` Andrew Lunn
2006-07-28 21:30           ` Joe Porthouse
2006-07-28 21:59             ` Laurie Gellatly [this message]
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=OBEELMDOHGDFDEMJCJCJGEHMKDAA.laurie.gellatly@netic.com \
    --to=laurie.gellatly@netic.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jporthouse@toptech.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).