search

trailofbits / algo

Set up a personal VPN in the cloud
https://blog.trailofbits.com/2016/12/12/meet-algo-the-vpn-that-works/
GNU Affero General Public License v3.0
29.02k stars 2.33k forks source link

SMB Connection From one computer to another (client side) #1027

Closed Viktova closed 6 years ago

Viktova commented 6 years ago

OS / Environment (where do you run Algo on)

Linux me 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29) x86_64 GNU/Linux

Cloud Provider (where do you deploy Algo to)

Digital Ocean, but i didnt use the script to deploy the whole thing, i manually set it up (using local installation)

Summary of the problem

Lets say I have 2 servers/computers (contains data, files, dbs) that are connected as clients to a main server (algo server). let's call these computers 1 and 2. how can i connect 1 to 2 or vice versa using SMB protocol. note that both servers have SMB enabled and are accessible locally. (used to work with openvpn).

edit: after i removed the following drop rules:

-A FORWARD -s 10.19.48.0/24 -d 10.19.48.0/24 -j DROP
-A FORWARD -s 10.19.48.0/24 -d 10.19.49.0/24 -j DROP
-A FORWARD -s 10.19.49.0/24 -d 10.19.48.0/24 -j DROP
-A FORWARD -s 10.19.49.0/24 -d 10.19.49.0/24 -j DROP

I was able to ssh to computer 2 from computer 1 through the VPN, and i was able to login via FTP, but still SMB not working.. it says "Server Timed out"

Steps to reproduce the behavior

  1. Connect to algo on both clients (computers 1 and 2)
  2. try to access computer 2 from computer 1 via SMB
hyperbart commented 6 years ago

Experiencing this issue too, wasn't there when I was running Algo on Ubuntu 16.04 couple of weeks ago. However, I can't connect to SMB servers in the same network as the Algo server, it's not about not being able to connect to SMB on other Algo clients.

More specific: around the end of may my deployment with algo this was still working perfectly fine. Now it isn't anymore.

OS / Environment (where do you run Algo on)

Ubuntu 18.04 locally on ESXi

Cloud Provider (where do you deploy Algo to)

None, locally on ESXi

Summary of the problem

I'm using Algo as an entry point to a remote network hosted on a VMWare platform. Server running samba at remote network, in this remote network there is an Algo server deployed. When connected with algo server to the remote network and trying to connect to an SMB host in this network the connection can't be established. HTTP/SSH etc are working fine to this remote host, pings too but SMB fails.

Steps to reproduce the behavior

  1. Deploy an algo server on a remote network (i.e. your home network)
  2. Connect to algo server
  3. Try to connect to SMB server on remote network, error...
Viktova commented 6 years ago

@jackivanov disabling that option didn't work for me, here's what I did:

1- edited config.conf 2- executed ./algo update-users 3- enter the previous CA passphrase along with other information 4- rebooted the sevrer 5- tried to connect 2 computers to algo, then tried to access from one to the other via SMB, same issue.

Viktova commented 6 years ago

Worked, Thanks a lot for the quick fix!