Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3423

Neither OpenVPN nor WireGuard are configured to let Bullseye use the Internet servers

$
0
0
Good day all the good people! I'll bypass all the opposite characters and go strict to the point.
Having ProtonVPN service in Russia. That gives a bit of headache as if I broke down the law which I'm not even by distorted Russian judicial system. Pre-paid VPN services do connect and serve for both Android mobile and Android TV behind my router.
Debian and AsusWRT-Merlin router both are completely stuck in the initial phase of connection using OVPN and WG. I did try to establish VPN tunnel for Debian using OpenVPN-client for TCP and UDP protocols - has failed. Then I've initiated WireGuard-client for Debian. Failure. Same connection status for the same clients on router.
What irritates me most is that above mentioned Androids are connecting within the same WiFi ethernet without any delay. VPN config files for OpenVPN and WireGuard connections are set for different tunnels and for various platforms. Connection mode is described here: https://protonvpn.com/support/wireguard-linux and here: https://protonvpn.com/support/linux-openvpn . Upon setting either of two I could get 'ping', 'traceroute', 'dig' and 'nslookup' in the shell act absolutely normal.
No internet browsing or any IM are operational though.
Due to the nature of the connected services and Android clients behind router being successfully connected to VPN services I suggest I'm doing something wrong and need to correct my Debian configuration only. How to use OpenVPN or WireGuard in my Bullseye or router if nothing except 'ping', 'traceroute' and 'nslookup' shell commands seems to be passing through?
WireGuard shell output given below.

Code:

# Be advised that for privacy reasons I've replaced Endpoint Address and Port with other value from the same config for PC.#desktopuser@mydesktop:~$ sudo wg-quick up US21-TOR[sudo] password for desktopuser: [#] ip link add US21-TOR type wireguard[#] wg setconf US21-TOR /dev/fd/63[#] ip -4 address add 10.2.0.2/32 dev US21-TOR[#] ip link set mtu 1420 up dev US21-TOR[#] resolvconf -a tun.US21-TOR -m 0 -x[#] wg set US21-TOR fwmark 51820[#] ip -4 route add 0.0.0.0/0 dev US21-TOR table 51820[#] ip -4 rule add not fwmark 51820 table 51820[#] ip -4 rule add table main suppress_prefixlength 0[#] sysctl -q net.ipv4.conf.all.src_valid_mark=1[#] nft -f /dev/fd/63desktopuser@mydesktop:~$ sudo wginterface: US21-TOR  public key: KEYVALUE  private key: (hidden)  listening port: 34289  fwmark: 0xca6cpeer: PEER/KEYVALUE  endpoint: 84.17.63.17:51820  allowed ips: 0.0.0.0/0  transfer: 0 B received, 888 B sentdesktopuser@mydesktop:~$ dig ip.me; <<>> DiG 9.16.50-Debian <<>> ip.me;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44722;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:; EDNS: version: 0, flags:; udp: 1232;; QUESTION SECTION:;ip.me.INA;; ANSWER SECTION:ip.me.10720INA212.102.35.236;; Query time: 0 msec;; SERVER: 192.168.249.1#53(192.168.249.1);; WHEN: Sat Sep 14 15:47:32 MSK 2024;; MSG SIZE  rcvd: 50desktopuser@mydesktop:~$ nslookup google.comServer:192.168.249.1Address:192.168.249.1#53Non-authoritative answer:Name:google.comAddress: 142.251.1.139Name:google.comAddress: 142.251.1.113Name:google.comAddress: 142.251.1.101Name:google.comAddress: 142.251.1.100Name:google.comAddress: 142.251.1.102Name:google.comAddress: 142.251.1.138Name:google.comAddress: 2a00:1450:4010:c1e::8bName:google.comAddress: 2a00:1450:4010:c1e::64Name:google.comAddress: 2a00:1450:4010:c1e::65Name:google.comAddress: 2a00:1450:4010:c1e::8a

Statistics: Posted by nikobit — 2024-09-16 08:49 — Replies 1 — Views 40



Viewing all articles
Browse latest Browse all 3423

Trending Articles