OpenVpn issues Slate AX (GL-AXT1800). DNS issue

defibos · 2022-05-17T09:08:15.093Z

I am having some troubles with the device working as openvpn client, both with 4.0.0 beta4 and 4.0.0 beta8 (latest currently).
I configure openvpn connections to openvpn servers I can use with Flint and my personal laptop. Connection is successful but no internet connection.

Tue May 17 10:14:28 2022 daemon.notice ovpnclient[13191]: net_addr_ptp_v4_add: 10.8.0.126 peer 10.8.0.125 dev ovpnclient
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: Joining mDNS multicast group on interface ovpnclient.IPv4 with address 10.8.0.126.
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: New relevant interface ovpnclient.IPv4 for mDNS.
Tue May 17 10:14:28 2022 daemon.notice ovpnclient[13191]: /etc/openvpn/scripts/ovpnclient-up ovpnclient 0 ovpnclient 1500 1552 10.8.0.126 10.8.0.125 init
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: Registering new address record for 10.8.0.126 on ovpnclient.IPv4.
Tue May 17 10:14:28 2022 user.notice ovpnclient-up: env value:route_vpn_gateway=10.8.0.125 X509_0_emailAddress=me@myhost.mydomain daemon_log_redirect=0 X509_1_emailAddress=me@myhost.mydomain script_type=up proto_1=udp daemon=0 SHLVL=1 foreign_option_1=dhcp-option DNS 8.8.8.8 dev_type=tun route_network_1=10.8.0.1 remote_... (removed for security)
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: Interface ovpnclient.IPv4 no longer relevant for mDNS.
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: Leaving mDNS multicast group on interface ovpnclient.IPv4 with address 10.8.0.126.
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: Withdrawing address record for 10.8.0.126 on ovpnclient.
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: Joining mDNS multicast group on interface ovpnclient.IPv4 with address 10.8.0.126.
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: New relevant interface ovpnclient.IPv4 for mDNS.
Tue May 17 10:14:28 2022 daemon.info avahi-daemon[3788]: Registering new address record for 10.8.0.126 on ovpnclient.IPv4.
Tue May 17 10:14:28 2022 daemon.notice netifd: Interface 'ovpnclient' is now up
Tue May 17 10:14:28 2022 daemon.notice netifd: Network device 'ovpnclient' link is up
Tue May 17 10:14:28 2022 kern.info kernel: [ 1579.968114] IPv6: ADDRCONF(NETDEV_UP): ovpnclient: link is not ready
Tue May 17 10:14:28 2022 daemon.notice netifd: ovpnclient (13191): route: SIOCDELRT: No such process
Tue May 17 10:14:28 2022 daemon.notice netifd: ovpnclient (13191): route: SIOCDELRT: No such process
Tue May 17 10:14:29 2022 user.notice firewall: Reloading firewall due to ifup of ovpnclient (ovpnclient)
Tue May 17 10:14:30 2022 daemon.warn ovpnclient[13191]: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Tue May 17 10:14:30 2022 daemon.notice ovpnclient[13191]: Initialization Sequence Completed

defibos · 2022-05-17T17:12:38.117Z

Ok, it seems simply a DNS issue. I have to select manually the DNS servers or activate AdGuard Home to have the openvpn client working as expected.

The issue appears with the device working as openvpn client, AdGuard turned off and DNS Server Settings set to Automatic.
Is anyone having the same issue?

alzhao · 2022-05-18T07:24:02.023Z

defibos:

Tue May 17 10:14:28 2022 daemon.notice netifd: ovpnclient (13191): route: SIOCDELRT: No such process

This seems an error in routing setup.

Did you install Avahi-daemon manually?

defibos · 2022-05-18T09:01:03.571Z

Hi, I did not install/modify anything before the test (I restored to factory settings to be sure).
The openvpn servers are 1) a Mango I own in another country 2) a paid openvpn provider with servers in EU/US/Asia. Both of them working ok with Flint and a pc client.
I can provide any log/detail to narrow down the problem.
Not sure if I am the unique beta tester with that issue, or perhaps they enabled AdGuard and they did not find the issue. To replicate the issue default dns config must be present (AdGuard off and DNS to automatic).

defibos · 2022-06-07T12:58:12.749Z

Issue solved in firmware 4.0.0 (release3), first stable release.