This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
RE: BOOTP problem
- From: Jay Foster <jay at systech dot com>
- To: 'Alexey Shusharin' <mrfinch at mail dot ru>, ecos-discuss at ecos dot sourceware dot org
- Date: Fri, 8 Feb 2008 08:39:43 -0800
- Subject: RE: [ECOS] BOOTP problem
If you use the latest sources from CVS, you should enable the
CYGOPT_NET_FREEBSD_STACK_ACCEPT_UNICAST option to define BOOTP_COMPAT. This
will permit BOOTP to work. This assumes that you are using the Free BSD
network stack.
Jay
-----Original Message-----
From: Alexey Shusharin [mailto:mrfinch@mail.ru]
Sent: Friday, February 08, 2008 2:30 AM
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] BOOTP problem
Hello,
I'm trying to use BOOTP to gather configuration from server. RedBoot
BOOTP support works fine, but eCos application doesn't receive BOOTREPLY
message, although server sends it.
If i edit bootp_support.c and add broadcast flag to BOOTREQUEST (and so
server sends BOOTREPLY as broadcast) client receives information. But as
i understand it's not best decision.
DHCP works fine with RedBoot and eCos application.
There is the problem?
Does anybody use BOOTP (not DHCP) in eCos application?
I use lpc2xxx hal, Cirrus Logic CS8900A ethernet controller and freebsd
stack ecos port.
Thanks
Best regards
Alexey Shusharin
--
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