Appena sono a casa provo a vedere se c'è un firewall.
Cercando il problema, ma capendone poco, avevo visto che in situazioni analoghe parlavano di NAT reflection.
In particolare questo post (anche se in inglese).
If you have a server sat inside your LAN and you want to connect to it via www.server.com you've probably got your DNS outside your LAN containing that record and referring to your WAN IP, whilst doing port-forwarding of ports 80 and 443 to the server's LAN IP.
That's all fine and dandy until you want to connect to www.server.com from inside your LAN. Your PC will look up that address and come up with the WAN IP's address, and the traffic route from your PC (when on the LAN) to that address will essentially send it out to your WAN through the default route. The thing is there's no U-turns on that traffic so your PC can't connect to it.
There are 2 ways to fix this scenario. The first is running split DNS, where the DNS you're served whilst inside the LAN has different IPs than the DNS you're served from outside the LAN.
The second is NAT Reflection, which means that any request for a service from within the LAN that refers to the WAN IP is then processed by pfsense and sent back into the LAN as though your traffic was coming from the WAN.
