Can I make a wireless raspberry pie that can remote access my home network so i can stream video,...

[G+_Booo Urns]

Can I make a wireless raspberry pie that can remote access my home network so i can stream video, play mp3' access my document from anywhere??

Good project idea for the show :-D

[G+_David Peach]

I don't know that I have any answers, but wanted to clarify.

 

1. You want to take this Pi outside the home and have it auto connect to home, and then connect to the Pi locally (in the remote location) to stream?

 

2. Or, you want the Pi at home ready to receive a remote connection and pass the media through the Pi to the remote computer/phone/tablet?

[G+_Ben Reese]

To follow up on David Peach?'s response.... The answer is yes to both.

 

On the first you'll want a VPN (or at least something like Plex or ownCloud/NextCloud) running on your internal network.

 

On the second your Pi can be that VPN server that your phone/tablet/laptop connects to.

[G+_Black Merc]

Daren kitchen of hak5.. Did it with a lan turtle and a diy vpn server in the cloud to ssh(and more!)into and out of any network that he deployed the turtle on. The server was the pivot point for any lan turtle or system he set for it.(behind any nat)

[G+_Booo Urns]

Black Merc dumb that down for me please.

[G+_Ben Reese]

Booo Urns? I love the Hak5 implementation, but it's probably a bit overwhelming for most. Very cool stuff, but maybe not so much for beginners.

 

Essentially, the LAN Turtle (more or less a Raspberry Pi) plugs into network A. Something else (say a laptop) is connected to network B. Both of those connect to an OpenVPN server and form network C. That C network joins A and B so A and B can talk to each other... If the makes sense.

 

It again matters whether you want your Raspberry Pi to be the server that lets you in from outside, or the client that's coming in from outside... And a Raspberry Pi can do both. I've been helping a gentleman who's using a Raspberry Pi as the VPN server and connecting to that VPN with another Raspberry Pi from his car.

[G+_Black Merc]

Sorry i showed my nerd off.

Booo Urns mr. Ben Reese has it right.. However do be careful. If one net gets infected, that infection can travel across the vpn to the other. Rare but can happen.

[G+_Daniel Stagner]

Black Merc, Ben Reese; In the above implementations you have network c in the cloud. Can you expand on network c and how it connects the other two networks.

 

This is very interesting to me because I have two edge router-x's. One in my home and one in my parents home. but neither of us has a static IP. And I need to keep both updated. This is not so bad because I take the kids there on the weekends and can update at that point. But on more then one occasion the IP on one or the other network has changed with in hours.

 

I travel quite a bit as well and it would be nice to have secure access to the home network from nonsecure hotel networks. The edge router will not work from behind another router.

[G+_Ben Reese]

Daniel Stagner? here's that Hak5 video and maybe that will help.

Darren is using the OpenVPN Access Server which, I believe, is free for 2 connections. Around 12:45 is where he starts explaining how his Turtle user is configured as a gateway so the VPN server (the virtual router in network C) knows it can be used to access the target network.

 

So in your case... Perhaps you have these networks:

Home=10.0.1.x

Parents=10.0.2.x

VPN=10.0.3.x

 

You'd configure the VPN client for Parents to be a gateway to http://10.0.2.0/24 and, if you wanted, Home to be a gateway to http://10.0.1.0/24.

 

To take it to the next level, I think you could use static routing on the Home Edge Router so any traffic destined for 10.0.2.x goes to whatever client you're using on your network (Raspberry Pi, VM, old laptop, etc).

I can only say I've tested this static routing partially. My home VPN server uses something like 10.8.0.x and my home network uses something like 192.168.1.x. My OpenWRT sends all traffic destined for http://10.8.0.0/24 to the VPN server (http://192.168.1.4)... If that makes sense.

 

So a few things I don't know yet... How can you configure a client as a gateway without using OpenVPN Access Server? Access Server probably just configures the same OpenVPN server that's freely available without restrictions, so it should be possible.

Can the Edge Router act as the VPN client/gateway, but only send the traffic destined for that subnet over the VPN? (As opposed to sending all traffic over the VPN.)

 

Hopefully this helps and doesn't just confuse things more.

[G+_Black Merc]

In an instance without the lan turtle, the edge router is the gateway(twice, one for regular lan access to the internet... Two for the remote user using vpn to access the lan and the security of the lans firewall to the internet)