Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12
  1. #11
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    18,370

    Default

    http://whois.domaintools.com/69.63.167.0 (Universal Communications, Reallocated to Detel Wireless, LLC) This doesn't look Facebook to me.

    http://whois.domaintools.com/66.220.144.0 (this is directly assigned to Facebook, Inc CIDR range confirmed of 66.220.144.0/20) Translate this range in decimal form to 66.220.144.0 - 66.220.159.255

    Which means the third block you've placed (66.220.152.0/32), with a /32 mask is not only never going to matter because it's matching a singular invalid IP, but it's also apart of the greater range you've already blocked. Rule, is redundant and incorrect.

    http://whois.domaintools.com/69.63.184.0
    The fourth rule is also false, however it is indeed a range registered to Facebook, Inc. The CIDR is 69.63.176.0/20, this encompasses 69.63.176.0-69.63.191.255. Your rule is invalid and in need of correction.

    http://whois.domaintools.com/69.171.224.0
    Yet another CIDR block registered to Facebook, inc. The CIDR you've used is invalid, the registered range is 69.171.224.0/19, decimal range 69.171.224.0 - 69.171.255.255. Your rule is close, but blocking things that may not be Facebook related.

    Don't go throwing stuff into the firewall without doing the proper homework. Otherwise you're simply signing up for an unhappy customer when you break random things online.
    Rob Sandling, BS:SWE, MCP
    Intouch Technology
    Phone: 480-272-9889
    NexgenAppliances.com
    Phone: 866-794-8879

  2. #12
    Untangle Ninja mrunkel's Avatar
    Join Date
    Jul 2008
    Posts
    3,035

    Default

    Facebook's currently announced IPs: (the timestamps are the first and last times the range was seen).

    Code:
    2620:0:1c00::/40	61 - 73	40	2010-05-05 00:00	2011-08-17 00:00
    69.171.255.0/24	92	24	2010-11-05 08:00	2011-08-17 00:00
    69.171.239.0/24	91	24	2010-10-13 00:00	2011-08-17 00:00
    66.220.159.0/24	81 - 91	24	2010-09-01 00:00	2011-08-17 00:00
    204.15.20.0/22	102	22	2008-01-01 00:00	2011-08-17 00:00
    74.119.76.0/22	97	22	2009-11-04 08:00	2011-08-17 00:00
    69.63.176.0/21	91	21	2008-02-29 08:00	2011-08-17 00:00
    66.220.152.0/21	89	21	2009-08-25 08:00	2011-08-17 00:00
    69.63.184.0/21	102	21	2008-01-01 00:00	2011-08-17 00:00
    66.220.144.0/21	91	21	2009-08-20 00:00	2011-08-17 00:00
    69.171.240.0/20	88	20	2010-10-26 00:00	2011-08-17 00:00
    69.171.224.0/20	92	20	2010-12-19 08:00	2011-08-17 00:00
    http://stat.ripe.net/query/prefix-list/AS32934
    m.


    Big Frickin Disclaimer:
    While I'm pretty sure, I can't guarantee that I know what I'm doing. There might be a better way to do this, and this way might actually suck. Make sure you understand the implications of what you're doing before trying to follow these directions.

    It often helps troubleshooting if you have a good network map. Look here if you want my advice on how to draw one.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2