Nordvpn connects then internet stops

Hi - I am in Pakistan. I have a internet connections and wifi router

I have connected my axt1800 to the other wifi router via ethernet. Internet is available through the axt.
However when i enable my nordvpn to show United Kingdom through the VPN Dashboard - it shows as connected on the dashboard but then the wifi connection status changes to “connected without internet”. When i stop the VPN from dashboard - internet returns but with the local ip.

It has worked at another location in Pakistan and i had no issues with the VPN.

is there some type of blocking going on? I have NordVPN installed on my mobile and laptop and it works fine when connected to the same local wifi router. But its when i activate it through the AXT VPN dashboard that i seeing the internet drop.

This is the log- the last line mentions “firewall”:

Mon Mar 20 08:38:48 2023 daemon.info avahi-daemon[3704]: Registering new address record for 10.8.0.4 on ovpnclient.IPv4.
Mon Mar 20 08:38:48 2023 daemon.notice ovpnclient[9725]: /etc/openvpn/scripts/ovpnclient-up ovpnclient 0 ovpnclient 1500 1585 10.8.0.4 255.255.255.0 init
Mon Mar 20 08:38:48 2023 user.notice ovpnclient-up: env value:route_vpn_gateway=10.8.0.1 daemon_log_redirect=0 script_type=up proto_1=udp daemon=0 SHLVL=1 foreign_option_1=dhcp-option DNS 103.86.96.100 dev_type=tun foreign_option_2=dhcp-option DNS 103.86.99.100 remote_1=194.35.233.202 dev=ovpnclient X509_0_CN=uk1789.nordvpn.com remote_port_1=1194 X509_1_CN=NordVPN CA8 X509_2_CN=NordVPN Root CA X509_2_C=PA ifconfig_netmask=255.255.255.0 tls_digest_sha256_0=7a:7c:90:16:db:8c:a2:30:b6:af:cb:56:a7:d8:94:9e:32:87:07:0e:71:d1:ae:8c:2c:23:27:89:01:d5:59:49 daemon_start_time=1679301524 script_context=init ifconfig_local=10.8.0.4 common_name=uk1789.nordvpn.com tls_digest_sha256_1=55:e7:2d:68:c3:fb:82:f0:b3:0b:65:ec:91:46:47:33:02:c6:df:13:15:6d:46:7e:44:a5:7a:d0:20:e2:fb:e0 tls_digest_sha256_2=8b:5a:49:5d:b4:98:a6:c2:c8:ca:7a:f6:ae:4a:5c:df:65:e6:89:d0:6c:be:cc:b0:24:53:c9:1c:31:91:e2:ff verb=3 link_mtu=1585 trusted_ip=194.35.233.202 tls_serial_hex_0=1d:46:c5:2c:c9:9f:65:e4:b7:55:7b:d7:53:98:60:7a:b1:b7:48:5d X509_1_O=NordVPN tun_mtu
Mon Mar 20 08:38:48 2023 daemon.notice netifd: ovpnclient (9725): udhcpc: started, v1.33.2
Mon Mar 20 08:38:48 2023 daemon.notice netifd: ovpnclient (9725): udhcpc: sending discover
Mon Mar 20 08:38:51 2023 daemon.notice netifd: ovpnclient (9725): udhcpc: no lease, failing
Mon Mar 20 08:38:51 2023 daemon.info avahi-daemon[3704]: Interface ovpnclient.IPv4 no longer relevant for mDNS.
Mon Mar 20 08:38:51 2023 daemon.info avahi-daemon[3704]: Leaving mDNS multicast group on interface ovpnclient.IPv4 with address 10.8.0.4.
Mon Mar 20 08:38:51 2023 daemon.info avahi-daemon[3704]: Withdrawing address record for 10.8.0.4 on ovpnclient.
Mon Mar 20 08:38:51 2023 daemon.info avahi-daemon[3704]: Joining mDNS multicast group on interface ovpnclient.IPv4 with address 10.8.0.4.
Mon Mar 20 08:38:51 2023 daemon.info avahi-daemon[3704]: New relevant interface ovpnclient.IPv4 for mDNS.
Mon Mar 20 08:38:51 2023 daemon.info avahi-daemon[3704]: Registering new address record for 10.8.0.4 on ovpnclient.IPv4.
Mon Mar 20 08:38:51 2023 daemon.notice netifd: Interface ‘ovpnclient’ is now up
Mon Mar 20 08:38:51 2023 daemon.notice netifd: Network device ‘ovpnclient’ link is up
Mon Mar 20 08:38:51 2023 kern.info kernel: [ 8533.835794] IPv6: ADDRCONF(NETDEV_UP): ovpnclient: link is not ready
Mon Mar 20 08:38:52 2023 user.notice mwan3[10426]: Execute ifup event on interface ovpnclient (ovpnclient)
Mon Mar 20 08:38:52 2023 user.notice mwan3[10426]: Starting tracker on interface ovpnclient (ovpnclient)
Mon Mar 20 08:38:53 2023 daemon.warn ovpnclient[9725]: WARNING: this configuration may cache passwords in memory – use the auth-nocache option to prevent this
Mon Mar 20 08:38:53 2023 daemon.notice ovpnclient[9725]: Initialization Sequence Completed
Mon Mar 20 08:38:54 2023 user.notice firewall: Reloading firewall due to ifup of ovpnclient (ovpnclient)

Hope someone can help with this. Thank you

What is your firmware?

The newly released 4.2.0 has a bug if you upgrade from old firmware. Just reset your firmware and configure again.