[ECOS] Error: Socket was forcibly closed by remote host

[Vijay Padiyar]

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"

Why could this be happening? We are also including the DNS package while
building our application library. Could this by any chance have any effect?

I have attached the Ethereal capture data for both Redboot and application
DHCP handshakes [PLZ OPEN IN ETHEREAL].

Regards

Chandrashekhar Padiyar



----- Original Message -----
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Vijay Padiyar" <vijay_padiyar@hotmail.com>
Cc: "eCos Support" <ecos-discuss@sources.redhat.com>
Sent: Wednesday, September 29, 2004 5:13 PM
Subject: Re: [ECOS] Error: Socket was forcibly closed by remote host


> On Wed, Sep 29, 2004 at 04:50:31PM +0530, Vijay Padiyar wrote:
> > Hi Andrew
> >
> > In our current setup, the Redboot monitor gets its IP address from a
DHCP
> > server probably (it's certainly not our BOOTP server) coz the IP address
> > keeps on varying.
> >
> > Whereas for the application image, we're using BOOTP to get the IP
address
> > and we have our BOOTP server installed on a computer on the network. So
the
> > IP addresses for Redboot and the application are different. However, the
two
> > IP addresses are from different subnets. The IP address assigned by DHCP
to
> > Redboot is something like 192.168.128.210 (last part varies) and the IP
> > address configured by us in our BOOTP server is 192.168.144.200. Could
the
> > different subnets (192.168.128.xxx and 192.168.144.xxx) be causing any
> > problems by any chance??
>
> It should not cause this problem. You might have problems later if
> your gateway is not configured correctly to have two subnets on one
> physical net.
>
> > Everything else is as you've suggested it should be. Thanks for your
help!
>
> Look at the sources for your bootp server. Find out what it means by
> the error it is giving. bootp is based on UDP, so there is no
> connection between the client and the server, so the error seems
> strange to me. Understanding the error will probably get you a big
> step towards finding the problem.
>
>         Andrew
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: redboot.out
Type: application/octet-stream
Size: 7532 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20041005/89e3c076/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: application.out
Type: application/octet-stream
Size: 35069 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20041005/89e3c076/attachment-0001.obj>
-------------- next part --------------
-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss