North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Has PSI been assigned network 1?

  • From: Jeremy Porter
  • Date: Mon Apr 17 18:01:09 1995

Marty, and others:
	Yes, the Ascend's are fundenmentally broken, BUT
and this is a big one, there are work arounds for the problems with
Ascend's broken routing protocols, i.e. don't use them, or filter them.
This is easy enough to do.  

The problem is more general than Ascend however.  There are MANY
boxes out there (terminal servers) who's PPP is broken in this way.
Telebit Netblazers and Livingston Portmasters included.

It's kind of sad, really, when a small company like mine, can make this
work and the "world's largest ISP" can't fix the problem.

It is good to point out that other large ISPs have this same problem.

>there are about a dozen ISP's extensively using ascend's which have this hole.
>
>our original RFP to them dealt with this issue
>
>but they did not execute
>
>they keep trying to fix this, but so far no go
>
>we have tried to keep this quiet so that
>
>microsoft/uunet/psinet/etc.....
>
>don't get extensively hacked
>
>we have had two occurences of this so far in one year that I know of though 
>there are probably more
>
>marty
>
>> PSI allows people to negotiate PPP addresses, and then 
>> propagates everything everywhere w/o even token filtering.  I.e. any 
>> idiot can subscribe to PSI service and kill the Internet. 
>>  
>> --vadim 
>>  
>> Date: Sun, 16 Apr 95 21:02:04 MET DST 
>> >From: Peter Lothberg <[email protected]> 
>> To: [email protected], [email protected], [email protected] Subject: Has PSI 
>> been assigned network 1? 
>>  
>> Or why are they announcing it to the rest of the Internet through 
>> their box at MAE-East??? 
>>  
>> bash$ whois 1.0.0.0 
>> No match for "1.0.0.0". 
>>  
>> The InterNIC Registration Services Host contains ONLY Internet 
>> Information (Networks, ASN's, Domains, and POC's). 
>> Please use the whois server at nic.ddn.mil for MILNET Information. 
>>  
>>  
>> traceroute 1.1.1.1 
>> traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 40 byte packets 
>>  1  sl-dialup-2.sprintlink.net (192.157.36.128)  252 ms  245 ms  223 
>>  ms 2  192.157.36.1 (192.157.36.1)  251 ms  250 ms  251 ms 3  sl-dc-1-
>>  S3-T1.sprintlink.net (144.228.0.225)  252 ms  262 ms  253 ms 4  
>>  icm-dc-1-F0/0.icp.net (144.228.20.101)  275 ms  269 ms  252 
>>  ms 5  psi-mae-east-1.psi.net (192.41.177.235)  268 ms  254 ms  241 
>>  ms 6  washington2.dc.isdn.psi.net (38.146.99.110)  261 ms  271 ms  262 
>>  ms 7  1.1.1.1 (1.1.1.1)  457 ms  1284 ms  543 ms 
>>  
>> bash$ traceroute 1.1.1.2 
>> traceroute to 1.1.1.2 (1.1.1.2), 30 hops max, 40 byte packets 
>>  1  sl-dialup-2.sprintlink.net (192.157.36.128)  253 ms  253 ms  246 
>>  ms 2  192.157.36.1 (192.157.36.1)  246 ms  243 ms  228 ms 3  sl-dc-1-
>>  S3-T1.sprintlink.net (144.228.0.225)  249 ms  447 ms  313 ms 4  
>>  icm-dc-1-F0/0.icp.net (144.228.20.101)  274 ms  251 ms  278 
>>  ms 5  psi-mae-east-1.psi.net (192.41.177.235)  265 ms  257 ms  266 
>>  ms 6  core.net228.psi.net (38.1.2.7)  286 ms  278 ms  276 
>>  ms 7  core.net99.psi.net (38.1.2.10)  338 ms  370 ms  279 
>>  ms 8  core.net228.psi.net (38.1.2.7)  306 ms  326 ms  290 
>>  ms 9  core.net99.psi.net (38.1.2.10)  335 ms  308 ms  325 ms 
>> 10  core.net228.psi.net (38.1.2.7)  372 ms  353 ms  341 ms 11  
>> core.net99.psi.net (38.1.2.10)  376 ms  385 ms  377 ms 12  
>> core.net228.psi.net (38.1.2.7)  438 ms  375 ms  365 ms 13  
>> core.net99.psi.net (38.1.2.10)  384 ms  441 ms  371 ms 14  
>> core.net228.psi.net (38.1.2.7)  394 ms  426 ms  474 ms 15  
>> core.net99.psi.net (38.1.2.10)  427 ms  540 ms  565 ms 16  
>> core.net228.psi.net (38.1.2.7)  521 ms  500 ms  489 ms 17  
>> core.net99.psi.net (38.1.2.10)  530 ms  483 ms  527 ms 18  
>> core.net228.psi.net (38.1.2.7)  567 ms  493 ms  561 ms 19  
>> core.net99.psi.net (38.1.2.10)  779 ms  462 ms  670 ms 20  
>> core.net228.psi.net (38.1.2.7)  531 ms  620 ms  613 ms 21  
>> core.net99.psi.net (38.1.2.10)  562 ms  728 ms  598 ms 22  
>> core.net228.psi.net (38.1.2.7)  812 ms  566 ms  835 ms 23  
>> core.net99.psi.net (38.1.2.10)  661 ms  678 ms  574 ms 24  
>> core.net228.psi.net (38.1.2.7)  647 ms  820 ms  666 ms 25  
>> core.net99.psi.net (38.1.2.10)  649 ms  625 ms  628 ms 26  
>> core.net228.psi.net (38.1.2.7)  900 ms  634 ms  733 ms 27  
>> core.net99.psi.net (38.1.2.10)  648 ms  659 ms  656 ms 28  
>> core.net228.psi.net (38.1.2.7)  776 ms  979 ms  834 ms 29  
>> core.net99.psi.net (38.1.2.10)  715 ms  689 ms  734 ms 30  
>> core.net228.psi.net (38.1.2.7)  782 ms  785 ms  677 ms 
>>  
>>  
>> ---Peter 
>>  
>>  
>
>


-- 
----------------------------------------------------------------------------
|  Jeremy Porter (512)-339-6094 Freeside Communications, Inc. [email protected]  |
|  [email protected]  (512)-339-4466 (data) P.O. Box 530264 Austin, TX 78753    |
----------------------------------------------------------------------------