/usr/share/doc/sendpage-common/docs/pc-testing.txt is in sendpage-common 1.0.3-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 | This document is a really rough example of how to examine a paging central to
figure out the paging limits for a particular pager or service.
(See "examples/configure-pc" for a quick perl script that does this part.)
start with PC configuration defaults.
send a page just to make sure you CAN get a page.
set "esc=true"
Send page with "\n" and "\t"'s (eg "This\nis a CR and this\tis a tab.")
if you see \n and \t okay, you have a real 1.8 TAP, and you're done.
otherwise:
remove "esc=true"
set "ctrl=true"
Send page with "\n" and "\t"'s (eg "This\nis a CR and this\tis a tab.")
if both \n and \t show up correctly, you have a weak TAP, but you're done.
if only the \n was displayed correctly, you can pass \n's only, so:
unset "ctrl=true"
set "lfok=true"
and you're done
otherwise:
unset "ctrl=true"
you can't send ctrl chars at all. sorry!
now, gauge the size of your paging length (test with ctrl/esc/lfok off):
page of 100 chars:
a123456789b123456789c123456789d123456789e123456789f123456789g123456789h123456789i123456789j123456789
page of 200 chars:
a123456789b123456789c123456789d123456789e123456789f123456789g123456789h123456789i123456789j123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J123456789
page of 240 chars:
a123456789b123456789c123456789d123456789e123456789f123456789g123456789h123456789i123456789j123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J123456789a123456789b123456789c123456789d123456789
page of 250 chars:
a123456789b123456789c123456789d123456789e123456789f123456789g123456789h123456789i123456789j123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J123456789a123456789b123456789c123456789d123456789e123456789
page of 300 chars:
a123456789b123456789c123456789d123456789e123456789f123456789g123456789h123456789i123456789j123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J123456789a123456789b123456789c123456789d123456789e123456789f123456789g123456789h123456789i123456789j123456789
start with X=100 chars
start with SIZE=100 chars
try to send a page:
send a page with SIZE chars
if it xmit fail or go through truncated?
decrease X by half
decrease SIZE by X
else
increase SIZE by X
try page again
Some PCs will stall on a "continued.." block, so you may need to force splits
at 250 - pinsize - 2 chars (usually 240).
-Kees Cook
kees@outflux.net
|