What's new

'Cosmetic' OpenVPN client bug: VPN's public IP not updated after changing VPN server (in 384.19 / 386.1)

  • 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!

Intrepid2007

Regular Contributor
I noticed this 'issue' when I changed the VPN server.. It's not a 'game-stopper' but I thought it is still worth mentioning.

When an active VPN client connection is stopped, the VPN server address is changed and the connection is started again, the VPN's public IP address is not updated.


The detected public IP-address doesn't change in these screens:

In the OpenVPN client settings:
1606562635596.png


In the OpenVPN client overview screen:
1606562681064.png



What did I do to reproduce this?

1. Stopping the active VPN connection by switching the 'Service state' to OFF
2. Change the VPN server address (other server)
3. Starting the active VPN connection by switching the 'Service state' to ON

When the VPN connection is established, the public IP address remains the same.
Only after a reboot of the router, the correct public IP address is shown finally.

I noticed this in both firmware versions 384.19 and 386.1 alpha 2.

I remember that in older firmware versions this worked correctly...
 

Attachments

  • 1606562447143.png
    1606562447143.png
    41.6 KB · Views: 166
Last edited:
Same issue for me on 384.19 on the 86U... it's been like that for a while, and don't trust the output. I typically just head over to https://www.iplocation.net/ to see what I am and where I'm at.
 
What does the following command returns?

Code:
/usr/sbin/ministun -t 5000 -c 1 -i tun11 stun.l.google.com:19302

(replace tun11 by tun12, 13, 14 or 15 if you are not using VPN CLient 1).
 
This is the reply (this IP should be shown in GUI instead of the one shown in the screenshots):

--------------
xxxxxx@RT-AX88U-B230:/tmp/home/root# /usr/sbin/ministun -t 5000 -c 1 -i tun11 stun.l.google.com:19302

45.86.200.29

xxxxxx@RT-AX88U-B230:/tmp/home/root#
--------------

What does the following command returns?

Code:
/usr/sbin/ministun -t 5000 -c 1 -i tun11 stun.l.google.com:19302

(replace tun11 by tun12, 13, 14 or 15 if you are not using VPN CLient 1).
 
This is the reply (IP is correct, should be shown in GUI):

--------------
xxxxxx@RT-AX88U-B230:/tmp/home/root# /usr/sbin/ministun -t 5000 -c 1 -i tun11
stun.l.google.com:19302

45.86.200.29

xxxxxx@RT-AX88U-B230:/tmp/home/root#
--------------

Thanks, might be that the nvram content doesn't always get refreshed after a disconnect/reconnect then.
 

Similar threads

Sign Up For SNBForums Daily Digest

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