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 7160190 for ecs-isp@2rosenthals.com; Sat, 13 May 2023 23:57:31 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:42428 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1py2rI-00052Q-2w for ecs-isp@2rosenthals.com; Sat, 13 May 2023 23:57:20 -0400 Received: from mta-102a.earthlink-vadesecure.net ([51.81.61.66]:45983) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1py2rG-00023k-0A for ecs-isp@2rosenthals.com; Sat, 13 May 2023 23:57:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=bumEJeH/KSNofY0/hmvSrWFnfHALp7odNDgX++ Gu1Zg=; 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=1684036637; x=1684641437; b=rX6wWXtC/13+ZI3zSDHNizE+Q58Yaz0TRpWoGlFsAj79uKtVEKqy97V i2g/lZwl3EtRIIx2vnxNztIO0GdPI15UZXI1GfAasRG6HeeJW9VpVJKPN8CSUNFt1f3iUVe 1wqguL0h1m4WUos38ilehqQx8/y4rjVFgJ9p7YGHFJjPTtOh3Xmu8qEvsifmKPiKSAWKkrl MHkPsnIILWoagRiUV0fwTPRA55Ms7jLCujuc7y/TNpi+X2NEP0KQmX3AI67qsHV/9H6VTZ2 +72QrPYjuLW0GhrnbkefQ8iCLAh540TnnXNZmvCYB+kACn1NU7UoS87X5g+1ijHAgb5cPMG Lvw== Received: from slamain ([108.193.254.60]) by smtp.earthlink-vadesecure.net ESMTP vsel1nmtao02p with ngmta id 852b213f-175ee6662e024cbf; Sun, 14 May 2023 03:57:17 +0000 Message-ID: <646057ae.10.mr2ice.fgrirsq@earthlink.net> Date: Sat, 13 May 2023 20:38:22 -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/13/23 at 10:17 PM, "Massimo S." said: HI Massimo, >BWW asked to use a lower port for the rule, i tried, but it show the same >issue I would have been surprised if it did. FWIW, you don't really yet know exactly what it triggering the failure. To track this down, you need start with a working setup and add rules one by one until you get the failure. Once you get to this point, swap the last rule added with the rule you would have added it the failure had not occurred. If the failure presists, you know the number of rules is contributing to the failure in some way. If not you know that something about the combined set of rules is triggering the problem. You know you can do a lot of testing without touching your working production rule set. Copy your injoy install to a test directory. Then when you have some time to test, shutdown the production gateway and run the gateway from he test directory. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------