AOL Proxy Servers not connecting via https - resolved

A Clue Bat was gently swung by a friendly and clueful (semi-anonymous)
AOL NetOps guys who contacted me from my post on Nanog. Thanks Nanog,
and this sounds strange from me, but Thank's AOL. :slight_smile:

And yes, it should have been obvious on my part.. a router
was configured with a 172.0.0.0/8 netmask.

This might be helpful to people setting up ACLs and the like:

http://webmaster.info.aol.com/proxyinfo.html

I think the point that Mike was making is that RFC1918
space is 172.16.0.0/20 not a /8.

-ron

Actually a /12. But the value of 172.16.0.0 0.15.255.255 has been
burned into my head for some reason...

---snip---

Page 4

3 Private Address Space
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:

     10.0.0.0 - 10.255.255.255 (10/8 prefix)
     172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
     192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

---snip---

At least two people have posted incorrectly about 172.16, wrt who has what
and how big it is.

Rekhter, et al Best Current Practice [Page 3]
RFC 1918 Address Allocation for Private Internets February 1996

3. Private Address Space

   The Internet Assigned Numbers Authority (IANA) has reserved the
   following three blocks of the IP address space for private internets:

     10.0.0.0 - 10.255.255.255 (10/8 prefix)
     172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
     192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

AOL has

NetRange: 172.128.0.0 - 172.191.255.255
CIDR: 172.128.0.0/10
NetRange: 172.192.0.0 - 172.211.255.255
CIDR: 172.192.0.0/12, 172.208.0.0/14

and apparently a bunch of other blocks.

yup... s/20/12/ typo...thanks Andy
-ron