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 9315641 for ecs-isp@2rosenthals.com; Sun, 17 Mar 2024 18:13:41 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:56748 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 1rlyl0-0006BO-2T for ecs-isp@2rosenthals.com; Sun, 17 Mar 2024 18:13:30 -0400 Received: from mta-102b.earthlink-vadesecure.net ([51.81.61.67]:34447 helo=mta-102a.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 1rlykr-00083M-01 for ecs-isp@2rosenthals.com; Sun, 17 Mar 2024 18:13:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=NWFpjp+heixo/HRG/Uu0CEtX+dcgKobY2yMPtz HADBo=; 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=1710713600; x=1711318400; b=i9ita6Lcy4hF48Q2KrDKcRJG5eBi/Qh9qmQ7Iqs+GPC/IZgBqVPmvq4 tguJXpHvUT81gysinromjbcuM7wGUkWrA8t/+yvUTLf02ZuQZLvB7DFGZO4RJvvscfOAFHT 0vyoAFPNWoOiCAJhT54iSyRxNj7hFCuh49YLjj3pO7yZle5BAkpty6PHQHU8exqu04oyqXi Ger57TvriOgCTh9x5iuuflY3f+jc198YWJ4WDZiUSfzJJ/Ih+RcnCSYi2JFL3J0eqE4w0Lm pJHYpjjuxCkKrr/2z1Ul7vCeGxVUc1OzPaSjJrMNb/5hMDLpzFkieMax8IWSLytP0vdQcPd f1g== Received: from slamain ([108.193.253.210]) by vsel1nmtao02p.internal.vadesecure.com with ngmta id b3e7ecc9-17bdacf4a0a82d32; Sun, 17 Mar 2024 22:13:20 +0000 Message-ID: <65f76863.2.mr2ice.fgrirsq@earthlink.net> Date: Sun, 17 Mar 2024 15:02:11 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] help about an Injoy FW rule X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 03/17/24 at 07:50 PM, "Massimo S." said: Hi Massimo, >the firewall in that condition do not reach the internet so each 30 >minutes the fault daemon gives a reboot OK. The be clear, ijfw is not reaching the internet because gateway.exe is shutting itself down and you are running with device-fxwrap,sys /S in config.sys? >assist_rem_srv6_in > Destination-Port = "55000", > Source = "1.2.3.4", > Destination = "My_IP", > Rule-Action = Portmap, > Mapping-Dest-IP = "192.168.1.8", > Mapping-Dest-Port = 3389 >assist_rem_srv6_out Rule-Status = Disabled > Source-Port = "3389", > Source = "192.168.1.8", > Rule-Action = Portmap, > Mapping-Dest-Port = 65488 >ext_m_in > Destination-Port = "55000", > Source = "1.2.3.5", > Source-Netmask = 255.255.255.254, > Destination = "My_IP", > Rule-Action = Portmap, > Mapping-Dest-IP = "192.168.1.8", > Mapping-Dest-Port = 3389 >ext_m_out > Source-Port = "3389", > Source = "192.168.1.8", > Rule-Action = Portmap, > Mapping-Dest-Port = 55000 What happens if you disable the ext_m_in rule and enable the assist_rem_srv6_in rule? Does gateway.exe run without dieing? >i guess the issue that create problems is the one "assist_rem_srv6_in" If that's the only rule you added, this is probably true. >> Have you checked if the recently announced ijfw 4.2.3 release has any >> effect on his failure? >still not OK. I recommend you give it a try. I recommend using the .zip file and just replacing the binaries (*.exe, *.dll and *.sys). The rest of the files are unchanged, so your existing rules and configuration files should works as is. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------