What's new
  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Merlin 384.13. My iPhone can't remote access my LAN via OpenVPN. Original ASUS firmware worked fine.

markpaterson

New Around Here
If I can't figure this out, I'll have to roll back to the stock firmware *sad trombone*.

I've exported the ovpn file and added it OpenVPN app on the iPhone and I can connect to the VPN just fine. The router's VPN page says I'm "connected" and the logs on the router show that I'm connected too. However, I just can't access my LAN at all.

I did NOT have this problem with the original ASUS firmware, although I do appreciate that the Merlin version is newer and has some more settings. I've also tried the default Merlin VPN settings too with no luck.

I've searched this forum and found similar questions, but the solutions show screenshots for older firmware with different settings.

My router's LAN address range is 192.168.50.1 to 255, and Subnet Mask 255.255.255.0.

My VPN settings are below…

iRYQvjd.png
Uxiduf8.png
 
First difference I see is you enabled a few OpenVPN 2.4.x features here, which did not exist on Asus's firmware. Double check that your client and server settings are properly matched.
 
I see. What are those 2.4.x features I enabled? I tried the default Merlin settings and had the same issue. After that I rolled back to the original ASUS firmware and it worked fine, but I would like to continue using Merlin. I have the same issue on both my iPhone OpenVPN app and Tunnelblick on my Mac. I'm not aware of a ton of settings on either so I assume I'm using default settings.
 
I see. What are those 2.4.x features I enabled?

Your screenshot shows them with a notice stating that the feature requires OpenVPN 2.4.x.

When changing anything on the server side, you have to also update the configuration on the client side. If your client works with stock firmware, then it means you did not enable LZ4 V2 on the client to match what you configured on the router side, for instance.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top