PM2 rev 3.3.3, Ascend P50s and P130s, mostly 4.6C and above
Below shows two traces (done on the portmaster) from a PC
to a web server on the other end of a PM2->Ascend
link. The first one is successful, the second one isn't.
In the scenario that Doesn't work, it seems as if the remote end
never gets the ACK to their SYN ACK.
Now, How close to the actual output of the packet on the
ISDN port is this trace? Is there a possibility of the ACK
packet being lost on the way out of the PM2, or is the
trace nearly positive proof that the packet leave the PM2
and goes into ISDN land, and is lost by the Ascend?
Is there a way to dump incoming packets on an Pipeline?
Also, ICMP packets always seem to get through reliably.
Anybody see this before or know what might be happening?
-Ed
(Sorry for the wide trace listing.)
Good request:
rbtserv2> TCP from 205.164..176.34.2483 to 206.84.156.131.80 seq FC40CD91, ack 0x0, win 8192, SYN
TCP from 206.84.156.131.80 to 205.164.176.34.2483 seq 96BF344, ack 0xFC40CD92, win 8576, SYN ACK
TCP from 205.164.176.34.2483 to 206.84.156.131.80 seq FC40CD92, ack 0x96BF345, win 8576, ACK
TCP from 205.164.176.34.2483 to 206.84.156.131.80 seq FC40CD92, ack 0x96BF345, win 8576, PUSH ACK , 16 bytes
TCP from 206.84.156.131.80 to 205.164.176.34.2483 seq 96BF345, ack 0xFC40CDA2, win 8560, ACK
TCP from 206.84.156.131.80 to 205.164.176.34.2483 seq 96BF345, ack 0xFC40CDA2, win 8560, PUSH ACK , 105 bytes
TCP from 206.84.156.131.80 to 205.164.176.34.2483 seq 96BF3AE, ack 0xFC40CDA2, win 8560, FIN ACK
TCP from 205.164.176.34.2483 to 206.84.156.131.80 seq FC40CDA2, ack 0x96BF3AF, win 8576, ACK
TCP from 205.164.176.34.2483 to 206.84.156.131.80 seq FC40CDA2, ack 0x96BF3AF, win 8576, FIN ACK
TCP from 206.84.156.131.80 to 205.164.176.34.2483 seq 96BF3AF, ack 0xFC40CDA3, win 8560, ACK
TCP from 205.164.176.34.2482 to 206.84.156.131.25 seq FB42AC6E, ack 0x96AA3C5, win 8576, FIN PUSH ACK , 31 bytes
TCP from 206.84.156.131.25 to 205.164.176.34.2482 seq 96AA3C5, ack 0xFB42AC8E, win 8545, ACK
TCP from 206.84.156.131.25 to 205.164.176.34.2482 seq 96AA3C5, ack 0xFB42AC8E, win 8545, PUSH ACK , 29 bytes
TCP from 205.164.176.34.2482 to 206.84.156.131.25 seq FB42AC8E, ack 0x0, win 0, RST
TCP from 206.84.156.131.25 to 205.164.176.34.2482 seq 96AA3E2, ack 0xFB42AC8E, win 8545, FIN PUSH ACK , 29 bytes
TCP from 205.164.176.34.2482 to 206.84.156.131.25 seq FB42AC8E, ack 0x0, win 0, RST
Bad Request - in the middle of the request I give up and abort:
rbtserv2> TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697055, ack 0x0, win 8192, SYN
TCP from 206.84.156.131.80 to 205.164.176.34.2484 seq 96C26A1, ack 0xFC697056, win 8576, SYN ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697056, ack 0x96C26A2, win 8576, ACK
TCP from 206.84.156.131.80 to 205.164.176.34.2484 seq 96C26A1, ack 0xFC697056, win 8576, SYN ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697056, ack 0x96C26A2, win 8576, ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697056, ack 0x96C26A2, win 8576, PUSH ACK , 16 bytes
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697056, ack 0x96C26A2, win 8576, PUSH ACK , 18 bytes
TCP from 206.84.156.131.80 to 205.164.176.34.2484 seq 96C26A1, ack 0xFC697056, win 8576, SYN ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697068, ack 0x96C26A2, win 8576, ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697056, ack 0x96C26A2, win 8576, PUSH ACK , 18 bytes
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697056, ack 0x96C26A2, win 8576, PUSH ACK , 18 bytes
TCP from 206.84.156.131.80 to 205.164.176.34.2484 seq 96C26A1, ack 0xFC697056, win 8576, SYN ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697068, ack 0x96C26A2, win 8576, ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697068, ack 0x96C26A2, win 8576, FIN PUSH ACK , 5 bytes
TCP from 206.84.156.131.80 to 205.164.176.34.2484 seq 96C26A2, ack 0xFC697056, win 8576, ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC697056, ack 0x96C26A2, win 8576, FIN PUSH ACK , 23 bytes
TCP from 206.84.156.131.80 to 205.164.176.34.2484 seq 96C26A2, ack 0xFC69706E, win 8553, ACK
TCP from 206.84.156.131.80 to 205.164.176.34.2484 seq 96C270B, ack 0xFC69706E, win 8553, FIN ACK
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC69706E, ack 0x96C26A2, win 8576, ACK
TCP from 206.84.156.131.80 to 205.164.176.34.2484 seq 96C26A2, ack 0xFC69706E, win 8553, PUSH ACK , 105 bytes
TCP from 205.164.176.34.2484 to 206.84.156.131.80 seq FC69706E, ack 0x0, win 0, RST
rbtserv2> ptrace
--------------------------------------------------------------
edward jung atlantic internet technologies, inc.
ejung@exit109.com 628 shrewsbury ave - red bank - nj
(908)758-0505, -0869 (FAX) http://www.exit109.com/