Mailing List ecs-isp@2rosenthals.com Archived Message #466

From: "Massimo S." <ecs-isp@2rosenthals.com> Full Headers
Undecoded message
Subject: Re: [eCS-ISP] InJoy FW 4.2.2 issue with a rule "failed to send packet"
Date: Thu, 27 Apr 2023 23:04:34 +0200
To: eCS ISP Mailing List <ecs-isp@2rosenthals.com>



Il 27/04/2023 21:32, Steven Levine ha scritto:
In <list-7060516@2rosenthals.com>, on 04/27/23
    at 07:37 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:


Hi Massimo,

i've 3 include files containing rules and another number of rules in
firerule.cnf

#include <firewall/spam.cnf>
                                                  #include
<firewall/r_p_ddos.cnf>
                                                                                                    #include
<firewall/url_filter.cnf>

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

no, if i add the new rule IF give the issue of:   Fatal: failed to send packet...

if i just comment one of the 3 includes, the issue is fixed
(of course after reboot of the server)


massimo

Subscribe: Feed, Digest, Index.
Unsubscribe
Mail to ListMaster