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 A6FF625442
	for <ml@inbox.vuxu.org>; Sat, 27 Jul 2024 02:25:22 +0200 (CEST)
Received: from gaff.inri.net ([168.235.82.67]) by 9front; Fri Jul 26 20:20:54 -0400 2024
Message-ID: <65669461B2780267EEAFB7B99374421F@gaff.inri.net>
Date: Fri, 26 Jul 2024 20:20:53 -0400
From: sl@stanleylieber.com
To: 9front@9front.org
In-Reply-To: <E8D8FF3D708E5C1102FE4C200FC9809E@gaff.inri.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: flexible lossless package metadata AJAX over WEB2.0 app blockchain 
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

use of the | separator seems to break filtering for the entire line:

	aux/dial -e 'ipmux!ver=4;src=85.208.96.0&255.255.255.0|85.208.98.0&255.255.255.0' >/dev/null &

list one ip and it works, list two and it doesn't work.

sl