From owner-freebsd-ipfw@freebsd.org Wed Aug 7 05:33:45 2019 Return-Path: Delivered-To: freebsd-ipfw@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 161EFBF4C1 for ; Wed, 7 Aug 2019 05:33:45 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 463KtJ5bCFz4G8g for ; Wed, 7 Aug 2019 05:33:44 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: by mailman.nyi.freebsd.org (Postfix) id BFCC0BF4C0; Wed, 7 Aug 2019 05:33:44 +0000 (UTC) Delivered-To: ipfw@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BF8A8BF4BF for ; Wed, 7 Aug 2019 05:33:44 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 463KtH5RJJz4G8f for ; Wed, 7 Aug 2019 05:33:43 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x774xMXA085943; Tue, 6 Aug 2019 21:59:22 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x774xLDT085942; Tue, 6 Aug 2019 21:59:21 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201908070459.x774xLDT085942@gndrsh.dnsmgr.net> Subject: Re: amazonaws In-Reply-To: To: Michael Sierchio Date: Tue, 6 Aug 2019 21:59:21 -0700 (PDT) CC: "Rodney W. Grimes" , "ipfw@FreeBSD.org" , starikarp@dismail.de X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: 463KtH5RJJz4G8f X-Spamd-Bar: ++++++++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-rwg@gndrsh.dnsmgr.net has no SPF policy when checking 69.59.192.140) smtp.mailfrom=freebsd-rwg@gndrsh.dnsmgr.net X-Spamd-Result: default: False [10.14 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; GREYLIST(0.00)[pass,body]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.93)[0.935,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.95)[0.951,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.81)[0.807,0]; URIBL_SBL(6.50)[parkingcrew.net]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.05)[ip: (0.15), ipnet: 69.59.192.0/19(0.08), asn: 13868(0.05), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] X-Spam: Yes X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2019 05:33:45 -0000 > On Tue, Aug 6, 2019 at 6:23 PM Rodney W. Grimes < > freebsd-rwg@gndrsh.dnsmgr.net> wrote: > > > > Hi! > > > > > > Is it possible to bl;ock compute.amazonasws.com with ipfw firewall. I > > > have a table with many amazonasws IPs but every time when I start > > > Firefox it shows the new one (I am checkong with tcpdump). > > > > Since it is almost impossible to keep up with the IP's.... > > > > This is not even remotely true. > > https://ip-ranges.amazonaws.com/ip-ranges.json > > is kept up-to-date, and you can subscribe to an SNS topic to be notified of > changes: That is ALL amazon address space, not the specific "compute.amazonasws.com" address only. I do not see how you can derive the valid values of this from the presented URL. > arn:aws:sns:us-east-1:806199016981:AmazonIpSpaceChanged > > > > You could put the entire contents, or a portion of it, in an ipfw table and > swap tables atomically upon change. Which would block ALL amazon hosted services, not just the specific that is "compute". # drill compute.amazonasws.com ;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 35891 ;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1 ;; QUESTION SECTION: ;; compute.amazonasws.com. IN A ;; ANSWER SECTION: compute.amazonasws.com. 600 IN A 185.53.179.8 ;; AUTHORITY SECTION: amazonasws.com. 172799 IN NS ns2.parkingcrew.net. amazonasws.com. 172799 IN NS ns1.parkingcrew.net. ;; ADDITIONAL SECTION: ns1.parkingcrew.net. 300 IN A 13.248.158.159 Which I believe to be an advertising sprinkler used by all sorts of stuff to spam your browser with a random ad page. > -- > > "Well," Brahm? said, "even after ten thousand explanations, a fool is no > wiser, but an intelligent person requires only two thousand five hundred." > > - The Mah?bh?rata > _______________________________________________ > freebsd-ipfw@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw > To unsubscribe, send any mail to "freebsd-ipfw-unsubscribe@freebsd.org" > > -- Rod Grimes rgrimes@freebsd.org