This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Error: Socket was forcibly closed by remote host


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??

Everything else is as you've suggested it should be. Thanks for your help!

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 3:52 PM
Subject: Re: [ECOS] Error: Socket was forcibly closed by remote host


> On Wed, Sep 29, 2004 at 03:24:05PM +0530, Vijay Padiyar wrote:
> > Hi all
> >
> > We are facing a strange problem. We first run the Redboot monitor with
> > Ethernet support and obtain the Redboot prompt. Then we load the
application
> > image obtained by compiling 'hello.c' with
'init_all_network_interfaces()'
> > and the net template build in eCos Config Tool.
> >
> > When the Redboot monitor executes, it is able to successfully get the IP
> > address from a BOOTP/DHCP server. But when we execute the kernel image,
it
> > sends a BOOTP request to the BOOTP server, and the BOOTP server even
> > responds to it (we can see this in the BOOTP log window), but then the
BOOTP
> > server flashes a dialog saying "Error: Socket was forcibly closed by
remote
> > host". And the terminal window shows "BOOTP/DHCP failed on eth1". We are
> > using FCC2/eth 1 for our board.
>
> Redboot and the applications need to have different IP addresses. One
> way to do this is to use bootp for redboot and DHCP for the
> application. You can then configure your servers so that they give out
> different addresses. Do you have this setup or do you assign the same
> IP address to both redboot and the application.
>
>         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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]