Hacker News Reader

Comment by xurukefi | Hacker News Reader

Programmatically retrievable via

  whois -h whois.radb.net -- '-i origin AS32934' | grep ^route

Source: https://developers.facebook.com/docs/sharing/webmasters/craw...

View on HN

Done, and used daily :

https://github.com/smigniot/smigniot.github.io/blob/master/i...

For the google part I had to recurse through the AS list first, and perform cidr merging

Wouldn't ipset be easier to use and potentially faster?

Probably yes. It seems easier to write. As it's a set of IPs instead of a set of rules it should be faster. Thanks.

However I can't seem to find the --match-set option for my Android's iptables version. I Will test.

Dunno if it's enough, for example:

https://whois.arin.net/rest/net/NET-63-150-141-224-1.html

is Facebook's range not included above.

    $ sudo nmap -sn 63.150.141.224-231
    [sudo] password for alice:

    Starting Nmap 7.40 ( https://nmap.org ) at 2021-02-11 06:41 CET
    Nmap done: 8 IP addresses (0 hosts up) scanned in 9.15 seconds

Well, good, though that doesn't mean other 50 similar FB IP ranges in other collocation facilities are also not responding to ping.

https://search.arin.net/rdap/?query=FACEBOOK

The links contain the IP ranges (4 and 6). Testing all those should be sufficient.

What about other continents? Are FB addresses all under ARIN, even in EU?

There are some small ranges in RIPE too: https://apps.db.ripe.net/db-web-ui/query?searchtext=facebook

Reply on news.ycombinator.com