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 9311736 for ecs-isp@2rosenthals.com; Sat, 16 Mar 2024 16:35:13 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:52459 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 1rlakI-0008Dv-1u for ecs-isp@2rosenthals.com; Sat, 16 Mar 2024 16:35:10 -0400 Received: from mta-101b.earthlink-vadesecure.net ([51.81.61.61]:53879 helo=mta-101a.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 1rlakB-0008Tn-3A for ecs-isp@2rosenthals.com; Sat, 16 Mar 2024 16:35:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=50xk0AmWC9Wadghjk6arqNohlPMzaW8YMZrHeA YfNAM=; 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=1710621303; x=1711226103; b=AvFvZtPw+HhxugLO7MKWhpf2waWjqXPC7NMGuxi7ohue9P+smAAgLpI xgZxKYdu/08rCLmLknLn3h2EBuf1dn658pC4m68Y5WVbay4E+Em52U18q9BDVKjrF2xNWuf CVB48XhN6lSApXBCbJRK1HpEac6hocybfB1Dwe4ny5XpPFWu2v3mW8hdWzBSuWHK7hqxrqA KLQK+mQKSZH7o2RdarT0ehFJHpAIwDpWB4abrhvAzG2vWffuIPvwJjloTA3SjErt+NtNxLw bKGvkGq92LsZHNWqLUwYgFwEociS4KSoSZgQr3pW+npwu7BnWYQEsaKYn9NEgFsHoFL+kl9 WZg== Received: from slamain ([108.193.253.210]) by vsel1nmtao01p.internal.vadesecure.com with ngmta id fa77ecb9-17bd590312f5b297; Sat, 16 Mar 2024 20:35:03 +0000 Message-ID: <65f5f5a6.4.mr2ice.fgrirsq@earthlink.net> Date: Sat, 16 Mar 2024 12:40:22 -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/16/24 at 11:35 AM, "Massimo S." said: Hi Massimo, >this is a very old post nov. 2022 That's for sure. :-) >i created the rule (using FW gui), reloaded the fw rules, all ok at the >reboot of the firewall server (early in the morning i scheduled a reboot) >Injoy stop completely to work and the firewall "close" all communications >so that you can't connect anymore with the remote console to fix the >issue Oops. >i repeat that i created the rule using FW gui, so there can't be an space >or a bad char in firerule.cnf This is irrelevant. The GUI cannot totally prevent you from creating rules that will not work. >Injoy don't show any error in firewall.log In my experience, firewall.log is good at detecting and reporting syntax errors, but it's not as good at detecting and reporting semantic errros. >while i get in activity.log >this: >Fatal: failed to send packet (32799 - 0) This is from gateway\fxio.c:429 rc = FX_Ether_Send(hPipe, packet, len, &ulBytes, pppoe); if (rc) syslog(TRACE_FATAL, "failed to send packet (%d - %d)", rc, ulBytes); and #define ERROR_LONGLOCK 32799 This implies that fxwrap.sys is stuck for some as yet unknown reason and this cause the underlying DosWrite to fail with ERROR_LONGLOCK. >that's a mistery to me >any idea? Did the failure presist when you forced a reboot? How did you recover from the failure? Did you forget to include a copy of the problematic rule in your message? Have you checked if the recently announced ijfw 4.2.3 release has any effect on his failure? Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------