All TCP errors or unusual events should now generate a debugging message at DBGLVL_LOG, with enough information (SEQ and ACK numbers) to be able to identify the corresponding packet (or missing packet) in a network trace from the remote end.tags/v0.9.8
|
|
||
402 |
|
402 |
|
403 |
|
403 |
|
404 |
|
404 |
|
|
405 |
|
|
405 |
|
406 |
|
406 |
|
407 |
|
407 |
|
408 |
|
|
|
||
438 |
|
439 |
|
439 |
|
440 |
|
440 |
|
441 |
|
441 |
|
|
|
|
442 |
|
|
|
443 |
|
|
|
444 |
|
|
442 |
|
445 |
|
443 |
|
446 |
|
444 |
|
447 |
|
|
|
||
495 |
|
498 |
|
496 |
|
499 |
|
497 |
|
500 |
|
498 |
|
|
|
499 |
|
|
|
|
501 |
|
|
|
502 |
|
|
|
503 |
|
|
|
504 |
|
|
|
505 |
|
|
|
506 |
|
|
|
507 |
|
|
|
508 |
|
|
|
509 |
|
|
500 |
|
510 |
|
501 |
|
511 |
|
502 |
|
512 |
|
|
|
||
510 |
|
520 |
|
511 |
|
521 |
|
512 |
|
522 |
|
513 |
|
|
|
|
523 |
|
|
514 |
|
524 |
|
515 |
|
|
|
|
525 |
|
|
516 |
|
526 |
|
517 |
|
527 |
|
518 |
|
528 |
|
|
|
||
547 |
|
557 |
|
548 |
|
558 |
|
549 |
|
559 |
|
|
560 |
|
|
550 |
|
561 |
|
551 |
|
562 |
|
552 |
|
563 |
|
553 |
|
564 |
|
554 |
|
|
|
|
565 |
|
|
|
566 |
|
|
|
567 |
|
|
555 |
|
568 |
|
556 |
|
569 |
|
557 |
|
570 |
|
|
|
||
577 |
|
590 |
|
578 |
|
591 |
|
579 |
|
592 |
|
580 |
|
|
|
581 |
|
|
|
|
593 |
|
|
|
594 |
|
|
|
595 |
|
|
|
596 |
|
|
|
597 |
|
|
|
598 |
|
|
|
599 |
|
|
|
600 |
|
|
|
601 |
|
|
|
602 |
|
|
582 |
|
603 |
|
583 |
|
604 |
|
584 |
|
605 |
|
|
|
||
728 |
|
749 |
|
729 |
|
750 |
|
730 |
|
751 |
|
731 |
|
|
|
732 |
|
|
|
|
752 |
|
|
|
753 |
|
|
733 |
|
754 |
|
734 |
|
755 |
|
735 |
|
756 |
|
|
|
||
785 |
|
806 |
|
786 |
|
807 |
|
787 |
|
808 |
|
788 |
|
|
|
|
809 |
|
|
|
810 |
|
|
|
811 |
|
|
789 |
|
812 |
|
|
813 |
|
|
790 |
|
814 |
|
791 |
|
815 |
|
792 |
|
816 |
|
|
|
||
844 |
|
868 |
|
845 |
|
869 |
|
846 |
|
870 |
|
|
871 |
|
|
847 |
|
872 |
|
848 |
|
873 |
|
849 |
|
874 |
|