2 Issues:
- ProtonVpn (free tier) generates an error message in the interface when using udp (no issue with tcp). You cannot disconnect the vpn or change to another one. Pic attached. Despite that it seems the vpn is working. Rebooting does nothing.
multiple vpn in the same group (tcp and udp):
only one ovpn in the group (udp):
log details:
Wed May 18 16:00:58 2022 daemon.notice ovpnclient[28710]: TUN/TAP device ovpnclient opened
Wed May 18 16:00:58 2022 daemon.notice ovpnclient[28710]: net_iface_mtu_set: mtu 1500 for ovpnclient
Wed May 18 16:00:58 2022 daemon.notice ovpnclient[28710]: net_iface_up: set ovpnclient up
Wed May 18 16:00:58 2022 daemon.notice ovpnclient[28710]: net_addr_v4_add: 10.17.0.10/16 dev ovpnclient
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: Joining mDNS multicast group on interface ovpnclient.IPv4 with address 10.17.0.10.
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: New relevant interface ovpnclient.IPv4 for mDNS.
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: Registering new address record for 10.17.0.10 on ovpnclient.IPv4.
Wed May 18 16:00:58 2022 daemon.notice ovpnclient[28710]: /etc/openvpn/scripts/ovpnclient-up ovpnclient 0 ovpnclient 1500 1584 10.17.0.10 255.255.0.0 init
Wed May 18 16:00:58 2022 user.notice ovpnclient-up: env value:route_vpn_gateway=10.17.0.1 daemon_log_redirect=0 script_type=up proto_1=udp CLIENT_CERT=0 daemon=0 proto_2=udp SHLVL=1 foreign_option_1=dhcp-option DNS 10.17.0.1 proto_3=udp dev_type=tun remote_1=185.177.125.196 proto_4=udp dev=ovpnclient remote_2=185.177.125.196 proto_5=udp X509_0_CN=node-nl-114.protonvpn.net remote_port_1=4569 remote_3=185.177.125.196 proto_6=udp X509_1_CN=ProtonVPN Intermediate CA 1 X509_1_C=CH remote_port_2=443 remote_4=185.177.125.196 proto_7=udp X509_2_CN=ProtonVPN Root CA X509_2_C=CH remote_port_3=1194 remote_5=185.177.125.196 proto_8=udp remote_port_4=80 remote_6=185.177.125.196 proto_9=udp ifconfig_netmask=255.255.0.0 remote_port_5=80 remote_7=185.177.125.196 proto_10=udp tls_... (removed for security)
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: Interface ovpnclient.IPv4 no longer relevant for mDNS.
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: Leaving mDNS multicast group on interface ovpnclient.IPv4 with address 10.17.0.10.
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: Withdrawing address record for 10.17.0.10 on ovpnclient.
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: Joining mDNS multicast group on interface ovpnclient.IPv4 with address 10.17.0.10.
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: New relevant interface ovpnclient.IPv4 for mDNS.
Wed May 18 16:00:58 2022 daemon.info avahi-daemon[4160]: Registering new address record for 10.17.0.10 on ovpnclient.IPv4.
Wed May 18 16:00:59 2022 daemon.notice netifd: Interface 'ovpnclient' is now up
Wed May 18 16:00:59 2022 daemon.notice netifd: Network device 'ovpnclient' link is up
Wed May 18 16:00:59 2022 user.notice firewall: Reloading firewall due to ifup of ovpnclient (ovpnclient)
Wed May 18 16:01:01 2022 daemon.warn ovpnclient[28710]: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed May 18 16:01:01 2022 daemon.notice ovpnclient[28710]: Initialization Sequence Completed
- Resetting firmware: After resetting to factory settings, once the vpn configuration errors were still there. So either you clean manually the config files connecting to the router or you flash the firmware again without keeping settings. This has happen only once, cannot replicate again.