hey lovely folks!
currently trying to setup a site-to-site VPN so I can tunnel my traffic through my home network when I travel abroad.
As such, I had to set up portforwarding on my verizon fios router (using the internal IP adddress assigned to my Slate AX router and the provided port). I set up port forwarding by consulting online resources (youtube and other documentation in concert with the documentation provided by GL.iNet)
However, when I check to see if the port is open, it’s noted as closed and I keep getting the following error when I try and validate DDNS on my slate router
“The IP from DDNS domain resolution is not the same as the WAN IPs of the device. You need an Internet Public IP address to use the Dynamic DNS. If this router is behind NAT, you may need to set up port forward in your ISP router. If you have VPN Client enabled, please disabled “Services from GL.iNet Use VPN” in the global options.”
Was wondering what I might be missing here and if anyone has any experience with this setup or any other items I can check to otherwise troubleshoot. Likely going to call Verizon but was looking for any guidance in the interim.
TIA!
Your post appears to be a very commonly asked question or thread here relating to VPNs and/or hiding your location. Please check out the VPN Wiki for common answers to these common questions. You can also find other recent posts related to this topic here
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
If you don’t get an answer here, you might want to try r/techsupport.
For sure here is a link to the interfaces
https://imgur.com/a/s5HoChk
Screenshots of the different Verizon router pages might be helpful
Do you think purchasing a static IP from the ISP would get around this? I’m also very interested in setting up one of these!
I had the same setup and I went to a forgon country. My company is not allowing me to. Connect to vpn. It looks like they are detecting the undelying vpn and some how blocking it. I am traveling back to usa because of this.
Wiregaurd home vpn setup, wiregaurd client, gli net slate router.
I am a computer science guy and have the basics strong. Until you get to a foreign country you dont know what your company setting are. It could be as simple is there is a vpn outage at my firm but it just happened to be this weekend and I dont know , I will find out tomorrow. As far the back up, I had express and a static vpn provider, but did not work either. Everything worked at home. I tested for a month.
OP, any luck with port forwarding on the Verizon fios router? I’m getting the same message when I run the DDNS test. I also confirmed that the IPs don’t match with the method provided by gl-inet here. My IP from my gl-inet home router did not match the public IP that I found by googling on the web browser.
This is where I researched and discovered that our ISP (Verizon) does not support public IP address here.
Have you figured out a work around? There’s currently two routes I’m looking at taking:
- Using an internal static IP address that matches what my Verizon IP address is. Got that suggestion here
- Using the AstroRelay to set up a reverse proxy which was suggested by gl-inet for situations like this. Link is here
I’ll also DM you a message.
Interesting, can you explain your exact setup and any testing you did before and upon arrival to the country you were in
Interesting, maybe ur company has more advanced detection systems. Never heard of anyone being caught using this. Will look to try it out myself and see what happens
Fair enough, this is definitely risky to do but you’ll never know until u try it
I dont know myself, I had some os update on the company laptop. I will be able to update once I head back the US tonight . Hopefully I was not flagged by the IT admin. Wasted $1000 in just travel last 2 days. I dont think my company is that advanced. When I logged vpn logs, it mentioned one of the thread disconnected because of network discovery making the whole vpn shut down… Luckily I tested in on sunday, and I was able to book my return flight. Fingers crossed I am not fired tomorrow.
Just wanted to follow up. It looks like there was nothing on vpn side. There was an OS update thst screwed up the vpn client which did not connect. Its my unfortunate timing that it happened during the first day of the trip. The IT Admin guys fixed it today. I am back in the US, but what a trip, I wish I did not come back but better be safe than sorry.
Did you have the kill switch enabled?
An OS update on the company issued laptop? How would that prevent the wireguard client from working? Presumably, any OS change update would necessarily need to use the encrypted traffic enabled by the Wireguard client. Trying to get a better sense of what might have caused this
No. I read about it this morning.
Its nothing related to wiregaurd. Initially I thought the setup did not work. But apparently it was a coincindence that the the vpn client inside the laptop did not work with OS update over the weekend. Where are you planning on going as a digital. Nomad?
Yep, that explains it then. The kill switch would prevent any unencrypted traffic.