Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sun-barr!texsun!texbell!uhnix1!moray!urchin!Eric.Green From: Eric.Green@urchin.fidonet.org (Eric Green) Newsgroups: comp.dcom.modems Subject: (#2 in series) Interesting PC Pursuit info Message-ID: <11184.2467C083@urchin.fidonet.org> Date: 9 May 89 15:02:04 GMT Organization: Urchin - Unix <--> Fido gateway, Houston, Tx Lines: 225 (Continued from previous message) Almost a year ago a small selected group of devoted individuals got together to discuss problems with the PC- Pursuit Network, in the middle of our discussions a question was asked as to how the network really processes our calls. This was intended to help us assess SET? commands and other such matters. When the address hypothesis was offered we quickly set out to prove it. It was proved in about 3 minutes with the discovery of 2011 (First try was xxx1). The data has continually been collected and analyzed ever since, but until now, has never been mass released. A small group of teen age hackers discovered several interesting things that can be done with these addresses-- many of which will not be discussed here short of mentioning that these ports connected to via these addresses are not limited to PC-Pursuiters. You can, however, fight "dead" dialout modems in cities via the address method. Dead modems can be located in about 10 seconds (faster than Telenet), and can either be reported or skipped past by the user connecting to the next modem in the sequence after the "dead" one. (Note: Say 2011.3 is dead, connect to 2011.4 and you will be past it. If 2011.4 is busy, go to 2011.5. The reader should notice 2011.3 is the same as 2011C.) The most interesting value of these addresses is that one can count the number of ports that Telenet keeps so secret (Grin). When there were only 28 cities in operation there were an average of 2.7 300 baud, 9.4 1200 baud, and 2.5 2400 baud modems in each city. Some cities had as little as 2 modems on a port and as many as 12. Only recently has the number of modems per city begun to jump. How To Update The Count Yourself: ================================= An ID is not required to "request" one of these ports, thus the tallying can be done any time of day by simply typing the number at the @ prompt. Here is an example with four modems (NJNEW/24): @20122.1 201 22A REFUSED COLLECT CONNECTION 19 80 @20122.2 201 22B REFUSED COLLECT CONNECTION 19 80 @20122.3 201 22C REFUSED COLLECT CONNECTION 19 80 @20122.4 201 22D REFUSED COLLECT CONNECTION 19 80 @20122.5 201 22E ILLEGAL ADDRESS 19 80 The reader should be aware that PC-Pursuit ports always respond with '19 80'. Do not confuse it with '19 00', which are not PC-Pursuit ports. In the above example we know there are four ports because the forth was the last existing port before we encountered the 'ILLEGAL ADDRESS.' There are several ways to signify that you have gone one beyond the end of the ports: 1) xxx xxx ILLEGAL ADDRESS 19 80 2) xxx xxx NOT OPERATING 19 80 3) The request freezes (Note: Issue a BREAK then D to abort the attempt yielding 'ATTEMPT ABORTED'.) You should be aware that modems which are out of order in the middle of the sequence can respond with 'NOT OPERATING' or may freeze the request. You should also note that when updating the existing list, all you need to do is try to request the next modem beyond the end as of the last check. Finding Newly Added Ports: ========================== Many ports have not yet been installed; hence, we do not yet know the addresses. New ports may be found by entering the first three digits of the area code and appending (1-29, 101-129, 201-229, 301-329, etc.) until the 'REFUSED COLLECT CONNECTION 19 80' appears. Once this is found, simply log onto the port address with your ID and R/V dial some silly series of digits, disconnect the port, then connect to the PC-Pursuit mnemonic you think it might be and R/V redial the last number. If the numbers match, you found it. -------- U P D A T E ------- Below is an update I made on 5/4/89 to the original PCPCOUNT.TXT file. I have added all the missing addresses except for CAGLE/3 and CAGLE/24; these have been difficult to find. On the same date I made a new count of all modems responding and have included this along with the originally published count. The numbers have fluctuated daily in some areas. Also note that some areas have a number of addresses which report "NOT OPERATING 09 80" rather than "ILLEGAL ADDRESS 03 80". This could possibly be an indication of planned modem additions. Or not. . . --- FS 5/4/89 |-- Modems --| Mnemonic Address Orig 5/4/89 Count Count -------- ------ ----- ------ AZPHO/3 60222 . 4 5 AZPHO/12 60223 .12 12 AZPHO/24 60226 . 4 4 (5-14 report 'not operating') CACOL/3 71423 . 4 4 CACOL/12 7144 .10 10 CACOL/24 71424 . 4 4 CAGLE/3 ??? CAGLE/12 81821 .18 17 (18-20 n/o) CAGLE/24 ??? CALAN/3 213412 . 8 8 CALAN/12 213413 .28 28 CALAN/24 21323 . 4 16 (1-12 n/o) CAOAK/3 4155 . 4 4 CAOAK/12 415216 . 8 8 CAOAK/24 41511 . 4 4 CAPAL/3 415106 . 4 16 CAPAL/12 415224 . 8 10 CAPAL/24 415108 4 CASAC/3 9167 . 4 4 CASAC/12 91611 . 8 8 CASAC/24 91612 . 4 4 CASAN/3 714119 . 4 4 CASAN/12 714213 .12 8 (9-12 n/o) CASAN/24 714124 . 4 4 (5-10 n/o) CASDI/3 714102 . 4 4 CASDI/12 714210 .14 14 CASDI/24 714121 . 4 4 (5-8 n/o) CASFA/3 415215 . 6 6 CASFA/12 415217 .10 34 CASFA/24 41523 . 4 4 CASJO/3 408111 . 4 4 CASJO/12 40821 .26 18 CASJO/24 408110 . 4 4 CODEN/3 303114 . 4 4 CODEN/12 303115 .18 18 CODEN/24 30321 .22 22 CTHAR/3 203105 . 4 CTHAR/12 203120 . 8 8 CTHAR/24 203121 . 4 DCWAS/3 202115 . 6 6 DCWAS/12 202116 .24 24 DCWAS/24 202117 .16 16 FLMIA/3 305120 . 6 6 FLMIA/12 305121 .18 18 FLMIA/24 305122 . 4 4 (5-6 n/o) FLTAM/3 81320 . 4 4 FLTAM/12 81321 .10 14 FLTAM/24 813124 . 4 4 (5-6 n/o) GAATL/3 404113 . 8 8 GAATL/12 404114 .20 20 GAATL/24 40422 . 4 4 (5-8 n/o) ILCHI/3 312410 . 8 8 ILCHI/12 312411 .28 28 (29-30 n/o) ILCHI/24 31224 . 4 4 (5-10 n/o) MABOS/3 617311 . 4 6 MABOS/12 617313 .20 22 MABOS/24 61726 . 8 8 (9-10 n/o) MIDET/3 313214 . 6 8 MIDET/12 313216 .18 18 MIDET/24 31324 . 6 10 MNMIN/3 612120 . 4 4 MNMIN/12 612121 .14 14 MNMIN/24 61222 . 4 4 (5-8 n/o) MOKCI/3 816104 . 4 4 MOKCI/12 816221 .12 12 MOKCI/24 816113 . 4 4 (5-6 n/o) MOSLO/3 3145 . 4 4 MOSLO/12 314421 . 8 8 MOSLO/24 31420 . 4 4 NCRTP/3 91920 . 4 4 NCRTP/12 91921 .12 12 NCRTP/24 919124 . 4 4 NJNEW/3 2011 .12 12 NJNEW/12 201301 .40 40 NJNEW/24 20122 . 4 20 NYNYO/3 212315 . 4 6 NYNYO/12 212316 .14 not reachable NYNYO/24 21228 . 4 8 OHCLE/3 21620 . 4 4 OHCLE/12 21621 .18 18 OHCLE/24 216120 . 4 6 (7-8 n/o) ORPOR/3 50320 . 2 4 ORPOR/12 50321 . 6 12 (12-99 n/o) ORPOR/24 503120 . 4 PAPHI/3 215112 . 6 8 PAPHI/12 2155 .22 22 PAPHI/24 21522 . 8 8 (9-10 n/o) TXDAL/3 214117 . 6 6 TXDAL/12 214118 .22 24 TXDAL/24 21422 . 4 4 (5-16 n/o) TXHOU/3 713113 . 8 8 TXHOU/12 713114 .24 24 TXHOU/24 71324 .10 10 (11-16 n/o) UTSLC/3 80120 . 4 4 UTSLC/12 80121 .14 14 UTSLC/24 80112 . 4 4 WASEA/3 20617 . 4 not reachable WASEA/12 20619 .22 not reachable WASEA/24 20621 . 4 not reachable WIMIL/3 41420 . 4 5 WIMIL/12 41421 .16 16 (17-20 n/o) WIMIL/24 414120 . 4 4 ber of specific kinds of ports supported, not to mention the number of 'dead' or 'down' modems you will find when you verify the totals. Usually, 2% to perhaps 10% of the modems are 'dead' with specific ones repeatedly failing week after week. History Of This Collection: =========================== (End of series)