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

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: Sun, 14 May 2023 10:04:00 +0200
To: eCS ISP Mailing List <ecs-isp@2rosenthals.com>



Il 14/05/2023 05:38, Steven Levine ha scritto:
In <list-7151547@2rosenthals.com>, on 05/13/23
    at 10:17 PM, "Massimo S." <ecs-isp@2rosenthals.com> 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

Good hint this one, thanks a lot

but anyway doing this kind of tests on a production server is an issue
since i've to do it late in the night

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)

the server takes about 5 minutes to restart
so doing this kind of tests on a production server is a pain in the ..

massimo




massimo

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