cam@saturn.ACC.COM (Chris Markle acc_gnsc) (09/07/89)
Folks,
(Sorry for the previous null msg; where's the system administrator when
you need 'em?)
Our TCP/IP implementation seems to be having a problem interoperating
effectively with another vendor's implementation. The other vendor's
implementation is supposedly based upon the bsd 4.2 networking code.
So...
1) Does anyone maintain a list of 4.2 networking code bugs/problems?
If so, could they point me to it or send it to me via US- or e-mail
(preferably email)?
2) The specific trouble involves the FTP data connection. We are sending
to the "4.2" system. One of our packets gets lost/mangled/whatever. We
have transmitted segments into the receiver's window beyond the lost
segment. Eventually we retransmit the lost segment which gets ack'ed by
the receiver.
But somewhere in here it seems as if our notion of the receiver's window
and the receiver's ("4.2") notion may have become different.
After the packet get retransmitted, the receiver seems to continously
discard two (2) packets from the "righthand" side of the receiver's
receive space, even though the segments are within the calculated receiver
window. (Also, although the receiver varies the rwindow up to the point
of the packet lost, after that the receiver seems stuck on a 8192 rwindow;
maybe that's what he really thinks but it seems curious.)
Does this sound familiar to anyone who knows the 4.2 networking code?
3) Are there some secret / "under-the-cover" trace or debugging facilities
in 4.2 that can easily be manipulated to help us get more doc on this
situation?
Thanks in advance for anyone's help with this...
(Reply to me or to the net, as you see fit...)
Chris Markle
ACC
10220 Old Columbia Rd.
Columbia, MD 21046
(301)290-8100
(301)290-8106 (fax)