Using MT300N-v2 wirelessly with VPN

grazie · 2017-12-16T17:54:58.000Z

I got this device as a platform for my VPN which is Torguard. However, Torguard customer support state this device won’t support a VPN client when using a wireless connection. Is this correct? If so, it seems to defeat the whole suppose of this product.

alpha1974 · 2017-12-16T20:38:42.000Z

I am not using Torguard but my own OpenVPN Server… Of course you can use MT300n-V2 for wireless VPN connections. The device connects to the foreign wifi net and establishes a vpn connection to my VPN server. All traffic coming from/to the wifi clients (that are connected to MT300N-V2´s own wifi) will be routed through the vpn tunnel.

grazie · 2017-12-16T20:56:24.000Z

Thanks alpha, it did seem to me like what this product was designed to do.

What can I do to troubleshoot my problem? I can make an IP connection with the Torguard VPN enabled, but I can’t get any data transfer. Any links I could follow?

alpha1974 · 2017-12-17T03:12:56.000Z

I am not familiar with Torguard VPN. On their website they mention a “OpenVPN config generator”. Have you tried to generate an ovpn-config file that can be uploaded to the MT300N-V2 via the device´s webgui?

BTW: I found that the option “Force VPN (No Internet if VPN is not connected)” has some problems in my individual config, e.g. no data transfer to some local subnets. Without this option everything works fine.

alzhao · 2017-12-19T13:28:01.000Z

@alpha1974, the “Force VPN” option will disable access to local subnets.

@grazie, I don’t think there is a problem of using vpn on wireless. If you cannot access the Internet, maybe it is because of DNS. Can you set up custom DNS and try again?

grazie · 2017-12-19T22:54:12.000Z

Thanks again, alpha. TorGuard provide both TCP and UDP config files, so haven’t tried to generate my own.

However. if I don’t enable"Force VPN" I too get connection without problems. So this seems to be what this issue was for me and no doubt many others. Thanks for the suggestion of using a custom DNS, alzhao, but I don’t know what settings to use. I also get the message “please setup custom DNS to prevent DNS leaks”. This is using an ADSL internet connection with an ADSL router/modem.

I also wanted to use this Gli mini router with VPN enabled in combination with a 4G/LTE modem with wifi hotspot when travelling (Alcatel Osprey which has no ethernet). Should a VPN still work using this type internet connection? If not, what would be needed to make a VPN work on the mini router or would I need a different 4G device?

EDIT : The 4G connection works fine too with the “Force VPN” disabled, so ignore the last paragraph.

alzhao · 2017-12-21T18:01:33.000Z

To set up custom DNS, just click when it shows to you and set up a public DNS server. You can use google or other up to you.

Google DNS: 8.8.8.8 and 8.8.4.4

grazie · 2017-12-22T01:29:36.000Z

Thanks alzhao, that’s great.

Anyone have any ideas on why TorGuard believe this device can’t provide a VPN service when connected wirelessly? Or are they relying on the “Force VPN” flag for the VPN to work securely?

grazie · 2017-12-27T05:03:55.000Z

Had this working for 3 days without problems. However, I then disconnected and couldn’t reconnect. I haven’t been able to do so for the last 2 days. Will the log file(s) show when it worked OK and what the problem now is? If so, how do I look at them?

alzhao · 2017-12-29T11:47:23.000Z

What is the log shown in openvpn page?

grazie · 2017-12-29T20:14:24.000Z

I only know how to capture the log file with screen shots. The 4 images attached show the messages, although they may not be in the correct sequence.

grazie · 2018-01-05T22:27:16.000Z

This is what I get in the syslog when trying to make a connection.

Fri Jan 5 14:00:51 2018 daemon.err openvpn[2154]: RESOLVE: Cannot resolve host address: lon.uk.torguardvpnaccess.com:1912 (Try again)
Fri Jan 5 14:00:56 2018 daemon.err openvpn[2154]: RESOLVE: Cannot resolve host address: lon.uk.torguardvpnaccess.com:1912 (Try again)
Fri Jan 5 14:00:56 2018 daemon.warn openvpn[2154]: Could not determine IPv4/IPv6 protocol
Fri Jan 5 14:00:56 2018 daemon.notice openvpn[2154]: SIGUSR1[soft,init_instance] received, process restarting
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'lan' is now down
Fri Jan 5 14:00:57 2018 daemon.info odhcpd[1144]: Raising SIGUSR1 due to address change on br-lan
Fri Jan 5 14:00:57 2018 daemon.info odhcpd[1144]: Raising SIGUSR1 due to address change on br-lan
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'lan' is disabled
Fri Jan 5 14:00:57 2018 daemon.notice netifd: VLAN 'eth0.1' link is down
Fri Jan 5 14:00:57 2018 daemon.notice netifd: bridge 'br-lan' link is down
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'lan' has link connectivity loss
Fri Jan 5 14:00:57 2018 daemon.info dnsmasq[4644]: read /etc/hosts - 4 addresses
Fri Jan 5 14:00:57 2018 daemon.info dnsmasq[4644]: read /tmp/hosts/odhcpd - 0 addresses
Fri Jan 5 14:00:57 2018 daemon.info dnsmasq[4644]: read /tmp/hosts/dhcp.cfg02411c - 5 addresses
Fri Jan 5 14:00:57 2018 daemon.info dnsmasq-dhcp[4644]: read /etc/ethers - 0 addresses
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'loopback' is now down
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'loopback' is disabled
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Network device 'lo' link is down
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'loopback' has link connectivity loss
Fri Jan 5 14:00:57 2018 daemon.notice netifd: wan (4578): udhcpc: received SIGTERM
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'wan' is now down
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'wan6' is now down
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'wan' is disabled
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'wan6' is disabled
Fri Jan 5 14:00:57 2018 daemon.notice netifd: VLAN 'eth0.2' link is down
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'wan' has link connectivity loss
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Network device 'eth0' link is down
Fri Jan 5 14:00:57 2018 daemon.notice netifd: wwan (4569): udhcpc: received SIGTERM
Fri Jan 5 14:00:57 2018 daemon.notice netifd: Interface 'wwan' is now down
Fri Jan 5 14:00:58 2018 daemon.notice netifd: Interface 'wwan' is disabled
Fri Jan 5 14:00:58 2018 daemon.notice netifd: Network device 'apcli0' link is down
Fri Jan 5 14:00:58 2018 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Fri Jan 5 14:00:59 2018 user.notice : Added device handler type: 8021ad
Fri Jan 5 14:00:59 2018 user.notice : Added device handler type: 8021q
Fri Jan 5 14:00:59 2018 user.notice : Added device handler type: macvlan
Fri Jan 5 14:00:59 2018 user.notice : Added device handler type: bridge
Fri Jan 5 14:00:59 2018 user.notice : Added device handler type: Network device
Fri Jan 5 14:00:59 2018 user.notice : Added device handler type: tunnel
Fri Jan 5 14:01:00 2018 daemon.notice procd: Segmentation fault
Fri Jan 5 14:01:01 2018 daemon.notice procd: Segmentation fault
Fri Jan 5 14:01:04 2018 user.notice root: drv_ralink_cleanup
Fri Jan 5 14:01:04 2018 daemon.notice netifd: Interface 'lan' is enabled
Fri Jan 5 14:01:04 2018 daemon.notice netifd: Interface 'lan' is setting up now
Fri Jan 5 14:01:04 2018 daemon.notice netifd: Interface 'lan' is now up
Fri Jan 5 14:01:04 2018 daemon.notice netifd: Interface 'loopback' is enabled
Fri Jan 5 14:01:04 2018 daemon.notice netifd: Interface 'loopback' is setting up now
Fri Jan 5 14:01:04 2018 daemon.notice netifd: Interface 'loopback' is now up
Fri Jan 5 14:01:04 2018 daemon.notice netifd: Interface 'wan' is enabled
Fri Jan 5 14:01:04 2018 daemon.notice netifd: Interface 'wan6' is enabled
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'wwan' is enabled
Fri Jan 5 14:01:06 2018 daemon.info odhcpd[1144]: Raising SIGUSR1 due to address change on br-lan
Fri Jan 5 14:01:06 2018 daemon.notice netifd: bridge 'br-lan' link is up
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'lan' has link connectivity
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Network device 'eth0' link is up
Fri Jan 5 14:01:06 2018 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Fri Jan 5 14:01:06 2018 daemon.notice netifd: VLAN 'eth0.1' link is up
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Network device 'lo' link is up
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'loopback' has link connectivity
Fri Jan 5 14:01:06 2018 daemon.notice netifd: VLAN 'eth0.2' link is up
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'wan' has link connectivity
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'wan' is setting up now
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'wan6' has link connectivity
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'wan6' is setting up now
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Network device 'apcli0' link is up
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'wwan' has link connectivity
Fri Jan 5 14:01:06 2018 daemon.notice netifd: Interface 'wwan' is setting up now
Fri Jan 5 14:01:06 2018 daemon.notice odhcpd[1144]: Got DHCPv6 request
Fri Jan 5 14:01:06 2018 daemon.warn odhcpd[1144]: DHCPV6 SOLICIT IA_NA from 0001000121bc500574de2b374040 on br-lan: ok fd42:9de7:d216::9fc/128
Fri Jan 5 14:01:07 2018 daemon.notice netifd: wwan (6392): udhcpc: started, v1.25.1
Fri Jan 5 14:01:07 2018 daemon.notice netifd: wan (6394): udhcpc: started, v1.25.1
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[4644]: exiting on receipt of SIGTERM
Fri Jan 5 14:01:07 2018 daemon.notice netifd: wwan (6392): udhcpc: sending discover
Fri Jan 5 14:01:07 2018 daemon.notice netifd: wan (6394): udhcpc: sending discover
Fri Jan 5 14:01:07 2018 daemon.info odhcpd[1144]: Using a RA lifetime of 0 seconds on br-lan
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: started, version 2.78 cachesize 150
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: DNS service limited to local subnets
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq-dhcp[6463]: DHCP, IP range 192.168.8.100 -- 192.168.8.249, lease time 12h
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using local addresses only for domain test
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using local addresses only for domain onion
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using local addresses only for domain localhost
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using local addresses only for domain local
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using local addresses only for domain invalid
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using local addresses only for domain example.net
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using local addresses only for domain example.org
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using local addresses only for domain example.com
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: using 3 more local addresses
Fri Jan 5 14:01:07 2018 daemon.warn dnsmasq[6463]: no servers found in /tmp/resolv.conf.auto, will retry
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: read /etc/hosts - 4 addresses
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: read /tmp/hosts/odhcpd - 0 addresses
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq[6463]: read /tmp/hosts/dhcp.cfg02411c - 0 addresses
Fri Jan 5 14:01:07 2018 daemon.info dnsmasq-dhcp[6463]: read /etc/ethers - 0 addresses
Fri Jan 5 14:01:08 2018 daemon.info odhcpd[1144]: Using a RA lifetime of 0 seconds on br-lan
Fri Jan 5 14:01:08 2018 daemon.info dnsmasq-dhcp[6463]: DHCPREQUEST(br-lan) 192.168.8.137 b4:b5:2f:89:6e:b6
Fri Jan 5 14:01:08 2018 daemon.info dnsmasq-dhcp[6463]: DHCPACK(br-lan) 192.168.8.137 b4:b5:2f:89:6e:b6 w7pro-4340s
Fri Jan 5 14:01:08 2018 daemon.notice odhcpd[1144]: Got DHCPv6 request
Fri Jan 5 14:01:08 2018 daemon.warn odhcpd[1144]: DHCPV6 REQUEST IA_NA from 0001000121bc500574de2b374040 on br-lan: ok fd42:9de7:d216::9fc/128
Fri Jan 5 14:01:08 2018 daemon.info dnsmasq[6463]: read /etc/hosts - 4 addresses
Fri Jan 5 14:01:08 2018 daemon.info dnsmasq[6463]: read /tmp/hosts/odhcpd - 1 addresses
Fri Jan 5 14:01:08 2018 daemon.info dnsmasq[6463]: read /tmp/hosts/dhcp.cfg02411c - 1 addresses
Fri Jan 5 14:01:08 2018 daemon.info dnsmasq-dhcp[6463]: read /etc/ethers - 0 addresses
Fri Jan 5 14:01:10 2018 daemon.notice netifd: wwan (6392): udhcpc: sending discover
Fri Jan 5 14:01:10 2018 daemon.notice netifd: wan (6394): udhcpc: sending discover
Fri Jan 5 14:01:12 2018 daemon.info odhcpd[1144]: Using a RA lifetime of 0 seconds on br-lan
Fri Jan 5 14:01:12 2018 daemon.info dnsmasq-dhcp[6463]: DHCPINFORM(br-lan) 192.168.8.137 b4:b5:2f:89:6e:b6
Fri Jan 5 14:01:12 2018 daemon.info dnsmasq-dhcp[6463]: DHCPACK(br-lan) 192.168.8.137 b4:b5:2f:89:6e:b6 w7pro-4340s

alzhao · 2018-01-06T13:26:05.000Z

The first log: RESOLVE: Cannot resolve host address: lon.uk.torguardvpnaccess.com:1912 (Try again)

is the reason. It cannot find out the server.

Have you set up an internal DNS server?

grazie · 2018-01-06T17:28:12.000Z

Yes, I used the Google DNS addresses as suggested above.

It only fails to connect when the link between my mini router and my main router is wireless. TorGuard claim this will never work, but you say it will. It did appear to work wirelessly for a number of days when “Force VPN” was disabled, but not been able to get it to work again for nearly 2 weeks now.

alzhao · 2018-01-08T18:25:39.000Z

can you change lon.uk.torguardvpnaccess.com to 5.133.176.8 and try again? After this there will no DNS problem.

grazie · 2018-01-09T01:50:36.000Z

I edited the .ovpn file making the change you suggested. I’ve never done this before, so don’t know if this is valid.

Changing domain name to the IP address gives no connection (disconnecting the ethernet cable between the 2 routers and connecting them wirelessly). It again failed to connect, so I checked IP address for that domain name and noticed it had changed to 88.202.183.62. Tried again with this new IP address, but still no connection. On reconnecting the ethernet cable I get connection without problems using the IP address.

Mon Jan  8 21:57:14 2018 daemon.info procd: - init complete -
Mon Jan  8 21:57:18 2018 daemon.notice openvpn[2183]: TCP/UDP: Preserving recently used remote address: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:18 2018 daemon.notice openvpn[2183]: UDP link local: (not bound)
Mon Jan  8 21:57:18 2018 daemon.notice openvpn[2183]: UDP link remote: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:18 2018 daemon.err openvpn[2183]: write UDP: Network unreachable (code=128)
Mon Jan  8 21:57:18 2018 daemon.notice openvpn[2183]: Network unreachable, restarting
Mon Jan  8 21:57:18 2018 daemon.notice openvpn[2183]: SIGUSR1[soft,network-unreachable] received, process restarting
Mon Jan  8 21:57:22 2018 daemon.info dnsmasq-dhcp[2059]: DHCPDISCOVER(br-lan) 08:eb:74:f2:07:50
Mon Jan  8 21:57:22 2018 daemon.info dnsmasq-dhcp[2059]: DHCPOFFER(br-lan) 192.168.8.216 08:eb:74:f2:07:50
Mon Jan  8 21:57:22 2018 daemon.info dnsmasq-dhcp[2059]: DHCPREQUEST(br-lan) 192.168.8.216 08:eb:74:f2:07:50
Mon Jan  8 21:57:22 2018 daemon.info dnsmasq-dhcp[2059]: DHCPACK(br-lan) 192.168.8.216 08:eb:74:f2:07:50
Mon Jan  8 21:57:23 2018 daemon.notice openvpn[2183]: TCP/UDP: Preserving recently used remote address: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:23 2018 daemon.notice openvpn[2183]: UDP link local: (not bound)
Mon Jan  8 21:57:23 2018 daemon.notice openvpn[2183]: UDP link remote: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:23 2018 daemon.err openvpn[2183]: write UDP: Network unreachable (code=128)
Mon Jan  8 21:57:23 2018 daemon.notice openvpn[2183]: Network unreachable, restarting
Mon Jan  8 21:57:23 2018 daemon.notice openvpn[2183]: SIGUSR1[soft,network-unreachable] received, process restarting
Mon Jan  8 21:57:28 2018 daemon.notice openvpn[2183]: TCP/UDP: Preserving recently used remote address: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:28 2018 daemon.notice openvpn[2183]: UDP link local: (not bound)
Mon Jan  8 21:57:28 2018 daemon.notice openvpn[2183]: UDP link remote: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:28 2018 daemon.err openvpn[2183]: write UDP: Network unreachable (code=128)
Mon Jan  8 21:57:28 2018 daemon.notice openvpn[2183]: Network unreachable, restarting
Mon Jan  8 21:57:28 2018 daemon.notice openvpn[2183]: SIGUSR1[soft,network-unreachable] received, process restarting
Mon Jan  8 21:57:33 2018 daemon.notice openvpn[2183]: TCP/UDP: Preserving recently used remote address: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:33 2018 daemon.notice openvpn[2183]: UDP link local: (not bound)
Mon Jan  8 21:57:33 2018 daemon.notice openvpn[2183]: UDP link remote: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:33 2018 daemon.err openvpn[2183]: write UDP: Network unreachable (code=128)
Mon Jan  8 21:57:33 2018 daemon.notice openvpn[2183]: Network unreachable, restarting
Mon Jan  8 21:57:33 2018 daemon.notice openvpn[2183]: SIGUSR1[soft,network-unreachable] received, process restarting
Mon Jan  8 21:57:43 2018 daemon.notice openvpn[2183]: TCP/UDP: Preserving recently used remote address: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:43 2018 daemon.notice openvpn[2183]: UDP link local: (not bound)
Mon Jan  8 21:57:43 2018 daemon.notice openvpn[2183]: UDP link remote: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:57:43 2018 daemon.err openvpn[2183]: write UDP: Network unreachable (code=128)
Mon Jan  8 21:57:43 2018 daemon.notice openvpn[2183]: Network unreachable, restarting
Mon Jan  8 21:57:43 2018 daemon.notice openvpn[2183]: SIGUSR1[soft,network-unreachable] received, process restarting
Mon Jan  8 21:58:03 2018 daemon.notice openvpn[2183]: TCP/UDP: Preserving recently used remote address: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:58:03 2018 daemon.notice openvpn[2183]: UDP link local: (not bound)
Mon Jan  8 21:58:03 2018 daemon.notice openvpn[2183]: UDP link remote: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:58:03 2018 daemon.err openvpn[2183]: write UDP: Network unreachable (code=128)
Mon Jan  8 21:58:03 2018 daemon.notice openvpn[2183]: Network unreachable, restarting
Mon Jan  8 21:58:03 2018 daemon.notice openvpn[2183]: SIGUSR1[soft,network-unreachable] received, process restarting
Mon Jan  8 21:58:41 2018 daemon.info dnsmasq-dhcp[2059]: DHCPREQUEST(br-lan) 192.168.8.190 74:de:2b:37:40:40
Mon Jan  8 21:58:41 2018 daemon.info dnsmasq-dhcp[2059]: DHCPACK(br-lan) 192.168.8.190 74:de:2b:37:40:40 w7pro-4340s
Mon Jan  8 21:58:41 2018 daemon.info odhcpd[1145]: Using a RA lifetime of 0 seconds on br-lan
Mon Jan  8 21:58:41 2018 daemon.notice odhcpd[1145]: Got DHCPv6 request
Mon Jan  8 21:58:41 2018 daemon.warn odhcpd[1145]: DHCPV6 SOLICIT IA_NA from 0001000121bc500574de2b374040 on br-lan: ok fd42:9de7:d216::9fc/128
Mon Jan  8 21:58:42 2018 daemon.notice odhcpd[1145]: Got DHCPv6 request
Mon Jan  8 21:58:42 2018 daemon.warn odhcpd[1145]: DHCPV6 SOLICIT IA_NA from 0001000121bc500574de2b374040 on br-lan: ok fd42:9de7:d216::9fc/128
Mon Jan  8 21:58:43 2018 daemon.notice openvpn[2183]: TCP/UDP: Preserving recently used remote address: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:58:43 2018 daemon.notice openvpn[2183]: UDP link local: (not bound)
Mon Jan  8 21:58:43 2018 daemon.notice openvpn[2183]: UDP link remote: [AF_INET]88.202.183.66:1912
Mon Jan  8 21:58:43 2018 daemon.err openvpn[2183]: write UDP: Network unreachable (code=128)
Mon Jan  8 21:58:43 2018 daemon.notice openvpn[2183]: Network unreachable, restarting
Mon Jan  8 21:58:43 2018 daemon.notice openvpn[2183]: SIGUSR1[soft,network-unreachable] received, process restarting
Mon Jan  8 21:58:44 2018 daemon.info dnsmasq-dhcp[2059]: DHCPINFORM(br-lan) 192.168.8.190 74:de:2b:37:40:40
Mon Jan  8 21:58:44 2018 daemon.info dnsmasq-dhcp[2059]: DHCPACK(br-lan) 192.168.8.190 74:de:2b:37:40:40 w7pro-4340s
Mon Jan  8 21:58:44 2018 daemon.notice odhcpd[1145]: Got DHCPv6 request
Mon Jan  8 21:58:44 2018 daemon.warn odhcpd[1145]: DHCPV6 SOLICIT IA_NA from 0001000121bc500574de2b374040 on br-lan: ok fd42:9de7:d216::9fc/128
Mon Jan  8 21:58:45 2018 daemon.info odhcpd[1145]: Using a RA lifetime of 0 seconds on br-lan
Mon Jan  8 21:58:48 2018 daemon.notice odhcpd[1145]: Got DHCPv6 request
Mon Jan  8 21:58:48 2018 daemon.warn odhcpd[1145]: DHCPV6 SOLICIT IA_NA from 0001000121bc500574de2b374040 on br-lan: ok fd42:9de7:d216::9fc/128
Mon Jan  8 21:58:49 2018 daemon.info odhcpd[1145]: Using a RA lifetime of 0 seconds on br-lan
Mon Jan  8 21:58:56 2018 daemon.notice odhcpd[1145]: Got DHCPv6 request
Mon Jan  8 21:58:56 2018 daemon.warn odhcpd[1145]: DHCPV6 SOLICIT IA_NA from 0001000121bc500574de2b374040 on br-lan: ok fd42:9de7:d216::9fc/128

grazie · 2018-01-26T07:05:43.000Z

Have you no further information on getting my VPN (Torguard) to work with the router wirelessly?

If not, can you at least give a list of VPNs that are known to work wirelessly with this router?

alzhao · 2018-01-29T16:42:14.000Z

Torguard uses Dynamic DNS so you cannot use static IP address.

Can you try Astrill?