From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 7160933 for ecs-isp@2rosenthals.com; Sun, 14 May 2023 17:27:23 -0400 Received: from [192.168.200.201] (port=54455 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.96) (envelope-from ) id 1pyJFG-0006P2-2v for ecs-isp@2rosenthals.com; Sun, 14 May 2023 17:27:10 -0400 Received: from mta-201b.earthlink-vadesecure.net ([51.81.229.181]:39521 helo=mta-201a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1pyJF8-0005Ce-2E for ecs-isp@2rosenthals.com; Sun, 14 May 2023 17:27:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=d+3d1SvyDPqQjP7dnPp1cWLfzhTbyttualUomk LsFq4=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1684099620; x=1684704420; b=M8UV+6uH/Uf6GKeMZwqUukCY4PdngRp4dmWvJfxjjikcyfKOi6SUi+o QUBldkJhmdR7brdaKnEJXjlMa4/SO5B1ze2p4fbuxPqlFEp69YqNAdIpDQ+gr65A2MsV4VB KVazRxmN/N6hDd1b7eexl+QljNvq1qdrIJHtrZbx8LMcRQgdNNr/oqkgaq+Okl5iNmCH8vU fpQQ+hHaxXjjfYMGB3Dbmvmkp4rpAO92jyJxWGpVrPMe8gU+LT3YKTQm74UAuwwBXij4+Wo rLRU6rGO0q7t29yHyj+vOakbDxZOtw7KNVkHPUcVCKtw2Qv5v9xL2YNLS5cnfo9/AMbfbHk U9g== Received: from slamain ([108.193.254.60]) by smtp.earthlink-vadesecure.net ESMTP vsel2nmtao01p with ngmta id c1356b11-175f1fae8a7aa11f; Sun, 14 May 2023 21:27:00 +0000 Message-ID: <64614eb9.13.mr2ice.fgrirsq@earthlink.net> Date: Sun, 14 May 2023 14:12:25 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] InJoy FW 4.2.2 issue with a rule "failed to send packet" X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 05/14/23 at 10:04 AM, "Massimo S." said: Hi Massimo, >but anyway doing this kind of tests on a production server is an issue >since i've to do it late in the night I understand. >and i've another problem too (this one since years ago) >reloading the rules don't show the issue >you have to restart the fw >if i restart the fw injoy do not work anymore even with a working rules >set all packets ends into SYN_SENT state and i've to reboot the server >(setboot /b) As with your "large ruleset" problem, we have never encountered this one either. Dan runs ijfw on 6 or 7 OS/2 instances with differing application mixes. The ijfw security levels vary. Most run 5 or 6, which is a fair set of rules and we also have a number of Observe rules to keep the annoying password guesses away. I can't recall a valid set of rules failing to reload either when using the GUI or with the sync command. Every now and then ijfw constructs a bogus blacklist rule which stops all packet transfers. However, since this is a known issue, it does not take us long to think to delete the blacklist file and sync the firewall. This does not occur often. I dimly recall the last occurance was something like 6 months ago. When you have more data to review on this issue, let us know. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------