In <list-11340426@2rosenthals.com>, on 12/11/24
    at 01:22 PM, "Massimo S." <ecs-isp@2rosenthals.com> 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?