Hello, All. I am new to the GL.INET family and just got my Flint 3. I typically am an individual that just likes my things to just work. I love the concept of the VPN Server from the router, particularly when I am traveling. I have purchased both the Slate 7 and the Flint 3 in this regard. I have my WireGuard VPN up and running as intended, but OpenVPN will not connect. It continually fails and timesout.
Port Forwarding is correct to port 1194 and my WireGuard is connecting fine on port 51820. Also, I have an non-DCO OpenVPN Server which runs on my Synology NAS at port 1195 an it works fine as well.
Just looking for any ideas of what could be the issue? Subnet for both the Synology and the Flint 3 are 10.8.0.0, but the Synoloy VPN will be retired once I get the GL.Inet OpenVPN-DCO running.
Please try to connect to the OpenVPN server on your phone to see if it works.
Here for reference to build the server and client connection:
I think you can swap another subnet for Flint3. And will check for DCO compatibility between the client and the server before they connecting, and will only enbale DCO if both parties support this.
I checked with DCO enabled and disabled and still couldn't get it to connect. Server Poll Timeout is what it continues to fail on. The Port Forwarding is all correct as well. Works for everything else but this.
Also, fails from my phone and work computer while Wireguard works on both. I plan to use WireGuard but helps to have the other option operable as well if ever needed.
Also, I fit scenario 2 and had set it up that way.
It seems that the client's requested connection cannot reach the server, which is talking about OpenVPN.
Please check the port forwarding rule in modem, whether TCP and UDP are allowed, and switch the OpenVPN server protocol to TCP or UDP in Flint3, and test it again.
If no luck, are you willing to share Flint3 with us through GoodCloud? we would like to remote to further check the Flint3 server.
Please let me know the router MAC and Web UI password in PM.
I've tried it with being set as UDP only and Both (TCP & UDP), and still no connection is made. The Port Forwarding Rule exists on Router 1 (Verizon FiOS G3100) and is set as follows
I even put the IP address of the Flint3 (which is static: 192.168.1.250) in the DMZ, and still no connection on Port 1194. However, all other services and port forwarding are fine. I even tried using a different port for the sake of it, and still nothing.
I live in a basement apartment. The internet is FREE for me as part of my lease, but it is the landlord's internet, and the router is upstairs, of which I have no direct access (though I do have the admin login and manage it).
When I first move here, I convinced her to upgrade to 1 GB internet, and will soon try and convince her to get 2.5 GB, and I've helped her with her tech, networking, etc. Since it is Verizon FiOS, I have MOCA devices here in the basement and get my direct internet connections via COAX and have created my own network (wifi, wired, etc.), using the Flint 3 as a replacement for a Netgear Access Point.
I travel a bit for work and became interested in the Slate 7 as a travel router, got that, and then started to explore opportunities for hosting my own VPN server from my home for when I'm traveling. That is how I stumbled across the Flint 3.
Okay. Sounds like you have a good working relationship with your landlord. I have Verizon Fios 1 GIG. I would say the 2 GIG service is overkill unless you're a video editor.
I think Tailscale, ZeroTier and AstroWarp are designed for your situation. Haven't tried them, so I can't really comment. I host a WireGuard server on my Flint3 and use my Beryl AX when I travel. Good luck with your setup.
I'm using Tailscale and that is fine. What I'm trying to do is setup VPN for when I'm traveling. Wireguard VPN is working fine. However, OpenVPN is not. I want to understand why it is not. That is the reason for the post. Everything else seems ok
If DMZ is enabled, neither WG nor OVPN can connect, I will submit this issue to R&D, I think it is the DMZ feature issue, it affects the port of the router local services (192.168.8.1).
If you must need to enable DMZ, you need to configure it as follows, adding new port forwarding rules, in order to make the router local services (192.168.8.1) occupy port 1194 and 51820, and set the DMZ level to the lowest.
The DMZ setting needed to be set up lowest priority
Port forward rule needed to be set. I modified to only use UDP and that worked fine.
The only port/service that had issue was OpenVPN on port 1194 on the Flint 3. Wireguard connected fine. Further, I have another OpenVPN server (non-DCO) configured on my NAS at port 1195 and that also connected without issue.
Thanks for your help and I hope my feedback helps.
Sorry, is there issue with the OpenVPN server?
I tested it again yesterday after I configured it, and it seems that my router (Ovpn client) is available to connect to it.
No. Your change, making DMZ Priority Lowest and doing Port Forward worked. What I'm saying is that the ONLY service that didn't work prior to that was OpenVPN. WireGuard didn't have any issues connecting. Nor, did the OpenVPN Server I serve on Port 1195 on my NAS. Only OpenVPN on the Flint 3 on Port 1194 didn't work until we did that.
Sorry, I would like to confirm one point, the WireGuard connection tested in my router, and it does not work if I did not add the port forwarding rules and DMZ priority lowest.
Could I check it with your Flint3 WG server again, in the GoodCloud remote?
I'd have to turn Good Cloud back on. I only opened the ticket because OpenVPN wasn't connecting. Everything else was fine and I didn't have port forwarding at all, but priority lowest wasn't set.
What I notice now, is that MLO isn't stable and I lose connection a fair amount when connected to MLO.
I remember that I tested the OVPN client on my router after setting up port forwarding (1194) + DMZ lowest on your Flint3, and no problem.
But the OVPN profile has been deleted and I cannot verify it again.
If you have shared Flint3 to me, I will verify the connection problem with OpenVPN server again.
If you have set up port forwarding (1194) + DMZ lowest and there is no problem with the connection of OVPN server, this is workaround solution, the issue has been submitted to R&D for inspection and repair.
