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

["Vijay Padiyar" <vijay_padiyar at hotmail dot com>]

Hi all

We solved the problem with our board not accepting the IP address correctly
from the DHCP/BOOTP servers during the application image execution.
Ultimately we just changed the BOOTP server we were using (BOOTP Desktop
v1.5 [WierdSolutions.com]) with another DHCP/BOOTP server (Tftpd32
[Tftpd32.jounin.net]) and it started working. Not entirely satisfactorily
though.

On executing the program, we INITIALLY get the desired output...

------------------------------------------------------------------

CEntry point: 0x00040000, address range: 0x00040000-0x000a4858
xyzModem - CRC mode, 9249(SOH)/0(STX)/0(CAN) packets, 2 retries
RedBoot> go
[cyg_net_init] Init: mbinit(0x00000000)
[cyg_net_init] Init: cyg_net_init_devs(0x00000000)
Init device 'fcc_eth0'
Getting MAC address from EEPROM...
Reading MAC Addr for FCC1

Current MAC address for unit 0 is ff:ff:ff:ff:ff:ff
Getting ESA from EEPROM...
Unsupported PHY device - id: ffffffff
Init device 'fcc_eth1'
Getting MAC address from EEPROM...
Reading MAC Addr for FCC2
Current MAC address for unit 1 is 0:a0:1e:1:7:b1
Getting ESA from EEPROM...
PHY: Intel LXT971A
Negotiating PHY parameters...
FCC eth1: 100Mb/Full Duplex
[cyg_net_init] Init: loopattach(0x00000000)
[cyg_net_init] Init: ifinit(0x00000000)
[cyg_net_init] Init: domaininit(0x00000000)
[cyg_net_init] Init: cyg_net_add_domain(0x000a3e40)
New domain internet at 0x00000000
[cyg_net_init] Init: cyg_net_add_domain(0x000a38f8)
New domain route at 0x00000000
[cyg_net_init] Init: call_route_init(0x00000000)
[cyg_net_init] Done

Starting network...
SIOCSIFADDR: Device not configured
BOOTP/DHCP failed on eth0
BOOTP[eth1] op: REPLY
       htype: Ethernet
        hlen: 6
        hops: 0
         xid: 0x0
        secs: 0
       flags: 0x0
       hw_addr: 00:08:e5:11:22:33
     client IP: 0.0.0.0
         my IP: 192.168.144.224
     server IP: 0.0.0.0
    gateway IP: 0.0.0.0
  options:
        subnet mask: 255.255.255.0
       IP broadcast: 192.168.144.255
            gateway: 0.0.0.0

-------------------------------------------------------------------

But then it's followed by a lot of junk, in the form of 'Unknown options'...

-------------------------------------------------------------------

Unknown option: a/10.29: 216 0 0 0 0 0 10 46 56 0 12 140 240 0 12 141 80 0 0
0 0
 0 0 0 0 0 0 0 0
Unknown option: 2/2.0:
Unknown option: 80/128.8: 0 0 0 0 0 0 0 0
Unknown option: 18/24.0:
Unknown option: 40/64.0:
        subnet mask:
        subnet mask:
Unknown option: 8/8.62: 212 0 0 0 0 0 0 0 0 0 8 67 232 0 0 0 0 0 0 0 0 0 0 0
0 0
 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 50 0 0 0 0 0
        domain name: <Not a string: 0xB5198>
          host name: @
Unknown option: fe/254.251: 239 245 191 46 0 0 0 0 1 9 221 221 89 136 247
222 23
4 87 223 199 8 2 255 55 70 255 253 102 68 0 253 239 159 219 254 163 3 32 118
197
 230 121 255 86 0 0 255 107 18 226 223 235 25 128 191 229 191 215 239 251
192 0
223 189 174 239 223 201 2 128 188 127 255 127 242 250 32 0 223 237 234 235
255 1
62 56 4 254 63 191 255 251 246 4 0 251 249 221 220 215 247 34 0 253 251 78
190 1
87 219 18 0 239 250 157 171 255 110 64 0 239 250 63 158 187 111 69 0 255 237
237
 255 235 66 132 0 116 206 75 234 173 41 17 4 255 61 255 238 253 181 42 72
245 23
3 223 246 174 37 32 0 245 255 182 118 127 91 34 0 223 251 127 205 249 198 44
1 2
51 214 250 247 255 249 8 0 255 190 159 218 255 213 8 32 252 157 207 251 27
227 0
 64 123 239 118 190 223 150 2 64 255 149 253 255 255 248 128 0 175 223 231
170 2
46 220 140 64 175 125 59 55 186 188 96 0 191 255 183 169 159 98 40 8 158 255
230
 223 235 81 74 128 223 191 58 183 183
Unknown option: a6/166.68: 0 255 223 101 247 191 41 1 0 253 155 191 127 245
113
42 2 0 0 1 9 83 116 97 114 116 105 110 103 32 110 101 116 119 111 114 107 46
46
46 10 187 22 155 253 189 117 136 0 127 239 182 229 125 89 32 2 255 251 239
37 24
7 66 34 2 238 235 93
Unknown option: fa/250.251: 243 17 0 252 247 221 165 253 189 40 0 252 255
220 22ghg
3 127 249 64 0 247 254 252 255 250 222 128 0 239 253 235 247 239 88 101 64
255 2
55 187 222 239 235 69 0 253 251 255 227 107 45 0 0 223 126 255 247 239 115
97 32
 191 239 102 175 203 229 2 0 254 215 127 255 175 73 16 66 251 223 207 175
255 86
 24 148 255 243 191 253 95 234 98 0 255 239 222 179 126 172 128 0 255 233
239 15
7 253 188 128 0 223 255 189 219 252 164 0 16 222 251 101 203 125 59 8 0 251
173
111 250 253 237 64 0 126 255 243 189 239 212 25 0 187 246 238 219 223 191 80
8 1
23 239 254 253 239 68 0 8 126 251 175 123 247 93 129 0 127 122 231 214 221
214 1
28 0 123 250 87 237 255 105 146 0 127 219 222 151 222 54 8 4 253 171 127 246
230
 236 5 64 223 250 121 255 191 205 33 0 222 89 142 183 237 73 20 0 7 240 11
177 1
26 186 128 0 223 247 73 213 219 123 72 1 95 255 83 222 217 121 4 0 255 90
187 25
1 127 118 68 68 255 207 175 253 206 57 0 4
..
..
..
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
[eth_drv_ioctl] Warning: Driver can't set multi-cast mode
Route - dst: 0.0.0.0, mask: 0.0.0.0, gateway: 5.3.7.3
SIOCADDRT 3: Network is unreachable
Network initialization failed for eth1

Hello, eCos world!

-------------------------------------------------------------------

So we're currently investigating where all these junk options are coming
from. And also, why everything started working with just a change in the
DHCP server. Any comments?

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
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss