Access to the Internic Blocked

Tue Aug 20 14:25:43 UTC 1996

On Tue, 20 Aug 1996 bmanning at ISI.EDU wrote:

> > 
> > Network Solutions has decided to filter our CIDR addr, 169.132 / 16
> > since about 5 PM yesterday from reaching the internic.  Below is
> > a forwarded copy of email exchange between myself, and MCI --
> 
> 	It was my understanding that Network Solutions was not a
> 	provider, but a customer of several providers, including MCI.
> 	Your statements and the attached note from MCI seem to indicate
> 	otherwise.
>       Or did this particular outage have anything to do
> 	with the MCI instabilities around KC yesterday?
> 	Or perhaps with your use of net10 in the path?

It doesn't appear to have anything to do with MCI's instabilities, or
or net10 path -- This happens only  from our 169.132 addresses,
below is a sample traceroute originating from 207.113.31.130 :

traceroute to rs.internic.net (198.41.0.6), 30 hops max, 40 byte packets
 1  eth-0.gw-1.hh.idt.net (207.113.31.158)  1.717 ms  1.679 ms  1.706 ms
 2  lp-6-5.gw-6.hck.idt.net (206.20.143.73)  6.731 ms  3.593 ms  3.588 ms
 3  eth-0.gw-1.hck.idt.net (169.132.34.250)  52.896 ms  62.393 ms  14.151
ms
 4  bb.gw-1.dc.idt.net (10.255.255.1)  15.797 ms  100.077 ms  94.122 ms
 5  mae-east-plusplus.washington.mci.net (192.41.177.181)  289.252 ms
116.522 ms  191.672 ms
 6  * core2-hssi2-0.Washington.mci.net (204.70.1.213)  33.655 ms  83.444
ms
 7  border7-fddi-0.Washington.mci.net (204.70.74.51)  86.084 ms  98.839 ms
95.518 ms
 8  network-solutions.Washington.mci.net (204.70.77.42)  176.883 ms
131.873 ms  162.567 ms
 9  rs1.internic.net (198.41.0.6)  109.422 ms *  134.412 ms

- Golan