[comp.protocols.tcp-ip] mysterious 0x80... bytes from rlogin servers

chris@GYRE.UMD.EDU (Chris Torek) (09/30/88)

These bytes are sent as urgent (in 4BSD, `out of band') data, and
are intended to act as control operations.  The bits are defined
as follows:

#define	TIOCPKT_FLUSHREAD	0x01	/* flush packet */
#define	TIOCPKT_FLUSHWRITE	0x02	/* flush packet */
#define	TIOCPKT_STOP		0x04	/* stop output */
#define	TIOCPKT_START		0x08	/* start output */
#define	TIOCPKT_NOSTOP		0x10	/* no more ^S, ^Q */
#define	TIOCPKT_DOSTOP		0x20	/* now do ^S ^Q */
#define	TIOCPKT_WINDOW		0x80	/* can use new window size protocol */

The window size protocol consists of having the rlogin client send window
size changes as the sequence 0xff, 0xff, 's', 's', <rows>, <columns>,
<x-pixels>, <y-pixels>, where <> quantities are two bytes in network
(BigEndian) order.

There is (as yet) no way to send 0xff bytes when using the window size
protocol, but obviously one of (0xff <something other than 0xff>) or
(0xff 0xff <something other than `ss'>) will be used.  I favour 0xff 0x00
myself...

Chris