Log entry with no port number - Can't create quick rule.
-
Hello,
I noticed a blocked connection (no port displayed/logged) from a remote file server that I fetch backups from via an outgoing rsync connection to the remote server over a wireguard VPN on port 873.
(The wireguard tunnel is 10.80.0.0/24, the remote site net is 192.168.0.0/24 and my net is 192.168.42.0/24. The outgoing connection goes out from my NAS, through my pfSense to the remote pfSense box, then onto the remote LAN to their NAS. Each connection is made between 192.168.42.0/24 and 192.168.0.0/24 as the VPN endpoint IPs point to the pfSense boxen. Each pfSense box has a route to the remote site and I only allow 873 through.)

The backup works fine, but I am seeing a denied connection without a port number. Simply identified as 'TCP:' from a private ip (no port) to a private IP (no port).

If I add an easy Rule...

It errors out with 'No port number' but I can't add one - not that I know what port to add.

I haven't noticed TCP traffic without port numbers before.
Any info on what may be causing this?
Thank you.
Privacy Policy · Cookie Policy