Thread View: fa.tcp-ip
1 messages
1 total messages
Started by Jeffrey I. Schiller
Mon, 30 Sep 1985 04:00
problems getting to CISL-SERVICE-MULTICS
Author: Jeffrey I. Schiller
Date: Mon, 30 Sep 1985 04:00
Date: Mon, 30 Sep 1985 04:00
16 lines
1522 bytes
1522 bytes
Actually the situation with CISL-SERVICE-MULTICS is more complicated then that. CISL is running an IP/TCP which doesn't understand about any other network but net 10 (The ArpaNet). There is a kludge installed in its IP that sends any non-net-10 packet to MIT-MULTICS who then routes it apropriately. Now MIT-MULTICS is constrainted to not send packets greater then 200 bytes (because if it does, the IMP it is plugged into crashes... a problem (unresolved now for over two years) with message mode HDH support in the IMP). So chances are now that CISL is sending you 572 byte packets which are being fragmented by MIT-MULTICS. It is quite possible that either your reassembly code is bad or MIT-MULTICS's fragmentation code is bad (MIT-MULTICS's TCP arranges never to send segments that would be fragmented by the IP layer). Some IP tracing would probably help. -Jeff
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads