From: "Steven Levine" <ecs-isp@2rosenthals.com>
Message-ID: <644a1f17.4.mr2ice.fgrirsq@earthlink.net>
Date: Thu, 27 Apr 2023 00:07:03 -0700
To: "eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In-Reply-To: <list-7057545@2rosenthals.com>
Subject: Re: [eCS-ISP] InJoy FW 4.2.2 issue with a rule "failed to send packet"

In <list-7057545@2rosenthals.com>, on 04/26/23
   at 09:20 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi Massimo,

>rule123
>         Protocol = TCP,
>         Destination-Port = "54444",
>         Destination = "My_IP",
>         Rule-Action = Allow,
>         Direction = Bidirectional

>to my firerule.cnf

>injoy stop working, every tcpip connection do not work (server completely
>isolated) and i get this error in activity.log

>Fatal: failed to send packet (32799 - 0)

The error code translates to

#define ERROR_LONGLOCK                  32799

and 0 is the number of bytes sent.

This means for an as yet unknown reason the DosWrite to the pipe that
gateway.exe uses to communicate with fxwrap.sys timed out.

Did you check ijfw\logs\firewall.log?  This is where rule errors are
typically reported.

>since i use includes (with 3 rule files) and i've about 417 KiloBytes in
>total of rules anyone knows if i'm reaching a physical limit of the
>product?

If you were, it would be reported in firewall.log.

>to have the firewall working again and so tcp/ip communications i had to
>comment one of these 3 include file

What does this mean?  You stated above, you added one rule and thi broke
the firewall.  What does have to do with "these 3 include file"?

Steven

-- 
----------------------------------------------------------------------
"Steven Levine" <steve53@earthlink.net>  Warp/DIY/BlueLion etc.
www.scoug.com www.arcanoae.com www.warpcave.com
----------------------------------------------------------------------