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 7060950 for ecs-isp@2rosenthals.com; Thu, 27 Apr 2023 16:15:10 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:39859 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 1ps817-0001GW-0D for ecs-isp@2rosenthals.com; Thu, 27 Apr 2023 16:15:01 -0400 Received: from mta-202b.earthlink-vadesecure.net ([51.81.232.241]:37639 helo=mta-202a.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 1ps811-0007dH-0Q for ecs-isp@2rosenthals.com; Thu, 27 Apr 2023 16:14:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=5yD6BhiCx+2MIZSbtCVpmnqaSpW67Fkpp0jZu+ 6j0NQ=; 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=1682626493; x=1683231293; b=ihpWxREno4sFG6QUy2DtobsiH3WRm3WSxtL5QRckn1zpG+ZCBCzjltQ NDs+E2kIc0uUbzSZ5b4cEUIQ9fSGW/aLZKf2bY9JlhOTxWVU2SXG/o1DnK6X6Cpy7QUt2xz RKVTvKlbLzJKONgBAagBsMz5xqWCmNVmJAhdmlDd9YsyzHLAHyrkByKKFOUybcbc8UUxtx0 quIMbGwMetSpAVXHYITIKKNZ5BCsYMF4+Wb00D2oXNtKeIUk0/eKAbFN9OksbLioaV/FGuf cBE+Tn+l6MHylKuR5Kc0RieVpmcQ0wKtBdSMF/5FtryaUv9yx6IlGiNgZMYHNz1LwulmDwq QOw== Received: from slamain ([108.193.254.151]) by smtp.earthlink-vadesecure.net ESMTP vsel2nmtao02p with ngmta id 1da895c0-1759e3e165e7a925; Thu, 27 Apr 2023 20:14:53 +0000 Message-ID: <644acdde.6.mr2ice.fgrirsq@earthlink.net> Date: Thu, 27 Apr 2023 12:32:46 -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 04/27/23 at 07:37 PM, "Massimo S." said: Hi Massimo, >i've 3 include files containing rules and another number of rules in >firerule.cnf >#include > #include > > #include > >i had to comment one of these to have injoy working again I'm still confused about what you actually did. Are you saying that simply removing the new rule123 was not sufficient to allow ijfw to start working again? For those reading along, ijfw does all the rule processing in ring3 (i.e. gateway.exe and firewall.dll). The ring0 driver fxwrap.sys is part of the NDIS protocol stack and past packets up and down the stack after they have been processed by the firewall, assuming the firewall is enabled. What's failing for Massimo is the DosWrite that passes a packet from the ring3 code to the ring0 code. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------