AC86U VPN issue 386.7.0

joeejo

Occasional Visitor
I have a dedicated IP address with my vpn supplier. When the VPN client is enabled, the router reports the Public IP address in Merlin-Asus v386.5.2, however once I upgrade to 386.7.0 the VPN reports the public IP as "unknown".

Once I downgrade to 386.5.2 and the Public address is reported properly once again leading me to believe the firmware may have an issue.

Attached are screen shots of both firmware versions illustrating the issue. (Part of IP blurred intentionally)

Any advice would be appreciated.
 

Attachments

  • 'ASUS Wireless Router RT-AC86U - OpenVPN Client Settings'386.7 - http.jpg
    'ASUS Wireless Router RT-AC86U - OpenVPN Client Settings'386.7 - http.jpg
    92.9 KB · Views: 65
  • 'ASUS Wireless Router RT-AC86U - OpenVPN Client Settings'386.5.2 - http.jpg
    'ASUS Wireless Router RT-AC86U - OpenVPN Client Settings'386.5.2 - http.jpg
    85.2 KB · Views: 71

eibgrad

Part of the Furniture
Don't really know why that is. 386.7 works fine for me (although mine is a clean upgrade). Might be one of those quirks that sometimes happens w/ a dirty upgrade.

Other than that issue, does the OpenVPN client work as expected? IOW, is this just a cosmetic issue?
 

joeejo

Occasional Visitor
The vpn does work outbound (myip shows correct vpn IP), however, I cannot access my open ports from outside my network when it shows "UNKNOWN" public ip.

Thank you for the response
 

eibgrad

Part of the Furniture
Cannot access open ports over the WAN, or open ports over the VPN tunnel (i.e., VPN provider port forwarding)?

Do these open ports provide access to the router itself, or are they port forwards to other devices on the LAN?

Are you using the VPN Director?
 

joeejo

Occasional Visitor
Cannot access open ports over the WAN, or open ports over the VPN tunnel (i.e., VPN provider port forwarding)?

Do these open ports provide access to the router itself, or are they port forwards to other devices on the LAN?

Are you using the VPN Director?


The ports are open on the vpn tunnel and actually your original post gave me the answer...a clean install of the new firmware resolved the issue completely....

Thank you for your assistance.
 

Latest threads

Sign Up For SNBForums Daily Digest

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