This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Error: Socket was forcibly closed by remote host
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Vijay Padiyar <vijay_padiyar at hotmail dot com>
- Cc: eCos Support <ecos-discuss at sources dot redhat dot com>
- Date: Tue, 5 Oct 2004 13:51:53 +0200
- Subject: Re: [ECOS] Error: Socket was forcibly closed by remote host
- References: <BAY1-DAV9FRaqbC8wSA0004ef05@hotmail.com> <20040929102257.GB18964@lunn.ch> <BAY1-DAV8tFlmmlQ0800004f93a@hotmail.com> <20040929114303.GF18964@lunn.ch> <BAY1-DAV622ZhCl8aii00036eb6@hotmail.com>
On Tue, Oct 05, 2004 at 05:11:37PM +0530, Vijay Padiyar wrote:
> Hi all
>
> Well we analyzed the network data with Ethereal. We find that during the
> Redboot initialization, the DHCP protocol works fine. The flow is as
> follows:
>
> Board DHCP Server
> ------------ -------------------
>
> DHCP INIT ----->
> <----- DHCP OFFER
> DHCP REQUEST ----->
> <----- DHCP ACK
>
> But during the application image execution, the DHCP phase goes as follows:
>
> Board DHCP Server
> ------------ -------------------
>
> DHCP INIT ----->
> <----- DHCP OFFER
> DHCP REQUEST ----->
> (TIMEOUT)
> DHCP REQUEST ----->
> (TIMEOUT)
> ..
> ..
> ..
> "BOOTP/DHCP Failed on eth1"
Have you tried actually debugging the problem? Is the packet received
by the ethernet driver? Does it get passed into the IP stack? Does the
IP stack pass it to the bootp code?
Once you have found out where the packet gets dropped you will be half
way to solving your 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