Kain, Becki (B.) wrote:

We have this continuing issue - we have the same software talking to the same mainframe. On the solaris to mainframe side, we send a fin,ack, the mainframe sends back a fin,psh,ack, solaris sends an ack. On linux, we send the same fin, ack to the mainframe then immediately send rst,ack. How do I tell why the linux side sent the rst? Or how do i tell it not the send a rst, just to test? Other ideas? I looks to us that the linux side says "okay, we're done, see ya bye" in two packets.

Thanks in advance

Is there a firewall between you and mainframe? maybe iptables running with a rule that includes REJECT --reject-with tcp-reset -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Kain, Becki (B.) wrote:

We have this continuing issue - we have the same software talking to the same mainframe. On the solaris to mainframe side, we send a fin,ack, the mainframe sends back a fin,psh,ack, solaris sends an ack. On linux, we send the same fin, ack to the mainframe then immediately send rst,ack. How do I tell why the linux side sent the rst? Or how do i tell it not the send a rst, just to test? Other ideas? I looks to us that the linux side says "okay, we're done, see ya bye" in two packets.

I'm no expert but it seems that the following section from http://en.wikipedia.org/wiki/Transmission_Control_Protocol#Connection_termin... may be relevant: "Some host TCP stacks may implement a "half-duplex" close sequence, as Linux or HP-UX do. If such a host actively closes a connection but still has not read all the incoming data the stack already received from the link, this host will send a RST instead of a FIN" The rest of the section explains how some application programming issues can cause this circumstance. Are you sure your application has read everything before closing? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org