I don’t think it is because I heard of a similar project someone did, although not creating their own VPN service, where they set up PIs throughout a library. Even if anyone did happen to find them they presumably couldn’t find the logs of who would be connected because you could just encrypt the PI.
Cap: “I understood that reference”
That’s true. Like I said in another reply, it’s just kind of an idea that popped up in my head just because I always think input stuff like this, so it would require a lot more thought to actually get it setup. Thanks for the thoughts though, I haven’t really thought that far into the technical side of things and it’s quite interesting.
You can run an SSH reverse proxy tunnel from the Pi to a remote server and then the remote server can send packets to the pi through the tunnel. The tunnel can be opened on port 80 if that is the only port that is open on the public wifi’s firewall.
I once wanted to ssh from my computer to my pi which were both connected on a public network. The public network kept all hosts separated from each other for security reasons, so I had to set up the pi to reverse proxy into my remote server, then I could simply ssh into the pi from my remote server.
A lot of open networks have a few open ports. Could always try reusing those ports.
This is what I was thinking. I haven’t really thought that deep into it, so for ow my idea is kinda shallow.
Essentially yes, all I would be doing is creating my own VPN server so I wouldn’t have to deal with big companies and logs, etc.
Not over free vpns, over log free vpns, and I wouldn’t risk a felony over this. I was just seeing if it was a viable option so I would know I have a log free vpn and won’t have to guess.
It can be tied back to you, if the authorities ask the vps provider to snitch on you.
Like reverse tunneling ?
It is feasible with reverse ssh tunnel. The pi can contact a remote server as a client over port 80 and the client can then route any packets it wants across that port 80 TCP connection. To the router, it would look like a standard server response on port 80. Since the TCP connection was already established by the Pi as a client, the router will know how to route packets to the Pi (using Port Address Translation presumably).
I’m currently using this technique to route traffic from my remote server to my continuous integration server that is sitting on my home network without a static IP. There was no port forwarding setup required to do this. The SSH reverse tunnel maintains the TCP connection so the continuous integration server doesn’t need a static IP at all.
Could you clarify what you mean by this
Yes, I use Tor on a daily basis, but in some instances you don’t want network admin or isp to know you are using tor. In addition, the vpn would help stop DNS leaks from what I understand, which while not common, are a possible occurrence while using Tor.
Also I would like to be able to use the clear net just for the browsing speeds, which from what I’ve learned so far from this thread, would most likely be quite slow.
VPN companies can snitch on you if asked by the big guys.
This would not modify the local network.
He is not trying to modify anything, he is trying to take advantage of free public wifi as his own to run a VPN. But he doesn’t understand he needs a static internal IP so that your VPN server doesn’t change on you and you can’t connect. You also need a DDNS client to update the external IP should it changes. It’s simply not practical but not illegal unless he tries to configure the public wifi’s routing.
Scratches that part of my brain…
Haha yep, wasn’t sure how many people would get it lol
This case, as I remember was done at a college as a project. More than likely they had permission .