From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 0D02121FAB for ; Sat, 27 Jul 2024 01:49:04 +0200 (CEST) Received: from gaff.inri.net ([168.235.82.67]) by 9front; Fri Jul 26 19:47:46 -0400 2024 Message-ID: Date: Fri, 26 Jul 2024 19:47:45 -0400 From: sl@stanleylieber.com To: 9front@9front.org In-Reply-To: <2de5d40b-e34b-420d-a86b-50d444e8caa4@posixcafe.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: abstract decentralized package-aware core-based locator Subject: Re: [9front] WANTED: ip based filtering of incoming connections Reply-To: 9front@9front.org Precedence: bulk > For anyone following along at home, this has now been fixed in commit 605bed312a0a24db6cce2f7170353351cbddbd2d. i can now successfully block an individual ip: 168.235.81.125&255.255.255.255 or a /24: 168.235.81.0&255.255.255.0 but not a /14: 47.128.0.0&255.252.0.0 sl