Thread View: comp.protocols.tcp-ip
4 messages
4 total messages
Started by Tony Mountifield
Wed, 30 Nov 1994 13:02
TCP Protocol problem Solaris<->KA9Q
Author: Tony Mountifield
Date: Wed, 30 Nov 1994 13:02
Date: Wed, 30 Nov 1994 13:02
140 lines
8405 bytes
8405 bytes
Hi!
I wonder if there are any TCP protocol gurus out there who could shed some
light on a protocol problem?
(please excuse the wide cross-posting, but I imagine that such people are
not exactly plentiful in the world! :-)
I am trying to communicate between an Atari ST running the KA9Q NOS package
and a PC running Sun's Solaris 2, using PPP. Mostly it works. The Solaris
machine quite happily acts as a gateway, and has no problems accepting TCP
connections from the KA9Q clients.
The problem is that clients on the Solaris seem unable to make TCP connections
to servers on the KA9Q, and complain of a protocol error. Other, BSD-based
clients can connect to the KA9Q without problem, but I am told a WinSock
client also couldn't connect to the KA9Q server.
The Solaris can talk to other kinds of machine with no problems.
I have traced the relevant packets, and would be grateful if anyone can
identify the problem, and whether the KA9Q is not adhering to the TCP
protocol correctly.
This is an example working connection from the KA9Q client to the
Solaris server:
Tue Nov 29 21:38:20 1994 - sl0 sent:
PPP: len 48 protocol: IP
IP: len 44 193.132.77.63->193.132.77.1 ihl 20 ttl 63 prot TCP
TCP: 1025->25 Seq xec2c000 SYN Wnd 11680 MSS 1460
0000 ff 03 00 21 45 00 00 2c 00 01 00 00 3f 06 5e 82 ...!E..,....?.^.
0010 c1 84 4d 3f c1 84 4d 01 04 01 00 19 0e c2 c0 00 A.M?A.M......B@.
0020 00 00 00 00 60 02 2d a0 7a 60 00 00 02 04 05 b4 ....`.- z`.....4
Tue Nov 29 21:38:20 1994 - sl0 recv:
PPP: len 48 protocol: IP
IP: len 44 193.132.77.1->193.132.77.63 ihl 20 ttl 254 DF prot TCP
TCP: 25->1025 Seq x943f8791 Ack xec2c001 ACK SYN Wnd 8760 MSS 1460
0000 ff 03 00 21 45 00 00 2c 58 6b 40 00 fe 06 07 17 ...!E..,Xk@.~...
0010 c1 84 4d 01 c1 84 4d 3f 00 19 04 01 94 3f 87 91 A.M.A.M?.....?..
0020 0e c2 c0 01 60 12 22 38 69 e6 00 00 02 04 05 b4 .B@.`."8if.....4
Tue Nov 29 21:38:20 1994 - sl0 sent:
PPP: len 44 protocol: VJ Uncompressed TCP/IP
connection 0x00
IP: len 40 193.132.77.63->193.132.77.1 ihl 20 ttl 63 prot TCP
TCP: 1025->25 Seq xec2c001 Ack x943f8792 ACK Wnd 11680
0000 ff 03 00 2f 45 00 00 28 00 02 00 00 3f 00 5e 85 .../E..(....?.^.
0010 c1 84 4d 3f c1 84 4d 01 04 01 00 19 0e c2 c0 01 A.M?A.M......B@.
0020 94 3f 87 92 50 10 2d a0 76 3b 00 00 .?..P.- v;..
Tue Nov 29 21:38:20 1994 - sl0 recv:
PPP: len 176 protocol: IP
IP: len 172 193.132.77.1->193.132.77.63 ihl 20 ttl 254 DF prot TCP
TCP: 25->1025 Seq x943f8792 Ack xec2c001 ACK PSH Wnd 8760 Data 132
0000 ff 03 00 21 45 00 00 ac 58 6d 40 00 fe 06 06 95 ...!E..,Xm@.~...
0010 c1 84 4d 01 c1 84 4d 3f 00 19 04 01 94 3f 87 92 A.M.A.M?.....?..
0020 0e c2 c0 01 50 18 22 38 a0 d3 00 00 32 32 30 2d .B@.P."8 S..220-
0030 7a 65 75 73 2e 74 63 70 2e 63 6f 2e 75 6b 20 54 zeus.tcp.co.uk T
0040 6f 74 61 6c 20 43 6f 6e 6e 65 63 74 69 76 69 74 otal Connectivit
0050 79 20 50 72 6f 76 69 64 65 72 73 20 53 65 6e 64 y Providers Send
0060 6d 61 69 6c 20 38 2e 36 2e 39 2f 38 2e 36 2e 39 mail 8.6.9/8.6.9
0070 20 72 65 61 64 79 20 61 74 20 54 75 65 2c 20 32 ready at Tue, 2
0080 39 20 4e 6f 76 20 31 39 39 34 20 32 31 3a 33 39 9 Nov 1994 21:39
0090 3a 35 36 20 47 4d 54 0d 0a 32 32 30 20 45 53 4d :56 GMT..220 ESM
00a0 54 50 20 73 70 6f 6b 65 6e 20 68 65 72 65 0d 0a TP spoken here..
Tue Nov 29 21:38:20 1994 - sl0 sent:
PPP: len 33 protocol: VJ Compressed TCP/IP
changes: 0x34 TCP checksum: 0xbc60 PUSH
delta ACK: 0x84 delta ID: 0x02
0000 ff 03 00 2d 34 bc 60 84 02 48 45 4c 4f 20 73 6f ...-4<`..HELO so
0010 66 74 69 6e 73 2e 74 63 70 2e 63 6f 2e 75 6b 0d ftins.tcp.co.uk.
0020 0a .
And so on....
Here is an example of the failed connection from the Solaris client
to the KA9Q server.
Tue Nov 29 21:38:28 1994 - sl0 recv:
PPP: len 48 protocol: IP
IP: len 44 193.132.77.1->193.132.77.63 ihl 20 ttl 254 DF prot TCP
TCP: 45214->25 Seq x9456f791 SYN Wnd 8760 MSS 1460
0000 ff 03 00 21 45 00 00 2c 58 82 40 00 fe 06 07 00 ...!E..,X.@.~...
0010 c1 84 4d 01 c1 84 4d 3f b0 9e 00 19 94 56 f7 91 A.M.A.M?0....Vw.
0020 00 00 00 00 60 02 22 38 1c 05 00 00 02 04 05 b4 ....`."8.......4
Tue Nov 29 21:38:30 1994 - sl0 sent:
PPP: len 82 protocol: IP
IP: len 78 193.132.77.63->193.132.77.1 ihl 20 ttl 63 prot TCP
TCP: 25->45214 Seq x112d8000 Ack x9456f792 ACK PSH SYN Wnd 11680 MSS 1460 Data 34
0000 ff 03 00 21 45 00 00 4e 00 16 00 00 3f 06 5e 4b ...!E..N....?.^K
0010 c1 84 4d 3f c1 84 4d 01 00 19 b0 9e 11 2d 80 00 A.M?A.M...0..-..
0020 94 56 f7 92 60 1a 2d a0 e5 d5 00 00 02 04 05 b4 .Vw.`.- eU.....4
0030 32 32 30 20 73 6f 66 74 69 6e 73 2e 74 63 70 2e 220 softins.tcp.
0040 63 6f 2e 75 6b 20 53 4d 54 50 20 72 65 61 64 79 co.uk SMTP ready
0050 0d 0a ..
Tue Nov 29 21:38:30 1994 - sl0 recv:
PPP: len 44 protocol: IP
IP: len 40 193.132.77.1->193.132.77.63 ihl 20 ttl 254 DF prot TCP
TCP: 45214->25 Seq x9456f792 Ack x112d8023 ACK Wnd 8760
0000 ff 03 00 21 45 00 00 28 58 84 40 00 fe 06 07 02 ...!E..(X.@.~...
0010 c1 84 4d 01 c1 84 4d 3f b0 9e 00 19 94 56 f7 92 A.M.A.M?0....Vw.
0020 11 2d 80 23 50 10 22 38 a2 61 00 00 .-.#P."8"a..
Tue Nov 29 21:38:30 1994 - sl0 recv:
PPP: len 44 protocol: IP
IP: len 40 193.132.77.1->193.132.77.63 ihl 20 ttl 254 DF prot TCP
TCP: 45214->25 Seq x9456f792 Ack x112d8023 ACK FIN Wnd 8760
0000 ff 03 00 21 45 00 00 28 58 85 40 00 fe 06 07 01 ...!E..(X.@.~...
0010 c1 84 4d 01 c1 84 4d 3f b0 9e 00 19 94 56 f7 92 A.M.A.M?0....Vw.
0020 11 2d 80 23 50 11 22 38 a2 60 00 00 .-.#P."8"`..
Tue Nov 29 21:38:30 1994 - sl0 sent:
PPP: len 44 protocol: IP
IP: len 40 193.132.77.63->193.132.77.1 ihl 20 ttl 63 prot TCP
TCP: 25->45214 Seq x112d8023 Ack x9456f793 ACK FIN Wnd 11680
0000 ff 03 00 21 45 00 00 28 00 18 00 00 3f 06 5e 6f ...!E..(....?.^o
0010 c1 84 4d 3f c1 84 4d 01 00 19 b0 9e 11 2d 80 23 A.M?A.M...0..-.#
0020 94 56 f7 93 50 11 2d a0 96 f7 00 00 .Vw.P.- .w..
Tue Nov 29 21:38:32 1994 - sl0 recv:
PPP: len 44 protocol: IP
IP: len 40 193.132.77.1->193.132.77.63 ihl 20 ttl 254 DF prot TCP
TCP: 45214->25 Seq x9456f793 Ack x112d8024 ACK Wnd 8760
0000 ff 03 00 21 45 00 00 28 58 86 40 00 fe 06 07 00 ...!E..(X.@.~...
0010 c1 84 4d 01 c1 84 4d 3f b0 9e 00 19 94 56 f7 93 A.M.A.M?0....Vw.
0020 11 2d 80 24 50 10 22 38 a2 5f 00 00 .-.$P."8"_..
That is the complete conversation. It appears that the client, having made
the connection, doesn't like something, and closes it again.
Any suggestions would be most welcome.
Thanks in advance,
Tony
Re: TCP Protocol problem Solaris<->KA9Q
Author: Chris Butterworth
Date: Fri, 02 Dec 1994 01:32
Date: Fri, 02 Dec 1994 01:32
36 lines
2945 bytes
2945 bytes
In article <199411301302.NAA09562@ntl.com>
tonymo@ntl.com "Tony Mountifield" writes:
[much snipped]
> Here is an example of the failed connection from the Solaris client
> to the KA9Q server.
>
[SYN packet snipped]
>
> Tue Nov 29 21:38:30 1994 - sl0 sent:
> PPP: len 82 protocol: IP
> IP: len 78 193.132.77.63->193.132.77.1 ihl 20 ttl 63 prot TCP
> TCP: 25->45214 Seq x112d8000 Ack x9456f792 ACK PSH SYN Wnd 11680 MSS 1460
> Data 34
> 0000 ff 03 00 21 45 00 00 4e 00 16 00 00 3f 06 5e 4b ...!E..N....?.^K
> 0010 c1 84 4d 3f c1 84 4d 01 00 19 b0 9e 11 2d 80 00 A.M?A.M...0..-..
> 0020 94 56 f7 92 60 1a 2d a0 e5 d5 00 00 02 04 05 b4 .Vw.`.- eU.....4
> 0030 32 32 30 20 73 6f 66 74 69 6e 73 2e 74 63 70 2e 220 softins.tcp.
> 0040 63 6f 2e 75 6b 20 53 4d 54 50 20 72 65 61 64 79 co.uk SMTP ready
> 0050 0d 0a ..
The above packet carries a SYN as well as some data. This is said to
bother some TCPs. In the example trace of a working connection I note
that data and SYN were not present in the same packet.
In the KA9Q version that I use (ibm PC) the option to turn this off
is TCP SYNDATA OFF - this may exist in the version you are using.
Hope this helps!
--
Chris Butterworth | * * | "Everybody does it in the Zone"
Mail: Chris@lunchbox.demon.co.uk | | | Hours: 9:30pm -> 1:00 am
Chris@lunchbox.dircon.co.uk| \_/ | telnet lunchbox.demon.co.uk 7777
Re: TCP Protocol problem Solaris<->KA9Q
Author: Alan Cox
Date: Fri, 02 Dec 1994 14:15
Date: Fri, 02 Dec 1994 14:15
20 lines
2438 bytes
2438 bytes
In article <199411301302.NAA09562@ntl.com> tonymo@ntl.com (Tony Mountifield) writes: >I am trying to communicate between an Atari ST running the KA9Q NOS package >and a PC running Sun's Solaris 2, using PPP. Mostly it works. The Solaris >machine quite happily acts as a gateway, and has no problems accepting TCP >connections from the KA9Q clients. Solaris 2.1 on PC's has this urge to protocol error the piggy backed data stuff done by KA9Q. Now KA9Q is stretching the spec a little, for a massive performance gain for some operations on slow links (eg amateur radio), but Solaris is violating the fundamental 'be liberal in what you accept' ethic. You can either talk to sun or turn the piggy backing of data off on KA9Q. I can't remember how you do that offhand. Alan -- ..-----------,,----------------------------,,----------------------------,, // Alan Cox // iialan@www.linux.org.uk // GW4PTS@GB7SWN.#45.GBR.EU // ``----------'`--[Anti Kibozing Signature]-'`----------------------------'' One two three: Kibo, Lawyer, Refugee :: Green card, Compaq come read me...
Re: TCP Protocol problem Solaris<->KA9Q
Author: Tony Mountifield
Date: Mon, 05 Dec 1994 08:40
Date: Mon, 05 Dec 1994 08:40
21 lines
2341 bytes
2341 bytes
In article <D06sx4.6q6@info.swan.ac.uk>, Alan Cox <iialan@iifeak.swan.ac.uk> wrote: >In article <199411301302.NAA09562@ntl.com> tonymo@ntl.com (Tony Mountifield) writes: >>I am trying to communicate between an Atari ST running the KA9Q NOS package >>and a PC running Sun's Solaris 2, using PPP. Mostly it works. The Solaris >>machine quite happily acts as a gateway, and has no problems accepting TCP >>connections from the KA9Q clients. > >Solaris 2.1 on PC's has this urge to protocol error the piggy backed data >stuff done by KA9Q. Now KA9Q is stretching the spec a little, for a massive >performance gain for some operations on slow links (eg amateur radio), but >Solaris is violating the fundamental 'be liberal in what you accept' ethic. > >You can either talk to sun or turn the piggy backing of data off on KA9Q. >I can't remember how you do that offhand. Yes, that was the problem. Many thanks to Alan and to Chris Butterworth, who pointed me to the command TCP SYNDATA OFF in KA9Q. This completely cured the problem. Tony
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