I've been having problems with a coda client that runs something like
mobile IP and is on a wavelan.  When the client lists a directory, the
server sends a 2208 byte packet.  This is fragmented at the server.
Both fragments travel to the home agent, and the first fragment is
further fragmented to fit in the tunnel.  Then, with multi-hop wavelan
forwarding, one (the second chunk) is almost always lost.  Adding
IPSEC and PPP links with <1500 byte MTUs makes this worse.
While my network should perhaps be better behaved, I'd like to avoid
IP fragmentation entirely most of the time.

Is there some way to configure rpc2 to only send packets with 1K of
data?  The "-se" part seems to break things up like this.

I'm running code from anoncvs from the last few weeks.  I've been
impressed at how stable this is compared to the code from a year ago!

        Greg Troxel <gdt_at_ir.bbn.com>