Plusnet blocking Open VPN port 1194 TCP and UDP

[#1]

The VPN server is on a Synology NAS drive (just for the record I have also tried the VPN server on my ASUS router too with the same result that 1194 is blocked)

If I use my VPN client (using a a local IP address) on my LAN then I can connect to my VPN without problems. Outside of my LAN using a DDNS address the connection gets blocked.

[#2]

Is the synology NAS drive connected directly to the router?

With a bit of digging I can see that the port is showing as open but filtered:

PORT     STATE         SERVICE
1194/tcp filtered      openvpn
1194/udp open|filtered openvpn

This matches what would happen if the traffic was hitting your router but being dropped/firewalled/not responded to.

Explanation of the states below:

Open means that an application on the target machine is listening for connections/packets on that port. Filtered means that a firewall, filter, or other network obstacle is blocking the port. Closed ports have no application listening on them, though they could open up at any time.

I could try altering the route your traffic takes across our network, however at this stage, I'm not convinced it's likely to help, when others seem to have successfully achieved what you're trying to.

[#3]

Yes my Synology NAS is directly connected to the router.

As I stated before I can connect to the synology VPN server when the VPN client is on my LAN

I am happy to assist in whatever you want to try as I've never had this persistent issue setting up a VPN before

Moderator's note by Adie (Dvorak): Full quote of preceding post removed as per the forum rules

[#4]

As I stated before I can connect to the synology VPN server when the VPN client is on my LAN

Stab in the dark but have you checked the default gateway on the synology VPN Server?

Dan.

[#5]

Default gateway is set to the LAN address of the router

Moderator's note by Adie (Dvorak): Full quote of preceding post removed as per the forum rules

[#6]

@massive You'll probably have read it but is this any help to you?

https://www.synology.com/en-uk/knowledgebase/SRM/help/VPNCenter/vpn_setup

[#7]

Yes, I know how to set up a VPN on my NAS. (Message 14 says how I am using a workaround on port 443 until this 1194 conundrum is solved) 

Moderator's note by Adie (Dvorak): Full quote of preceding post removed as per the forum rules

[#8]

Only trying to help @massive, I have an RS815+ and it all works for me using these settings.

[#9]

I have practically the same settings (using SHA1 though), I've mentioned before that I've never had problems setting up a VPN on Sky or Virgin previously, been dabbling with VPN's since before 2012 so I know what should settings should be working. Appreciate the advice

Moderator's note by Adie (Dvorak): Full quote of preceding post removed as per the forum rules

[#10]

@massive - You're welcome.

[#11]

@massive, are you using the same dynamic IP address range as @Anonymous?

Edit: in fact, ignore. Bit of a moot question if TCP works.

[#12 · Accepted solution]

@massive, I've altered the routing of your connection. Interested to know if it's made any difference?

[#13]

---

@bobpullen wrote:

@massive, are you using the same dynamic IP address range as @Anonymous?

Edit: in fact, ignore. Bit of a moot question if TCP works.

---

Yes using the same range

[#14]

---

@bobpullen wrote:

@massive, I've altered the routing of your connection. Interested to know if it's made any difference?

---

Thanks Bob, this appears to have sorted the problem, I am now getting access to my VPN on 1194 using UDP.

May I ask what is different about the way my connection is now routed compared to before?

[#15]

@massive, thanks that's good to hear.

I have assigned you a static IP address and routed your connection using L2TP rather than PTA.

To further prove the theory, I'm going to revert the change I made, so we can make sure things break again. This will also allow me to grab some diagnostics that I can forward to our engineers.

Don't worry, if things do break again, I'll quickly reinstate the working routing.