Packet sizes using pdl mlp

This topic has 1 reply, 1 voice, and was last updated 19 years, 7 months ago by Bob Schmid.

Creator

Topic
May 3, 2005 at 2:33 pm #47712
Bob Schmid
Participant
Very interesting problem. Basic question is: What dictates packet size.

I have a messaeg with mlp encapsulation characters of x 1C0D at the end and the X’0d’ is being separated in a second packet all by itself…causing the recieving app not to see the final character. Yet when I send this same message to another ip/port on our network…it works and the entire message is in the first packet. It would seem that somehow on the engine (Running IBM AIX) it determines the packet size but in the case to a specific ip and port …it decides to use a smaller packet size than other interfaces….any idea where to start..it would seem to me to have to be at the network level on the interface engine somewhere…looking for specifics.
Creator

Topic

Viewing 0 reply threads

Author

Replies
- May 3, 2005 at 2:40 pm #56521
  Bob Schmid
  Participant
  TCP header breakdown:
  
  th_seq=3ec110d9, th_ack=48a52377
  
  th_off=5, flags
  
  th_win=32768, th_sum=0, th_urp=0
  
  00000000 0b4d5348 7c5e7e5c 267c4842 4f437c4a |.MSH|^~&|HBOC|J|
  
  00000010 7c454e47 494e457c 45444a7c 32303035 ||ENGINE|EDJ|2005|
  
  00000020 30353032 31313138 7c7c4144 545e4130 |05021118||ADT^A0|
  
  00000030 337c3138 31363336 31377c50 7c322e32 |3|18163617|P|2.2|
  
  00000040 7c313831 36333631 377c7c41 4c7c3431 ||18163617||AL|41|
  
  00000050 0d45564e 7c413033 7c323030 35303530 |.EVN|A03|2005050|
  
  00000060 32313131 380d5049 447c7c30 30303638 |21118.PID||00068|
  
  00000070 3330377c 30303232 39393630 5e5e5e4a |307|00229960^^^J|
  
  00000080 7e303131 37393734 355e5e5e 457c3835 |~01179745^^^E|85|
  
  00000090 38343533 305e4a38 38327c53 41595245 |84530^J882|SAYRE|
  
  000000a0 535e474f 52444f4e 5e4c7c7c 31393331 |S^GORDON^L||1931|
  
  000000b0 30393132 7c4d7c7c 377c3130 32204152 |0912|M||7|102 AR|
  
  000000c0 4d532042 4c56445e 41505420 355e4e49 |MS BLVD^APT 5^NI|
  
  000000d0 4c45535e 4f485e34 34343436 5e55535e |LES^OH^44446^US^|
  
  000000e0 435e5452 554d427c 5452554d 427c2833 |C^TRUMB|TRUMB|(3|
  
  000000f0 33302935 34342d36 3435387c 7c7c4d7c |30)544-6458|||M||
  
  00000100 4348527c 30353132 32303033 31385e5e |CHR|0512200318^^|
  
  00000110 5e4a7c32 38372d32 382d3433 31390d50 |^J|287-28-4319.P|
  
  00000120 56317c7c 457c4544 4a5e5e5e 4a7c317c |V1||E|EDJ^^^J|1||
  
  00000130 7c7c3135 3538355e 4d4f4f53 414c4c59 |||15585^MOOSALLY|
  
  00000140 5e524f42 4552545e 5e5e5e44 4f7c7c7c |^ROBERT^^^^DO||||
  
  00000150 4d45447c 7c7c7c37 7c7c7c31 31383236 |MED||||7|||11826|
  
  00000160 5e464f4e 54414e41 524f5341 5e4d4152 |^FONTANAROSA^MAR|
  
  00000170 595e414e 4e5e5e5e 4d447c45 444a7c30 |Y^ANN^^^MD|EDJ|0|
  
  00000180 35313232 30303331 385e5e5e 4a7c4d7c |512200318^^^J|M||
  
  00000190 7c7c7c7c 7c7c7c7c 7c7c7c7c 7c7c7c31 ||||||||||||||||1|
  
  000001a0 7c7c7c4a 7c7c7c7c 7c323030 35303530 ||||J|||||2005050|
  
  000001b0 32303934 367c3230 30353035 30323130 |20946|2005050210|
  
  000001c0 34357c7c 20302e30 300d5a43 457c7c7c |45|| 0.00.ZCE||||
  
  000001d0 7c7c7c7c 7c7c350d 5a43567c 33317c7c |||||||5.ZCV|31|||
  
  000001e0 55483033 4331307c 7c7c4144 4d495420 |UH03C10|||ADMIT |
  
  000001f0 494e2045 52524f52 7c45444a 7c300d1c |IN ERROR|EDJ|0..|
  
  tcp broke up the message in between the the envelope characters x 1c and x0d…what does this ?..the pdl ?
  
  second packet:
  
  TCP header breakdown:
  
  th_seq=3ec112d9, th_ack=48a52377
  
  th_off=5, flags
  
  th_win=32768, th_sum=0, th_urp=0
  
  00000000 0d
Author

Replies

Viewing 0 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.