From nobody Sun Jul 13 21:18:05 2025 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4bgJG10F1vz61Vhx; Sun, 13 Jul 2025 21:18:17 +0000 (UTC) (envelope-from vadimnuclight@gmail.com) Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bgJG02Qjxz3Qrf; Sun, 13 Jul 2025 21:18:16 +0000 (UTC) (envelope-from vadimnuclight@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=ifELgDAv; spf=pass (mx1.freebsd.org: domain of vadimnuclight@gmail.com designates 2a00:1450:4864:20::12b as permitted sender) smtp.mailfrom=vadimnuclight@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-lf1-x12b.google.com with SMTP id 2adb3069b0e04-553d771435fso3230961e87.3; Sun, 13 Jul 2025 14:18:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1752441489; x=1753046289; darn=freebsd.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:from:date:from:to:cc:subject:date:message-id :reply-to; bh=74sHvhR5eDSEl5tATw3s0/299SzGiE/vJOtPnxw7ER4=; b=ifELgDAvUlkzjhWfyqooF9Wec9+UrESBUYYHeW0T27Iy0IURIXBvq0qSHu6XIOgpqE 0qt9Z+lTvLkE3LCJsswatN6ybdjajBTo802uDR5aOp1icwRwyUhGblOCPyvuh88i2r3J VVMLvc/34rZzKVj4w/AKhv5btKEiLfI3YK4EGo8D8fBCfM+uUGAUVk56kPv6l7DE/E/q nT2AEE2jMzsBDUfn0ZmyIAFEMIIszSgrgwQqIuRLn9OdFeWoMWn0bZ220ufcOT8isKJz kYR6lGeZEBlFVkl/kMz1OAoXW/lQ4ua25CoqekfRX7lfo7ILBEc14no28ma+5axbIt9Y QRuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752441489; x=1753046289; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=74sHvhR5eDSEl5tATw3s0/299SzGiE/vJOtPnxw7ER4=; b=nZ9c2Ue5K2NlefQYOEaUCWYBTLpBmjkCXGxgtB9Uj6IEw7/yGPBlGYjiH6yb4+lljm uYlgOh1Td2mPtpQ38CxCJdKdm/Xj1P8Zjtbxf29gKIlvduO6WO617tM8li0Zl3v032N6 qOdjPoqEjZ1xYzLHurul0R+PPHL0rdIrHI+dDYR0uJL1KI+uM60+kHo5OHAQcZyrPYWN bvUiezaEzhGCl7V7Vtv8zSzD699Q3Odl5c5IYDRM0EWVrctBRch+Ic5VCq98ZcWFsqJi N6EORAZOFMLexMCgIPAWhCV5DI8TmotjREjQL5HWKC7f0JwTo75RCZBH55bMkF3RebmA 3YZw== X-Forwarded-Encrypted: i=1; AJvYcCUgWjhRSZ2roytreottUSfuY27kmX8+akz1mTn8e+HApZTCgQ+s9G4E+dbBn/Gc7IpBlV5f46L8qT5iNa5QW94BoQ==@freebsd.org X-Gm-Message-State: AOJu0YyJ3C0hL2Lxndb5QT40KUlFD1kaYw0jV/1phKhRDCJWkEN2r6Nv azMbbvJSokKeIMKDNHQ9h/wnjdyP9pwKIfmgt0qxu01eRIlbQEoeS8O4EW+SZQ== X-Gm-Gg: ASbGnctHZvJfcE/pvF2BzAJo8B+LwzyPmpWgA/jNzng/EZiQhu8zRIHRBnsO67FW9bI gWx5T4V07Glg0MpF4IPXyihbsrYFcRqH7XblzKztArvr3MHrffnJImCTVDDtu2f9mBe/axGCTtb eOIOZ4zJPMbN2Alg8xm4bCJc8og4S9VRWosz9M3tot05vRRpkYkL3J2AvJ4D1Lyo/BF3069sO5l AXevyJjGfvfUcFm2UUsLVW8XVrKhPiwpEnm42iu0yLsGftiSPEn+FFH93tQfxBFzQG98l7vv6j9 0GvXIuAbi54iNHpt5vXHLC/HPUvbwMI3U0qKVNVLvp9axjsqUVytrKg9xAJgASvgv9KiUK+lAl3 7n2asTI2+2xXWTl4cUMuge6ngmRaoBHJ+yAc4MH3rrSyryLf4Q1Bb8whac+yesgHk X-Google-Smtp-Source: AGHT+IENBOTZYMFj8qMaKdj5VJpCZ4GH+pfSTLZRjbUiJdtfk1xYRgWDvYnKCB7tL7QXi2PK2yQb4Q== X-Received: by 2002:a05:6512:1317:b0:54a:cc76:1676 with SMTP id 2adb3069b0e04-55a058a4bd9mr2917544e87.44.1752441488687; Sun, 13 Jul 2025 14:18:08 -0700 (PDT) Received: from nuclight.lan (broadband-77-37-180-76.ip.moscow.rt.ru. [77.37.180.76]) by smtp.gmail.com with ESMTPSA id 2adb3069b0e04-55943b79b58sm1730085e87.231.2025.07.13.14.18.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 13 Jul 2025 14:18:08 -0700 (PDT) Date: Mon, 14 Jul 2025 00:18:05 +0300 From: Vadim Goncharov Cc: freebsd-net , FreeBSD Questions Mailing List Subject: Re: Issues with IPFW skipto Rule and Whitelisting Logic Message-ID: <20250714001805.073389b5@nuclight.lan> In-Reply-To: References: <3A01EF48-EBE8-48C3-9C66-6A250A240341@cretaforce.gr> X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.4) List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [2.54 / 15.00]; MISSING_TO(2.00)[]; NEURAL_SPAM_LONG(1.00)[0.996]; NEURAL_SPAM_MEDIUM(0.89)[0.890]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.35)[-0.349]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FREEMAIL_FROM(0.00)[gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org,freebsd-questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::12b:from]; RCVD_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+] X-Rspamd-Queue-Id: 4bgJG02Qjxz3Qrf X-Spamd-Bar: ++ On Sun, 13 Jul 2025 23:53:25 +0300 Christos Chatzaras wrote: > > My intended logic is that any IP present in table(3) should always be > > allowed, even if it or its subnet also appears in table(1). > > > > For instance, 175.178.167.241 is in table(3), while 175.178.0.0/16 is > > present in table(1). > > > > After rebooting the server and populating the tables by running the update > > script for the first time, access from 175.178.167.241 works correctly. > > However, after subsequent runs of the update script - which only updates > > unrelated entries and does not modify 175.178.167.241 or 175.178.0.0/16 - > > access from 175.178.167.241 is no longer permitted. > > > > Additionally, when this issue arises, adding 175.178.0.0/16 to table(3) > > allows access again. Even after removing that entry, as long as > > 175.178.167.241 remains in table(3) and I wait for any active sessions to > > clear, access continues to work. > > To add more detail: > > When this issue occurs, I can resolve it by just removing 175.178.167.241 > from table(3) and then immediately re-adding it to table(3). > > These commands restores access for the IP: > > ipfw table 3 delete 175.178.167.241 > > ipfw table 3 add 175.178.167.241 Did you try to remove `-q` from all your scripts and see if there are errors? May be something in dmesg? Adding another log rules for your test IP? tcpdump? -- WBR, @nuclight