VPN and NAS using SMB
I have a Firewalla Purple. I would like to use it to setup a VPN server which will allow me to connect remotely to my home network and use a NAS drive (mycloud) as if I am connected to the local network while I am traveling. I have setup the VPN server using WireGuard and have setup the client on my laptop. I am able to connect and surf the web as if I am at my home computer (IP appears as my home IP address no matter where I am) so VPN is working. However, when I open Windows Explorer and click the Network pull-down it does not show any of the devices connected to my home network. I believe this may be that my VPN interface IP address is on a different subnet from the rest of my network (home network is 192.168.1.0, Wireguard automatically setup my interface for 10.200.181.2)
It is possible that this is why Windows is unable to find any other network hardware (no printers, no NAS, no other computers)? If so, how do I make Wireguard assign my interface an IP within the 192.168.1.0 subnet? Even better would be to make Wireguard use DHCP from my home router to dynamically assign an IP.
Don't know if this makes sense but based on my limited knowledge it sounds like it could be the problem and might be a solution.
Thanks!
-
Yea, when you are on layer 3 VPN, you can't see the LAN devices, because that device is not on the LAN at your home. So, the best way is to access your resources using their IP address or firewalla local domain directly https://help.firewalla.com/hc/en-us/articles/1500002445242-What-is-the-Firewalla-local-domain-and-search-domain-
-
Okay, I read the post at the link you shared. The mycloud NAS is clunky when not using Windows SMB networking. I believe the only way I can access the mycloud device file structure using it's IP address is FTP, or NFS. I'll try to setup an NFS client and see if I can make an NFS drive mapping work well enough. It's super handy just having a share show up in Windows Explorer. If I can map the drive using NFS I'm guessing that will work.
Any way to make SMB work with the Firewalla and Wireguard?
-
So, the NFS works, but the CAD software I used didn't like it. It couldn't link files that it needed and kept giving me errors when using NFS.
I'm back to SMB. I don't know enough about it to figure out how to make it work. Am I correct that the subnet being different is causing SMB not to work? If so, any way to reconfigure the Firewalla VPN server to assign IPs on the same subnet as my NAS?
-
BTW, I have the NAS connected to the Firewalla LAN port and the Firewalla connected to my ISP router in Bridge mode. My initial thought was that I would be able to help guard my NAS from WAN attacks this way. Is there a way to use the DHCP in the Firewalla to assign an IP on the 10.200.181.0 subnet for the NAS? If so that may work also. What would be ideal would be to setup two IPs for the NAS. One on the 192.168.1.0 network and the other on 10.200.181.0 so that I could access it from both local and VPN.
-
https://help.firewalla.com/hc/en-us/articles/360007345553-Fun-Things-To-Do-with-Firewalla
I'm 100% sure it is possible to do what I'm wanting to do now. Just a matter of how much time I have to spend, how much support I can get, and how secure it will be when I'm all said and done.
Yes?
Can you point me to some information about how to customize the way Wireguard Server assigns IPs to Interfaces on Firewalla? I'm guessing there is a config file somewhere that I could play with that would assign different IPs when a new client is added.
Please sign in to leave a comment.
Comments
6 comments