[ECOS] Re: connect Ethernet cable at run-time

[Grant Edwards]

On 2009-09-26, Laurie Gellatly <laurie.gellatly@netic.com> wrote:

> For our product there is a reason. If there is no Ethernet
> connection other operations can still be done.

They can't be done while the DHCP client retries?

> As the web server is monitored by the watchdog it's important
> that it not get stuck waiting on DHCP.

I guess I don't understand your requirements.  If there's no
EThernet link, what else does the web server have to do except
wait for it?  It can't it kick the watchdog timer while the
DHCP client is attempting to acquire an address?

> So we don't need the device to be plugged into the network
> either and it will continue to work with what it can. When the
> network does connect, other capabilities start.

All of which is fine, but what I don't understand is why it
precludes the DHCP client from retrying.  When the DHCP client
does acquire an address and brings up the interface, then those
"other capabilities" can start.  None of my products have the
requirement that "capabilities" can only start during a certain
time window after the board starts.  They could start whenever
the Ethernet link does comes up?

> If the user wants to change between DHCP and static addresses
> then that too is possible without having to restart our
> device.

That's a nice feature, but again I don't understand why it
precludes the DHCP client from retrying.

-- 
Grant



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