- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
VPN for Remote Access into my Local LAN
Posted on 4/22/20 at 12:16 pm
Posted on 4/22/20 at 12:16 pm
TLDR: I suck at networks.
I've been spectacularly unsuccessful at gaining remote access to my local LAN via VPN. The goal is to be able to connect remotely with my Windows laptop and access file folders in my Synology NAS via mapped network drive. If anyone has any helpful advice, it is much appreciated.
I've got EATEL fiber optic into my Google Wifi router. My Synology NAS is connected directly to that router via ethernet.
My NAS has been assigned a 'reserved IP' (Google's terminology for static, I assume) from the router.
Synology has a package called "VPN Server" and offers a few different types of protocols for connecting. I have been attempting to use L2TP/IPsec. I've defined all necessary information in the server that is required in the client L2TP configuration such as a pre-shared key, the authentication protocol, etc. Likewise I have a user account set up in the Synology that has appropriate privileges.
The "VPN Server" package requires certain ports be open. I added those to Google Wifi's port forwarding.
Depending on which tutorial I read, I have gotten different advice on how to configure Synology's firewall. While I may have an issue with how my firewall is set up, currently I cannot connect even if I have the firewall turned off so I have an issue elsewhere.
I have DDNS configured on Synology and have a unique hostname. I've tried using both this and the WAN IP of my home in my laptop client VPN configuration.
I have rebooted the Google Wifi and stopped/restarted the VPN Server as one tutorial recommended to ensure any changes went through.
When I am connected to a remote Wifi and then click to connect via L2TP it asks for my account credentials which I supply. After 30 seconds to a minute it says that the VPN Server is not responding.
Recognizing there are incomplete details, are there any obvious things I am missing?
Thanks for reading if you got this far.
I've been spectacularly unsuccessful at gaining remote access to my local LAN via VPN. The goal is to be able to connect remotely with my Windows laptop and access file folders in my Synology NAS via mapped network drive. If anyone has any helpful advice, it is much appreciated.
I've got EATEL fiber optic into my Google Wifi router. My Synology NAS is connected directly to that router via ethernet.
My NAS has been assigned a 'reserved IP' (Google's terminology for static, I assume) from the router.
Synology has a package called "VPN Server" and offers a few different types of protocols for connecting. I have been attempting to use L2TP/IPsec. I've defined all necessary information in the server that is required in the client L2TP configuration such as a pre-shared key, the authentication protocol, etc. Likewise I have a user account set up in the Synology that has appropriate privileges.
The "VPN Server" package requires certain ports be open. I added those to Google Wifi's port forwarding.
Depending on which tutorial I read, I have gotten different advice on how to configure Synology's firewall. While I may have an issue with how my firewall is set up, currently I cannot connect even if I have the firewall turned off so I have an issue elsewhere.
I have DDNS configured on Synology and have a unique hostname. I've tried using both this and the WAN IP of my home in my laptop client VPN configuration.
I have rebooted the Google Wifi and stopped/restarted the VPN Server as one tutorial recommended to ensure any changes went through.
When I am connected to a remote Wifi and then click to connect via L2TP it asks for my account credentials which I supply. After 30 seconds to a minute it says that the VPN Server is not responding.
Recognizing there are incomplete details, are there any obvious things I am missing?
Thanks for reading if you got this far.
4
Posted on 4/22/20 at 12:50 pm to RoyalWe
without going through documentation for the VPN software you are using, you may not have all the appropriate ports open.
For my VPN server i run at my house, I have to open two different ports. One port is used for handshake/authentication and then the other port for actual communication/data transfer.
Try verifying all applicable ports that are supposed to be open on your router show up as open to the web. Use something like canyouseeme.org.
For my VPN server i run at my house, I have to open two different ports. One port is used for handshake/authentication and then the other port for actual communication/data transfer.
Try verifying all applicable ports that are supposed to be open on your router show up as open to the web. Use something like canyouseeme.org.
Posted on 4/23/20 at 8:28 am to notsince98
Thanks for the link. I was using an iOS port scanner, but this is much more efficient and faster.
Posted on 4/23/20 at 8:28 am to TAMU-93
I am, but it's Windows 10. I'll check the reference you cite. I'm also considering going OpenVPN.
Posted on 4/23/20 at 10:07 am to RoyalWe
can you explain the physical topology for your network?
Does your google wifi have a Public IP on the WAN side or is your ISP's modem doing the NATing?
Does your google wifi have a Public IP on the WAN side or is your ISP's modem doing the NATing?
Posted on 4/23/20 at 2:25 pm to jeff5891
I learn more every time someone with knowledge asks the right question.
I ran a traceroute to Google's DNS server via "tracert 8.8.8.8" using a command prompt. If I'm interpreting the results correctly, the first hop is a private IP and the second is a public IP. From what I've read, this should mean that my Google Wifi is doing the NATing and the ISP is not.
The public address on the traceroute is not the same as the public IP I see when I Google "what is my IP address". I don't know if that's significant or not.
When I look at the WAN IP address on my Google Wifi router it's a public address which I think confirms there is no double NATing going on.
Here's the physical set up, not showing a few other Google Wifi pucks connected wirelessly in a mesh. All connections I see are ethernet. I think they convert from fiber optic to coax at a box in my yard and then to a modem on my brick exterior.
I ran a traceroute to Google's DNS server via "tracert 8.8.8.8" using a command prompt. If I'm interpreting the results correctly, the first hop is a private IP and the second is a public IP. From what I've read, this should mean that my Google Wifi is doing the NATing and the ISP is not.
The public address on the traceroute is not the same as the public IP I see when I Google "what is my IP address". I don't know if that's significant or not.
When I look at the WAN IP address on my Google Wifi router it's a public address which I think confirms there is no double NATing going on.
Here's the physical set up, not showing a few other Google Wifi pucks connected wirelessly in a mesh. All connections I see are ethernet. I think they convert from fiber optic to coax at a box in my yard and then to a modem on my brick exterior.
Posted on 4/23/20 at 4:23 pm to RoyalWe
google WiFi vpn
I would suggest looking into the link above. It'll allow you to set up a VPN server on your Google WiFi.
I would suggest looking into the link above. It'll allow you to set up a VPN server on your Google WiFi.
Posted on 4/23/20 at 5:23 pm to mchias1
Thanks, but apparently this project is dead. It worked on earlier versions of Google Wifi's firmware but apparently Google didn't like it and figured out how to brick their pucks if you installed it.
Posted on 4/23/20 at 5:53 pm to RoyalWe
Sometimes the consumer ISPs don't allow incoming traffic like http, L2TP, PPTp, etc. L2TP uses UDP 500 and 4500. You may need to ask your provider.
Posted on 4/23/20 at 6:08 pm to ColdDuck
Eatel allows it. I'm with them and I use OpenVPN running on my Asus router.
Posted on 4/28/20 at 9:01 pm to RoyalWe
FYI, I switched to OpenVPN and used OpenVPN Connect as the client and it worked. Go figure. Thanks for the help, everyone.
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News