Of course I ahve asked her to trace her IP address. That is the
information I have used. She got it from Earthlink.
On Sun, 04 Dec 2005 11:58:31 -0600, ibuprofin@painkiller.example.tld
(Moe Trin) wrote:
>On Sun, 4 Dec 2005, in the Usenet newsgroup comp.security.firewalls, in article
><leb5p199di5841jma16qidhdtvl1jbdst9@4ax.com>, Alec wrote:
>
>>She has three time asked them for her IP address She has been given an
>>address 172 xxx xxx xxx. Does not work. Pinged no response.
>
>What's preventing her from asking her own computer what address it is using?
>If you are using windows NT, w2k, or XP, the command "ipconfig /all".
>If you are using Windows 9X, ME then winipcfg and the more button.
>
>>I have asked her to check with WHAT IS MY IP, as I did for my own and
>>she came up with two addresses that did not work. Beginning 66.XXX XXX
>>XXX. My guess one could her machine and the other the ISP's address
>>for her.
>
>In your zeal to hide the IP information, you over did it. But let's see:
>
>[compton ~]$ grep ' 172\.' IP.ADDR/stats/[ALR]*
>IP.ADDR/stats/ARIN.gz:US 172.128.0.0 255.192.0.0 allocated
>IP.ADDR/stats/ARIN.gz:US 172.192.0.0 1638400 allocated
>[compton ~]$ grep -c ' 66\.' IP.ADDR/stats/[ALR]*
>IP.ADDR/stats/AFRINIC:2
>IP.ADDR/stats/APNIC:0
>IP.ADDR/stats/ARIN:754
>IP.ADDR/stats/LACNIC:3
>IP.ADDR/stats/RIPE:0
>[compton ~]$
>
>So, for the 66.XXX.XXX.XXX block, there are 759 ISPs around the world that
>have assignments. Pretty useless. On the other hand, ARIN has only two
>blocks assigned, which combined are 172.128.0.0 to 172.216.255.255, and
>those belong to AOL. I rather doubt that's what you are referring to, but
>there is a third address block not listed:
>
>>I did a reverse check on the two numbers and they went back to
>>Earthlink. The other went back I recal to some address in California
>>
>>OrgName: Internet Assigned Numbers Authority
>>OrgID: IANA
>>Address: 4676 Admiralty Way, Suite 330
>>City: Marina del Rey
>>StateProv: CA
>
> 1918 Address Allocation for Private Internets. Y. Rekhter, B.
> Moskowitz, D. Karrenberg, G. J. de Groot, E. Lear. February 1996.
> (Format: TXT=22270 bytes) (Obsoletes RFC1627, RFC1597) (Also BCP0005)
> (Status: BEST CURRENT PRACTICE)
>
> 3330 Special-Use IPv4 Addresses. IANA. September 2002. (Format:
> TXT=16200 bytes) (Status: INFORMATIONAL)
>
> 172.16.0.0/12 - This block is set aside for use in private networks.
> Its intended use is documented in [RFC1918]. Addresses within this
> block should not appear on the public Internet.
>
>That's 172.16.0.0 through 172.31.255.255. Those addresses are normally
>used behind NAT routers. You can't connect to them from the Internet,
>because they are not assigned to any one entity, and can be used, like
>the more familiar 10.0.0.0 - 10.255.255.255 and 192.168.0.0 - 192.168.255.255
>range at homes.
>
>>I reckon some support guy may have got it wrong with the 172 number,
>>gave had information to my colleague.
>
>No, 172.16.0.0/12 is handed out for systems that do not need to be
>contacted directly by someone else on the Internet. Sounds as if your
>friend is NATed and not directly reachable from the world, although she
>can reach OUT to the world.
>
> Old guy
Received on Sun Dec 11 14:24:15 2005