From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 11360347 for ecs-isp@2rosenthals.com; Wed, 11 Dec 2024 19:09:35 -0500 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:60082 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1tLWlr-000000003J3-0ODm for ecs-isp@2rosenthals.com; Wed, 11 Dec 2024 19:09:35 -0500 Received: from mta-101a.earthlink-vadesecure.net ([51.81.61.60]:56545) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1tLWlo-000000004u8-0d6e for ecs-isp@2rosenthals.com; Wed, 11 Dec 2024 19:09:32 -0500 DKIM-Signature: v=1; a=rsa-sha256; bh=8gu8ozzFe8HOMP3CfvJ1G88SLUK0JM4zhA5tKn N+7xM=; 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-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1733962171; x=1734566971; b=a6blVjReovoUNS19VQGO2c2nqOH eesf4sm6cO7QBa+DPDJTK6b5kSrXG8+mdKOfsOM1fyPDmHgmtViHUCkuHSDpx/JkTLv+G79 ynjoNY/vHtmvP5KUkhJqfup4HvbmVUOa/4vTIwTLpOkaUal1I6k6LqrK5/HvedV0VJvAB1U 9xhG1+BJ+EhtDBiuna7/x+6R/Y9KAbeMs17aHlFhmmo+90lTkExby0SkL0aOyTEpOO8SXNE cs1Gutz0UnSRMyylIixgulYzRXF/3ND//fLPOTSKkQ1pT9vhKFLvCJjusQftV+f5HVXc7PQ B/xXobJvEcpdLXTcMcEkpxFsvGi6snQ== Received: from slamain ([172.56.178.196]) by vsel1nmtao01p.internal.vadesecure.com with ngmta id f48c7e70-181045687340ec9a; Thu, 12 Dec 2024 00:09:31 +0000 Message-ID: <675a2736.16.mr2ice.fgrirsq@earthlink.net> Date: Wed, 11 Dec 2024 15:58:46 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] Injoy rule (portmap internet IP -> lan) X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 12/11/24 at 01:22 PM, "Massimo S." said: Hi Massimo, >This is the mlink rule: >link daytime 0.0.0.0:13 193.204.114.105:13 >access daytime 192.168.1.10 OK >I also read the portmap example rules, but none work. As I read the examples, not of the sample port map rules really do what you are trying to do. As I read they, they all exposed a server running on the host system to the WAN. What you are trying to do is allow a locally running client to access the daytime server on the WAN. >I tried this, but it neither produce a log when i start the ntp client on >the local PC that instead works correctly if i use mlink on the server. I recommend you add a couple of log only rules Daytime_in_log Rule-Action = Log, Comment = "Packet received from 93.204.114.105:13", Source = "193.204.114.105", Source-port = "13", Protocol = UDP, Log-Control = Enabled, Log-Mask = "date time severity message resolved_source resolved_dest", Log-File = "daytime_in.log" Daytime_out_log Rule-Action = Log, Comment = "Packet received from 192.168.1.10:13", Source = "192.168.1.10", Source-Port = "13", Log-Control = Enabled, Log-Mask = "date time severity message resolved_source resolved_dest", Log-File = "daytime_out.log" This will allow to verify the your daytime client is really talking to the ports you think it is. BTW, what daytime client are you trying to use? Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------