From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Trenton D. Adams" To: Cc: "'eCos Disuss'" Subject: [ECOS] RE: Networking in a ROM build Date: Thu, 23 Aug 2001 09:07:00 -0000 Message-id: <002901c12bed$a97f99c0$090110ac@TRENT> References: <3B8528A0.279236E4@rd.francetelecom.fr> X-SW-Source: 2001-08/msg00776.html Thanks for that. Unfortunately, I don't have a Linux machine near by to do any packet dumping. FYI: http://freshmeat.net/projects/tcpdumpfilter/ The utility there should make your life a little easier with tcpdump. -----Original Message----- From: ramparfa@theone.dnsalias.com [ mailto:ramparfa@theone.dnsalias.com ] On Behalf Of Fano Ramparany Sent: Thursday, August 23, 2001 10:01 AM To: Trenton D. Adams Cc: eCos Disuss Subject: Re: Networking in a ROM build Trenton, This is exactly the problem we are currently facing and trying to solve (see some recent threads). A socket configuration that might solve your problem is to increase the socket timeout value: #include #define SOCK_TIMEOUT 50 ... int sd,len,rc; sd = socket(AF_INET, SOCK_STREAM, 0); struct timeval tv; ... tv.tv_sec = SOCK_TIMEOUT; tv.tv_usec = 0; setsockopt(sd, SOL_SOCKET, SO_RCVTIMEO, &tv, sizeof(tv)); This partially solved our problem, however, by sniffing the network traffic (using tcpdump) We have observed some strange behaviour on the ROM version of our application, which seems to buffer the first packets and at some stage sends them alltogether over the network. I've also added some delay between the ethernet driver initialization and the ip stack initialization, but this didn't solve the problem. I'll now try to add some tracing (CYGDBG_USE_ASSERT) to go further. Fano > When using a ROM version, the following thing happens: > The transmit and status signal threads connect to my windows machine > just fine. After they are connected, my windows machine attempts to > connect back to the embedded system's CommandThread socket. The > connection attempt times out.