This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Problem with TCP Urgent data (old stack).
- From: Grant Edwards <grante at visi dot com>
- To: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 24 Apr 2003 10:10:18 -0500
- Subject: [ECOS] Problem with TCP Urgent data (old stack).
I'm using the old TCP/IP stack to talk to linux telnetd.
When my eCos app sends a Ctrl-C to telnetd, it kills the
running shell command and inserts a telnet data-mark (0xff
0xf2) as urgent data in the stream.
The eCos TCP/IP stack only removes the first byte of the
sequence so that my app sees the 0xf2 but not the 0xff.
There's a comment in the old TCP/IP code that says:
* According to RFC961 (Assigned Protocols),
* the urgent pointer points to the last octet
* of urgent data. We continue, however,
* to consider it to indicate the first octet
* of data past the urgent section as the original
* spec states (in one of two places).
Have I run into the a case where the Linux stack is following
RFC961 and eCos isn't, so the last byte of urgent data is
appearing in the data stream?
I don't care whether the two bytes of urgent data are present
in the data stream or not, but I can't deal with half one way
and half the other...
--
Grant Edwards
grante at visi dot com
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss