This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: problem with TCP/IP stack
- To: Gary Thomas <gthomas at cambridge dot redhat dot com>
- Subject: RE: [ECOS] problem with TCP/IP stack
- From: Gary Guangyu Pei <pei at CS dot UCLA dot EDU>
- Date: Fri, 26 Jan 2001 16:39:44 -0800 (PST)
- cc: ecos-discuss at sources dot redhat dot com
Yes, you are right. I modified one of the test program: udp_lo_test.c
program. Instead of using a loopback address, I use the real IP address.
Thank you,
Gary
On Fri, 26 Jan 2001, Gary Thomas wrote:
|Are you trying to run one of our test/demo programs? If not, I'm not
|sure I understand your "UDP server" terminology.
|
|On 26-Jan-2001 Gary Guangyu Pei wrote:
|> Hi,
|> I encountered the following problem with TCP/IP stack:
|> It cannot run both UDP server and client together. If I run server only,
|> it can receive UDP packets from the other nodes. However, if I run both
|> client and server, the client can keep on sending out packets, the server
|> will stop receiving packets after it receives the first packet (or
|> sometime the first 2 packets) from a client. I use the gdb to trace the
|> program. I find the received packages travelling along the protocol stack
|> all way up to udp_usrreq.c. After calling the sorwakeup() at line 565, the
|> server thread never gets to run.
|>
|> Does anyone know what might go wrong? Do you have similar experience?
|>
|> The network priority is 7. I tried both 6,7,8 priority for the udp server.
|>
|> Thank you very much, any suggestion is highly appreciated.
|>
|> Gary
|>
|