ProtonVPN configuration on RT-AX68U

[Deleted member 48162]

Hello comunity! I've tried to bind my existing Proton VPN Plus onto renewed 388.8_2 ASUS-Merlin firmware. Seems like with new firmware the previous VPN settings manual have become obsolete. 'Service state' toggle is totally missing along with Automatic start at boot time toggle. I suppose that is not a very big difference from the initial procedure, but it is there still. Not to mention that I can't connect from Russia. Am I doing something wrong in terms of VPN-Client settings? And why after enabling VPN-Client -> WireGuard Client -> Enable WireGuard -> toggle 'Yes' the connection continue to indicate as 'Stopped"?

 

[ColinTaylor]

'Service state' toggle is totally missing along with Automatic start at boot time toggle. I suppose that is not a very big difference from the initial procedure, but it is there still.

Those changes are described in the 3004.388.8 changelog.

 

[Deleted member 48162]

Those changes are described in the 3004.388.8 changelog.

I've edited a few lines after original post. And a support ticket have been placed for ProtonVPN support. Results are expected to be placed here as well.

 

[rageykiwi]

The link you mentioned is in regards to OPENVPN the wire guard instructions is here Proton VPN Wireguard I am running GT-ATX11000 Pro which not the same router you are using but i have had no issues with Wireguard on proton VPN the config files generate all the options you need

 

[Deleted member 48162]

The link you mentioned is in regards to OPENVPN the wire guard instructions is here Proton VPN Wireguard I am running GT-ATX11000 Pro which not the same router you are using but i have had no issues with Wireguard on proton VPN the config files generate all the options you need

I could manage to download and configure WireGuard config files. The thing is by switching WireGuard ON indicates it remains in 'STOPPED' state as I mentioned it from the first post. Just to make it clear. These are the settings I've made to VPN - WireGuard Client along with OpenVPN both TCP and UDP - see attachments. I'm a bit confused by WireGuard -> Peer -> Allow IP line. Should I assign my LAN here?

 

[Labdoc]

The link you mentioned is in regards to OPENVPN the wire guard instructions is here Proton VPN Wireguard I am running GT-ATX11000 Pro which not the same router you are using but i have had no issues with Wireguard on proton VPN the config files generate all the options you need

I am considering a Proton VPN (and email) subscription. What firmware are you using on the GT-ATX11000 Pro? Asuswrt-Merlin or stock? Version?

 

[rageykiwi]

I am using 3004.388.8_2 if i was you i would subscribe to Proton vpn and use the free subscription first it doesn't allow you to use p2p or anything like that u will have a limited number of servers

 

[Deleted member 48162]

I am using 3004.388.8_2 if i was you i would subscribe to Proton vpn and use the free subscription first it doesn't allow you to use p2p or anything like that u will have a limited number of servers

You forgot to mention that pre-paid features remove all these limitations. Forwarding back to initial post. Here is part of my syslog:

Aug 20 08:13:19 ovpn-client2[6589]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Aug 20 08:13:19 ovpn-client2[6589]: TCP/UDP: Preserving recently used remote address: [AF_INET]31.13.189.242:7770
Aug 20 08:13:19 ovpn-client2[6589]: Socket Buffers: R=[87380->87380] S=[16384->16384]
Aug 20 08:13:19 ovpn-client2[6589]: Attempting to establish TCP connection with [AF_INET]31.13.189.242:7770
Aug 20 08:13:19 ovpn-client2[6589]: TCP connection established with [AF_INET]31.13.189.242:7770
Aug 20 08:13:19 ovpn-client2[6589]: TCPv4_CLIENT link local: (not bound)
Aug 20 08:13:19 ovpn-client2[6589]: TCPv4_CLIENT link remote: [AF_INET]31.13.189.242:7770
Aug 20 08:13:19 ovpn-client2[6589]: TLS: Initial packet from [AF_INET]31.13.189.242:7770, sid=7f2f650e 7845bbc8
Aug 20 08:13:40 ovpn-client2[6589]: read TCPv4_CLIENT []: Connection timed out (fd=8,code=110)
Aug 20 08:13:40 ovpn-client2[6589]: Connection reset, restarting [0]
Aug 20 08:13:40 ovpn-client2[6589]: SIGUSR1[soft,connection-reset] received, process restarting
Aug 20 08:13:40 ovpn-client2[6589]: Restart pause, 16 second(s)
Aug 20 08:13:56 ovpn-client2[6589]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Aug 20 08:13:56 ovpn-client2[6589]: TCP/UDP: Preserving recently used remote address: [AF_INET]31.13.189.242:7770
Aug 20 08:13:56 ovpn-client2[6589]: Socket Buffers: R=[87380->87380] S=[16384->16384]
Aug 20 08:13:56 ovpn-client2[6589]: Attempting to establish TCP connection with [AF_INET]31.13.189.242:7770
Aug 20 08:13:56 ovpn-client2[6589]: TCP connection established with [AF_INET]31.13.189.242:7770
Aug 20 08:13:56 ovpn-client2[6589]: TCPv4_CLIENT link local: (not bound)
Aug 20 08:13:56 ovpn-client2[6589]: TCPv4_CLIENT link remote: [AF_INET]31.13.189.242:7770
Aug 20 08:13:56 ovpn-client2[6589]: TLS: Initial packet from [AF_INET]31.13.189.242:7770, sid=986a5823 dd53d443
Aug 20 08:14:17 ovpn-client2[6589]: read TCPv4_CLIENT []: Connection timed out (fd=8,code=110)
Aug 20 08:14:17 ovpn-client2[6589]: Connection reset, restarting [0]
Aug 20 08:14:17 ovpn-client2[6589]: SIGUSR1[soft,connection-reset] received, process restarting
Aug 20 08:14:17 ovpn-client2[6589]: Restart pause, 32 second(s)

As can be seen connection is dropped by ISP filter. Is there a way out of such confusion? And WireGuard protocol stll shows 'Stopped' no matter how I toggle it's state - see attachments above. What for 'Allowed IPs' in 'Peer' section of VPN - WireGuard Client purpose anyway?

 

[Deleted member 48162]

Edit to the OP. Suppose I'm affected by 'evil' ISP who eventually filters out all VPN connections due to the existing policy.
This way missing DNS queries will reflect the weak point in connection to be provided.
Is this a log, which shows just that?

Aug 20 23:18:06 rc_service: httpds 1118:notify_rc start_wgc 3
Aug 20 23:18:06 kernel: wireguard: WireGuard 1.0.20220627 loaded. See www.wireguard.com for information.
Aug 20 23:18:06 kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
Aug 20 23:18:06 WireGuard: Starting client 3.
Aug 20 23:18:06 dnsmasq[1928]: read /etc/hosts - 22 names
Aug 20 23:18:06 dnsmasq[1928]: using nameserver 81.91.189.7#53
Aug 20 23:18:06 dnsmasq[1928]: using nameserver 8.8.4.4#53
Aug 20 23:18:06 dnsmasq[1928]: using nameserver 81.91.189.7#53
Aug 20 23:18:06 dnsmasq[1928]: using nameserver 8.8.4.4#53
Aug 20 23:18:12 rc_service: httpds 1118:notify_rc restart_vpnrouting0
Aug 20 23:20:10 acsd: acs_set_chspec: 0x1002 (2) for reason APCS_CSTIMER

And how should I change current DNS setting to help WireGuard connection to be established?

 

[Tech9]

Not to mention that I can't connect from Russia.

Indeed. What you are trying to do simply won't work. I'm surprised you don't follow closer your local news and don't search for information sources in your language. RKN started filtering your Internet many years ago first by DNS and URL, dynamically updated IP database was added after, lately DPI engine inspects the traffic on top. Popular and known public VPN services are unlikely to connect. You still have some options left, but forget about speed and this forum is not the right place to get the information you need. Don't blame the ISPs - they follow the rules or get shut down, no choice.

 

[Deleted member 48162]

... Popular and known public VPN services are unlikely to connect. You still have some options left, but forget about speed and this forum is not the right place to get the information you need. Don't blame the ISPs - they follow the rules or get shut down, no choice.

Seems like you've argued with yourself. Neither speed nor ISP usefulness is top priority here. Such a naive desire to bypass opinion of the forum community! Those options you've been referring to are the only choice that opens opportunities with Merlin's work for us all. Discussion is the way out. Silence kills, though could pay some bill. Re: SNBForums Code of Conduct.

 

[Tech9]

According to recent changes sites providing VPN setup instructions are illegal in Russia. They are actively tracked and banned. Discussions like this here on SNB Forums may backfire on you. As I said there are still working options, the information is still available, but don’t get our forum involved in this. People who need just usual support may not be able to access SNB Forums anymore as a result. Folks around trying to help you may not be aware of this detail, potentially hurting other members of the community.

 

[Deleted member 48162]

According to recent changes sites providing VPN setup instructions are illegal in Russia. They are actively tracked and banned. Discussions like this here on SNB Forums may backfire on you. As I said there are still working options, the information is still available, but don’t get our forum involved in this. People who need just usual support may not be able to access SNB Forums anymore as a result. Folks around trying to help you may not be aware of this detail, potentially hurting other members of the community.

Well. That means escalation. It always works both ends. Good by, comrade Major! N&B - out and sign off!