What's new

VPN connected but ip address not changing

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

pojang

New Around Here
hi.

i have this problem since i update to 386.3 firmware. the vpn is connected, but the ip address still same as before it connected to vpn. hope anyone can help me here. im using asus AC86U router.below is the log that i copy.


Aug 9 16:37:15 ovpn-client1[4981]: WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Aug 9 16:37:15 ovpn-client1[4981]: OpenVPN 2.5.3 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Aug 6 2021
Aug 9 16:37:15 ovpn-client1[4981]: library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.08
Aug 9 16:37:15 ovpn-client1[4982]: WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
Aug 9 16:37:15 ovpn-client1[4982]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Aug 9 16:37:15 ovpn-client1[4982]: Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Aug 9 16:37:15 ovpn-client1[4982]: Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Aug 9 16:37:16 ovpn-client1[4982]: TCP/UDP: Preserving recently used remote address: [AF_INET]193.56.116.8:1195
Aug 9 16:37:16 ovpn-client1[4982]: Socket Buffers: R=[524288->1048576] S=[524288->1048576]
Aug 9 16:37:16 ovpn-client1[4982]: UDP link local: (not bound)
Aug 9 16:37:16 ovpn-client1[4982]: UDP link remote: [AF_INET]193.56.116.8:1195
Aug 9 16:37:16 ovpn-client1[4982]: TLS: Initial packet from [AF_INET]193.56.116.8:1195, sid=334dc5ac 84b5eca5
Aug 9 16:37:16 ovpn-client1[4982]: VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Aug 9 16:37:16 ovpn-client1[4982]: VERIFY OK: nsCertType=SERVER
Aug 9 16:37:16 ovpn-client1[4982]: VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-6016-0a, emailAddress=support@expressvpn.com
Aug 9 16:37:16 ovpn-client1[4982]: VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-6016-0a, emailAddress=support@expressvpn.com
Aug 9 16:37:16 ovpn-client1[4982]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
Aug 9 16:37:16 ovpn-client1[4982]: [Server-6016-0a] Peer Connection Initiated with [AF_INET]193.56.116.8:1195
Aug 9 16:37:18 ovpn-client1[4982]: SENT CONTROL [Server-6016-0a]: 'PUSH_REQUEST' (status=1)
Aug 9 16:37:18 ovpn-client1[4982]: PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.18.0.1,comp-lzo no,route 10.18.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.18.2.210 10.18.2.209,peer-id 185,cipher AES-256-GCM'
Aug 9 16:37:18 ovpn-client1[4982]: OPTIONS IMPORT: timers and/or timeouts modified
Aug 9 16:37:18 ovpn-client1[4982]: OPTIONS IMPORT: compression parms modified
Aug 9 16:37:18 ovpn-client1[4982]: OPTIONS IMPORT: --ifconfig/up options modified
Aug 9 16:37:18 ovpn-client1[4982]: OPTIONS IMPORT: route options modified
Aug 9 16:37:18 ovpn-client1[4982]: OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Aug 9 16:37:18 ovpn-client1[4982]: OPTIONS IMPORT: peer-id set
Aug 9 16:37:18 ovpn-client1[4982]: OPTIONS IMPORT: adjusting link_mtu to 1629
Aug 9 16:37:18 ovpn-client1[4982]: OPTIONS IMPORT: data channel crypto options modified
Aug 9 16:37:18 ovpn-client1[4982]: Data Channel: using negotiated cipher 'AES-256-GCM'
Aug 9 16:37:18 ovpn-client1[4982]: NCP: overriding user-set keysize with default
Aug 9 16:37:18 ovpn-client1[4982]: Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Aug 9 16:37:18 ovpn-client1[4982]: Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Aug 9 16:37:18 ovpn-client1[4982]: TUN/TAP device tun11 opened
Aug 9 16:37:18 ovpn-client1[4982]: TUN/TAP TX queue length set to 1000
Aug 9 16:37:18 ovpn-client1[4982]: /usr/sbin/ip link set dev tun11 up mtu 1500
Aug 9 16:37:18 ovpn-client1[4982]: /usr/sbin/ip link set dev tun11 up
Aug 9 16:37:18 ovpn-client1[4982]: /usr/sbin/ip addr add dev tun11 local 10.18.2.210 peer 10.18.2.209
Aug 9 16:37:18 ovpn-client1[4982]: ovpn-up 1 client tun11 1500 1557 10.18.2.210 10.18.2.209 init
Aug 9 16:37:18 openvpn-routing: Add pushed route: /usr/sbin/ip route add 10.18.0.1/255.255.255.255 via 10.18.2.209 dev tun11 table ovpnc1
Aug 9 16:37:18 openvpn-routing: Routing all traffic through ovpnc1
Aug 9 16:37:18 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:37:18 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:37:18 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:37:18 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:37:18 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:37:18 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:37:18 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:37:20 ovpn-client1[4982]: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Aug 9 16:37:20 ovpn-client1[4982]: Initialization Sequence Completed
Aug 9 16:40:51 rc_service: httpd 1870:notify_rc stop_vpnclient1
Aug 9 16:40:51 ovpn-client1[4982]: event_wait : Interrupted system call (code=4)
Aug 9 16:40:51 ovpn-client1[4982]: ovpn-route-pre-down tun11 1500 1557 10.18.2.210 10.18.2.209 init
Aug 9 16:40:51 ovpn-client1[4982]: Closing TUN/TAP interface
Aug 9 16:40:51 ovpn-client1[4982]: /usr/sbin/ip addr del dev tun11 local 10.18.2.210 peer 10.18.2.209
Aug 9 16:40:51 ovpn-client1[4982]: ovpn-down 1 client tun11 1500 1557 10.18.2.210 10.18.2.209 init
Aug 9 16:40:51 ovpn-client1[4982]: SIGTERM[hard,] received, process exiting
Aug 9 16:40:51 openvpn-routing: Clearing routing table for VPN client 1
Aug 9 16:40:51 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:40:51 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:40:52 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:40:52 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:40:52 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:40:52 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip
Aug 9 16:40:52 kernel: 10:7B:44:EC:8A:A8 not mesh client, can't update it's ip


1628499746337.png
 
The syslog indicates all is normal. The OpenVPN client is connected.

What are using to verify the public IP? If it's the OpenVPN client webpage, sometimes that can have trouble. What ultimately matters is what's reported by your VPN-bound clients. Try using an P checker site like ipchicken.com, infobyip.com, etc.

Btw, I assume you're NOT using PBR (policy based routing), but just routing *everything* through the VPN.
 
"No internet traffic" means you didn't configure the client to redirect Internet traffic.
 

Similar threads

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