home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!ames!data.nas.nasa.gov!taligent!apple!ntg!dplatt
- From: dplatt@ntg.com (Dave Platt)
- Newsgroups: comp.dcom.modems
- Subject: Re: UUCP 'G' protocol packet size
- Message-ID: <1992Sep9.173804.28612@ntg.com>
- Date: 9 Sep 92 17:38:04 GMT
- References: <1079@bazooka.amb.org> <kouqqB4w165w@zswamp.UUCP> <5259@airs.com>
- Organization: New Technologies Group, Inc. Palo Alto CA
- Lines: 29
-
- In article <5259@airs.com> ian@airs.com (Ian Lance Taylor) writes:
-
- >Moreover, every 'g' implementation that I am aware of will accept
- >varying block sizes in a single conversation, up to the requested
- >limit.
-
- Interesting - I've had almost the opposite experience. Both SunOS 4.1.x
- uucp (a HDB variant), and ULTRIX uucp (whatever version APPLE.COM is
- currently running) seem to have hard-coded 64-byte-packet receivers. If
- one tries to send them a shorter (32-byte) packet, neither one handles
- it properly... the packets are either rejected, or result in timeouts.
- I ended up deciding that "smart packet" mode (sending packets shorter
- than the limit) should be enabled only when the peer site sets a limit
- of 128 bytes or more.
-
- On the other hand, Taylor uucp is remarkably tolerant... it not only
- accepts packets which are shorter than the negotiated limit, but it also
- accepts packets which are _longer_ than the requested limit. I tried
- force-feeding it 256-byte packets, in a session which had requested a
- 64-byte limit, and it gobbled them down just fine. Nice work, Ian! [I
- know, I know, this technique is a revolting violation of protocol... but
- I haven't yet had the energy required to write up a set of Taylor-style
- configuration files which would enable g-protocol INIT negotiation of
- 256-byte packets... I'm still using HDB accomodation mode.]
-
- --
- Dave Platt VOICE: (415) 813-8917
- Domain: dplatt@ntg.com UUCP: ...netcomsv!ntg!dplatt
- USNAIL: New Technologies Group Inc. 2468 Embarcardero Way, Palo Alto CA 94303
-