I have not had any issues with this for years, and for the life of me have no idea what may be happening.
I have wireguard running on pfsense. It has been for many years. Recenly I upgraded to both the latest version of pfsense CE, and latest version of truenas scale. I am not sure the last time this was working, I may have been on truenas core still but I doubt it… hard to say for certain as I don’t routinly try and access SMB shares over my VPN connection.
All of that said, I can ping, SSH into, use webUI’s etc of services on the same subnet as the truenas SMB share. I can try and ping the smb IP, and I get Request Timeouts. If I SSH into any of the servers on the same subnet as the SMB Share, I can ping the SMB IP and get responses without issue.
I can get to all of my homelab WebUI’s just fine (including truenas), can SSH into all of my VM’s (including truenas), I just can’t seem to get to the SMB shares on any of the subnets truenas has bound SMB shares to.
Of note, I do not have a NIC in truenas for my VPN subnet, so I dont have SMB bound to the VPN subnet (but, I had never had this, nor would I think it needs to be, should be able to access the SMB share regardless of which subnet I am on assuming traffic can pass). Seeing as I can SSH and ping everything else on the subnet except the SMB shares, I am lead to beleive my pfsense rules didn’t get borked…
Thoughts?