This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: network test problem on ipaq
- To: Weilong Li <weilongli2000 at yahoo dot com>
- Subject: Re: [ECOS] network test problem on ipaq
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Mon, 02 Jul 2001 20:14:16 +0100
- Cc: ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat UK Ltd.
- References: <20010702190223.28396.qmail@web14308.mail.yahoo.com>
Weilong Li wrote:
>
> I also tried running tcp_echo before, after
> tcp_echo is running, I cannot ping ipaq,
> so tcp_source and tcp_sink will always
> return "no route to host" error message.
> The ip address of ipaq I'm talking about
> is assigned by running a dhcp server on linux host,
> then upon redboot boots, it will detect the
> socket communication ethernet card, and then
> assign the ip address. So in this sense,
> I think the ip address is redboot's ip address.
> I don't know how the ip address of ecos is assigned,
> can you elaborate on this ?
The eCos network stack does not use redboot's ip address ( you can't have
two different network stacks processing the same data). The eCos stack's IP
address is set according to the CDL data, either also from BOOTP/DHCP, or
statically. Try setting it statically as that's safest. Look for the
component CYGHWR_NET_DRIVER_ETH0_SETUP_OPTIONS and the options within it.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/