#TY
Senior Member
My iPhone, iPad, and MacBook Pro mostly.With what device(s) will you connect back to your network with?
My iPhone, iPad, and MacBook Pro mostly.With what device(s) will you connect back to your network with?
My iPhone, iPad, and MacBook Pro mostly.
Okay, not my area of comfort!
But as an overview, go to the VPN section on the lefthand side, click on the OpenVPN Server tab, Select Server 1, enable it, and 'Export' the OpenVPN configuration file.
Email this file to yourself and on each device, find the program that works with the .opvn configuration file you download.
https://openvpn.net/community-downloads/
I'm not sure if the above link will help you with your devices? Maybe you have to find them in the store?
It really is that easy though. Once connected with the OpenVPN client, SSH into your router or simply type in the IP address for it into the browser.
That's precisely what I'm trying to do. I'm currently looking for M&M like instructions to help me through the process.
384.10 is the firmware showingWhat firmware have you installed? If it's not 384.10 release, then it isn't the latest.
384.10 is the firmware showing
Actually I think this is a bug that's lined up for a fix, let me see if I can find the source of that thoughtIf you're already showing bugs and glitches like this, I would recommend a full M&M Config.
Please see my signature for the link and further info. The goal with this config is to reset the router fully with the new/desired firmware installed and minimally and manually configure it (do not use a saved backup file) to secure it and connect to your ISP.
This will ensure the router is in a good/known state. Right now, it is not.
2bc62226a6 rc: reset new firmware notification flag in case update check fails to run post-upgrade
On my to do list when I return home next week. I shut down power to my network before I left so I can't remote in to take updated screen shots. I am also several versions behind myself and need to get caught up. Should be able up to have everything updated no later than 13 April.NOTE: Both the video and Xentrk's screen-shots are out of date as it is difficult to keep up with GUI changes...sorry Xentrk to give you additional work, but 'Push LAN to clients' is now obsolete
UPDATE:
I got the OpenVPN Server to work on my router (the videos and links you guys posted were awesome and it was really simple). In order to take advantage of Stubby and the other scripts from my devices remotely though, I had go into the Advanced tab of the OpenVPN Server settings and simply switch Advertise DNS to clients to Yes.
Also Important: I also had to Turn Port Forwarding on in the Firewall and select OpenVPN Server and point it to my router.
Remaining challenge: If my OpenVPN Client is on (connected to ExpressVPN), I cannot connect to the OpenVPN Server remotely. I tried changing the DDNS IP setting from Internal to External but same result, I still cannot connect. The only way to connect remotely for now is to turn off my OpenVPN Client (ExpressVPN) on the router.
My objective is to keep all the LAN as private and secure as possible (hence ExpressVPN), AND to allow me to take advantage of my Lan when I'm away.
Any ideas? Thanks again to all in advance. We're almost there
Yes, it is currently set to All.Do you have 'Redirect Internet traffic=ALL' for the VPN Client or something similar in functionality?
"Computers only do want you tell them to do, which isn't necessarily always what you want them to do."Yes, it is currently set to All.
"Computers only do want you tell them to do, which isn't necessarily always what you want them to do."
If the OpenVPN server accepts a connection from the WAN (unless your VPN ISP supports/allows inbound unsolicited requests) via your external DDNS IP, where do you think the reply is sent?....yup via the VPN Client... as you have demanded where ALL LAN traffic (and the router is on your LAN - correct?) should be obfuscated/sent.
So either enable Selective Routing for the VPN Client, and manually invert the table entries so that everything on the LAN goes out via the VPN Client, except the router's traffic i.e services it is hosting e.g. OpenVPN or use Advanced Port Selective Routing for the outbound OpenVPN traffic (Port 1194) via the WAN.
So either enable Selective Routing for the VPN Client, and manually invert the table entries so that everything on the LAN goes out via the VPN Client, except the router's traffic i.e services it is hosting e.g. OpenVPN or use Advanced Port Selective Routing for the outbound OpenVPN traffic (Port 1194) via the WAN.
Yes.Is this what you mean? Thank you once again
Yes.
So does it work by still directing ALL LAN traffic out via the VPN, but now allows you to connect to your OpenVPN server from a device preferably not connected to your LAN.
Skynet shouldn't break anything you have going. Just start slow. Add features and test before going all in.Everything works!! THANK YOU SO MUCH
I think once I'm done, I will backup everything on this router and write up a How To for Dummies like me detailing Step by Step what needs to be done. You guys are unbelievably amazing. I can't thank this forum enough.
The only left for me to do for now is install SkyNet. I'm trusting nothing will blow up after getting this far.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!